Hi! I'm using spine pro and I have an enemy type animation. It has four skins(green,red,blue and yellow) and three animations (attack, idle and death)
So I finished all the animations and exported them as .PNG secuences. No problem for attack and idle animations, but for the death animations it appears as a blank image, for all the four skins.
Here is the death animation with the red skin (without bones):
Here are the images at the Windows explorer:
Any clues on why this happens?
I may be wrong, but where it disappears it looks like it is scaled to a supertiny size?
If not so, have you checked you didn't deactivate the attachment by chance?
I think something weird is going on.
Is it just 1 black pixel that was exported?
Did you select the correct skin (rojo) when you exported?
Erikari लिखाIf not so, have you checked you didn't deactivate the attachment by chance?
I ckecked the attachments and it seems that it's all in order
Pharan लिखाI think something weird is going on.
Is it just 1 black pixel that was exported?
Did you select the correct skin (rojo) when you exported?
Hi! The thumbnail with the black pixel is a preview from Windows(I don't know where it comes from ) when I open the file it appears completely blank . I selected all the skins, also tried to export with "Current" skin with same result.
It may be that we'll need your .spine project file and images so we can reproduce the problem. Would you mind emailing those? contact@esotericsoftware.com We will keep them completely confidential.
Hi! It has been a week since I emailed the problem, any solutions?
Okey so maybe I'm getting closer to the problem:
I exported each frame manually the "die" animation has 25:
-frames 0-17 export fine
-The rest is in blank
Not because the rest of the animation is in blank. Here's an image of frame 20 in spine:
There is still some beam particles in the animation. Could this be because it overwrites the other animations?
Looking forward for solutions
Sorry. Things have been extremely hectic the last week (huge runtime update). It's possible Nate have already looked at it. He should get back to you this coming week.
Apologies once again for the delay!
I'm very sorry we couldn't get to this sooner. I tracked it down to the path constraint, when the path gets scaled to zero it creates a singularity and everything crumples into nothingness. Eventually the NaN wrecks bounds calculations and the images output have bounds of 1x1. This has been fixed in 3.5.00-beta, available soon! If you need a solution before than, you can try scaling to almost-but-not-quite zero, like 0.0001.
Scale 0 strange behaviour is this finally fixed then 
