There are two ways I can see to fix this problem. The ideal way would be to keep track of whether or not a VertexArray has been transformed to make sure it is only applied once. This turns out to actually be harder than it looks because the osg::Array objects do not keep track of their parents or what type of an array it is which the TransformAttributeFunctor needs.
The second way is to make a copy of the vertex and normal arrays if they are referenced more than once. While this may not be an optimal from a space point of view, it does produce the correct results.
Unless anyone objects, I'll put a patch together and submit it. It's a simple 5 line patch.
John
On 9/26/06, John Aughey <[EMAIL PROTECTED]> wrote:
There is a problem with the osg Optimizer. I generally don't run the Optimizer on scenes because I want to preserve the node construction, but it is used by default in osgviewer and osgconv. I discovered this problem when trying to view a model in osgviewer.
A model that exhibits the problem can be found at http://thinksplat.com/cubetest-cleanup.osg You can ignore the textures. If you view this with osgviewer, you'll see a cube, an outline of a cube, and another cube 7 times higher than the outline. The correct viewing of this file should be to have the cube that is way up in the air be within the bounds of the wireframe cube.
If you modify osgviewer and comment out the optimize step, it looks like it is supposed to look. I do not have a fix for the Optimizer, but I can give some suggestions. The group that is offset has 7 children, and those children are offset by a factor of 7. It looks like the problem could be in Optimizer::*::removeTransforms methods.
John Aughey
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
