Placing one as normal in Scratch is OK, but lags a lot.

Also, there are also graphical issues.

here's the link

http://scratch.mit.edu/projects/13161191/

Sorry, can't vue your link on my phone but opening animated gifs splits them into costumes. Every frame is a different costume for a sprite.

In other words, there is no gif, animated or otherwise anymore to playback. Unless you know some way to import and use animated gifs that I've never heard of?

In my experience, there are no images that cause Scratch errors. Bigger and more colors may slow a program but that is normal.

Ps.. for those who don't know, animated Gifs are a GREAT way to load a lot of images into Scratch. I have projects using over 100 sprites, each with over 200 costumes. Arranging them all in an animated gif takes a bit but can be much faster than loading a bunch of costumes one at a time.

Locomule wrote:

Sorry, can't vue your link on my phone but opening animated gifs splits them into costumes. Every frame is a different costume for a sprite.

In other words, there is no gif, animated or otherwise anymore to playback. Unless you know some way to import and use animated gifs that I've never heard of?

In my experience, there are no images that cause Scratch errors. Bigger and more colors may slow a program but that is normal.

I imported it as a sprite, and there is every frame of it there.

the script also says forever next costume and that's it. i don't know why the images are fuzzy.

That isn't a glitch, is just a way that gif images are compressed. Instead of storing lots of full frames right on top of each other, only pixels that are changed are stored in each frame, and so the image size is cut down. Scratch, unfortunately, doesn't know this trick, so if it encounters a blank pixel, it literally interprets it as a blank pixel. That's what you're seeing.

As for the lag, Scratch has to go through each frame of the image, and that can be quite a bit of work, especially with long .gif's. That's also another reason why compressed gif's are nice, because of the file size.

With confidence,

ErnieParke

ErnieParke wrote:

That isn't a glitch, is just a way that gif images are compressed. Instead of storing lots of full frames right on top of each other, only pixels that are changed are stored in each frame, and so the image size is cut down. Scratch, unfortunately, doesn't know this trick, so if it encounters a blank pixel, it literally interprets it as a blank pixel. That's what you're seeing.

With confidence,

ErnieParke

I also want it to play at the same speed, but Scratch doesn't with the wait script.