I doubt my terrains will handle a single pass shader. I definitely need more than the SRP.
So I wonder how a higher end machine is defined? What GPUs will be required with HDRP? We do all of our development check on laptops to make sure that a decent laptop with a dedicated card will work.
Just saying higher end machines or lower end machines does not really help me to understand. Right now, we are fine in both my fancy desktop with the rtx 2080ti and the 1070 laptop and the 1050ti laptop.
Are those considered high end? I would really like it to work on slightly lower end machines too.
SRP stands for Scriptable Render Pipeline. Its the feature that is used to build these new graphics pipelines, such as the two Unity are doing, or ones people and companies may choose to make themselves.
The two Unity are doing are the Lightweight Pipeline (LWRP) and the High Definition Render Pipeline (HDRP).
Mostly I’m just saying this because I think you keep saying SRP when you actually mean LWRP, and that could cause much confusion. So please accept my apologies for this terminology lesson.
Technically, HDRP will work with a wide range of PC hardware. But just like the old built in Unity renderer, there is a difference between it working, and it being able to deliver your particular scenes, lighting etc at the framerate you need on a particular gpu & cpu. Just like any renderer, there are various settings which will affect performance, and things you can do that will make your scene either faster or slower on various hardware. Lots of HDRP features can be switched off entirely, or some can be cranked up or down to various extents, there are lots of choices that have performance implications.
For reasons of all the various flexibility in terms of settings, and variations between different peoples projects, its probably hard to give an exact guide as to where the realistic cutoff should with hardware. Take for example the HDRP documentation. When describing what HDRP is, its not that hard for them to state the platform requirements in terms of what features are required for HDRP to work at all. They put it like this:
Since HDRP is still in preview we dont know whether performance improvements may come in some areas one day, although half the point of it is that it takes a modern, flexible and efficient approach towards high end realtime graphics. Sp some things are likely already as fast as they are going to be, but still who knows what the future holds and the system is certainly still evolving at the moment.
Oh yeah I should really have mentioned the big clue there when trying to guess the minimum spec that there is any point trying to use HDRP with…
They have the intention of making HDRP work on higher-end mobile devices that have compute shader support one day. So that should give some sense of how far down the ranks of hardware power they hope it will scale to one day.
Absolutely no reason to apologize. I really appreciate the terminology lesson. Makes total sense and thanks so much. I feel much better about switching to HDRP in the future if necessary.
Thanks so much for taking time to explain this to me. Between you and Peter I understand now.
Appreciate this so much!!! Love this community and it reminds me why I love to to come here so often…not often enough anymore though.
There’s this piece of information from Unite Copenhagen 2019 Roadmap talk, please see the video at 37:26
It’s a bit hard to hear exactly what she says (is that Arisa Scott?). I heard it as “Right now we haven’t named it as legacy, so we’re definitely going to wait for an LTS, we’re definitely have a 19.4 LTS, and we’re continuing to bugfix for the built-in render pipeline. And our goal is to make Universal become a kind of default replacement and so we’re growing its feature set over the next year and we’d love to hear your feedback about what features might be missing for you.”
It would be great if someone at Unity could clarify this a little bit. So, if I understood right, Builtin pipeline will not be named as legacy in 2019.4 LTS, but in one of the next LTS releases (eg 2020 LTS or 2021 LTS?)
Also a very important thing for anyone who is starting with the production of their game is if builtin pipeline is going to be supported for next-gen consoles like PS5? Our previous game started as a mobile game but has gained enough popularity to port it to PC, PS4 and Switch and it actually sold much better on those platforms. So you never know if you’ll need to port your game, even if you don’t plan it right now.
As for "we’d love to hear your feedback about what features might be missing for you". Where should I leave that kind of feedback for Arisa to see? We’re using an asset “Fog Volume 3” by David Miranda (promoted by Unity), and we’re using fog volumes to build parts of some of our levels, so those volumes are the actual building blocks of our gameplay environments at times. I have contacted David but he’s unable to port Fog Volume 3 to new pipelines because it’s impossible without the RenderWithShader functionality which is missing.
So we’re just going forward with builtin and hope for it to be supported on PS5. And hoping is a bit scary at times
Whats exactly is involved in converting a scene into SRP, I know it involves redo lighting. How much can be scripted for existing scenes and so forth? (I had a scene that was configured wrong for indirect light, I corrected the light settings and then I scripted most of the reconfiguration of lights in the scene, could something similar be done for migrating from builtin) Sadly we have some assets that use amplify shaders, substance materials, are these easy to convert, etc.
For us quality of builtin is good enough, we would move because of getting better performance, the improved batching etc and to be able to upgrade Unity once builtin is deprecated. Also I hope SRP means we at some point can move away from baked lighting, because its a pain.
I fully expect the builtin pipeline to be supported at the beginning of the life of the console, since the release date of the next console is within the current roadmap of Unity, but keep in mind the lifespan of the console is typically around eight years. I fully expect the builtin pipeline to disappear before the console reaches its end of life.
Our team is currently working with HDRP, and while I’m not the developer responsible for bringing scenes into the new pipeline, to me it appears to be primarily a case of reworking the lighting, any custom shaders, and the post process.
It’s usual for a game to be 3-4 years in production, LTS lasts 2 years so that’s where the problem could arise for people who are currently in production. The new pipelines don’t seem to be that ready and builtin doesn’t have a clear future outlined so it’s very hard to make a choice now.
As for eight years, I don’t think that would be a problem though, because the new pipelines will surely be ready and feature-rich in two years, so anyone starting their production at that time will have an easy choice.
I feel that builtin deprecation should start only when the new pipelines are truly production ready, not only for big studios with vast resources and lots of programmers but for indies as well, and supported with plenty of features in the asset store. They should let them grow to match the builtin support.
Anyway, even if builtin makes it to 2020 LTS, Unity devs can easily decide not to support builtin for next gen consoles. That’s why some clarity about the future of builtin would be really welcome.
I really appreciate the terminology lesson. Makes total sense and thanks so much. I feel much better about switching to HDRP in the future if necessary. 