Hi Emmanuel, On Sun, Jun 26, 2011 at 2:52 PM, BARANGER Emmanuel <[email protected]> wrote: > So I remade my installation to find the error and here it is : > > > Code: > RenderStage::runCameraSetUp(), FBO setup failed, FBO status= 0x8cdd
The status maps to GL_FRAMEBUFFER_UNSUPPORTED so it would look like your scene graph is attempting to use a feature not supported by your graphics card/driver. The standard osgviewer won't be use FBO's with simply models like cow.osg, but as soon as you use a render to texture technique it'll be used in supported. There are extension checks that normally change the implementation down to using pbuffer or a frame buffer read to implement the render to texture, but if your scene graph explictly targets an FBO then this fallback won't be happending. So what app do you get the above error for? Does example like osgprerender cow.osg work? What restult do you get if you run: $ glxinfo This will list all the supported extensions. > After a little research I have seen that I was not alone in this: ( > > Currently I can use 3D with Blender, SuperTuxKart, Marble etc .... but not > with OSG :( It's likely that these applications just make very modest usage of OpenGL avoiding more advanced features like FBO's. The OSG only uses the advanced features if your scene graph uses them so given more modest scene graph it should just work. Now one of the odd things is your report things work with OSG-2.8.5, and the FBO support really hasn't changed much since then other than bug fixes. In the case of FlightGear it could be the low level customization of the cull traversal and other parts of the OSG have been broken by changes to the internals of the OSG, so now fail when otherwise they succedded. For now I'd recommend running a range of OSG examples to see how they behave. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
