Wasabibi

Hi, I've been working with spine for a few years now and It's my first time getting this bug I'm very confused.

I have a main directory containing ID folders for each character. each individual ID folder contains the .spine, as well as it's respective images, PSD and export folders.

This one character looked perfectly normal and I exported as usual but once imported in Unity it gave an error that it couldn't find it's atlas.

Usually, my fix for this is just to create a new .spine and import the old skeleton with its animations, and the new export from that file will work. However, this time, trying this fix got me a link to the atlas of another character, in a different directory.... ?????

So, of course, I tried correcting the image file path to the correct one but since the mesh did the whole resize thing they do when an image has the same name but isn't the same size I need to make new meshes.

Anybody got any clue what is going on and how I can tell spine to just NOT link to any random image directory when importing a skeleton and letting me tell it which path to go to? :think:

Wasabibi
  • Сообщения: 2

Nate

In older versons, Spine would adjust you meshes without telling you. In 3.7+ Spine will ask if you want to it to adjust your meshes. You can tell it to not mess up your meshes, then change the image folder and it should work as expected.
Аватара пользователя
Nate

Nate
  • Сообщения: 9241

Wasabibi

Thanks! It works! I just usually avoid updating to Beta for a production pipeline even though it's full of goodies since the files versions are not retro-compatible...
Wasabibi
  • Сообщения: 2

Nate

Yep, it's a good policy, except 3.7 is no longer in beta and is safe to use (the beta is 3.8). :) You may need to update your runtimes of course, and that may impact your application code, plus you should always test everything is still working before committing to a new version.
Аватара пользователя
Nate

Nate
  • Сообщения: 9241


Вернуться в Bugs