- Paril
- Curse Premium
-
Member for 12 years, 10 months, and 25 days
Last active Thu, Aug, 22 2019 05:06:22
- 9 Followers
- 980 Total Posts
- 547 Thanks
-
2
Demonturky posted a message on MCSkin 3DThanks a ton for the help Paril! The beta that you had me try out fixed the bug perfectly.Posted in: Skins -
1
Ashes_Sehsa posted a message on MCSkin 3DPosted in: SkinsQuote from Paril
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. -
1
Ashes_Sehsa posted a message on MCSkin 3DPosted in: SkinsQuote from Paril
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. -
1
Ashes_Sehsa posted a message on MCSkin 3DPosted in: SkinsQuote from Tender_Grilled
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. -
1
Posted in: SkinsQuote from Ashes_Sehsa
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 -
1
Ashes_Sehsa posted a message on MCSkin 3DPosted in: 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. -
1
Ashes_Sehsa posted a message on MCSkin 3DPosted in: Skins
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. -
1
Ashes_Sehsa posted a message on MCSkin 3DPosted in: Skins
I have opened it several times since then and it opened and worked properly. It was a one time event, so I wouldn't look too much into it. Everything else is working fine. The save function is working as well. So far you've fixed 2 of my problems, saving being the biggest reason to rejoice, and added a feature that vastly improved the ease of skinning. You deserve a medal or some other form of recognition. One for your skill with programming and the other functionality inclusion into your programs. Bravo.
EDIT: You fixed the villager layers too! Thank you. I wish I could do more than a thank you here and there, but I honestly mean it. The more I use this program the more it becomes my tool for every graphic problem on minecraft. Anything I don't like, I can change. It's wonderful. -
1
Ashes_Sehsa posted a message on MCSkin 3DI opened it right now to make a new player skin, and I got this.Posted in: Skins
System.IO.IOException: The process cannot access the file 'C:\Documents and Settings\Aaron Jackson\Desktop\Miner's Log\MCSkin3D\Updated =D\Swatches\Default Swatches.aco' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at MCSkin3D.Swatches.ACOSwatch.Load() in C:\MCSkinner\Swatches\ACOSwatch.cs:line 146
at MCSkin3D.SwatchContainer.AddDirectory(String dir) in C:\MCSkinner\Swatches\SwatchContainer.cs:line 76
at MCSkin3D.Editor..ctor() in C:\MCSkinner\Forms\Editor.cs:line 264
at MCSkin3D.Program.MainCore() in C:\MCSkinner\Program.cs:line 76
It did open however, but I'm not sure what I did different from the previous time I opened it that caused this error. Also, love the new GUI for the RGBA and HSVA. It takes less fiddling around with to get the exact color I'm looking for. - To post a comment, please login.
1
She is planned for 1.3. Section specificity, a term I just coined, will also be added.
-P
1
Canada is a far place! But yes, it will eventually, probably in 1.4. 1.3 will mostly be related to skin management and 3d view improvements.
-P
1
Planned for a later version.
-P
1
Thanks!
Basically, just create the skin externally at whatever resolution, and save it in the Skins folder.
-P
It will support them, yes.
-P
1
Yep, 1.3. Funny because I was just thinking about that like an hour ago...
-P
1
In what way? It's more of a skin management utility, but you'd have to explain what you mean. It will support mobs and blocks in the future.
-P
It's planned for 1.3.
-P
1
Can't tell if sarcastic...
Woo!
Extract it. I got rid of the exception in the next version, but basically it just means the Swatches and Skins directory is missing.
Yessir, however they must be the same aspect ratio (2:1) of the original skin. 2x1, 4x2, 8x4, 16x8, etc...
-P
1
Transparency won't turn off as in what?
Can you attach or PM me any reports?
-P
3
What are you doing here, this isn't even...
1
MC Skin Editor does not let you paint ON the 3d model, that's the whole idea behind this editor.
-P
They are equal exposure (25%), however they use different blend modes (subtract and multiply, respectively), which makes them incompatible. You're thinking about lighten and darken; planned, for future.
-P