Hi Sebastian, On 19 January 2015 at 21:42, Sebastian Messerschmidt < [email protected]> wrote:
> Windows 7, VisualStudio 2010. > It is crashing in a minimal application as well as using osgviewer. > Thanks for the additional details. Have you tried to use my minimal database? > Haven't tried yet, will try this morning once I've got through my email and admin work. > It reproduces the crash when loading it with the osgviewer and stiring > around with the mouse a bit. (Also take a look at the attached picture: It > shows a messed up State) > I was able to fix the crash by removing the GLExentsions::Set(contextId,0) > in the State destructor. But this seems plain wrong. I suspect on my > platform, the State is cleared and reinitialized for some reason. > When I can spent some time on this, I can try to create a minimal example. > Just out of curiosity: Is there any reason for the State to remove the > extensions for the ContextID? I suspect there is only one State per > Context, which seems ok, but I cannot grasp, why it is released in my > scenario. > The design is meant to have the osg::State created by an osg::GraphicsContext and managed through the lifetime of that GraphicsContext. One shouldn't in theory be creating osg::State or destroying osg::State outside of this context usage. Something somewhere is obviously trying to do it's own thing w.r.t osg::State, right now I don't know where this might be. > > Also I had problems after the fix loading other databases; It seems the > range lists in paging are invalid. It randomly displays the wrong tiles > with wrong facing. I'll try to hunt this down too. > Any suggestions how to narrow down the problem on my side? > What do you mean by range lists? You'll need to send me a screen shot. Robert.
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
