One of the things the MergeGraphOp does is remove transform cores. When
it does this it creates new copies of all the geometry cores and
transforms the contained data through the transformation matrix.
So when you clone a tree (osg::Node::clone) and then run a MergeGraphOp
on that new tree you effectively create an optimized copy of the
original tree with an entirely new copy of the contained geometry.
-Allen
Terry Welsh wrote:
Looking at the size of some scenegraphs saved by my app, I can only
guess that MergeGraphOp makes duplicate trees where cloneTree had been
used to make clones of subtrees. When I remove my MergeGraphOp call,
the filesizes are much smaller. Is this true, or am I barking up the
wrong tree?
--
Terry Welsh - mogumbo 'at' gmail.com
www.reallyslick.com | www.infiscape.com | www.vrsource.org
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
