I still have to do a rotation and scaling test with the current code, but the one I did very early in development didn’t show much of an impact, exception made to having hundreds of objects.

Using the single canvas bitmap method and blitting using copypixels from tilesheets definitely works amazing in that case as well as the obvious normal flash in browser case as well.

As far as memory consumption concerns why not simply store the tilesheet bitmap data as a static const bitmap data object? that way there is only one copy regardless of the numbers of sprites of a similar type? I couldn’t tell for sure but maybe you can’t do that in your test above because you are creating those bitmaps on the fly? It should work in a standard ‘sprite’ scenario though right?

Dig the new site design too!

e boaaaa…?

The last game we made had every frame cached with 16 angles for our zombies and it allowed for super fast rendering. http://www.daytradersofthedead.com/ (the game runs at 50fps)

In the game the only thing thats getting “rotated” is the main guy. everything else is copy pixels.

I guess the trade off is that it can take up a lot of memory. But if the sprites are small its the best way to go!

For a character with a number of animations, it ended up returning an error, don’t remember which one unfortunately.

I still believe that not caching and drawing the transformed texture is the way to do it because I can’t think of a scenario where we’ll have hundreds of rotated textures.