Hi Mark, The osgSim::ElevationSlice and underlying osgUtil::PlaneIntersector that do all the work are pretty new classes, and while I've tested it pretty thoroughly I can't recreate all possible combinations of data. I could well be that certain cases uncover a bug or an unhandled geometry case.
Unfortunately without the geometry in front of me and the exact settings of the slicing used to recreate the problem there is no real way for me to diagnose what might be amiss. Would it be possible for you to send me a dataset and example app with settings that recreate this problem? Robert. On 1/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I have been experimenting with the new osgSim::ElevationSlice class and have run across some problems. I setup an application which walks across an openflight database, creating ElevationSlices at every n intervals in order to obtain HAT values. The values that are returned are correct, but every so often I run into a problem. In ElevationSlice::computeIntersections(), I come across a few cases where the method does find any intersections and will print it out on screen (from line 1419 of ElevationSlice.cpp): osg::notify(osg::NOTICE)<<"No intersections found."<< std::endl; Furthermore, it will spit out the number 3, 2, or 1 on screen as well when no intersections are found. I traced this down and found it occuring in this method: osgUtil::PlaneIntersector inline void operator() It evaluates the value of numOnPlane, whether it is 3, 2, or 1, and executes osg::notify, printing the value of numOnPlane. I can't determine why this is happening when clearly there are intersection(s). I have even created an osg::Geometry* line that draws the 'slice' I created (where no intersections are reported) and I proceed to write it out as an .osg file. I then load osgviewer, supplying the terrain file and the .osg file I just created as command-line arguments. When viewing the scene in wire-frame mode, I can physically see the line geometry intersect with a triangle edge of the terrain. So to summarize, I can't determine why the elevationslice finds no intersections and it's reasoning behind it. Am I overlooking something? Mark Russell [EMAIL PROTECTED] This is an e-mail from General Dynamics Land Systems. It is for the intended recipient only and may contain confidential and privileged information. No one else may read, print, store, copy, forward or act in reliance on it or its attachments. If you are not the intended recipient, please return this message to the sender and delete the message and any attachments from your computer. Your cooperation is appreciated. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
