HI Rui & Sebastien, On 21 November 2014 02:13, Wang Rui <[email protected]> wrote:
> At the first sight I would prefer adding a new property to > osg::Camera::Attachment, which should be clear to MRT related programs. But > as Sebastian tells, there is also the draw_buffers_blend extension, which > requires buffer ID for separated blending functions. This may lead us to > rewrite the osg::BlendFunc and osg::BlendEquation implementations later. > I will need to look at the draw_buffers_blend extensions. I do suspect it'd be better to create new osg::StateAttribute subclasses rather than adapting existing ones like BlendFunc and BlendEquation. One possibility we could look at is using the StateAttribute::set/getMember() as a way of indexing the buffer ID - currently this exists for implementing glLight and glClipPlane. This way you'd specify the blend settings using one StateAttribute per render buffer. It could be that use of the StateAttribute::Member is the way forward for all these related bits of state rather than pushing settings into osg::Camera. I would first try to migrate current code to osg::Camera this weekend, if > my four-months old daughter agrees. :-) > Ooo, congratulations, there's a good excuse for not being able to code 24:7 :-) Robert.
_______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
