Thanks for your support; that's what we need the most.
-P
And you've earned it hands down. I found another bug just now. Using the dropper on the head(of a human), while showing a helmet will not get the color of the head itself, but instead gives you "blank" I suppose is the best term. It doesn't erase or paint emptiness, it doesn't do anything. Obviously if you turn helmet display off, grab the color and turn it on it's fine, but I thought you should know. And I'm still incurring problems trying to import.
And I have an interesting idea I wanted to run by you. It's very likely it's impossible, due to their nature, but I thought I'd ask.
Half pixels.
If you could work with half a pixel at a time you could create seemingly high-resolution skins, with normal resolution. It would completely revolutionize skins.
I'm gonna try it out now! This program looks like :tongue.gif:
Do it. The amount of time you put into a skin is the amount of awesome that comes out.
I re-skinned all of my villagers and I'm working on a Mewtwo skin, which is looking awesome.
And I have an interesting idea I wanted to run by you. It's very likely it's impossible, due to their nature, but I thought I'd ask.
Half pixels.
If you could work with half a pixel at a time you could create seemingly high-resolution skins, with normal resolution. It would completely revolutionize skins.
Impossible, even in the most powerful programs like photoshop, you can only edit a full pixel. That's just how computers work
Impossible, even in the most powerful programs like photoshop, you can only edit a full pixel. That's just how computers work
I knew that it was most likely impossible. I just wanted to throw it out there, it was wishful thinking. I'm having some difficulties and that half a pixel would do monumental things for my skin.
And you've earned it hands down. I found another bug just now. Using the dropper on the head(of a human), while showing a helmet will not get the color of the head itself, but instead gives you "blank" I suppose is the best term. It doesn't erase or paint emptiness, it doesn't do anything. Obviously if you turn helmet display off, grab the color and turn it on it's fine, but I thought you should know. And I'm still incurring problems trying to import.And I have an interesting idea I wanted to run by you. It's very likely it's impossible, due to their nature, but I thought I'd ask.Half pixels.If you could work with half a pixel at a time you could create seemingly high-resolution skins, with normal resolution. It would completely revolutionize skins.
It's not necessarily a bug in that that's the way the feature was intended - it's a bit difficult to explain, but basically when you "pick" a pixel on the screen, the method it uses to choose which pixel you clicked relies on a representation of the model painted where each pixel is a different color (0x0 to 0xFFFFFFFF - up to 4096x4096 combinations). The resulting pick is pixel-perfect - however, transparency is ignored in this mode, as it's rendered using that special color texture.
I'll try to think of a method of making the color picker pick through transparent pixels.. but, that's the way it was intended.
As for the import bug, I'm not really sure what to tell you - can you give me the exact structure of the program's path and the image path you're trying to import? Maybe that will help me track it down.
The closest thing you'd be able to get is by increasing the resolution of the skin. Mind you, it won't be uploadable, but you could use it in single player.
Do it. The amount of time you put into a skin is the amount of awesome that comes out.I re-skinned all of my villagers and I'm working on a Mewtwo skin, which is looking awesome.
We'd love to see you post some screenshots of your work here!
Impossible, even in the most powerful programs like photoshop, you can only edit a full pixel. That's just how computers work
Well, _technically speaking_ you could argue that a subpixel is kind of what he's talking about - but yeah, it's not gonna work for Minecraft :tongue.gif:
I knew that it was most likely impossible. I just wanted to throw it out there, it was wishful thinking. I'm having some difficulties and that half a pixel would do monumental things for my skin.
Wishful thinking strives the industry.
Recently just added this semi-"multi-monitor support".
Warning: big image.
It's not necessarily a bug in that that's the way the feature was intended - it's a bit difficult to explain, but basically when you "pick" a pixel on the screen, the method it uses to choose which pixel you clicked relies on a representation of the model painted where each pixel is a different color (0x0 to 0xFFFFFFFF - up to 4096x4096 combinations). The resulting pick is pixel-perfect - however, transparency is ignored in this mode, as it's rendered using that special color texture.
I'll try to think of a method of making the color picker pick through transparent pixels.. but, that's the way it was intended.
As for the import bug, I'm not really sure what to tell you - can you give me the exact structure of the program's path and the image path you're trying to import? Maybe that will help me track it down.
The closest thing you'd be able to get is by increasing the resolution of the skin. Mind you, it won't be uploadable, but you could use it in single player.
We'd love to see you post some screenshots of your work here!
Well, _technically speaking_ you could argue that a subpixel is kind of what he's talking about - but yeah, it's not gonna work for Minecraft :tongue.gif:
Wishful thinking strives the industry.
Recently just added this semi-"multi-monitor support".
Warning: big image.
I had been thinking it was something like that. It's not too big of a problem, I've already gotten used to switching back and forth. But maybe you could make transparent a valid, usable "color"?
The picture was of Ash that I was going to either edit or base mine off of.
The file path?
C:\Documents and Settings\Aaron Jackson\Desktop\Miner's Log\MCSkin3D\Updated =D\MCSkin3D.exe
I tried to import:
C:\Documents and Settings\Aaron Jackson\My Documents\Downloads\skin_120202040224197829.png
It gives me:
System.IO.DirectoryNotFoundException: Could not find a part of the path 'Skins\Mine\Other\skin_120202040224197829.png'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
at MCSkin3D.Editor.ImportSkin(String fileName, String folderLocation, TreeNode parentNode) in C:\MCSkinner\Forms\Editor.cs:line 1331
at MCSkin3D.Editor.ImportSkins(String[] fileName, TreeNode parentNode) in C:\MCSkinner\Forms\Editor.cs:line 1365
at MCSkin3D.Editor.PerformImportSkin() in C:\MCSkinner\Forms\Editor.cs:line 1380
at MCSkin3D.Editor.importToolStripButton_Click(Object sender, EventArgs e) in C:\MCSkinner\Forms\Editor.cs:line 3838
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Like you suggested earlier, I move everything into the skins folder and it works, so again it's not a huge fiasco at them moment. Am I the only person who's had this problem though? I'm running on XP SP3 if that helps. (I don't like 7)
I was thinking of making a high resolution skin, but I wanted to possibly start making skins for people. So I wanted to get more practice with basic skins before I start to make those.
And dual monitor support, brilliant. In a few weeks my new graphics card and RAM(both bought specifically to improve Minecraft) are coming in, and then I should have 2 monitors. Provided I can find the other cord.
I have been wondering, will panning on the 3D model be added later? I keep finding myself wanting and trying to before remembering that I can't. Maybe Shift + Middle Button to pan? What are your thoughts? And I would upload screens, but Mewtwo isn't near finished, despite all the work I've put into him. Also, my villagers don't look spectacular, they were just to get rid of the unappealing vanilla skins.
I hope I didn't forget to say anything. I haven't been awake that long.
Sorry i only just now got back, busy in my real life an all that. Thanks for looking in on the issue, since I know you're taking suggestions, how about this one on for size?
The ability to either push a keyboard button to switch to its shortcut tool. Or hold it down to temporarily switch to the tool for as long as the button in held down?
As an example, using your defaults.
I push e...it switches to eraser until I pick something else.
I hold down e, it switches to eraser until I release the e key, then goes back to whatever I was previously using.
I know its possible to do this...as I've seen other programs do it..but I have no idea how hard it is to do..so I figure I'd throw it out there :smile.gif:.
Another one that I think is useful as you add in more advanced brush type tools, and different things like the noise filter..is a selection tool. If you've seen other programs I'm sure you know what it does..but just in case, in basic thought. This tool lets you drag itself around a set of pixels...then release. Once you've done that the pixels are selected (most programs also allow you to add or subtract from the selection tool using modifier keys..like shift to go into add mode...ctrl into subtract mode...nothing just makes a new selection). From there on...you are only able to alter the selected pixels. You can also manipulate the selection in other ways. Like copy/cut pasting it (using a form of cut/pasting that lets you just drag it around so you can visually see where it goes as well).
I figure both of those would be useful for a minecraft editor....the selection thing is honestly only that useful if you add in more filters or ways of touching up.
Rollback Post to RevisionRollBack
Quote from Rezdude »
PvP is like sex. When both parties are willing, it can be a very enjoyable experience. However, when one party is not, it is bound to ruin someone's day.
I had been thinking it was something like that. It's not too big of a problem, I've already gotten used to switching back and forth. But maybe you could make transparent a valid, usable "color"?The picture was of Ash that I was going to either edit or base mine off of.The file path?C:\Documents and Settings\Aaron Jackson\Desktop\Miner's Log\MCSkin3D\Updated =D\MCSkin3D.exeI tried to import:C:\Documents and Settings\Aaron Jackson\My Documents\Downloads\skin_120202040224197829.pngIt gives me:System.IO.DirectoryNotFoundException: Could not find a part of the path 'Skins\Mine\Other\skin_120202040224197829.png'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at MCSkin3D.Editor.ImportSkin(String fileName, String folderLocation, TreeNode parentNode) in C:\MCSkinner\Forms\Editor.cs:line 1331 at MCSkin3D.Editor.ImportSkins(String[] fileName, TreeNode parentNode) in C:\MCSkinner\Forms\Editor.cs:line 1365 at MCSkin3D.Editor.PerformImportSkin() in C:\MCSkinner\Forms\Editor.cs:line 1380 at MCSkin3D.Editor.importToolStripButton_Click(Object sender, EventArgs e) in C:\MCSkinner\Forms\Editor.cs:line 3838 at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)Like you suggested earlier, I move everything into the skins folder and it works, so again it's not a huge fiasco at them moment. Am I the only person who's had this problem though? I'm running on XP SP3 if that helps. (I don't like 7)I was thinking of making a high resolution skin, but I wanted to possibly start making skins for people. So I wanted to get more practice with basic skins before I start to make those.And dual monitor support, brilliant. In a few weeks my new graphics card and RAM(both bought specifically to improve Minecraft) are coming in, and then I should have 2 monitors. Provided I can find the other cord.I have been wondering, will panning on the 3D model be added later? I keep finding myself wanting and trying to before remembering that I can't. Maybe Shift + Middle Button to pan? What are your thoughts? And I would upload screens, but Mewtwo isn't near finished, despite all the work I've put into him. Also, my villagers don't look spectacular, they were just to get rid of the unappealing vanilla skins.I hope I didn't forget to say anything. I haven't been awake that long.
I'll try to reproduce this. My best guess is that the file copy operation silently failed (possibly due to a try/catch), which would result in the load operation failing as a result.
Panning was asked for, but I'm not sure about it - the camera centers around the entire model (more specifically the parts that are made visible). Can you think of a scenario which would involve requiring to pan?
Sorry i only just now got back, busy in my real life an all that. Thanks for looking in on the issue, since I know you're taking suggestions, how about this one on for size?The ability to either push a keyboard button to switch to its shortcut tool. Or hold it down to temporarily switch to the tool for as long as the button in held down?As an example, using your defaults.I push e...it switches to eraser until I pick something else.I hold down e, it switches to eraser until I release the e key, then goes back to whatever I was previously using.I know its possible to do this...as I've seen other programs do it..but I have no idea how hard it is to do..so I figure I'd throw it out there :smile.gif:.Another one that I think is useful as you add in more advanced brush type tools, and different things like the noise filter..is a selection tool. If you've seen other programs I'm sure you know what it does..but just in case, in basic thought. This tool lets you drag itself around a set of pixels...then release. Once you've done that the pixels are selected (most programs also allow you to add or subtract from the selection tool using modifier keys..like shift to go into add mode...ctrl into subtract mode...nothing just makes a new selection). From there on...you are only able to alter the selected pixels. You can also manipulate the selection in other ways. Like copy/cut pasting it (using a form of cut/pasting that lets you just drag it around so you can visually see where it goes as well).I figure both of those would be useful for a minecraft editor....the selection thing is honestly only that useful if you add in more filters or ways of touching up.
No problem, life problems prop up for everybody, including myself.
The shortcut idea isn't a bad one - I'll write it down.
The selection tool is planned for the future; the issue is for proper selection support we need layers.
I'll try to reproduce this. My best guess is that the file copy operation silently failed (possibly due to a try/catch), which would result in the load operation failing as a result.
Panning was asked for, but I'm not sure about it - the camera centers around the entire model (more specifically the parts that are made visible). Can you think of a scenario which would involve requiring to pan?
No problem, life problems prop up for everybody, including myself.
The shortcut idea isn't a bad one - I'll write it down.
The selection tool is planned for the future; the issue is for proper selection support we need layers.
-P
Panning isn't necessary, but when working only on a certain body party I zoom in and hide all others. Panning comes into play during this because I try to look at only a certain area, but have to do so from an awkward angle because of the camera centering on the body part.
And I also like button-holding the shortcut idea. Adding it would simplify much of my work.
Still working on Mewtwo. Closer now, but still have some shading and other tweaks to work on. Will upload a screenshot when finished.
Panning isn't necessary, but when working only on a certain body party I zoom in and hide all others. Panning comes into play during this because I try to look at only a certain area, but have to do so from an awkward angle because of the camera centering on the body part.
And I also like button-holding the shortcut idea. Adding it would simplify much of my work.
Still working on Mewtwo. Closer now, but still have some shading and other tweaks to work on. Will upload a screenshot when finished.
If it centers on the body part you should be able to get a full 360 on each axis - can you maybe screenshot what might be the issue?
As for the import issue... I still can't find it. I use the full, absolute path when co... and then it occurs to me; are you using a shortcut to run the program, by chance?
If it centers on the body part you should be able to get a full 360 on each axis - can you maybe screenshot what might be the issue?
As for the import issue... I still can't find it. I use the full, absolute path when co... and then it occurs to me; are you using a shortcut to run the program, by chance?
It's not the best example, but it helps to explain part of my problem with the camera angles I'm a heavy zoomer and I prefer to work on pieces side by side or as a whole where possible. I try to make pieces blend with what is around them, keep sure what I am doing goes with the rest of the skin, or I use it to sample many colors at once.
And actually, yes, I am using a shortcut most of the time. But I ran the file straight from what you gave me and still got it an error.
I'm still not quite satisfied. The skin color could be better, I need to work on the hands, feet, and tail, I need to go over the shading again because I can never get it to turn out right. But despite the simplicity I put a lot of time and effort into this skin, so I thought I'd share it. Any insight accepted.
Very nice - is this in 1.3 or 1.4? I notice the toolbar thing at the top.
Okay, so the error basically tells me that it's a shortcut without the proper working directory. I shall fix this. Thanks for pointing it out.
As for the panning - I could see why it would be necessary, and we provide the parts disable/enable in order to work with other parts - but it would be important to keep them if you wish to work together on them. I'll add it to the list.
Very nice - is this in 1.3 or 1.4? I notice the toolbar thing at the top.
Okay, so the error basically tells me that it's a shortcut without the proper working directory. I shall fix this. Thanks for pointing it out.
As for the panning - I could see why it would be necessary, and we provide the parts disable/enable in order to work with other parts - but it would be important to keep them if you wish to work together on them. I'll add it to the list.
-P
Thank you. Any suggestions? This is 1.4. I decided to keep using it in case any other errors show up. I wouldn't want to report on errors from an older version that may have been fixed or had the code edited. I figured the updated version would be easier for you to debug/alter etc. And no problem, I'm glad to help. I would love to see panning, but like I said earlier, it's not necessary so I wouldn't worry too much about it.
Thank you. Any suggestions? This is 1.4. I decided to keep using it in case any other errors show up. I wouldn't want to report on errors from an older version that may have been fixed or had the code edited. I figured the updated version would be easier for you to debug/alter etc. And no problem, I'm glad to help. I would love to see panning, but like I said earlier, it's not necessary so I wouldn't worry too much about it.
Alright, it seems I forgot something in the Screenshot feature then.
The A-value of the colour screens also affects the darken/lighten and dodge/burn tools, it�s annoying sometimes, maybe you could do something about that. But it�s not really necessary!
Trying to save I got this:
System.Runtime.InteropServices.ExternalException: A generic error occurred in GDI+.
at System.Drawing.Image.Save(String filename, ImageCodecInfo encoder, EncoderParameters encoderParams)
at System.Drawing.Image.Save(String filename, ImageFormat format)
at System.Drawing.Image.Save(String filename)
at MCSkin3D.Skin.CommitChanges(Texture currentSkin, Boolean save) in C:\MCSkinner\Skin.cs:line 203
at MCSkin3D.Editor.PerformSaveSkin(Skin s) in C:\MCSkinner\Forms\Editor.cs:line 1689
at MCSkin3D.Editor.RecursiveNodeSave(TreeNodeCollection nodes) in C:\MCSkinner\Forms\Editor.cs:line 1720
at MCSkin3D.Editor.RecursiveNodeSave(TreeNodeCollection nodes) in C:\MCSkinner\Forms\Editor.cs:line 1723
at MCSkin3D.Editor.RecursiveNodeSave(TreeNodeCollection nodes) in C:\MCSkinner\Forms\Editor.cs:line 1723
at MCSkin3D.Editor.PerformSaveAll() in C:\MCSkinner\Forms\Editor.cs:line 1729
at MCSkin3D.Editor.saveAlltoolStripButton_Click(Object sender, EventArgs e) in C:\MCSkinner\Forms\Editor.cs:line 3562
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Saving had been working, so I'm unsure what happened or what I did differently. It has now stopped working. There is still the "Save As..." and replace the file option that works, so I'll use that in the time being.
And you've earned it hands down. I found another bug just now. Using the dropper on the head(of a human), while showing a helmet will not get the color of the head itself, but instead gives you "blank" I suppose is the best term. It doesn't erase or paint emptiness, it doesn't do anything. Obviously if you turn helmet display off, grab the color and turn it on it's fine, but I thought you should know. And I'm still incurring problems trying to import.
And I have an interesting idea I wanted to run by you. It's very likely it's impossible, due to their nature, but I thought I'd ask.
Half pixels.
If you could work with half a pixel at a time you could create seemingly high-resolution skins, with normal resolution. It would completely revolutionize skins.
Do it. The amount of time you put into a skin is the amount of awesome that comes out.
I re-skinned all of my villagers and I'm working on a Mewtwo skin, which is looking awesome.
Impossible, even in the most powerful programs like photoshop, you can only edit a full pixel. That's just how computers work
I knew that it was most likely impossible. I just wanted to throw it out there, it was wishful thinking. I'm having some difficulties and that half a pixel would do monumental things for my skin.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt's not necessarily a bug in that that's the way the feature was intended - it's a bit difficult to explain, but basically when you "pick" a pixel on the screen, the method it uses to choose which pixel you clicked relies on a representation of the model painted where each pixel is a different color (0x0 to 0xFFFFFFFF - up to 4096x4096 combinations). The resulting pick is pixel-perfect - however, transparency is ignored in this mode, as it's rendered using that special color texture.
I'll try to think of a method of making the color picker pick through transparent pixels.. but, that's the way it was intended.
As for the import bug, I'm not really sure what to tell you - can you give me the exact structure of the program's path and the image path you're trying to import? Maybe that will help me track it down.
The closest thing you'd be able to get is by increasing the resolution of the skin. Mind you, it won't be uploadable, but you could use it in single player.
It is indeed diamond-shaped!
We'd love to see you post some screenshots of your work here!
Well, _technically speaking_ you could argue that a subpixel is kind of what he's talking about - but yeah, it's not gonna work for Minecraft :tongue.gif:
MY CHESTS ARE FULL OH GOD
Wishful thinking strives the industry.
Recently just added this semi-"multi-monitor support".
Warning: big image.
http://alteredsoftworks.com/mcskin3d/multimonitor.png
-P
I had been thinking it was something like that. It's not too big of a problem, I've already gotten used to switching back and forth. But maybe you could make transparent a valid, usable "color"?
The picture was of Ash that I was going to either edit or base mine off of.
The file path?
C:\Documents and Settings\Aaron Jackson\Desktop\Miner's Log\MCSkin3D\Updated =D\MCSkin3D.exe
I tried to import:
C:\Documents and Settings\Aaron Jackson\My Documents\Downloads\skin_120202040224197829.png
It gives me:
System.IO.DirectoryNotFoundException: Could not find a part of the path 'Skins\Mine\Other\skin_120202040224197829.png'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
at MCSkin3D.Editor.ImportSkin(String fileName, String folderLocation, TreeNode parentNode) in C:\MCSkinner\Forms\Editor.cs:line 1331
at MCSkin3D.Editor.ImportSkins(String[] fileName, TreeNode parentNode) in C:\MCSkinner\Forms\Editor.cs:line 1365
at MCSkin3D.Editor.PerformImportSkin() in C:\MCSkinner\Forms\Editor.cs:line 1380
at MCSkin3D.Editor.importToolStripButton_Click(Object sender, EventArgs e) in C:\MCSkinner\Forms\Editor.cs:line 3838
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Like you suggested earlier, I move everything into the skins folder and it works, so again it's not a huge fiasco at them moment. Am I the only person who's had this problem though? I'm running on XP SP3 if that helps. (I don't like 7)
I was thinking of making a high resolution skin, but I wanted to possibly start making skins for people. So I wanted to get more practice with basic skins before I start to make those.
And dual monitor support, brilliant. In a few weeks my new graphics card and RAM(both bought specifically to improve Minecraft) are coming in, and then I should have 2 monitors. Provided I can find the other cord.
I have been wondering, will panning on the 3D model be added later? I keep finding myself wanting and trying to before remembering that I can't. Maybe Shift + Middle Button to pan? What are your thoughts? And I would upload screens, but Mewtwo isn't near finished, despite all the work I've put into him. Also, my villagers don't look spectacular, they were just to get rid of the unappealing vanilla skins.
I hope I didn't forget to say anything. I haven't been awake that long.
The ability to either push a keyboard button to switch to its shortcut tool. Or hold it down to temporarily switch to the tool for as long as the button in held down?
As an example, using your defaults.
I push e...it switches to eraser until I pick something else.
I hold down e, it switches to eraser until I release the e key, then goes back to whatever I was previously using.
I know its possible to do this...as I've seen other programs do it..but I have no idea how hard it is to do..so I figure I'd throw it out there :smile.gif:.
Another one that I think is useful as you add in more advanced brush type tools, and different things like the noise filter..is a selection tool. If you've seen other programs I'm sure you know what it does..but just in case, in basic thought. This tool lets you drag itself around a set of pixels...then release. Once you've done that the pixels are selected (most programs also allow you to add or subtract from the selection tool using modifier keys..like shift to go into add mode...ctrl into subtract mode...nothing just makes a new selection). From there on...you are only able to alter the selected pixels. You can also manipulate the selection in other ways. Like copy/cut pasting it (using a form of cut/pasting that lets you just drag it around so you can visually see where it goes as well).
I figure both of those would be useful for a minecraft editor....the selection thing is honestly only that useful if you add in more filters or ways of touching up.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI'll try to reproduce this. My best guess is that the file copy operation silently failed (possibly due to a try/catch), which would result in the load operation failing as a result.
Panning was asked for, but I'm not sure about it - the camera centers around the entire model (more specifically the parts that are made visible). Can you think of a scenario which would involve requiring to pan?
Main post, at the bottom.
No problem, life problems prop up for everybody, including myself.
The shortcut idea isn't a bad one - I'll write it down.
The selection tool is planned for the future; the issue is for proper selection support we need layers.
-P
Panning isn't necessary, but when working only on a certain body party I zoom in and hide all others. Panning comes into play during this because I try to look at only a certain area, but have to do so from an awkward angle because of the camera centering on the body part.
And I also like button-holding the shortcut idea. Adding it would simplify much of my work.
Still working on Mewtwo. Closer now, but still have some shading and other tweaks to work on. Will upload a screenshot when finished.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIf it centers on the body part you should be able to get a full 360 on each axis - can you maybe screenshot what might be the issue?
As for the import issue... I still can't find it. I use the full, absolute path when co... and then it occurs to me; are you using a shortcut to run the program, by chance?
Try this for me. Run this beta, and import a skin. If it opens a dialog, screenshot its contents here. http://alteredsoftworks.com/mcskin3d/betas/mcskin3db_1_4_0_201.rar
EDIT: If you'd like to contact me quicker for these issues, Skype or MSN would be a better choice.. if so, PM me here.
-P
http://i1259.photobucket.com/albums/ii544/Ashes_Sehsa/Reason.jpg
It's not the best example, but it helps to explain part of my problem with the camera angles I'm a heavy zoomer and I prefer to work on pieces side by side or as a whole where possible. I try to make pieces blend with what is around them, keep sure what I am doing goes with the rest of the skin, or I use it to sample many colors at once.
And actually, yes, I am using a shortcut most of the time. But I ran the file straight from what you gave me and still got it an error.
Error: http://i1259.photobucket.com/albums/ii544/Ashes_Sehsa/Error.jpg
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOkay, so the error basically tells me that it's a shortcut without the proper working directory. I shall fix this. Thanks for pointing it out.
As for the panning - I could see why it would be necessary, and we provide the parts disable/enable in order to work with other parts - but it would be important to keep them if you wish to work together on them. I'll add it to the list.
-P
Thank you. Any suggestions? This is 1.4. I decided to keep using it in case any other errors show up. I wouldn't want to report on errors from an older version that may have been fixed or had the code edited. I figured the updated version would be easier for you to debug/alter etc. And no problem, I'm glad to help. I would love to see panning, but like I said earlier, it's not necessary so I wouldn't worry too much about it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAlright, it seems I forgot something in the Screenshot feature then.
This is a mistake, I shall fix it.
-P
Umm... Actually, I forgot there was a screenshot feature. I'm used to taking screens the old-fashioned way and it completely slipped my mind.
System.Runtime.InteropServices.ExternalException: A generic error occurred in GDI+.
at System.Drawing.Image.Save(String filename, ImageCodecInfo encoder, EncoderParameters encoderParams)
at System.Drawing.Image.Save(String filename, ImageFormat format)
at System.Drawing.Image.Save(String filename)
at MCSkin3D.Skin.CommitChanges(Texture currentSkin, Boolean save) in C:\MCSkinner\Skin.cs:line 203
at MCSkin3D.Editor.PerformSaveSkin(Skin s) in C:\MCSkinner\Forms\Editor.cs:line 1689
at MCSkin3D.Editor.RecursiveNodeSave(TreeNodeCollection nodes) in C:\MCSkinner\Forms\Editor.cs:line 1720
at MCSkin3D.Editor.RecursiveNodeSave(TreeNodeCollection nodes) in C:\MCSkinner\Forms\Editor.cs:line 1723
at MCSkin3D.Editor.RecursiveNodeSave(TreeNodeCollection nodes) in C:\MCSkinner\Forms\Editor.cs:line 1723
at MCSkin3D.Editor.PerformSaveAll() in C:\MCSkinner\Forms\Editor.cs:line 1729
at MCSkin3D.Editor.saveAlltoolStripButton_Click(Object sender, EventArgs e) in C:\MCSkinner\Forms\Editor.cs:line 3562
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Saving had been working, so I'm unsure what happened or what I did differently. It has now stopped working. There is still the "Save As..." and replace the file option that works, so I'll use that in the time being.