Scriptable Render Pipeline Coexistence (experimental)
The following is intended for informational purposes only, and may not be incorporated into any contract. No purchasing decisions should be made based on the following materials. Unity is not committing to deliver any functionality, features or code. The development, timing and release of all products, functionality and features are at the sole discretion of Unity, and are subject to change.
If you have accepted to use functional cookies and logged in using your Unity ID at the top right of the page, then sharing feedback is as simple as clicking a card below, selecting a topic’s importance, adding your point of view, and submitting. If you prefer not to accept functional cookies or log in, you will be prompted to enter an email address and validate it, so we know how to reach out when the topic evolves. For more information read the Feedback and privacy terms.
We have delivered a series of improvements to coexistence in Unity 22LTS and Unity 6, and though it can ease and accelerate porting from one pipeline to another, multiple limitations and unknowns remain. We are for now pausing efforts on this initiative and focusing on Unifying the render pipeline. For more details of what is possible currently, check this forum post:
https://discussions.unity.com/t/the-state-of-srp-coexistence/948251
Summary
Specific projects aim to deliver high-fidelity content on high-end platforms while scaling to all other Unity-supported platforms with the proper visual fidelity and performance level.
It is currently impossible to author URP and HDRP assets in the same Unity project, requiring creators to utilize two separate Unity projects. This workflow is counter-intuitive and has a significant impact on iteration speed.
Scriptable Render Pipeline (SRP) Coexistence enables you to utilize multiple SRPs in a single Unity project side by side.
Intended Outcome/Use Case
With Render Pipeline Coexistence, you can utilize URP and HDRP pipelines in a single Unity project. You can author and maintain different visual assets tailored to each pipeline in a single project and build and run the content for a target platform with a specific rendering pipeline and its associated assets.