Hi Frank -- Just adding to what Robert said:
Although FrameBufferObject does derive from StateAttribute, I have never seen it
used as an attribute attached to a StateSet. Rather, it's something that Camera
uses essentially internally.
Previous postings from Art Tevs (osgPPU) have warned of issues when attaching a
FrameBufferObject as an attribute to a StateSet... I think he expected it to
override the FrameBufferObject used by some parent Camera, but it didn't work
that way. There were possibly other issues too, I don't recall.
The bottom line is that you should probably not use FrameBufferObject directly,
and should always let Camera manage it for you.
-Paul
On 2/5/2013 4:10 PM, Frank Sullivan wrote:
Hi,
I'm looking at the source code for osg::FrameBufferObject, and as far as I can
tell, I just have to set this as an attribute on a node's StateSet and be done
with it?
If this is true, then can I use it in conjunction with Nested Render cameras in
order to get render-to-texture cameras that render in the order in which they
are encountered in the scene graph?
Thank you!
Cheers,
Frank
------------------
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=52399#52399
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
