Hi Robert,
> although I'm not yet happy in having the mutable variable I haven't tought about threading issues... maybe moving this variable from osg::Program to osg::PerContextProgram would avoid any threading issue ? > Interesting suggestion. There is real problem with the disparity > between processing fixed function geometry and how shaders relate to > geometry. Whatever we do we'll need to provide some state related > mechanism that is able to tesselate and place objects on the CPU in > the same way that they are processed on the GPU. This is a really > bleeding edge scene graph problem, no prior art to inspire us on this > one. In my opinion, this is the best option, because you can now tell to a primitiveset exactly how it should be drawed. About tesselating data on CPU : forgot about it. It's impossible. It's as complex as executing a fragment shader on the CPU. Thank you! Cheers, Aurelien ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=54494#54494 _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
