Hi Robert, I was never able to find any problem with the data, although I did not spend a huge amount of time looking. I was able to remedy the problem (or so it seems so far) with another solution. In the past, I had been using the database pager with setDoPreCompile(false). I tried changing the value to true, the crash stopped occurring.
Another setting I changed was the target number of inactive paged LODs. I decreased it from 100 to 25, which obviously reduced my applications memory hunger. However, I don't think this solved the crash I was seeing. Can you think of any reason why setting the pager's pre-compile setting to true fixed my problem? Thanks, Andrew -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Osfield Sent: Monday, March 26, 2007 1:09 AM To: osg users Subject: Re: [osg-users] Viewer crash in osg/Geometry.cpp Hi Andrew, Just add debugging code into the core OSG to monitor the data such as in the Geometry::drawImplementation(), or write a custom Registry::ReadFileCallback that runs a custom NodeVisitor that checks all the geometry on load. The osgUtil::Optimizer has lots of cusotm NodeVisitor that would serve as a good template for finding the geometry. Robert. On 3/26/07, Weitz, Andrew C. <[EMAIL PROTECTED]> wrote: > Hi Robert, > > Thank you for the advice. I tried running the optimizer on my scene, > but it did not fix the crash. I'm not sure how to isolate the > problematic data because I'm working with several million textured > triangles. If I do find the problem, I'll let you know what it was. > > Thanks, > Andrew > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Robert > Osfield > Sent: Sunday, March 25, 2007 3:15 AM > To: osg users > Subject: Re: [osg-users] Viewer crash in osg/Geometry.cpp > > Hi Andrew, > > The most likely cause is an empty array or something similar in your > data. > > Its a long shot, but perhaps the following method would clean up your > data: > > osg::Geometry::computeCorrectBindingsAndArraySizes() > > The osgUtil::Optimizer has a visitor CheckGeometryVisitor that is as > part of the default traversals when running the optimizer, > CheckGeometryVisitor calls this method for all the geometry in the > scene. > > Robert. > > On 3/24/07, Weitz, Andrew C. <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I have a bunch of data I am trying to view in an OSG-based viewer. > The > > data is stored as OSG geometry (vertices, triangles, and compressed > > textures). When I am viewing the data, I can fly around for a while, > > and everything looks fine. Eventually, the viewer will crash. In > debug > > mode, it breaks on the following line in osg::Geometry:: > DrawTexCoord(): > > > > virtual void apply(const Vec2& v) { glTexCoord2fv(v.ptr()); } > > > > Does that mean something is wrong with texture coordinates or textures > > in my data? If so, is there an easy way to isolate the problematic > > data? > > > > Thanks, > > Andrew > > _______________________________________________ > > osg-users mailing list > > osg-users@openscenegraph.net > > http://openscenegraph.net/mailman/listinfo/osg-users > > http://www.openscenegraph.org/ > > > _______________________________________________ > osg-users mailing list > osg-users@openscenegraph.net > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ > _______________________________________________ > osg-users mailing list > osg-users@openscenegraph.net > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ > _______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/ _______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
