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. Image supprimée en raison de l'absence de support de HTTPS. | Afficher quand même Image supprimée en raison de l'absence de support de HTTPS. | Afficher quand même
The croco image is not a mesh. Image supprimée en raison de l'absence de support de HTTPS. | Afficher quand même
To begin with, I export the json with non essential (I want to keep colors and icons). Image supprimée en raison de l'absence de support de HTTPS. | Afficher quand même
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. Image supprimée en raison de l'absence de support de HTTPS. | Afficher quand même Image supprimée en raison de l'absence de support de HTTPS. | Afficher quand même
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? Image supprimée en raison de l'absence de support de HTTPS. | Afficher quand même
I was expecting this: Image supprimée en raison de l'absence de support de HTTPS. | Afficher quand même
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.