Hi Erikari,
Thank you for responding! I'm having a problem really following along with that section of the video, for the new skins. I've watched it a few times, but I just cannot seem to follow along during that part. The 'importer' part really threw me for a loop, as well.
Is there perhaps a resource that goes over these steps on perhaps a less complicated rig, or otherwise? I try to follow along, but I keep messing something up. I've tried probably half a dozen times so far, haha.
Erikari escribió...so far the fastest workflow has been this:
- export with the photoshop script
Okay, this part I think I got. From the same Photoshop file before, I exported all the skins together.
Erikari escribió
2. import the new json as a second skeleton in your existing project
This part seemed to go smoothly, all the parts are where they should be, on the new skeleton.
Erikari escribió
3. make a copy of an existing skin (especially if that shares some pieces with the new skin)
4. use find and replace to replace the pieces that are the same in both skin from one folder to the other skin folder
This part seems to work sometimes, and not others. For the life of me I cannot figure out why. Given that you were having issues with this part, in your demo video, I think that is why I have some confusion on this bit.
Erikari escribió
5. delete the not common/different mesh parts
Honestly, I didn't understand most of what was happening in this section, even after watching a few times.
Erikari escribió
6. drag the different parts from the new skeleton to the old one
What parts? There was a lot of importing of new skeletons, deleting them, importing again, doing the skins again, and in that process, I also got lost.
Erikari escribió
7. parent the images to the bones
[/quote]
I haven't succeeded far enough to even know if I'll do this part wrong or not.
Figured out one issue. Turns out that Find/Replace is case sensitive, even if you don't have that box selected.
Even after doing the 'trick' to replace images of different sizes (every single piece of my rig), they still all end up in the same location they would have, if I just did the Find/Replace alone, without ever bringing in a new skeleton and doing all that (meaning they aren't in the same location, as they are in the PSD file).
After more digging, it seems Spine also has a bug with bringing in a second skeleton, sometimes. Doing the same thing on multiple occasions, it appears that sometimes the images come with the skeleton, sometimes they do not. Refreshing the images path, brings the images in.
I've developed another way to do this, and got it to work.
Since I was able to repeat the bugs a few times in a row (and even noticed it in your video, once I figure out what it was), I also posted bugs.