hi Robert,
Okay then!
Well, the behavior actually surprised me (I had to step-by-step debug to
discover why I had so many StateSets after an optimization). This is why I
asked. However, if this is normal, then maybe we could just add a tiny comment
somewhere, to avoid loosing hours as I did?
As a side note, I'd like to mention that most elements I read (using
ReaderWriters in the distribution) are used directly, and thus have UNSPECIFIED
data variance.
--
Sukender
PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/
Le Wed, 27 Mar 2013 16:49:45 +0100, Robert Osfield <[email protected]> a
écrit:
Hi Sukender,
On 27 March 2013 15:35, Sukender <[email protected]> wrote:
Sure, sure... But I'm having UNSPECIFIED everywhere... This forces me to
trigger STATIC_OBJECT_DETECTION before.
If the DataVariance is UNSPECIFIED then there is no way for the
optimizer to know whether it's STATIC or DYNAMIC, one can try and
guess the appropriate DataVariance based on looking at update
callbacks etc. but it's just a best guess. Ideally a scene graph
should be created and setup with the appropriate DataVariance if you
are want to use the optimizer to optimize away nodes.
To me everything is working as it should.
Robert.
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
