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
Chris,
i dont know any, but since you are one of those few "elite" members of the OSG
community :-) Maybe you can help me understand what is going on:
http://forum.openscenegraph.org/viewtopic.php?t=3782
Thanks!
Sergey
Chris 'Xenon' Hanson wrote:
> I'm just wondering -- other than myself, are
Jeremy,
I hope everything goes well for you.
I have been using osgWidget extensively and it works great for me, i do have a
great number of workarounds though :D
Welcome back
Cheers,
sergey
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=18568
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
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"
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
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
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
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
10 matches
Mail list logo