[Papervision3D] BitmapMaterial, seems to auto update?
tyleregeto at gmail.com
Fri Aug 29 09:37:19 PDT 2008
I figured it as much, I got around it similar to your suggestion, but using
clone rather than copyPixels, and passing that in when I set the new
> I "discovered" this behavior some time ago. The way I see it is that a
> BitmapMaterial is just a link between a mesh and a texture represented by
> a bitmapData. So, and each render cycle pv3d just grabs the bitmapData
> itself and applies it to the mesh.
> If you take a look in the source, the MaterialObject3d.updateBitmap()
> method is actually empty :)
> If you want to animate a bitmapData and have another one used as texture
> you have to use a copy in the Material object, and use
> BitmapData.copyPixels() to update it whenever you need.
> On the other hand updating a bitmap texture this way seems really fast,
> much faster then an animated MovieMaterial.
> Tyler Egeto wrote:
>> Hey all,
>> I'm doing some work with the bitmap material, and have been getting some
>> unexpected results. I've got it on a plane with the bitmapData object I
>> used on it stored for access else where.
>> I am then updating the bitmapData object, but when I do so, it is also
>> changing the texture on the plane, inaccurately to the new
>> bitmapData(even though I am not calling update on it). Even stranger,
>> I've locked the bitmapData object, and it still updates the plane with
>> changes, but in an odd way, leaving triangles on the edges blank, or as
>> the original color drawn on it.
>> I was under the impression that the material would never update unless
>> you explicitly told it too, does anyone know if that is incorrect? It's
>> quite odd.
Have question? Email me at tyleregeto[at]gmail[dot]com
View this message in context: http://www.nabble.com/BitmapMaterial%2C-seems-to-auto-update--tp19213120p19223431.html
Sent from the Papervision3D mailing list archive at Nabble.com.
More information about the Papervision3D