google-code-export / papervision3d

Automatically exported from code.google.com/p/papervision3d
1 stars 1 forks source link

DAE BitmapFileMaterial / WireframeMaterial conflict after parsing. #248

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. CS4 branch - DAE (with baked textures in channel 1)
2. load and render...
3.

What is the expected output? What do you see instead?
DAE.getModelByName("childName",true).material = BitmapFileMaterial
instead:
DAE.getModelByName("childName",true).material = WireframeMaterial

The wireframe material (SOMETIMES) randomly shows up over texture.

What version of the product are you using? On what operating system?
"Papervision3D Public Alpha 3.0 - PapervisionX (18.09.08)"

Please provide any additional information below.
The BitmapFilesMaterials load during DAE parsing and show up on Mesh on
render, but the material property of the child objects show
WireframeMaterial instead (which may or may not show up over the texture
occasionally)

Original issue reported on code.google.com by daniels...@gmail.com on 6 Jan 2010 at 7:32

GoogleCodeExporter commented 9 years ago
to get the reference to a (rendered) material on a DAE object go this way:

for each ( var mat:* in DAE.materials.materialsByName){
   trace ( mat );      // mat is the reference...
   trace ( mat.name ); // returns null...for solution see issue 258 :
http://code.google.com/p/papervision3d/issues/detail?id=258
}

cheers.

Original comment by daniels...@gmail.com on 21 Feb 2010 at 3:22