Resolved SRP Adoption Rate

Hey! To give you a high-level idea, with 21LTS, around 30% of projects are already utilizing and building on SRPs. And this number has been increasing in each version we release as we improve the SRPs further with new features and better workflows and documentation. The growth is also organic, and Built-in is still our entry point 2D/3D pipeline in the hub. So these projects are opting in to use SRPs. If you are wondering about the successes of customer projects using URP and HDRP, here are some examples of amazing ones:

URP: Lost In Random, Circuit Super Stars, Neon White, The Spirit And The Mouse, HEROish, Wild Arena Survivors, Crash Bandicoot: On the Run!
HDRP: V Rising, Construction Simulator, Slime Rancher 2, Hardspace Shipbreaker, Disciples Revolution, I am Fish, Syberia The World Before, Metal: Hellsinger
URP & HDRP: Lego Builder’s Journey, Road 96
Full Custom SRP: Human Kind, OlliOlli World, Rollerdrome, Ori: Will of the Wisps

And there are many more, and I am only sharing titles where the information about SRP usage is publicly available.

Now to answer the other part about URP vs. HDRP. The more significant share of these projects is URP, but there are reasons for that. URP's goal has been to provide functional parity with Built-in; it's more familiar to adopt and learn for Built-in users. URP also scales to all platform Unity supports, but URP lacks the cutting-edge fidelity HDRP provides on PC and consoles. And it will stay that way as URP's focus is different. We will address this shortcoming and reduce the cost for cross-platform games that would want the fidelity of HDRP on high-end and optimal quality and performance of URP on other platforms, including mobile, through coexistence and improving the compatibility between the two pipelines. This means that users no longer have to sacrifice quality on high-end for platform reach, which will balance URP vs. HDRP adoption as well. The end goal is really about SRPs vs Built-in really .
(You can read more about our vision and plans in our recent post here).

 

We have an adoption rate target as a measuring tool and more of a guideline. But this is a guideline, and we have other factors we track in practice, such as customer and asset store feedback, to ensure we are not leaving them behind and not lacking the things they need for their use cases. For URP, performance against built-in is also crucial, so we have goals for that. We also look at bug reports and stability. We believe we will hit our targets in 23, but I don't want to promise anything here as we will have to hit our targets first. In the blog post, we mentioned we would not deprecate Built-in in 23 versions to ensure ample time for people to make the move.

 

Building on Ali's comments. First we'll make SRP the default and before we do that we have clear functionality, performance, documentation and robustness targets. Once it is default we'll see a huge increase in adoption automatically. We'll then need to track the adoption and user satisfaction and take the full ecosystem into account before we can deprecate.