• Editor
  • Yet another missing image problem I am banging my head around it.

I have a sequence win_fx going from 000 to 029 in its folder.

I already used that sequence in other files without issues.
I import one image, set it to sequence, add a path and my sequence appear and works. set animation from 0 to 29. fps 30.
But image win_fx_029.png is missing. Even though it's there in the folder, even though I can see it in images folder in spine.. even if I checked dozen of times if it's named correctly.




I have no idea what is going on and I am honestly lost an hour already banging my head on a desk.

Related Discussions
...

It seems like you're experiencing a common issue with image sequences in Spine where the last image in the sequence is not displaying, even though it is present in the folder. This can often be due to a mismatch in the naming convention or a missing image in the sequence. Ensure that the sequence is correctly named and that there are no gaps in the numbering. For example, if your sequence starts at 000, it should end at 029 for a total of 30 images. If the issue persists, double-check the path and naming conventions in the Sequence properties. If everything seems correct, try exporting the project to see if any warnings indicate a missing image, as this can help identify the problem.

Sorry you're having trouble! If the above hasn't solved it, you can email us a zip with the .spine file and images and we can take a look at what is happening: contact@esotericsoftware.com

The problem was stupid, so solution was stupid too and gives a clue about how Spine reads sequenced images. It seems Spine doesn't like when sequence is named file_000.png, file_001.png etc It sees, all the files, everything looks normal, just last image is missing in sequence.

Renaming sequence to be file_0.png, file_1.png solved the problem. Why it's always missing the last frame in first case is mystery for me.Fixing Spine to read common naming convention for video sequences might be helpful.

Version is 4.2.1 Pro. on Windows 11.

I'm glad you found a workaround, but it would help us to fix it if we could see the problem firsthand.

I will re-export the sequence and create the file with same issue when I get back to work.

  • Nate 님이 이 게시물을 좋아합니다..