Hi JS,
On Thu, Apr 23, 2009 at 7:27 PM, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com wrote:
As an additional data point, on Windows, the NVidia drivers ship with vsync
enabled by default, but ATI ships with it disabled. This always bugs me when
setting up a new machine.
Thanks for the
Hi Robert,
We could possible provide an env var to provide a hint to
DisplaySettings for what the defaults should be.
Yes, that would be nice.
As a related point, in Vortex we have a frame lock which will sleep a
given number of milliseconds at the end of the post-update phase before
Hi JS,
On Fri, Apr 24, 2009 at 2:37 PM, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com wrote:
As a related point, in Vortex we have a frame lock which will sleep a given
number of milliseconds at the end of the post-update phase before starting
the next frame. The amount of time it sleeps
Hi Robert,
The frame scheme I'm working on right now only affect Viewer::run(),
and you'll be able to switch it on/off as well. So if you don't use
Viewer::run() then you won't get this facility, and even if you do use
run then you'll be able to control the whether or not it does cap the
frame
Hi Evan,
On Wed, Apr 22, 2009 at 10:05 PM, Evan Andersen andersen.e...@gmail.com wrote:
Ryan,
Thank you for the suggestion. When I call
setTargetMaximumNumberOfPagedLOD(0) on the database pager, as you suggested
and then set the expiry delay to DBL_MAX and the expiry frames to 10, as
Jason
Robert,
Here's a simple viewer I wrote that does non-continuous render and exhibits
the problem. You can just run it like the osgviewer application, passing in
the path to a database on the command line. I have also included a stats
handler that will cause the app to switch to continuous render
Users
Subject: Re: [osg-users] DBPager continuously reloading tiles
Robert,
Here's a simple viewer I wrote that does non-continuous render
and exhibits the problem. You can just run it like the osgviewer
application, passing in the path to a database
Thanks Evan, with your example I'm able to see the problem when
browsing http://www.openscenegraph.org/data/earth_bayarea/earth.ive.
I'll now dig into the DatabasePager to see what is up.
On Thu, Apr 23, 2009 at 4:08 PM, Evan Andersen andersen.e...@gmail.com wrote:
Robert,
Here's a simple
On Thu, Apr 23, 2009 at 4:32 PM, Robert Osfield
robert.osfi...@gmail.com wrote:
Thanks Evan, with your example I'm able to see the problem when
browsing http://www.openscenegraph.org/data/earth_bayarea/earth.ive.
I'll now dig into the DatabasePager to see what is up.
The culprit looks to be
Robert,
Things seem to work fine if I only call advance() when a render is done.
Off the top of your head, can you think of any problems that might be caused
by not doing an advance for every iteration of the event and update
traversals? Would it be better to advance the reference time at each
HI Evan et. al,
On Thu, Apr 23, 2009 at 5:16 PM, Robert Osfield
robert.osfi...@gmail.com wrote:
Tweaking the
application code so that it doesn't do an viewer.advance() until a new
frame is actually required.
I've now tried this and got the viewer supplied by Evan to do lazy
updating of the
On Thu, Apr 23, 2009 at 5:51 PM, Evan Andersen andersen.e...@gmail.com wrote:
Things seem to work fine if I only call advance() when a render is done.
Off the top of your head, can you think of any problems that might be caused
by not doing an advance for every iteration of the event and update
Hi All,
Out of curiosity I did some power tests viewing a paged database with
different viewer frame updating configs. Power is measure at the wall
using so it's the complete machine. T
103W Compute at idle
103W Lazy frame rendering (based on modified version of Evan's viewer)
125W Continuous
Hi Robert,
On the same track,
perhaps we should also consider artificially restricting frame rate to
prevent running apps running at full pelt due to vsync being off.
The later is possible more important under Linux as I've found ATI,
Nvidia and Intel drivers neglect to enable vysnc by default.
[mailto:andersen.e...@gmail.com]
*Sent:* Monday, April 13, 2009 10:08 AM
*To:* OpenSceneGraph Users
*Subject:* Re: [osg-users] DBPager continuously reloading tiles
I tried the settings you suggested Jason, but I still get the same
behavior.
-Evan
On Fri, Apr 10, 2009 at 5:57 PM, Jason Beverage
Company
Training Systems Services
Software Engineer
From: Evan Andersen [mailto:andersen.e...@gmail.com]
Sent: Monday, April 13, 2009 10:08 AM
To: OpenSceneGraph Users
Subject: Re: [osg-users] DBPager continuously reloading tiles
I tried the settings you suggested Jason, but I still get the same behavior.
-Evan
On Fri, Apr 10, 2009 at 5:57 PM, Jason Beverage jasonbever...@gmail.comwrote:
Hi Evan,
What happens if you set the expiry frame to something like 10 and the
expiry time to DBL_MAX?
I haven't tried running
Hi Evan,
Which version of the OSG are you using?
Robert.
On Fri, Apr 10, 2009 at 6:07 PM, Evan Andersen andersen.e...@gmail.comwrote:
I'm working on an application which uses osgEarth to display terrain
databases to users. I need the application to use as little CPU time as
possible while
Sorry, I forgot to mention that. I'm using version 2.9.2 from the trunk.
-Evan
On Fri, Apr 10, 2009 at 11:28 AM, Robert Osfield
robert.osfi...@gmail.comwrote:
Hi Evan,
Which version of the OSG are you using?
Robert.
On Fri, Apr 10, 2009 at 6:07 PM, Evan Andersen
Hi Evan,
What happens if you set the expiry frame to something like 10 and the expiry
time to DBL_MAX?
I haven't tried running the DatabasePager without non-continuous rendering,
so I'm not sure how well it works.
Jason
On Fri, Apr 10, 2009 at 5:20 PM, Evan Andersen
20 matches
Mail list logo
