The Universal Render PipelineA series of operations that take the contents of a Scene, and displays them on a screen. Unity lets you choose from pre-built render pipelines, or write your own. More info
See in Glossary (URP) replaces the Lightweight Render Pipeline (LWRP) in Unity 2019.3. If your Project uses LWRP, you must upgrade it to use URP to use Unity 2019.3.
Unity upgrades some things automatically, and you must make some manual changes. Follow the steps in this guide to transition from using LWRP to using URP.
URP uses GUIDs instead of Assembly Definition string names. If you are using Assembly Definition Assets (ASMDefs) in your Project, you should ensure that Use GUIDs is enabled on each of them.
Unity upgrades any existing string references to LWRP automatically as part of the upgrade process, but it is best practice to use GUIDs on your Assembly Definition Assets for future proofing.
For each Assembly Definition Asset in your Project:
For information on using Assembly Definition files, refer to the documentation on Assembly Definitions.
To start the upgrade process:
Unity automatically updates LWRP to a 7.x.x version, and pulls in the URP package as a dependency of the updated LWRP package. The Unity script updater automatically upgrades your script files. When the script updater has finished, all of your scriptsA piece of code that allows you to create your own Components, trigger game events, modify Component properties over time and respond to user input in any way you like. More info
See in Glossary should compile properly.
If your LWRP Project uses Shader.Find
to search for LWRP ShadersA program that runs on the GPU. More info
See in Glossary, you need to change the search path.
To do this:
Shader.Find
that search for Lightweight
to search for Universal
.URP uses its own scripting tags. If your Shaders use the LWRP LightMode
tags, they will work in your URP Project, because Unity uses an internal alias for this. However, you should change the tags manually to future-proof your Project.
To do this:
Lightweight2D
tag to Universal2D
.LightweightForward
tag to UniversalForward
.In addition to this, URP also uses a different RenderPipeline tag to LWRP. If your own Shaders include this tag, you need to change it manually for the Shaders to work:
LightweightPipeline
tag to UniversalPipeline
.The following Shader names have been changed for URP, so you need to manually update your Shader files:
UsePass 'Lightweight Render Pipeline/...'
to UsePass 'Universal Render Pipeline/...'
URP uses different include paths to LWRP. LWRP 7.x.x contains forwarding includes, so your custom Shaders will upgrade from LWRP to URP. However, URP 7.x.x does not contain forwarding includes, so you must then manually update the include paths.
#include 'Packages/com.unity.render-pipelines.lightweight/xxx'
to #include 'Packages/com.unity.render-pipelines.universal/xxx'
In the .cs files in your Project, find and replace references to the LWRP namespace with the new Universal namespace.
UnityEditor.Rendering.LWRP.xxx
to now UnityEditor.Rendering.Universal.xxx
URP version 7.x supports both Post Processing Stack v2 (PPv2) and its own integrated post-processing solution. If you have the Post Processing Version 2 package installed in your Project and you want to use URP’s integrated post-processingA process that improves product visuals by applying filters and effects before the image appears on screen. You can use post-processing effects to simulate physical camera and film properties, for example Bloom and Depth of Field. More info post processing, postprocessing, postprocess
See in Glossary solution, you need to delete the Post Processing Stack v2 package before you install URP into your Project. When you have installed URP, you can then recreate your post-processing effects.
Upgrading post-processing effects from LWRP to URP is a manual process. You must manually recreate each Post-Processing Profile in your Project, using URP’s post-processing implementation.
URP’s integrated post-processing solution does not currently support custom post-processing effects. If your Project uses custom post-processing effects, these cannot currently be recreated in URP’s integrated post-processing solution. Custom post-processing effects will be supported in a forthcoming release of URP.
As part of the automatic upgrade process, Unity installed URP as a dependency of LWRP. You must now install URP as a dependency of the Project itself, so that when you remove LWRP, Unity does not automatically remove URP.
To install URP as a dependency of the Project:
<project>/Packages
directory. The Package Manager uses it to configure many things, including a list of dependencies for that project, as well as any package repository to query for packages. More info"com.unity.render-pipelines.universal": "[Version number you noted earlier]"
So, for example, if the version of URP was 7.1.1, your dependencies section would look like this:
"dependencies": {
"com.unity.render-pipelines.universal": "7.1.1",
...
}
This marks the version of URP that you have installed as a dependency of the Project. You can now safely remove LWRP.