0
Fixed

No Image for Animation character

Ted Ollikkala 5 years ago in By Screen / Interact updated by Ezra Weinstein (Administrator) 5 years ago 12
When I try to view the animation of a character (I've tried 10 frames, 3 frames with completely different images) I always get a green box with a single diagonal line across it instead of the character that I'm trying to animate after it loads in the player. The ones I created on the previous build of InteractBuilder still play fine (they are have not been run through the new build. (I updated earlier today, though) - What does the box with the green strikethrough mean?

Answer

Answer
Fixed
Well, it took closer to 30 hours, but nonetheless the issue has now been fixed with the latest release 4.0.3.
Under review
Ted, would you mind sending me a copy of your app folder via DropBox or another file sharing service? It's best if you could zip up your application folder.  

I suspect it's because you have two animations that are named the same name (it's a bug that we are fixing), but I'd like to confirm this.
This is the animation with ten frames imported as png images. There is one image that looks like it shouldn't be there (It happened when I added an image accidentally that was already in the sequence, deleted and replaced it. 

Skul Walk zip
This shows the extra file that doesn't appear in the builder. I wonder if that's the bug? 
You're right - I deleted 0025 5 from the folder and ran it through the player. The bug is still there.
Maybe because the bookshelf image is the same as one of the frames in the animation? But it did get renamed...
We are looking at it right now, should have an answer in just a few minutes.
The good news is that I can animate all of my characters with walk cycles and I wanted to test it out :-) Thanks, Ezra~!
+1
Ted, we have to issue an update to the Builder to get this resolved.  We will try to have something available within the next 12 - 18 hours, we realize this is a critical issue.
OK, great - glad it's fixable so soon
Answer
Fixed
Well, it took closer to 30 hours, but nonetheless the issue has now been fixed with the latest release 4.0.3.