Hi, I have a very similar issue. Spine 3.8.99 will open fine, but i need to run 3.6.53 for an old project. Spine runs, downloads old version, then nothing happens. But in the Finder launcher its running fine (hasn't crashed or hung). I checked the log and it says there's an "Error reading hotkeys.txt file" and error loading Spineboy project. I've reset and reinstalled everything and deleted the spine folder from Application Support as well but no joy.. I'm running an iMac 5k with default screen size.

Ah, I seemed to have found a fix (well at least for my setup). Before i was opening my existing Spine app (black and white logo) then manually setting the version i needed in the app settings, quitting and relaunching.

However, after I had 3.8.99 running again, I double clicked on a spine file and it opened the new Spine Launcher (red and black logo). I then changed the version in that dialogue from 3.8.99 to 3.6.53 and after launching, Spine switched to 3.6.53 and it's running fine. In fact both versions of Spine are running. Normally I open app from the launch bar at the bottom of the screen.

We're using spine to create 10 cutscenes in an HTML5 game at the moment, treating each as a linear animation with different skeletons of equal time length to create a few layers so we have bit more control and keep the structure clean. Works well.

A feature request really.

Would it be possible in the future to import existing texture sheets and associated atlases from a third party source (such as TexturePacker) and then have multiple Spine skeletons referencing multiple sheets at the same time?

The json created by Spine only references a single png but it could also specify from which texture sheets images are held in.

for instance currently:

"eyes": {
"eyes_blink": { "name": "front/kitten_eyes_f_blink_grey_00", "rotation": -90.93, "width": 98, "height": 32 },

would become

"eyes": {
"eyes_blink": { "name": "front/kitten_eyes_f_blink_grey_00", "sheet": "kitten_blue", "rotation": -90.93, "width": 98, "height": 32 },

this would help organising sprites & flexibility.

thanks...

Spine is still the best 2D animator by a country mile :-)

I agree a 'load settings' would be useful, but is it possible to retain export settings on a per file basis? We often switch between exporting for unity and html5 depending on projects, or between users too and it would be great to have settings retained in the file itself rather than on a general basis.