On closer inspection, i think I do see some LOD changes on the slave
cameras, but the pixel aliasing is masking it. I think the bad aliasing
may be due to larger view frustums on the slave cameras, causing less
available screen pixels per geo-inch, which means I should consider
tightening the LOD ranges to be closer in? Does this make sense?
Thanks
Bob.
---------------------------------------------------------------------
Bob wrote:
I'm using an LOD (not Paged) textured terrain model built with osgdem.
In my app (OSG 2.4-based), configured with just the main default camera,
the LOD terrain levels are clearly visible as they change from one to
another.
In my same app, configured with two slave cameras (looking 45 left &
right), there is NO visible evidence that the LOD levels are changing!
It appears that the highest resolution (6") imagery is staying in at all
times (causing lots of aliasing and stressful graphics pipe texture
paging as a result). [Other LOD building models in the scene do seem to
LOD properly.]
What could cause what appears to be a perfectly good LOD terrain model
to no longer function properly when using slave cameras?
Bob.
--
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
