Hi there.
Before I export my animation as a png. image sequence, the animation is displayed perfectly in Spine.
However, when I export them, the last images are not exported correctly and I get the "Missing Image" symbol.
And then all of a sudden I cannot view the animation in spine either, anymore:
Here are my export settings:
Why is this happening?
Can you please try the latest 4.0 beta? It may be a bug in 3.8 that is fixed in 4.0.
The image is at least correctly displayed in the animation after export when I use the beta version:
However it still does not export all of the images:
I used beta 4.0.76
All the other exports I made after this worked, also when I tried to export the same animation again, it exported correctly. So the beta version possibly solved the issue.
Alright the first time I export something it creates 2 wrong frames, and the second and consecutive times it works. So I have to export the animation at least twice.
So would that mean there is still some debugging to do?
That is strange. Could you post or email use the .spine file and images so we can see the problem and fix it? contact@esotericsoftware.com We'll keep your files private.
Okay, I sent it.
Could it be related to my Windows settings maybe?
Got it, thanks! Unfortunately I don't see the same problem on 3.8.99 or 4.0.77-beta.
Something is weird in your screenshot:
This shows an orange key for the red bone, but you have auto key enabled, so that shouldn't be possible. I don't see an orange key when I open the project. Any idea how you got that?
Next, your skeleton only uses one image. There should not be any loading or unloading of the image when doing an export, not unless the image file changes on disk by some other software. Spine already has the image loaded when it's shown in the editor, so when you export it will just use that, no loading is needed at all. I can't imagine why it would write a few frames with the image, then lose the image (frame with missing placeholder image), then load the image (frame with loading placeholder image), then write more good frames. No Windows setting should affect that.
I'm really not sure what is going on. Do you see the problem as soon as you run Spine and open the project? I tried that a number of times, but it worked correctly for me each time. Are you working with files on a network drive?
I see your screenshot of the icons, do the images really look like that when you open them? Windows caches thumbnail icons and they can't always be trusted. For example, some PNGs have thumbnails with a black background when the image has a transparent background.
After some thought, my guess is you are exporting to the same folder that contains your Spine project images. This may cause Spine to reload images. It shouldn't happen during export though, we'll take a look at that. It's hard to work on because it's hard to reproduce!
This shows an orange key for the
redbone
I'm not sure what you mean with red bone.
Are you talking about the orange dot next to the red image node?:
In any case maybe it happened because I used the find-replace tool, to quickly create the same animation for white, red and blue flowers, by simply changing white to red in the tree node.
However I do not believe that that is what led to the problem of the sprite export.
If I remember correctly it also happened before I had changed the plant image.
So to answer some of your questions:
Do you see the problem as soon as you run Spine and open the project? I tried that a number of times, but it worked correctly for me each time. Are you working with files on a network drive?
Well I do not see the problem right when I open Spine because it is displayed correctly in the beta version. But before I would see the wrong images right from the start. I do not work with files on a network drive.
I see your screenshot of the icons, do the images really look like that when you open them?
Well, no, the black background is actually transparent and not black. So you are absolutely right, there is no problem with that, otherwise I would have mentioned that. However the sprites with the 'Missing Image' and 'Loading' symbol are displayed exactly like the icons when I open the image.
After some thought, my guess is you are exporting to the same folder that contains your Spine project images.
Yes, that would make absolute sense. Because I could export other animations without any problems.
I will see if I can reproduce it on my computer with the new beta version.
So yes, I could recreate the problem:
So it doesn't happen when I export it in the same folder as the project file.
But when I create a folder into the same folder as the project file, and export the animation into that first folder, then the erroneous sprites appear.
For clarification:
This happens to me with the newest beta version 4.0.79.
May I ask, were you able to recreate the problem?
Sorry for the delayed response!
In 4.0.82-beta (up now) we've fixed two problems:
1) When exporting into a skeleton's images folder, it was triggering the images to be reloaded unnecessarily. This slowed down the export a little and caused some images to not be loaded on some frames, sometimes.
2) We fixed a bug with ensuring that all images are loaded for each export frame. So even if the images are reloaded, it can no longer mess up exports.
Thanks for reporting and for your patience while we got it fixed up! :beer:
Hi!
When will the 4.0.82 beta version be out for installing?
For now the highest installable is 4.0.79 and it still has the bug
The latest editor is 4.0.04. It is no longer beta, so non-beta versions started at 4.0.00 and go up. Non-beta version numbers are newer than beta version numbers.
Oh yeah, I just realized, sorry!
Thank you so much for the fix! I tested it and it works!! Awesome! 8)
Cheers!
Great, thanks for confirming! :cooldoge:
