Hi Robert, and thanks for your thoughts on the subject. I hoped I messed up the context setup/extension checking code but sadly I didn't, I tested the code successfully on both Windows 7 using Visual studio as well as on Mac OS X using XCode.
This problem only happens on mingw when using osg. And since it crashes on the osg supplied example "osgprerender" I assume It's not about my app at all. The biggest issue is that there are so many parameters that could affect this. win7, the gl headers supplied by mingw (I have tested with the nvidia sdk ones as well as those distributed with mingw) osg versions, how mingw hadles defines etc etc Has anyone successfully built and run osgprerender using mingw? /Filip On Fri, Apr 30, 2010 at 12:02 PM, Robert Osfield <[email protected]> wrote: > Hi Filip, > > I don't enough about how you are using your code in the wider app, but > the extension mechanism requires a graphics context to be able to > initialize itself - perhaps this may be affecting your local test for > the graphics context support. > > Beyond this I can't really help as I can't reproduce the problem. The > best I can suggest is to try and add to step through The FBOExtensions > object initialization to study what is happening w.r.t function > pointers and the extension support queries. > > Robert. > > On Fri, Apr 30, 2010 at 10:47 AM, Filip Wänström <[email protected]> > wrote: >> More info: If I print the process addresses of some of the extensions like >> so: >> >> osg::FBOExtensions* ext = osg::FBOExtensions::instance(0,1); >> printf("got ext %p \n", ext); >> printf("Address of glFramebufferRenderbuffer : %p\n", >> ext->glFramebufferRenderbuffer); >> if (ext->isSupported()) >> printf("FBO is supported!\n"); >> else >> printf("FBO is NOT supported!\n"); >> >> I get that the extension is not supported and the address is 0. (On >> mac and visual studio this reports fbo support as well as a valid >> address) >> The weird thing is that OSG as a whole reports that framebuffer >> extensions are supported when printing debug notifications. >> >> /Filip >> >> >> On Fri, Apr 30, 2010 at 10:25 AM, Filip Wänström <[email protected]> >> wrote: >>> Hi, >>> I have a very simple app that uses FBOs to do some post processing of >>> a scene. It works great on Mac OS X and windows 7 using visual studio. >>> >>> When compiling for windows 7 using mingw (codeblocks) however, I get >>> an app that crashes on framebuffer creation. The osg debug info >>> (OSG_NOTIFY_LEVEL=DEBUG) only tells us that we DO have support for the >>> framebuffer extension (both the EXT and the ARB version) but it >>> crashes when trying to set up the fbo. (seems to be related to >>> glFramebufferRenderbuffer). If we use FRAME_BUFFER (not object) as >>> fallback it works but obviously that is not a solution. >>> >>> After this failure we tried to make a simple program on mingw in "raw" >>> OpenGL and GLFW + GLEW that uses FBOs. It worked fine. So there is no >>> issue with mingw and fbos in general. >>> >>> After this I tried to run the osg example osgprerender but it also >>> crashes with the same problems. The same example, on the same machine >>> built with Visual Studio 2008 (express) runs great. >>> >>> So, as far as I can tell there is some problem with the combination of >>> mingw and osg. I tried to follow the osg code using both debugger and >>> printfsin the osg source but I failed to follow all levels of >>> indirections in the abstraction layers in order to reach a conclusion. >>> It seems like the functions pointers are NOT NULL but erroneous. >>> >>> Does anyone have any idea of where to look? Or even better, a fix? >>> Been on this for many days now and have run out of ideas... >>> >>> /Filip >>> >>> system info: >>> win7 >>> core i3 >>> nvidia gtx 260 with 197 series drivers (tested a few others as well) >>> latest codeblocks >>> >> _______________________________________________ >> osg-users mailing list >> [email protected] >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
