- Bearbeitet
PhotoshopToSpine Offset Issue/Bug?
Hi guys,
Im doing yet more tests before we go into production. One of these has been an issue with exporting from Photoshop without trimming whitespace (as an option to make sure all art is correctly placed). When doing so, I am moving the rulers in photoshop so (0,0) is at the base of the image in the center. Export is at 100%, Json File made. DONT trim whitespace, and 0 padding.
When importing data into Spine, my images are coming in offset up and to the left, not at the desired (0,0) as expected.
Any ideas? I'm trying to find all of the issues we might face in production now before we start, and I am finding odd issues like this.
Link to Video on Youtube: https://youtu.be/PbGGPYie_Ao
Any help is greatly appreciated!
Thanks,
Matt
Thanks for the clear video, and sorry you've run into trouble. This was a bug which we've fixed in v7.31 of the script, available now:
https://esotericsoftware.com/spine-scripts/PhotoshopToSpine.jsx
Amazing! Thanks for the rapid turnaround on this!
Matt
So, off the back of this issue, I have another couple queries! (Sorry!!!!)
https://www.youtube.com/watch?v=qWaJKb0dolI
When NOT trimming whitespace, adding [bone] to a layer name creates the bone at the center of 'the trimmed whitespace' part of the layer, NOT at the center of the layer. Is this correct behavior?
Also, I have another Test that I can't share, but when I have a group with the [bone] tag. (All images are 1920x1440, zero is at the bottom middle). The bone is being created at -234.0,85.0? The only bone above it is the root bone (0,0). I don't know why this is happening, but it doesn't feel correct, my guess is it should be at (0,0)?
Thanks
Matt
matt_foxfuelled schriebWhen NOT trimming whitespace, adding [bone] to a layer name creates the bone at the center of 'the trimmed whitespace' part of the layer, NOT at the center of the layer. Is this correct behavior?
It is expected behavior, though I realize it makes the bone tag not version useful when not whitespace stripping. We could place the bone more smartly, but we'd need to do it in the Photoshop script by actually doing the whitespace stripping to determine the bone location, but not using it. That will slow the script down a lot compare to the current behavior (Photoshop scripting is very slow). I wonder if it is worth the effort? Even with this change, you'll probably need to move the bone into the right position. I personally tend to not use the bone tag.
I can't say what is going on with your other issue. We'd need to have the PSD so we can try an export, see the incorrect behavior, and investigate.