• Bugs
  • Spine Won't Open Any Projects

I'm an animator for a game project, and have been using Spine for the past months. However, as of today, it won't open any projects anymore (http://prntscr.com/eglvu5) - I have reason to believe this isn't a problem with a specific project, because it's showing the same error for dozens of animations. Shortly after this started happening, Spine automatically updated to version 3.6.07 BETA. I hoped that this would fix the issue, but it didn't, and returning to an earlier version hasn't worked either. It also won't import the projects, stating that it isn't a valid Spine file (http://prntscr.com/eglvfr).

Is this a problem with the new update, or an issue with Spine running on my laptop specifically?

Related Discussions
...

Can you please post or email a .spine project file that won't open? contact@esotericsoftware.com

You may not want beta versions, please read this:
Settings - Spine User Guide: Version
However, beta versions should read all older project files, so if you inadvertently changed from non-beta to beta, it should not cause the problem you are seeing.

Hello Nate, thanks for your response! I have actually discovered that it may be a specific Spine project causing the issue. It will not open, and once I have attempted to open it, Spine can no longer open any other projects either (which is why I thought no files could open at all). Spine can, however, open other projects if that particular file is not opened first. I'll mail this project file now.

Got it, thanks. We just released (about 15 minutes ago!) version 3.5.50 which fixes the problem with opening older projects. I get a few warnings on opening saying a slot has an invalid bone. This happens when a slot somehow gets left attached to a bone that is no longer in the skeleton (eg maybe that bone has since been deleted). This sort of bad state can happen from a bug in an older version. The project is fixed up a warning shown when opening with a newer version, it is usually not a problem.

Note you still probably don't want to be using a beta version.

Ah, you're right, the update fixed it!

Thanks a lot for your help, Nate!