What is the purpose of this setting?

[Ewanuk]

The documentation here does not cover it:

[ManueleB]

Hey!
This feature was recently added and should be available in the 21.2 release, the documentation has been added in this PR:

Updated the universal renderer asset documentation

From the PR:

Indicates whether to use URP’s Native RenderPass API. When enabled, URP uses this API to structure render passes. As a result, you can use programmable blending in custom URP shaders. For more information about the RenderPass API, see ScriptableRenderContext.BeginRenderPass.Note: Enabling this property has no effect on OpenGL ES.

What this does is making every ScriptableRenderPass use, under the hood, the Unity RenderPass API, which allows to explicitly declare RenderPasses, SubPasses, Input Attachments for framebuffer fetch etc. (which map 1:1 to Vulkan Render Passes and Metal Encoders). This feature will only affect TBDR GPUs (mobile) when targeting Metal and Vulkan, and is currently experimental. It is already functional but not enabled by default since it is still work in progress

For more implementation details you can check NativeRenderPass.cs

Expect more information and documentation to be available in the near future

[Nexusmaster]

Hi, just had the bug where our Renderer Feature doesn’t work in Build (only Editor), if we use Native RenderPass, do you know why this might happen? When I turn it off the RendererFeature also works in Build.
(Unity 2021.2.16f1 , URP 12.1.6 , Windows11 64bit)

[eizenhorn]

@Nexusmaster

Hi, just had the bug where our Renderer Feature doesn’t work in Build (only Editor), if we use Native RenderPass, do you know why this might happen? When I turn it off the RendererFeature also works in Build.
(Unity 2021.2.16f1 , URP 12.1.6 , Windows11 64bit)

When you enable that it starts to using framebuffer fetch which you can use in your shaders (which is supported only on gles,gles3,metal)
https://docs.unity3d.com/Manual/SL-PlatformDifferences.html#using-shader-framebuffer-fetch
https://docs.unity3d.com/Packages/com.unity.render-pipelines.universal@15.0/manual/urp-universal-renderer.html#native-renderpass

[Jonas_Sid]

@Nexusmaster - custom Renderer Features sadly are not supported by Native Render Passes. The way current URP works we have no way of enforcing strict dependencies (inputs/outputs) of the passes without breaking the API so we ultimately decided to disable it automatically on renderer features until we are able to have that.

[JesOb]

@Jonas_Sid

@Nexusmaster - custom Renderer Features sadly are not supported by Native Render Passes. The way current URP works we have no way of enforcing strict dependencies (inputs/outputs) of the passes without breaking the API so we ultimately decided to disable it automatically on renderer features until we are able to have that.

Do Unity 2023 URP Render Graph will fix this?

[Nexusmaster]

@Jonas_Sid

@Nexusmaster - custom Renderer Features sadly are not supported by Native Render Passes. The way current URP works we have no way of enforcing strict dependencies (inputs/outputs) of the passes without breaking the API so we ultimately decided to disable it automatically on renderer features until we are able to have that.

Thanks for the info!

[Jonas_Sid]

@JesOb

Do Unity 2023 URP Render Graph will fix this?

Sorry for the late reply!

Yes, it should fix this. As RenderGraph will know the dependencies, it will be able to make the decision to merge it into subpass and so on.

[AljoshaD]

@JesOb

Do Unity 2023 URP Render Graph will fix this?

Yes, this is now handled automatically in Unity 6 (from 23.3.beta) with RenderGraph. You can find more info on how to set this up [here]( https://discussions.unity.com/t/930355 page-7#post-9787632).