Known issues in URP

This page contains information on known issues you may encounter when using URP.

Long build times when using the Forward+ Rendering Path

Due to the wide variety of use cases, target platforms, renderers, and features used in projects, certain URP configurations can result in a large number of shaderA program that runs on the GPU. More info
See in Glossary variants. That can lead to long compilation times.

Long shader compilation time affects both player build time and the time for a sceneA Scene contains the environments and menus of your game. Think of each unique Scene file as a unique level. In each Scene, you place your environments, obstacles, and decorations, essentially designing and building your game in pieces. More info
See in Glossary to render in the Editor.

The per-camera visible light limit value affects the compilation time for each Lit and Complex Lit shader variant. In the Forward+ Rendering PathThe technique that a render pipeline uses to render graphics. Choosing a different rendering path affects how lighting and shading are calculated. Some rendering paths are more suited to different platforms and hardware than others. More info
See in Glossary, on desktop platforms, that limit is 256.

Refer to the following page to learn how to reduce the build time in the Forward+ Rendering Path by reducing the maximum number of visible lights:

• Reduce build time in Forward+ Rendering Path

When importing the URP package samples, Unity does not set the necessary URP asset in Quality > Render Pipeline Asset

When importing the URP package samples, Unity does not set the necessary URP asset in Quality > Render Pipeline Asset, and certain sample rendering effects do not work.

To fix this issue:

In Project Settings > Quality > Render Pipeline Asset, select SamplesPipelineAsset.

Renaming a URP Renderer asset to a name matching one of the Renderer Feature names causes erroneous behavior

If a URP Renderer asset has any Renderer Features assigned, renaming the Renderer asset to a name matching one of the Renderer Feature names causes erroneous behavior: the URP Renderer and the Renderer Feature switch places.

The following scenario shows how the error occurs:

• Let’s assume that the URP Renderer in your project is called UniversalRenderer.

• The Renderer has a Renderer Feature called NewRenderObjects assigned.

  

• Renaming UniversalRenderer to NewRenderObjects causes erroneous behavior:
  The Renderer switches places with the Renderer Feature and does not behave correctly.

To avoid the issue, do not give the URP Renderer asset the same name as the Renderer Feature asset.

To find updates on this issue, refer to the Unity Issue Tracker.

Warning about _AdditionalLights property when upgrading the URP package

In certain cases, you might receive the following warning when upgrading the URP package to a newer version:

Property (_AdditionalLights<...>) exceeds previous array size (256 vs 16). Cap to previous size.

This warning does not cause issues with the project, the warning disappears if you restart the Editor.