customisable character

tali

Hi Erika,
Just to clarify, do you mean i should have 1 skin for 'head' parts, another skin for 'body' parts, etc?
OR... a skin per 'theme', like skin for outfit 1, skin for outfit 2, etc...
Not all parts have a whole 'theme' or 'outfit' for the entire character. ie. we may have more arm parts than heads for instance.
Please pardon my newbiness! 🙂

If I have all the body parts under slots in 1 skin, would it be more difficult to turn the parts on & off in the code?

Regarding the unique animations, some of them may require extra bones, yes!

Many thanks for your help 🙂

Erika

Eheh, it's good you asked for clarifications, because I meant something like this:

Skins:

head-helmet
head-coppola
head-santa-hat
body-leather-jacket
body-striped-shirt
body-pantyhoses

OR:

Skins:

Knight
Rogue
Golden-knight
Phantom

Slots are meant to change parts during a single animation by activating/deactivating/switching the attachments inside them. Not across different customizations.
This is a very important concept to understand, so it's ok to repeat it a little (;

Everyone was a newbie at some point! Take no shame, and I'm looking forward to see what you'll create (:

tali

Thank again for your help Erika!! You're a legend!

After setting up my character PSD with all the skins & slots all organised, i've now had an error when trying to import the data to Spine.
After trying all sorts of fixes, I made a small test PSD with just a couple of images to try to figure out what the problem is.

It seems the error only happens when I have skins in the photoshop file. If i only have slots, it works.
Any ideas what's going on?
I've made sure I downloaded the latest script.

Thanks in advance!

Nate

Can you please post or email the PSD? contact@esotericsoftware.com
Thanks!

tali

Sure! It's just a test PSD. Attached!

Erika

Hey tali, thanks for sending us the psd, what version of Spine are you using? the latest should have fixed this problem, or at least I exported your files and everything was fine both in the photoshop export and then in Spine. Could you try to update the editor, if you didn't please?

tali

This is the version i'm using. Doesn't it auto-update??

Erika

Yes it does, and if you also were using this script: spine-scripts/PhotoshopToSpine.jsx at master · EsotericSoftware/spine-scripts and still got this error we have the same setup. (it got updated very recently)

tali

Yep. I see the script was updated an hour ago! I just tried this latest script and still have the same problem 😢 😢
It exports fine, but doesn't import to Spine.

Is there a manual way to update Spine? Should I try uninstall & install again?

Erika

Ok, so we have the same setting. (I'm on windows 10 though)
My export settings are as follows:

then I drag and drop the json that was created by Photoshop in Spine and I have this window:

then I just make the skin visible and I see your character:

I've attached the resulting json, is it the same as yours? does it give you problems importing it?

test-rig.json

tali

Hi Erika,
I checked out your json and it was different to mine! The x,y coordinates were all 1px off.
I used exactly the same export settings as you in Photoshop. I'm on a mac, using the latest version of Photoshop (CC 2017.1.1) - not sure if that makes a difference?!
When I used your json file instead of mine, and imported it (import data) into Spine, it worked!

I've attached my json file.

So still not sure what's going on there... I still can't use the script with my setup for some reason.
Man, I wish I could get to animating! 🙂

Nate

An older version of the script was incorrectly shifting the images imported into Spine by the script's padding. Make sure you are using the latest script, which you can get by right clicking this link and choosing Save As:
http://esotericsoftware.com/git/spine-scripts/raw/photoshop/PhotoshopToSpine.jsx

Maybe we should start versioning the Photoshop script every time it is updated, to make it easier to know if you have the latest.

tali

Hi Nate,
I'm using the latest script, even downloaded it again from your link above, but it's still happening. :S

Erika

Hi Tali, good news! the problem was in the output json, so if you can convert your EOL to CRLF you'll be able to use it immediately, otherwise, we've added support for this in Spine 3.6.44 (:

tali

Thanks Erika, how do i do that? Google it, but still stumped!! :S

Nate

You can either wait for 3.6.44 (should be available today), use a text editing program that allows for EOL conversion (Text Wrangler for OS X is good, see Document Options), or use terminal (use copy & paste, don't try to type this insanity):

perl -pi -e 's/\r\n|\n|\r/\r\n/g' yourfile.json

Sorry for the trouble!

tali

Hurray! It's working now.
Thanks for the update! :rock:

BEBOP

Hi, sorry for a newbe question, but I've watched few tutorials, and searched through forum and didn't find a solution for my issue.

I'm trying to list in the dopesheet keys for switchable parts (like muzzles in spineboy example). Whenever I'm trying to click on slot or muzzles in spineboy example nothing appears in the dopesheet. I know there are some muzzles changing while playing animation but don't know how to get keys view in the dopesheet.

btw: I'm running newest Spine softwaer on Windows 10

Erika

It looks like you have a filter active on the dopesheet (probably on translate keyframes)!

click the filter icon to pick attachments instead, or to reset it and be able to see everything:

BEBOP

Thank you Erikari - I thought it should be as simple as you described, but couldn't find it. Thanks again!