• 中文
  • json file size too big cant import to spine

hi,I have a spine json file that has size 100 mb ,it can't import to spine cause it's too huge,I wonder if there is a tool or way to delete some of animations of this file to make it work?

Related Discussions
...
  • Изменено

Interesting. Can you post or email (contact@esotericsoftware.com) the file? Please ZIP it first! That way we can see why it fails and maybe fix it.

You can process the JSON data to remove animations, though if you wanted to import all the animations that wouldn't help.

yes here is the file


Nate написал

Interesting. Can you post or email (contact@esotericsoftware.com) the file? Please ZIP it first! That way we can see why it fails and maybe fix it.

You can process the JSON data to remove animations, though if you wanted to import all the animations that wouldn't help.

I have already posted it


the other one

The JSON is from 2.1.27, so you will need to use that version to import the data. You can run Spine with -Xmx1200M to give Spine more memory. 1200 MB is around the most Windows will give because 2.1.27 is 32-bit. Spine 4.0+ is 64-bit so can use much more memory, but won't be able to read the old 2.1.27 JSON data.

If you have the .spine files, that would be best. Worst case I guess you could use a text editor to delete some of the animations. Find the animations section, identify each block that is one animation, and delete some until you can get it imported without running out of memory.

Nate написал

The JSON is from 2.1.27, so you will need to use that version to import the data. You can run Spine with -Xmx1200M to give Spine more memory. 1200 MB is around the most Windows will give because 2.1.27 is 32-bit. Spine 4.0+ is 64-bit so can use much more memory, but won't be able to read the old 2.1.27 JSON data.

If you have the .spine files, that would be best. Worst case I guess you could use a text editor to delete some of the animations. Find the animations section, identify each block that is one animation, and delete some until you can get it imported without running out of memory.

May I ask how to use -Xmx1200M? Do I need to use command line or what? Thanks.

Ah, sorry, it seems -Xmx is not applied to Spine editor version < 4.0. This is because those are 32-bit and the memory they can allocate isn't much more than 1024MB. Most of the time we can't pass the -Xmx value that works with 64-bit Spine version to the old version because it would too high and Spine would fail to start.

I'm afraid the data is just too big to load into the old version of Spine.

Nate написал

Ah, sorry, it seems -Xmx is not applied to Spine editor version < 4.0. This is because those are 32-bit and the memory they can allocate isn't much more than 1024MB. Most of the time we can't pass the -Xmx value that works with 64-bit Spine version to the old version because it would too high and Spine would fail to start.

I'm afraid the data is just too big to load into the old version of Spine.

Ok,thank you for the explanation, I think i can only delete some animations now.