Found a curious bug where if you attempt to create an animation in the javascript side as an array of img it works fine, but the instant you name that animation (and I assume it gets “compressed” into the jres area) it’ll break. From what I can tell it doesn’t translate well into the named asset, is destroyed completely, then the error flys about getting null and not an array.
Sorry the video cut off the actual naming of the animation.
I was using this in combination with some of the “import images” tools externally to help build my animations in an external tool.
4 Likes
@richard don’t recall having seen this before? Interesting bug
3 Likes
huh, that’s a new one for me too. @Kikketer mind filing that as an issue on pxt-arcade?
2 Likes
Will do wasn’t sure if your GitHub was getting flooded (AI is a monster). I’ll post anything else I find in the future over there as well. Thanks!
2 Likes
On the streams @richard did say that animations can also be used as image arrays, I have yet to use this information.
That aside this might be a compiler error.
1 Like
Yeah I actually did use that once or twice already, it’s super handy when you want to just create animations and then “frame 1” is that thing standing still. It’s really awesome that way.