Hi Zach, Comments are added as node descriptions like before. The new loader doesn't parse for carriage return and line feed but adds the whole comment as one description string. Be aware that optimizations might merge or remove records loosing the comment in the process. To avoid this I do as follows.
1) Read file with reader options preserveFace and preserveObject. 2) Traverse model with comment parser vistor. 3) Tag nodes I need to preserve during optimization with setPermissibleOptimizationsForObject() 4) Optimize I'm familiar with the use of comments to add additional information to the OpenFlight format. OpenGVS had the possibility to add lights with sectors and blink sequences using comments before it was available in the OpenFlight specification. Regards, Brede On 2/4/07, Zach Deedler <[EMAIL PROTECTED]> wrote:
Hi Brede, I know rendering options in the comment field is not part of the OpenFlight specification. But, the old loader would read the comment fields into description field of groups/objects. This allows one to write a node visitor that does use the comment field to do rendering things not in the OpenFlight specification. Using the comment fields to extend OpenFlight files has been a common method used by many. Since comment fields are in the OpenFlight specification, it would be nice if they were preserved in the scene graph, or at least an option to do so. You know what I mean? I can do this at a later date. I know you put a lot of work into the new plugin, so I want to help as much as I can. Zach
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
