Hi Robert,
I presume that you won't be selecting too many objects in the scene,
so it's not like you'll be doubling the cost of the whole scene, and
if there is only one object in the scene that you select you are
unlikely to be breaking frame...
Well, that assumption is one I can't make... Since this is an
application similar to a modeling application, the user could load
anything up. And yes, we support multi-select, so the user could
conceivably select the whole scene.
Now, of course if the user loads objects which bring their system to a
crawl, I can't do anything to prevent that. However, if they load up
objects and the app just barely make frame, and then selects one of them
and it suddenly breaks frame, it makes our app look bad. It's a
contrived example, but it could really happen. And that's supposing they
only select that one object - they could select them all, and then the
total frame time might triple (I haven't tested this, but my results
with multiple objects seem to indicate that would be the result).
Anyways, the more general question: why is the frame time so affected by
such a simple effect? As I said, it's a two-pass effect, I would expect
the time for the selected object(s) to double, but not more... And I
disable lighting, blending, texturing for the second pass, so I would
think that pass would be quicker than the first.
Thanks,
J-S
--
______________________________________________________
Jean-Sebastien Guay [EMAIL PROTECTED]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
