Crocodilum

Hello!

I'm under Win10 with Spine 3.6.53
I have an issue concerning the Import data feature.

Here is what I have and what I want, both being at 100% zoom. The second screen is from when my spine has been reduced at 25%, using images being transformed in photoshop to be 25% smaller.


The croco image is not a mesh.


To begin with, I export the json with non essential (I want to keep colors and icons).


The problem is, if I export the json into the same folder as my spine file, the default behavior of Spine is to search for any images folder.
This will break up the spine, because the new spine is at 25% from the original spine now, but the images folder is targetting my 100% images folder. And even if I now select the proper images folder (images being at 25% from the original images), it will still be broken.



My question is, can we break this spine rule, only for the import data ? Because my new spine file is for now temporary, it doesn't even being saved yet. Why searching for some folder images that can break the spine? Although I don't even know where I'll save my spine file. Once I save it, next Spine could search for any images folder. Couldn't it?


I was expecting this:


After tests, I understood it must be in relation with where the json file is being exported. If I export it somewhere else, it's ok. But tell me it's kind of weird nontheless :p

I also recently have some same issues, images being broken because of full size image folder, even with the json being export somewhere else. Spine was targetting the image folder from a previous spine file I previously had open. Obviously, the new spine was broken as well.
I 'fixed' it restarting Spine. But it's weird. Not happening everytime.
User avatar
Crocodilum
Posts: 134

Pharan

I'm confused. What was the problem and what were the steps? Can you simplify it?
You overwrote the images you were working on?
Or Spine changed the images path on the project you left open? Spine doesn't automatically search for a folder.
User avatar
Pharan

Pharan
Posts: 5211

Erikari

It actually does, but that's not necessarily bad.
The steps to follow to obtain what crocodilium wants are these: Fitting new high-res assets with a smaller skeleton? paying attention to rename/remove the images folder until the new folder is linked to it.
User avatar
Erikari

Erikari
Posts: 1284

Pharan

I mean it doesn't automatically search for a new folder with an open project.
User avatar
Pharan

Pharan
Posts: 5211

Crocodilum

Let's recap. I have a spine_A, my images are big and at real size. I want a spine_B, but 25% smaller, with images 25% smaller. I'm speaking about another images folder, of course, which have been reduced by 25%.

My base folder:

Full size images inside the images folder.


I export my spine_A in the same folder.


When I import data,

Spine is automatically finding the images folder path, in which the images are full.

Now my spine is broken.

Even if right now, I change the path for a new one, a folder I just prepared, in which my images have been reduced in photoshop by 25%

It's too late, it's broken.

The only way to bypass this is to export the json/atlas/texture somewhere else. Not in the same folder as my spine_A. And it's strange.
User avatar
Crocodilum
Posts: 134

Erikari

Well, it's not so strange, if you export a Spine project json in the same folder of the original Spine project that was using that images folder, then import the json that was using "images" as images folder, I'd say it's pretty logic it tries to load those images. Just rename the old images folder to something else until you relink them to the new folder.
User avatar
Erikari

Erikari
Posts: 1284

Crocodilum

Anyway, I took the habit of exporting the json somewhere else. And sometimes it's working, sometimes I have to restart Spine. Without doing anything else. Like if sometimes, Spine had some path memory saved somewhere.

:wait: I also noticed that bones with a shear deformation didn't keep the shear deformation at all.

EDIT : Fine, I found what I wanted to show you.
Check the video:
http://goorlik.free.fr/spine/import_data_issue.mp4

What's happening? I'm doing the same process 2 times.
1/ Exporting the file
2/ Importing with a smaller scale.

To what end? Choose aaaaafter a new image folder path, with smaller images.

But in the video, 2 different things. One with messed up images (with the meshes). The other with clean dimensions, with red squares. That's the red squares that I want.

The difference? here it is:
In the first try, I'm opening a spine file.
In the second, I'm launching spine software directly on the software icon.

That's it.
I'm guessing in the first try, spine is keeping in memory the path of the file I just opened.
User avatar
Crocodilum
Posts: 134

Erikari

Nice catch Crocodilium!
At first I couldn't repro, because if you just rename the smaller images folder to "images" it doesn't show the problem, but if you leave the folder at 100% in place and export the json to a different location, it indeed presents this problem.

Here's the issue! Double clicking on the project file makes Spine remember path even on new projects · #376 · EsotericSoftware/spine-editor
User avatar
Erikari

Erikari
Posts: 1284

Crocodilum

Cool :yes:

Don't forget the shear not taken into account also :o
User avatar
Crocodilum
Posts: 134

Erikari

I verified the shear and opened a separate issue for it here: shear not taken into account on json import · #378 · EsotericSoftware/spine-editor thank you!
User avatar
Erikari

Erikari
Posts: 1284


Return to Bugs