[Papervision3D] Optimizing performance: anything else I can do?

[Alan Pinstein]

> I would also make sure:
>
> 1) tiled = true for your material

Is this to fix the "seam" bug? Tiled is true for the 2nd and 3rd  
slice, as done in the example code I found... somewhere. Is that  
correct?

> 2) check your thumbnail code to make sure its not running when it  
> doesn't need to be: use bitmap caching until the mouse is over the  
> area of interacting with that menu, stop all recalcuing of positions  
> and such unless the mouse is near it. (often times pv3d is greatly  
> affected by the 2d stuff left running in a project)

This is a good idea. I will definitely check into that. I believe that  
the "root" DisplayObject of the "Dock" is set to cache as bitmap, but  
I will double-check.

Alan

>
> hth
>
>
> On May 9, 2009, at 9:35 AM, Alan Pinstein wrote:
>
>>> I believe it's good practice to keep bitmap dimensions to x2  
>>> (64,512,etc) - not sure how much performance boost you'll get from  
>>> that one tweak tho.
>>
>> Why? From everything I've read the point of this is simply to  
>> benefit from Flash built-in mipmapping. Outside of that I know of  
>> no reason why this matters (yet).
>>
>> If it's just mipmapping, then this can't possibly have an effect at  
>> full-screen for my application since none of my textures ever get  
>> "shrunk" in the viewport.
>>
>> Alan
>>
>> _______________________________________________
>> Papervision3D mailing list
>> Papervision3D at osflash.org
>> http://osflash.org/mailman/listinfo/papervision3d_osflash.org
>
>
> _______________________________________________
> Papervision3D mailing list
> Papervision3D at osflash.org
> http://osflash.org/mailman/listinfo/papervision3d_osflash.org