- 已编辑
issues with importing spine into game maker studio 2.3
So ok, I been using spine with game maker for a while now. No issues. GMS atm can only support 3.7 of spine and thats what i been using.
On a recent spine animation, gms is unable to import it, despite using same as my other spines, even using the same export settings, yet anytime i try to import this specific one gms gets an error is saying the json file isnt using supported spine version or w.e. Yet, using same project, able to import all my other spines.
The new one doesnt do anything diff. Tho, the images are huge reso (doing this for some other person, and these were the ones that he sent me).
Are the reso too big or what?
Does the 3.7 Skeleton Viewer load the data files? If so then all the 3.7 runtimes should also, therefore GameMaker should load them too. It's possible there is a bug in a runtime that isn't in the runtime used by Skeleton Viewer, though it's more likely loading in GameMaker fails for other reasons (such as the images are too large). Do you get any error messages from GameMaker?
FWIW, we've been talking to GameMaker and they are planning to update to 4.0 and will likely update to the latest future versions more rapidly.
error i get is to check compile window for messages...which doesnt show anything wrong.
I ran the skeleviewer and it has the "default" ksin selected so no images util i select the only other skin it has and it shows up in SkeViewer.
before this i went into the json files in notepad++ to compare with my other working jsons and the one difference on my problem json is that its "images" entry is empty while all my working ones have some path. idk if that has to do with anything
so i also did another est. i started a new spine project, and dragged all t he imgaes in there, only kept root bone, and i was able to import that test file into game maker no problems. ofc it only has the root bone and no animations.
Sounds like it works correctly in the Skeleton Viewer. We'd need more information about the error to make any progress on the problem. You may need to contact GM, explain you are using 3.7 but it won't load your 3.7 data. If they can give more information about the error, that would help a lot, otherwise we're in the dark.
I believe GM uses multiple Spine Runtimes, depending on what platform your app is targeting. If we could guess at what Spine Runtime they are using, we could write the code to load the data using that runtime, just to check if the problem is with the runtime rather than GM's integration of the runtime into their stuff.
The images
path is only used if you import the data back into Spine. It isn't used at runtime (unless GM is doing something unexpected).
You could try using much smaller images to eliminate that as a problem. The test you did may also do that, though it's not clear if GM is loading all the images in that test.
thank you for your replies. Unfortunately only error i get from GMS is at import saying its wrong spine version, cehck compiler for errors (shows none).
However, the same spine file i have other skeletons. All of them uses the same skeleton exported from original skeleton (which has the problem json)
HOWEVER, any exports from the other skeleton in the same spine file and version imports properly into game maker. Though, the original images used on those are somehwat smaller than the first problem one. So for some reason, the problem only exists in the first/original rig.
Ive only tried posting in forum, ill try contacting GMS directly. I just didnt know if this was a spine thing or GMS's issue. If the original images have to be smaller then ill have to make sure they arent too big, because the later ones work in GMS despite being exported from same spine file. ill come back if i get more info from GMS.
ok so found out issue with the later ones, just had to fix some issues with some erroneous keyed frames.
Great you got past the problem! Maybe you could explain the issues briefly in case someone else runs into the same problem?