Running multiple versions of resources

Nnorthwood · 18 мая 2023

Hello
I purchased the license thanks to your kind reply in the previous inquiry.
We are currently testing the animation on the web page using the runtimes webplayer.
However, the resources we have secured are for 3.8.99, 3.8.95 and 2.1.27 versions. (atlas, json, png)
There are some issues related to this, so I have a few questions.

I'm currently using runtimes webplayer 3.8.99, is there a way to display the 2.1.27 version resources?
Is there a way to change the 2.1.27 version resources you have secured to the 3.8.xx version?
When checking the sample code of the 2.1.xx release version, the png file is cut into 10₂₀ pieces, not 1 piece, so is this the right way to import one by one?
In Spine Runtimes Software License v2.5, the version of runtimes is different from the release spine version, which version of runtimes should I use to use the 2.1.27 version of the resource?

Nate · 18 мая 2023

Welcome to Spine!

1) The runtimes version must match the data version:
http://esotericsoftware.com/spine-versioning#Synchronizing-versions

2) Yes, run the old version, import the data, save a project file, open the project with a newer version, and export it. You can write a script to do that if you have many data files.

3) I don't understand. To load image in Spine, they need to be individual images. At runtime they are usually packed into a texture atlas. If you have only a texture atlas, you can unpack it.

4) I don't understand. The version number on the runtimes license is separate from the runtimes version. If you want to use 2.1.27 data then you must use 2.1.27 runtimes. That version is ancient and I doubt there is a Spine web player for it.

3.8.99 is also very old. There is no reason to keep using 3.8, I highly suggest using the latest, currently 4.1. The Spine web player is newer, has many fixes and improvements, and will work better.

Nnorthwood · 22 мая 2023

Thank you for your kind reply.
We are going to convert 2.1.27 version resources to new version resources according to answer 2.
Here's the problem.
A resource that is normally exposed in the skeleton viewer looks abnormal in the spine editor.

The resource is version 2.1.27.
I set both editor and viewer to the same 2.1.27 version.
It consists of json, png, and atlas. png is image sprite.
Editor has not modified any settings.

How do I load this 2.1.27 version resource from editor?

Harald · 22 мая 2023

northwood If you want to import previously exported assets into Spine via the Spine Editor GUI, you need to unpack the atlas images as well via Spine - Texture Unpacker..
http://esotericsoftware.com/spine-texture-packer#Texture-Unpacker
Then you can set the image directory of your imported Spine project to your unpacking directory.
If you only import the skeleton data, you're missing the attachment images.

Nate · 22 мая 2023

Here's an explainer video that covers just about every scenario where images are missing in the Spine editor:

Nnorthwood · 23 мая 2023

Nate Harald

Thank you. I think we're in the final stage.
After unpacking the image with a texture unpacker, we proceeded to import resources.
First, the message 'internal edge loss' is checked.

And as shown in the image below, some images are being exposed, but the rest are not.

Seeing that the normal image is exposed when you mouse over 1/weapon2 mesh, there seems to be no problem with directory settings.
I think it's an 'internal edge lost' problem. Is there a way to solve it?
Always appreciate your help.

Misaki · 23 мая 2023

northwood Perhaps the scale setting was incorrect when you imported the skeleton file. Even without internal edges, it should display correctly if imported with the correct scale setting. Please refer to this blog post for more information: Blog: Importing skeleton data #Importing skeleton data

Nnorthwood · 24 мая 2023

Misaki Unfortunately, there was no change when I tried both 'Unpremply alpha check'.
Also, the 2.1.27 version was old, so the scale was not in atlas.
Once I checked one by one, the region is exposed normally, and the mesh is exposed to an unexposed or unintended size.

Misaki · 25 мая 2023

northwood I understand. If you don't mind, could you please send the skeleton files to us via email?: contact@esotericsoftware.com
Unfortunately, even we don't know for sure how far older versions of data can be imported correctly until we try them out on actual data, so it is difficult to guess and help you with only that information.