Hi Ryan,
Today I checked changes to the DatabasePager to use a custom observer_ptr<>
rather than a ref_ptr<> with the intention of fixing the outstanding issues
with the pager such as the ones you've observered with multiple views.
Could you please test the svn/trunk version of the OSG and see if
Greetings,
Forgot to mention that I have three hacks that fix/minimize the issue:
Hack #1: Check for duplicates when adding PagedLod to the activeLODList in
FindPagedLODsVisitor. If a duplicate is found it is removed. This code
helped determine if there are duplicates.
Hack #2: In the Terrapage
Debugging terrapage plugin results:
We've been seeing the same problem with a single camera moving around in the
database.
Here's what I've been seeing:
TXPNode::traverse -> this handles the unloading and loading of LOD 0 tiles.
When loading a tile here's what I see:
When the tile has no other l
Hi All,
I've now checked in the new testbed example, osgmultiviewpaging, for
sorting out database paging. It's just a first cut so far, but I'll
add to it as we go on. An svn update will get this example.
This example we'll need to add support for specifying animation paths
for each of the view
Hi Michael,
On Wed, Nov 25, 2009 at 9:13 AM, Michael Bach Jensen wrote:
> You are free to use my code as you wish :-)
Thanks.
> Do I need to download anything extra wrt the earth.ive you linked to? It does
> not contain any PagedLOD nodes (at least the statistics view does not report
> any),
Hi, Robert!
You are free to use my code as you wish :-)
Do I need to download anything extra wrt the earth.ive you linked to? It does
not contain any PagedLOD nodes (at least the statistics view does not report
any), and so will not have any issues.
Thanks for looking into the issue and thanks
Hi Sergey et. al,
I'm finally getting back ontop of my submissions backlog and will be
allotting time this week to investigating outstanding issues. The
DatabasePager issue being one of them. The first step for me is
recreating the issue so I've got your main.cpp example up and
compiling under m
Hi everyone!
This is a tough one. I'm now certain that there is more than one bug at large
here! At least one in the pager (the one mentioned in the PagedLOD experts
thread) and at least one in the txp plugin.
The one I have been chasing for the past 2 days is within the txp plugin and
looks
> BTW are aware of any publicly available Terra Page terrain?
Off hand I'm not sure that there is any! Have you tried contacting Presagis?
Thay have the rights for Terra Page and might have a sample.
I'm about to challange Presagis to make a "ive" output for there TerraVista
program.
I ha
Wojtek,
I tried what you suggested. Unfortunately it did not solve the problem :-(
Does this look like what you were referring to?
osg::ref_ptr opt = new
osgDB::ReaderWriter::Options;
opt->setObjectCacheHint(osgDB::ReaderWriter::Options::CACHE_NONE);
osgDB::Registry::instance()->setOptions(opt.g
Hi,
:-* looks like I did forget to attach the file,
Thank you!
Cheers,
sergey
BTW are aware of any publicly available Terra Page terrain?
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=18439#18439
/* OpenSceneGraph example, osgcompositeviewer
Hi Sergey,
did you forget to attach it?
jp
sergey leontyev wrote:
I have created an example for the memory growth problem.
If you have a chance can you please run it with the following command arguments
:
" -3", where is your database main txp file.
It creates 3 views. In order to
I have created an example for the memory growth problem.
If you have a chance can you please run it with the following command arguments
:
" -3", where is your database main txp file.
It creates 3 views. In order to trigger the memory growth problem.
First get closer to the terrain slo
robertosfield wrote:
> Hi Sergey,
>
> On Tue, Oct 13, 2009 at 11:41 PM, sergey leontyev <> wrote:
> I don't have any ideas why this occurring. One would expect the
> number of nodes to increase when you move to the new camera positions
> but "should" settle down quite quickly once all the requir
Hi Sergey,
On Tue, Oct 13, 2009 at 11:41 PM, sergey leontyev wrote:
> Robert and others,
> I checked the stats as you recommended. What I see is that "LOD" value for
> both cameras is increasing when nothing in the application is changing. The
> same is true for the "CULL" value. No other value
Robert and others,
I checked the stats as you recommended. What I see is that "LOD" value for both
cameras is increasing when nothing in the application is changing. The same is
true for the "CULL" value. No other values change by any significant amount,
but LOD and CULL increase indefinitely. A
HI Sergey,
On Sat, Oct 10, 2009 at 12:03 AM, sergey leontyev wrote:
> Robert,
> I tried the 2.9 trunk code with.
> osg::DisplaySettings::instance()->setMaxTexturePoolSize(1);
> osg::DisplaySettings::instance()->setMaxBufferObjectPoolSize(2);
>
> The problem still exists. As memory
Robert,
I tried the 2.9 trunk code with.
osg::DisplaySettings::instance()->setMaxTexturePoolSize(1);
osg::DisplaySettings::instance()->setMaxBufferObjectPoolSize(2);
The problem still exists. As memory usage was growing and growing. I just left
the computer running and observed th
Hi All
Just wantet to add that we are also using Delta3d and as a consequence we
are using the composite viewer.
Brgs.
Ralf Stokholm
2009/10/8 Michael Bach Jensen
> Hello everyone,
>
> We are having the exact same problem at our company for quite some time
> (currently on osg 2.8.0 via Delta3
Hello everyone,
We are having the exact same problem at our company for quite some time
(currently on osg 2.8.0 via Delta3D and using TerraPage terrains). I have
verified that viewing the terrain in the osgViewer works fine, but in our app,
which also uses multiple cameras, the memory-keeps-gro
Hello,
I am happy to see that others have the same problem, which means I am not crazy
:-). I am going to try to port my application to trunk verstion of the OSG and
to see if this issue was solved.
Cheers,
sergey
--
Read this topic online here:
http://forum.openscenegraph.or
Hi Ralf.
On Wed, Oct 7, 2009 at 10:33 AM, Ralf Stokholm wrote:
> I was wondering if somthing in the database pager is preventing the release
> like a copy of a refptr or similar?
I believe this would be very unlikely. There is no special handling
of multiple view points, and there needn't be as
Hi Robert
Unfortunatly I cant upgrade to trunk without a considerable effort, so that
wont happen right now. But the texture pools looks really interesting with
regards to large paged terrains.
I doubt if its a driver thing directly, as Im able to run osgviewer on the
same dataset without problem
HI Sergey and Ralf,
I haven't seen this behavior in the DatabasePager before, and it might
not be directly related to the DatabasePager at all. The
DatabasePager itself doesn't actually know anything about cameras, it
just handles requests made to it from the cull traversals. The code
for handli
Hi Sergey
Im afraid I dont have an answer, but I can back up your observations.
We are using two cameras for our application one for a standard view the
other for an IR targeting POD. The two cameras are looking in opposite
directions and have different lodscales.
I have also notised that the me
Hello,
(i am using OSG 2.8.2)
Let me try to explain the problem :
I have a big database (TerraPage). I load it into my application. I have two
views (cameras) within a window and i can position each camera individually
looking directly down at the terrain ( I am using orthographic projection
26 matches
Mail list logo
