- Editado
New PSD on an old character
Hello,
I've asked this before, but I can't find my old post, even though I know how to search for every post I've ever made. Sorry for the repeat question.
I have a character that has many different layers. My artist just changed all the character's facial expressions and moved the hair around, too (by changing the layer order). He may have even made other changes that I'm not aware of yet. The latest PSD he gave me looks correct. How do I get these changes into my old spine project?
I remember that I'm supposed to import the PSD script's json file into Spine, create a new skeleton, and transfer things from one skeleton to the other (new skeleton to old?). But what's the quickest way to do such a thing?
My attempt was to filter by regions and skin placeholders only. From that point, I wish I could copy all the regions from the new skeleton to the old, but that messes everything up (all the sprites are out of place after pasting). The only thing I've found that works is to copy region by region from the new to the old. Since there are 50, this is very painful.
All I want to copy over is the new transforms for the old regions and the new draw order. Does this have to take 50x multiple clicks/scrolls to achieve? If not, what's the best way to go about it?
To clarify, I think all the old layers are still there in the new PSD, but my artist has moved a few around and maybe rearranged the order of the layers, too.
Hello,
Was it this thread perhaps:
Best way to import PSD changes into spine??
Hello AoF
Spine can now import PSD data directly inside an existing Spine skeleton, populating it with new skins, and if you want, replacing the position of already placed attachments with the ones in your PSD (but if you replace the images and they were meshes, they will be reverted to normal attachments)
In case you choose to use this new import feature, you won't be able to also acquire the new draw order, as it populates already present slots.
Import - Spine User Guide: Data
Changing the draw order using shortcuts is fairly easy though. For example you can filter the tree on slots then click in the viewport and press +
and -
to change the draw order of the selected slot. More shortcuts can be found here: Spine: Cheat Sheet
Thank you both. Erikari, are you saying instead of using import data and picking json, I can import data and import a PSD file instead? If so, how does it deal with the origin issue? It doesn't seem like you can save the origin change, and that's what it uses to position the new import.
Erikari escribióChanging the draw order using shortcuts is fairly easy though.
I imported 2 skeletons (new/old), and I wanted the old one to have the same draw order as the new. The problem is, it's very difficult to compare the draw orders of two skeletons at the same time because only one draw order fit on the screen at the same time. This means I had to look at the top skeleton, see that the top draw order is a region called A, then scroll down to the bottom skeleton's draw order and see that its region was also A. I'd have to do this over and over again, remember where I was at last, until I found one that differed. But when I found one, it was like, "Wait... maybe I made a mistake with my eyes. Does it go JKL in both? I think the bottom one had JLK. Let me check again." And then if there was a whole group of regions that were out of place, it is too much information to hold in my head at once to figure out if I can move the whole group and by how much.
So, I may be going about this wrong, but it seems to me the easy solution would be to make it possible to see both skeletons' draw orders at the same time. Here's an alternative solution: Can I open two spine projects at once? If so, I could just split the screen to left and right with new and old, then I could look at both draw orders side by side that way.
Anyway, your solution is good if I want to use my eyes until things "look" right, but if there's a known "good" and known "bad" skeleton, I'd prefer an easier way to make the bad skeleton's draw order the same as the good skeleton.
BTW, let me know if I'm trying to solve a problem I shouldn't try to solve. I just know I'm the type of guy who will easily miss that a hair strand is behind a character's ear when it should be in front, especially if my artist has given me an edit to a shirt and there's already 50 shirts in that PSD. I'd feel much more comfortable if there were some easier know this draw order is like that draw order.
You can have two Spine instances open at the same time
Just uncheck Reuse instance
to open a new Spine window every time you double click a Spine file Settings - Spine User Guide: Reuse instance
What's the problem with the origin? You mentioned in another thread your artist removed the guides, did you manage to get them back in the right position or not?
The fact that there's 50 shirts shouldn't impact the draw order, as they would go all in the same slot but in different skins, normally. Did you see this video?
AoF escribióErikari, are you saying instead of using import data and picking json, I can import data and import a PSD file instead?
No, sorry for the confusion, Erikari misspoke. She means in version 3.8 Spine can import JSON data into an existing skeleton. In your case, you can export your PSD to JSON data, import the JSON data into Spine, work on your skeleton in Spine, then later you can add more layers to your PSD, export to JSON, and import that JSON into the existing skeleton in Spine. It will bring in the new slots in the same draw order you have in the PSD, so you should not need to run two Spine instances to compare the draw orders.
Erikari escribióYou can have two Spine instances open at the same time
What's the problem with the origin? You mentioned in another thread your artist removed the guides, did you manage to get them back in the right position or not?
I think Nate answered this for me, I was confused.
I don't know what happened with that PSD, but my artist said he sent me the wrong one, and he gave me another one with the guide. If he had deleted it, I still don't know how I could have recovered from that, though.
Nate escribióin version 3.8
Is this out yet? How do I get it? My version doesn't say it's available in the dropdown: https://imgur.com/xIbcz2r
3.8 is in beta, so you'd need to check the box in your screenshot to opt-in to the beta. The select box only shows versions you've used previously. 3.8 is almost out of beta, but be wary about using beta versions, see here:
Settings - Spine User Guide: Version
Great, thanks!