Speaking of the timing stats, I've been using the stat class with our game and it looks like so:

||  <-- event
| | <--  update
              ?      |     cull |
| Draw | --- gpu--- | | gpu |

The interesting thing about this is that there is a space gap between the update and the cull. Not sure yet if this is due to sleep or due to code workload. In the worse case all these bars are spread out where there are gaps in between each (I'm guessing cpu workload).


James Killian
----- Original Message ----- From: "Robert Osfield" <[EMAIL PROTECTED]>
To: "OpenSceneGraph Users" <[email protected]>
Sent: Friday, July 04, 2008 11:35 AM
Subject: Re: [osg-users] Update Optimization


Opps typo...

You *haven't* said anything about what you do in the
update other that update positions.

You need to provide us with far more info about what you are doing,
including actual timing stats on the operations.

Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to