[osg-users] DBPager continuously reloading tiles

2009-04-10 Thread Evan Andersen
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 still providing good user interaction, so I have set my viewer up so that it only renders when necessary. I keep a loop running that does

Re: [osg-users] DBPager continuously reloading tiles

2009-04-10 Thread Evan Andersen
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 andersen.e

Re: [osg-users] DBPager continuously reloading tiles

2009-04-13 Thread Evan Andersen
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 andersen.e...@gmail.comwrote: Thanks for your response Robert. I just tried setting the expiry delay of the database pager to 10, 100, and 1000

Re: [osg-users] DBPager continuously reloading tiles

2009-04-22 Thread Evan Andersen
of consuming too much memory for a 32 bit application on Windows. Because of time restraints, I have not been able to follow-up on this problem. Sorry. *Ryan H. Kawicki* The Boeing Company Training Systems Services Software Engineer -- *From:* Evan Andersen

Re: [osg-users] DBPager continuously reloading tiles

2009-04-23 Thread Evan Andersen
reloading. I had a co-worker try this out and he was able to duplicate the problem pretty quickly, so hopefully it will happen easily for you too. Evan On Thu, Apr 23, 2009 at 2:14 AM, Robert Osfield robert.osfi...@gmail.comwrote: Hi Evan, On Wed, Apr 22, 2009 at 10:05 PM, Evan Andersen

Re: [osg-users] DBPager continuously reloading tiles

2009-04-23 Thread Evan Andersen
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