You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[reporter="spacegaier", created="Sat, 24 Nov 2012 19:54:16 +0100"]
Original reporter: rride
In a current version there is no possibility to set stencil ops, masks, values etc in material files, this feature is enabled only in compositor files, but stencil can be used not only in post-processing and stencil shadow-related effects.
Sometimes this feature be VERY useful, because it would help to avoid setting stencil values through RenderQueueListener class.
Shouldn't be difficult to add, in theory. The main problem is that it will conflict with other stencil uses (compositor stencil operation, stencil shadows).
On the other hand, if we have material stencil, the compositor stencil would be somewhat obsolete since the same thing can then be achieved by changing the compositor's materials. And as it stands, it looks like stencil shadows are going to be removed in Ogre 2.0, which would also make things easier.
paroj
changed the title
[OGRE-24] [Papercut] Add possibility to control stencil usage from material files!
[OGRE-24] Add possibility to control stencil usage from material files!
Jul 5, 2017
implementing this would increase the size of every pass. Given that this only enables very specific use-cases, I think the current approach with Compositors / RenderQueueListener is sufficient.
[reporter="spacegaier", created="Sat, 24 Nov 2012 19:54:16 +0100"]
Original reporter: rride
In a current version there is no possibility to set stencil ops, masks, values etc in material files, this feature is enabled only in compositor files, but stencil can be used not only in post-processing and stencil shadow-related effects.
Sometimes this feature be VERY useful, because it would help to avoid setting stencil values through RenderQueueListener class.
Original Mantis Ticket: http://www.ogre3d.org/mantis/view.php?id=370
The text was updated successfully, but these errors were encountered: