On 9/21/06, Stephan Maximilian Huber <[EMAIL PROTECTED]> wrote:
In OpenGL and the OSG PixelBufferObjects are entirely seperate from FrameBufferObjects. The osg::CameraNode only deals in Pbuffers, FBO's and frame buffer, without any reference to PBO. I presume you mean FrameBufferObjects in this context.
Hi,
I am rendering a part of my scene into an image to print it out. I am
doing this via a cameranode, setting its RenderingTargetImplementation
to PIXEL_BUFFER_RTT or PIXEL_BUFFER (FRAME_BUFFER_OBJECT renders the
scene in 256 colors, bending occurs)
If I compile my application under Windows with VisualStudio 2005 in
debug-mode, everything works as expected, but If I compile it in
release-mode, I get a *message-box* with the message "Can't create
temporary window"
I know, that the ATI-driver for my MacBookPro under windows is crappy,
and does not support PixelBufferObjects so the CameraNode falls back to
pbuffers, but why do they work onyl in debug-mode?
As for working in debug but not release, my best guess would be some unitialized variable perhaps. The message box perhaps in an indicator that the setup of the Pbuffer failed in Producer so I'd recommend digging through this code and placing stop points on the code to see what it does and where the release vs debug difference might be comming in.
It might be that the glue code osgProducer that allows CameraNode to set up the pbuffer is causing some difference. See osgProducer::GraphicsContextImplementation for this glue code.
Robert.
Robert.
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
