• Bugs

  • Removed bone having parent with invalid skeleton

Related Discussions
...

Hi, I've just encountered an error, and the bones went missing, with error log "Removed bone having parent with invalid skeleton"

Steps to replicate:

  1. Open KIWI_STOAT_NEW_BEAK.spine
  2. Bones are missing.

First time it crashes was when I finished working, and I was closing the program, but instead of prompting me to save, Spine just closed right away. When I tried to open it again, the bones are all missing, and the poses/animations that I did was gone :bang: :bang: :bang:

May I know whether the file is recoverable or not? I have included the error log and the project file (version 3.7.8.7. )

I will appreciate any suggestions on these.

Regards,

Erick S.

Hello Erick!
Regarding recovery, I think your safest bet is to try to look in your backups folder, which you can find in the Spine settings: Settings - Spine User Guide: Auto backup

If you can retrieve a backup, and make this happen again reliably, could you please attach that file and the steps to make it happen?
It doesn't seem like the errors were caused by a crash, did you work on this project from an older version of Spine before?

Sorry this happened to you! 🙁

When Spine crashed when saving/exiting, it would help to grab the spine.log file. If you start Spine again, it overwrites the spine.log file with a new one. The log you posted shows warnings about loading the project, but doesn't show us the crash.

The errors you see when loading a project are integrity checks that Spine does every time a project is loaded. Various bugs may cause such warnings, often they are bugs in older versions and you see the warnings the first time you open with a newer version, but it's possible bugs in the current version could leave a project in a bad state. The warnings are just to let you know that Spine cleaned up the project. You probably want to check to make sure everything is like you want it to be.

It's very unlikely that if Spine crashed while saving a project that it would cause such warnings. It's much more likely that the file would not be readable at all.

Your best bet is to look at the backups folder, as Erikari mentioned. Sorry we can't do more! We'd love to see the crash log. Did you submit it when/if Spine prompted? If so can you drop us a quick email from the address on your Spine account so we can look up the error? You can just include a link to this thread as the email body.

Thanks Erikari & Nate.

I did not know that there is a backup folder! It seems that there's a file backup that has the missing bones and the previous version which has none.
I am very sorry I am not able to recreate the error.
But to clear things up, I don't see any error message when this happens. It's just that Spine does not prompt to save when I close the program, just went to close instead.

I will make sure to put the report log once this problem happens again.

FYI: I attached an image for keyframing purpose before the error happens, and this image loads in the screen, BUT I am not able to find it in any of the attachments. The image closes when I closed the skeleton (the file had a few skeletons), and shows up when I turn on the skeleton, but there is none in the attachment.

Thanks for the clarification. I've never seen Spine not prompt to save on close when there were changes. If you saved manually, it won't prompt of course. Many people subconsciously hit ctrl+S every few minutes. If there is a case where you make a change and Spine doesn't prompt to save, we'd love to fix it!