• Bugs
  • Importing an invalid JSON file

Related Discussions
...

I tried importing a json from the latest version of Affinity designer. However I'm using Spine 3.7xx for gms purposes. When I tried to import the json I got an error that it wasn't valid. Ok that's fine, i guess it's a compatibility issue. However, it disabled undo for all further actions. The bug vanished when the program was restarted. I don't know if it would apply to other jsons generated by other programs but I just thought I'd leave it here. thanks!

Edit: I realise cause I'm using an older version maybe i shouldn't have posted. But it might prove helpful in some manner, so I'll leave it up.

Oh, did AD update their Spine export? We'll take a look ASAP! They had planned to support tags, then we can finally promote AD instead of nasty old Photoshop!

Ideally the AD export uses the slightly older JSON format. The newest versions of Spine have special cases so they will accept that older JSON, at least enough so that older export scripts don't have to be rewritten. The AD guys are awesome though and very responsive, so we'll drop them a line if there's a problem.

At first I was a bit wary of you guys, but I must honestly say you do sterling work and cannot emphasise how wrong i was. I look forward to hearing about future updates! Now, if only GMS2 were to update their Spine compatibility...

Nate yazdı

Oh, did AD update their Spine export? We'll take a look ASAP! They had planned to support tags, then we can finally promote AD instead of nasty old Photoshop!

Ideally the AD export uses the slightly older JSON format. The newest versions of Spine have special cases so they will except that older JSON, at least enough so that older export scripts don't have to be rewritten. The AD guys are awesome though and very responsive, so we'll drop them a line if there's a problem.

Thanks! :fiesta:

Last we heard from the GMS guys they are planning to jump from 3.7 to 4.0 and then to stay on top of updates. Hopefully they make that move soon. Maybe they are waiting for 4.0 to go non-beta.