On 5/31/07, sherman wilcox <[EMAIL PROTECTED]> wrote:
Since I didn't get any replies the first time around, I'd like to
offer a possible solution.
What if the main visualization app sent queries (TCP/IP, IPC, etc.) to
another process which performed all the intersection tests.
Admittedly, this isn't high-performance, but performing these
intersection tests from another app most certainly wouldn't result in
dropped frames. For my particular problem I can suffer through the
lazy intersection tests. One question I have is whether or not I can
share the same paged database between two different apps.
Thoughts...comments?
Running another application on a separate process or machine would
reduce the chances of breaking frame on the main graphics application.
If you are willing to duplicate all the paged data then you could just
run a separate process in the background of the graphics app that
works entirely on its own scene graph, and has its own paging code.
The osgSim intersection classes have their own syncronous paging code
so you could get away with just one separate process. You might find
the disk and front side bus overly contended though with both the
graphics and the intersections via for bandwidth.
Robert.
_______________________________________________
osg-users mailing list
osg-users@openscenegraph.net
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
