Cool, it can be done easily, or I better wait for a public api/doc?
Hmm, I'm not sure I understand you.
SceneViewExtension is used for the plugin's functionality, including achieving effect that apply only to specific objects on the scene. In the current version of the plugin, this can be done using plugin's blueprint library or console commands. What do you mean by public api/doc?
84 days ago (+2)
Well I'll see what I can do with gameplay tags since that's a good idea. But first, I need to finish functionality related to custom depth and stencil.
I think the new update is more than halfway done, so it will include expanded functionality for excluding objects.
I've found a proper way to read Stencil values of objects for operations within the shader, but I still need to find a more optimal way to pass this values and work with this array inside the shader code (which is always tricky with arrays in HLSL).
Hey!
I’m planning to completely revamp how users can control and use the effect, since I think I’ve found the right way to handle it through the material system in the engine, which should be much more user friendly.
But there's still a lot stuff to test.
For example, for some reason, masked materials start leaving a slight trail in the texture. This is related to the texture format, tho I'm not quite sure how to fix it yet due to the specifics of texture format conversions in RDG.