|
Thank you, Robert, tried as suggested but the issue remained. Yes, I am on
Windows. I played more with this and noticed the line that was commented in the
original osgsimplepager saying
scene->getState()->reset().
After uncommenting that line, the issue seems to be resolved.
Thanks again,
Sinisa
----- Original Message -----
Sent: Tuesday, September 12, 2006 8:50
AM
Subject: Re: [osg-users] Texture paging
issue when changing the viewpointposition (txp, DatabasePager)
HI Sinisa,
Try disabling the pre compile operations to
see if its the thing that is causing the slow loading of tiles. This
might not be a long term solution but should give you more insight what might
be up. I don't know what OS you are under, but under Windows in a
console you'll do:
set OSG_DO_PRE_COMPILE=OFF
Then run
your app. You can print out all the env var options by
doing:
osgviewer --help-env
Robert.
On 9/11/06, Sinisa
Popovic <[EMAIL PROTECTED]>
wrote:
Hi
all,
In my app, I need to play several few-minute-long scenarios in a
row, where in each scenario the viewpoint is placed on a different spot
on a TXP terrain (and once it is positioned it can only rotate, not
translate). For this I use OSG-VR Juggler combination, but in trying
to simplify things to resolve the issue I encountered, I modified
osgsimplepager to match the situation I
have: - RenderSurface (window) is created once at
the app startup; it is not
re-created on each iteration (scenario) when SceneView
is
re-created - I place a viewpoint to a different
predefined position on each
iteration, and viewpoints in different iterations are far
enough to require paging
in/out.
_Issue_ For the first iteration, textures are shown within
a few seconds, and for third iteration on, no textures are shown for
several minutes (then I stop waiting). Second iteration more often
behaves like the 3rd one, and sometimes like the 1st one (but then it
still takes noticeably longer to show the textures). However, if I
recreate the RenderSurface on each iteration (as done in original
osgsimplepager), and keep everything else the same as above, the
textures are shown about as fast as for the first viewpoint. I appreciate
any insight into why this might happen and/or how to overcome it without
re-creating the window.
_Additional info_ I printed to a file the
console output for three iterations in both situations (common window
vs. window-per-iteration) with DEBUG_FP notify level, and the same tiles
and subtiles are getting merged (only order differences). I can even see
that the changes in the shape of the terrain look the same, but in
common-window case the terrain is made up of shaded polygons, without
textures or additional LOD objects (e.g. trees) that show up in the
window-per-iteration case.
Thank
you, Sinisa
_______________________________________________ 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/
|