Hi Rory, The intersection routines are designed to be general useful rather than highly optimized, if you want to great deal of intersection testing then optimizing both the intersection routines and the database would be best. Not loading textures might make loading a bit faster, and will reduce memory footprint but it won't effect intersection performance unless you are memory bound.
There are lots of ways to optimize intersection routines and databases. Perhaps members of the community can pick up on this thread as my RSI just can't cope with indepth stuff. Robert. On 5/8/07, Breen.Rory (UK) <[EMAIL PROTECTED]> wrote:
Hi all, Having just started looking at OSG I am having a few issues. I am currently loading in an OpenFlight DB and doing intersection tests with it. This eats up the CPU and I was wondering if there was any optimization that could be done? I do not actually need to render the terrain at all just interrogate it for intersections, so is there something I can do? I.e. not load the texture? Would it be better to use DTED, as this is another option? Thanks Rory ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
