I am not a big papervision fan, and I don’t usually hide it.
PV3D is interesting and versatile, and allows great flexibility in developing great websites and apps, however it’s always a pain to optimize, and I always end up spending 40% of my development time dealing with memory leaks, optimization techniques, objects that don’t really get removed from stage, events that don’t get fired.. etc… and now that I moved to flex development and have a profiler running on my applications, I see the incredible amount of junk that remain alive in the stage after 3d objects are removed.
so I started a quest to look for optimization techniques on the net, and bank them to get a reference for later projects.. here is the first one, courtesy of Seb Lee-Delisle
http://interactivehug.com/2008/04/21/john-iacoviello-papervision3d-optimization-tips/#comment-463
if you set your bitmap sizes to exponents of two, ie, 64, 128, 256, 512 etc. that way the built-in mipmapping in the FlashPlayer will enable much faster and smoother bitmap scaling and manipulation.
So a bitmap sized 512 x 512 will work a lot better than one that is 500 x 500
this is really interesting, we never actually take those things into consideration when we develop our code as we get the files from designers. will do some benchmarking and get back on that topic