4.1.04 FFD keys breaking glitch

Paperbot

Hello
I'm just bringing this to your attention since I don't think it's intended behavior. I tried it on two separate projects and a new one, barring a corrupt installation on my part I think it should be consistent enough for you to reproduce.

When a mesh is reset, FFD keys on all attachments, used on every animation are destroyed (disappear).
I don't think this is how it used to work, and I doubt it's intentional.

Thanks for the continuous support.

Misaki

Hello, @[obrisani korisnik]

Thank you for your reporting. Conclusively, it is not a bug. Resetting Meshes in Setup mode will remove all deformation keys for the attachments in all animations. This behavior is not only in 4.1 but also in the previous versions. However, there is a difference between 4.1 and previous versions. In previous versions, it will show a warning dialogue before keys removal, but 4.1 will show only a toast after doing that, so it may be the reason why you got confused.

Because resetting meshes will delete not only deformation keys but also other keys so the toast “Attachment keys have been deleted” will pop up in 4.1.

I hope this will help.

Paperbot

Maybe I'm going crazy but I could've sworn using the reset button only removed the keys of that specific attachment.
Just to be absolutely clear:
The reset button, when a single mesh is chosen, will delete ALL FFD keys for the selected attachment and ALL OTHER existing attachments in the skeleton, not just the FFD keys relevant to the selected attachment.

If that's the case, sorry for the confusion and thank you.

EDIT: I just tested on non-beta (4.0.0.9, random pick) version, and the behavior isn't the same, other attachments keep their keys intact when a single attachment is reset. Only the relevant FFD keys to the attachment reset are deleted.

As I said, this is not about keys relevant to the attachment being removed, that's expected. All FFD keys in the whole skeleton disappear.

Misaki

I’m sorry I missed that point! We confirmed the bug can be reproduced and we will fix it in the future version. I made an issue ticket for this problem : https://github.com/EsotericSoftware/spine-editor/issues/609

Paperbot

Thanks for the attentive support

Just as an update, the glitch is not limited to the reset button, can't say exactly what else triggers it though.

I appreciate the support and everything, and I did sign up for it when I decided to move to Beta, so I can't get upset.
That said, I am working on a massive scale project and this is absolutely destroying my workflow and wasting many work hours. Despite having many backups to re-import everything, things shift around and I have to spend a lot of time re-constructing everything every time this glitch triggers.

Is there an unorthodox way to roll back/import the project on an older version?
Thank you

Misaki

Sorry for the trouble. Since 4.1-beta has just started and is unstable, I think it is a good idea to avoid using it in real projects except to try out the new features.

Regarding roll back, please confirm your backup folder first. It is explained Recovering work from a newer version section in the Versioning of the user guide : Versioning - Spine User Guide: Recovering work from a newer version

If you couldn’t find backup files or if you want to remain the change that you added in 4.1-beta, you can roll back your project on an older version by following the steps below:

【STEP1】Open the project that you saved in 4.1-beta, then open the Export window and set the following options:

Set Format to JSON
Set Version to 4.0.
Check Nonessential data.

Once you have configured the above, export the file. (Packing images is not required.)

Note: If you check Warnings, you will see a warning dialogue “Exporting JSON from 4.1 to 4.0 may lose information”. It is no problem if you didn’t use any 4.1 features like the Sequence option of attachments.

【STEP2】Switch the Spine Editor’s version to 4.0 and run it.

【STEP3】Select Import Data via the Spine menu at the upper left corner, and when the dialog opens, select JSON or binary file for the Import section, and specify the JSON file exported in STEP1 at the File field.

【STEP4】Immediately after you import the JSON, you will see all of the skeleton’s images are missing, but don’t worry. Saving the project and fixing the Image Files Path allow you to see your skeleton correctly, and you can restart working in 4.0.

Please let us know if you run into any trouble.

Paperbot

Worked like a charm. You're a life saver, thank you so much

Misaki

I'm glad to hear that it worked! 😃

We've fixed the problem in 4.1.05-beta. Cheers! :beer: