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
[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/