Hey,
 
I need to correct my answer. ;-) There are still problems with the visual overlay of the highlight material.
 1.) If I use a wireframe as highlight the overlay works as expected..
 2.) If I use GL_FILL for the highlight it is not rendered over the 'normal material'. For example if I render a cube with backface culling enabled, I can see no difference form the outside, but inside I can see the highlight material.
My first guess was depth buffer related issueds. I already tried to manipulate the DepthChunk but even with GL_ALWAYS I can't see the highlight from the outside.
3.) If I use a transparent material as highlight, the transparency is only correct applied within the sub tree.
 
Thanks,
Michael
 
Gesendet: Mittwoch, 01. Oktober 2014 um 11:27 Uhr
Von: "Michael Raab" <michael-r...@gmx.de>
An: opensg-users@lists.sourceforge.net
Betreff: Re: [Opensg-users] Material Override
Works great. Thanks. Maybe a very short tutorial/explanation about stages, their capabilities and the rendering process in OpenSG2 would be useful ;-)

Michael

Am 01.10.2014 10:41 schrieb Carsten Neumann <carsten.p.neum...@gmail.com>:
>
> Hello Michael,
>
> On 09/30/2014 04:46 PM, Michael Raab wrote:
> > thanks for your explanation. I followed your hint and tried implement a
> > Stage similar to DepthPeelingStage but the rendering looks broken.
> > The geometry to highlight looks like it is rendered unlit. I'm attaching
> > the source code, maybe someone has some minutes to look at.
>
> in your case I don't think you want to disable the default partition,
> that is intended for Stages that want to take over rendering entirely [1].
> You can also avoid having to copy the viewport and camera settings, by
> changing the pushPartition call to:
>
> this->pushPartition(a, RenderPartition::CopyAll);
>
> I think it would also be better to set the override material on the
> partition that should use it, instead of the parent partition and have
> it inherited.
> I'm thinking something like the attached (completely untested).
>
> Cheers,
> Carsten
>
>
> [1] and probably only makes sense for stages that are used very near the
> root of the scene - otherwise I think that is likely to skip rendering
> of objects (namely those that have already been added to the default
> partition).
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Opensg-users mailing list
> Opensg-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/opensg-users
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to