URP Render Objects support for Rendering Layers

[Prodigga]

There was some movement on this here

RenderObjects Rendere Feature is missing support for Rendering Layer Mask

Hi there, I was wondering if there was an ETA for this or if this was even on the horizon? RenderObjects is very convenient! And Rendering Layer’s seems just as powerful. A renderer can be a part of multiple different layers. This means we can have different special effects (Like the mage Occlusion example) use a specific Rendering Layer to ‘select’ renderers to apply the effect to. This way we can have multiple effects similar to the Occlusion example (multiple RenderObjects renderer features)…

Here is the last pull request I know of with any movement on this before it was shelved:

[10.x.x] Adding Rendering Layer Mask to the Render Objects renderer feature

It seemed to have been shelved because the URP team was trying to figure out how to make it work with shadows and such.

I think it would be useful to have even if it didn’t work with lighting systems.

Using RenderObjects for an Occlusion Effect is a common example:

Occlusion

If we were allowed to specify Render Layer’s in the RenderObject’s pass then we could dedicate certain layers to be for certain effects.

For example, in my project RenderingLayer 25 could be for the Occlusion Effect. RenderingLayer 26 could be for Outline effect. RenderingLayer 27 could be for SomeOtherCoolEffect.

Now any MeshRenderer in the game can ‘opt in’ to be a part of any number of my effects! I just have to include it in the appropriate RenderingLayer. This is easy to control at runtime too. IE when the cursor hovers over an object, add RenderLayer 26 to its RenderingLayerMask and boom - outline effect around the item your cursor is hovering over…!

[LukasCh]

Hey,

For 2022.2 we made improvement regarding RenderingLayers (There is really cool new changes Rendering Layers | Universal RP | 14.0.11).
Additionally, we started working on exposing RenderingLayers for renderer and render objects. We also considering backporting it until 2022.2.

[forteller]

@LukasCh

Hey,

For 2022.2 we made improvement regarding RenderingLayers (There is really cool new changes https://docs.unity3d.com/Packages/com.unity.render-pipelines.universal@14.0/manual/features/rendering-layers.html).
Additionally, we started working on exposing RenderingLayers for renderer and render objects. We also considering backporting it until 2022.2.

I don’t notice renderingLayerMask being exposed on RenderObjects in Unity 2022.3.15f1 LTS. Any updates?

I would love not to need to create my own custom render pass via code just to add a filter that using the renderingLayerMask.

[MUGIK]

@forteller

I don’t notice renderingLayerMask being exposed on RenderObjects in Unity 2022.3.15f1 LTS. Any updates?

I would love not to need to create my own custom render pass via code just to add a filter that using the renderingLayerMask.

Were you able to find a solution to this?

Because I don’t even know how to add that renderingLayerMask filter. Also, RenderObjects ignores renderingLayerMask set on source renderer:(

UPD
So, strange behavior.
I wanted to make decals not render on player’s FirstPersonView objects that are drawn in RenderObjects feature.
What ends up working is to set proper renderingLayerMask on renderers and DecalProjectors. And to enable UseRenderingLayers on UniversalRenderPipelineAsset.

Interestingly, you don’t need to enable UserRenderingLayers on Decal feature.

[forteller]

@MUGIK

Were you able to find a solution to this?

Because I don’t even know how to add that renderingLayerMask filter. Also, RenderObjects ignores renderingLayerMask set on source renderer:(

UPD
So, strange behavior.
I wanted to make decals not render on player’s FirstPersonView objects that are drawn in RenderObjects feature.
What ends up working is to set proper renderingLayerMask on renderers and DecalProjectors. And to enable UseRenderingLayers on UniversalRenderPipelineAsset.

Interestingly, you don’t need to enable UserRenderingLayers on Decal feature.

My solution was just to create my own custom render pass instead of using RenderObject’s functionality. Much more boilerplate unfortunately.