Hi Robert,
On Wednesday 08 November 2006 10:23, Robert Osfield wrote:
> There are lots of issues besides thse to be mindful when composing an
> efficient scene graph. There are also lots of tips and tricks you can
> deploy to help out. What is appropriate will depend on where you are
> starting from and your current bottlenecks.
Ok. Bought that.
Return to my prevous question:
how can I find out the bottlenecks?
... CPU profiling with whatever CPU profiler is out of question.
Or other asked different:
What tools do you use for that?
> When you have a working port of FlightGear I'll download it and see if
> I can get it running will give me a better insight. However, I am
> really busy with work, so tinkering with other code no matter how
> curious has to take a back seat to my core duties.
Thanks for the offer. I will return to that.
:)
> Things I'd suggest are putting in update, cull and draw stats is also
> very useful, if you can have these on screen then it'll help. Another
> trick is to output the scene graph to a .osg file and just look
> through it, looking for how balanced the scene graph is, and if
> certainly nodes are being overused perhaps mis-used.
I used osgedit for that so far.
Other suggestions?
> Are there developer docs on FlightGear?
Mostly the source.
:-/
There are some bits on www.flightgear.org.
The wiki is growing and has partly interresting bits.
BTW: you told me that there is a scenegraph balancer in the Optimizer?
Which optimization flag is that?
Greetings and thanks
Mathias
--
Dr. Mathias Fröhlich, science + computing ag, Software Solutions
Hagellocher Weg 71-75, D-72070 Tuebingen, Germany
Phone: +49 7071 9457-268, Fax: +49 7071 9457-511
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
