Hi Roger, Could you disable the context sharing?
Robert. On Wed, Jul 15, 2009 at 12:10 PM, Printy, Roger-P57305<[email protected]> wrote: > I added the same call to each view as they are created and that fixed the > problem in some instances but not all. I am using context sharing, was > thinking something changed in OSG that would cause the issue to be with > respect to context sharing, at least that is what I was going to look at > today. > > > Roger D Printy > General Dynamics C4 Systems > 12001 Research Parkway, Suite 500 > Orlando, FL 32826 > > Office: (407) 281-5608 > Fax: (407) 823-7012 > Email: [email protected] > > This email message is for the sole use of the intended recipient(s) and may > contain GDC4S confidential or privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not an > intended recipient, please contact the sender by reply email and destroy all > copies of the original message. > > > ________________________________ > From: [email protected] > [mailto:[email protected]] On Behalf Of I-Nixon, > Anthony D > Sent: Tuesday, July 14, 2009 11:24 PM > To: OpenSceneGraph Users > Subject: Re: [osg-users] osgViewer::CompositeViewer Texture Issue > > I have seen a similar problem to this, but only with paged terrain > databases. My problem was that the second view would not load textures that > had already been loaded by the first view. > > Calling view->getDatabasePager()->setUnrefImagedataAfterApplyPolicy(true, > false); > > fixed it for me, but I've never been sure if that was the "correct" way of > fixing the problem. I'm not sharing contexts between the views (perhaps I > should be). > > I'm currently running 2.9.3 but have seen this of 2.8.1 as well - on nVidia > with the latest drivers. > > Anthony Nixon > > ________________________________ > From: Mark Sciabica [mailto:[email protected]] > Sent: Wednesday, 15 July 2009 12:41 PM > To: OpenSceneGraph Users > Subject: Re: [osg-users] osgViewer::CompositeViewer Texture Issue > > Hello Roger, > > I remember running into a similar problem that I attributed to an nVidia > driver bug. You might want to try upgrading your driver. I worked around the > problem by calling dirtyTextureObject() on each texture in the model > whenever I created a new window, forcing the driver to reload the texture > data from system memory. I think the driver got confused with shared > contexts and this function was an effective reminder of what the texture > data was supposed to be. > > Regards, > > Mark > > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Printy, > Roger-P57305 > Sent: Tuesday, July 14, 2009 8:36 AM > To: [email protected] > Subject: [osg-users] osgViewer::CompositeViewer Texture Issue > > > > I am upgrading to OSG 2.8.1 from OSG 2.4 and am having a problem with use of > the osgViewer::CompositeViewer. My application adds/destroys views > dynamically and I am having an issue when I have two views loaded with the > same terrain/textures (for example a terrain) when I close one view the > textures in the 2nd view all get removed from the scene. The only way I am > able to get the textures in the remaining view to reload is to close the > view, leaving none open, and opening a new view. This process destroys and > recreates the composite viewer. > > I have tried calling setUnrefImagedataAfterApplyPolicy(true, false) on each > view as they are created but this has not helped resolve the issue. > > Can anyone provide any advice to help with this? > > Thanks, > Roger > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
