Этот сайт лучше всего просматривать в современном браузере с включённым JavaScript.

Import error in UE4

Antidamage

I'm getting a runtime/asset version mismatch, except the editor I'm using to export is 4.1.20, and the runtime branch I'm using is 4.1.

This is from a brand new spine project, but all of the existing projects that I updated using this version of the editor work fine.

What could be causing that?

Antidamage

Just in case it's useful, this is the line of bash that I use to export it:
"/mnt/c/Program Files/Spine/Spine.com" --input "${input_path}" --output "${export_path}" --export "${json}" --input "${images_path}" --output "${export_path}" --name "${book} p$(printf %02d $i)" --pack "${atlas}"

Antidamage

And just to confirm the export does work:

----------count 06------------------------ Exporting 'Y:/Poppy & Buddy/Animation/count/count p06.spine' to 'Y:/Poppy & Buddy/Export/count/' [sudo] password for antidamage: Spine Launcher 4.1.12 Esoteric Software LLC (C) 2013-2022 | http://esotericsoftware.com Windows 10 Pro amd64 10.0 Starting: Spine 4.1.20 Professional Spine 4.1.20 Professional Licensed to:xxx JSON export: count p06 Pack: count p06 Complete.

Mario

Sorry for the trouble! Could you share your exported .json file and possibly your .atlas/.png files as well?

Antidamage

Yup! I don't want to share them publicly though, I'll DM you a link.

Mario

Cheers! I've opened an issue here:
EsotericSoftware/spine-runtimes2279

Mario

Just had a quick look. The skeleton wasn't exported with Spine 4.1, but 3.8 as per the .json file. That won't load with a 4.1 runtime.

Which is extremely weird, as both your CLI command and the log say you exported with 4.1.20.

Could you share your export .json file you pass on the CLI?

Antidamage

I think this is what you mean?

{ "class": "json", "extension": ".json", "format": "JSON", "nonessential": true, "prettyPrint": true }

Antidamage

The only other possibility I can think of is that while the project is new, the images and layout are an old export from photoshop. Could it be that?

Nope, there's no version mentioned in that.

Mario

No, data coming in as images doesn't matter when it comes to the exporting version.

One last idea: could you open your project in Spine, then check the JSON export settings? It has a "Version" field. What is it set to?

Antidamage

Mario It's set to 4.1. I've never done a manual export of this project though, could there be a default setting for Spine.com only?

I've also just realised I can export those settings, so I'm going to set some ideal params and try again.

Antidamage

It's fixed.

Before I tried anything else, I deleted the old export before re-exporting. I don't think that I'd done that before and was exporting over-top of the old one. This time though the version came out correctly.

Is it possible that if there's an existing file, that it only updates it?

Mario

No, the export should always overwrite existing files. But maybe there's a bug. I'll pass it on to Nate. Thanks for helping diagnose this and sorry for the time you had to spend!