It looks like the new OpenFlight loader parses mesh records the same way as it parses face records. Indeed, prior to 16.0, these records were identical in the spec.
The OpenFlight 16.0 spec states that a previously undocumented "reserved" field, length four bytes, should be at offset 12. This has the net effect of pushing all other field back four bytes. Since the face record doesn't contain this extra field, the two records are now different. Brede, what's your take on this? Is your new OpenFlight plugin able to handle mesh records? I'll poke around for a model that uses the mesh record and do some testing, if I can find one. -Paul _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
