SRP 9.x.x - and SRP 10.x.x Important information

Unity Engine
, ,
1

Hi,

It appear to us that we haven’t communicate about the new “-preview” package that we have done.

Here is a sum up of binary version and HDRP package compatibiltiy

Unity 2019…2 - HDRP 6.x.x family
Unity 2019…3 - HDRP 7.x.x family
Unity 2020…1 - HDRP 8.x.x family / HDRP 9.x.x-preview family
Unity 2020…2 - HDRP 10.x.x family

The Package 8.x.x are similar to 7.x.x (Same bug fixes, few minor features in addition).

The package from the 9.x.x-preview will not be supported packages. It have several features that are available in 10.x.x but will not be supported and is provided as a way for users to experiment with future features. When we release those 9.x.x-preview package we perform a very minimal QA.

Our recommendation is of course to not use a preview package for a production. 9.x.x-preview is not mean to be used in production.

About the reason why we have done a 9.x.x-preview package:
SRP team wasn’t able to catch up with the 2020.1 cycle release after the very long 2019.3 release cycle that the whole team have focus on. It have been decided to move the effort to have a proper 2020.2 release cycle. But we are still providing a way to experiment earlier with new features via the 9.x.x-preview package.

8 Likes
2

It would also be very helpful if DOTS preview packages that rely on a specific branch/version keep their changelogs updated with that information. The best I have seen is they do an initial release and say use X, but when the dependencies change never a mention. Really doesn’t take that long to put it in the changelog and most of us that are using preview stuff watch changelogs.

1 Like
3

Perhaps sticky this thread?

4

Is 10.x available now as a package in 2020.2, or we still have to do the workarounds to get it going from github? - which is still a bit confusing to me on how to get things going from there by the way

5

Not yet in the package manager.

6

Some question and request

  • There was in old github repo a commit for 40-60% less draw calls and improved performance in HDRP. Is it possible to backport this to 7.x in LTS?
  • For 2020 LTS please add Switch support and HDRP. Doesn’t have it currently.
7

Wait what? Can you elaborate?

8

https://github.com/Unity-Technologies/Graphics/pull/2

9

Hi,

  1. This doesn’t reduce the number of drawcall, just help with C# lightloop iteration. No backport plan, we only backport critical bugfix to 7.x.x

  2. HDRP Switch support is not plan currently.

10

Can we please get a step by step for dummies, on how to load HDRP 10.x into our 2020.2 projects.

I got as far as isolating all the 10 builds in Github with the 10 tag, but then no idea how to get it into UNity. I got halfway, but then apparently Iwas supposet to also download all the othe components also.

So yes please, a step by step for non programming dummies would be great!

11

No takers to explain this then?

12

Might be partly because this is one of those moments where current master branch on github requires a version of the Unity editor that isnt available to us yet - currently its set to require alpha 20.

When a modern branch is actually working with a Unity version we can get, I use a very lazy method for using it on a per-project basis.

I make sure there is no HDRP etc already in my package manifest for the project. I download an entire branch from github. And then I simply copy the folders for pipeline core, HDRP, HDRP config, shadergraph, and in my case also visual effect graph, into the Packages folder that existing within my project folder . This may be quite different to the approved way of installing packages locally to a project, but it has continued to work for me for a number of years now.

1 Like
13

Thanks for the info.
How can I see from the branch, which version is required, I know you said 20 in this case, but where do I see that?

Also, any idea whats the rough ETA of 2020.2 moving to Beta?

14

I look at the package.json file inside the root of each packages main folder. So in this case for master branch:

https://github.com/Unity-Technologies/Graphics/blob/master/com.unity.render-pipelines.high-definition/package.json

This bit:

I havent been keeping up with any chatter about release schedules so cannot offer info about that.

1 Like
15

Question: v7.5 is verified but is not available in PacM. Why?

16

@valarus Something version tagged doesn’t mean it’ll even make it to package manager. There could be several reasons why but in the nutshell, it needs to pass QA, could have documentation issues etc. It’s not uncommon that some SRP versions never make it past github but even if they do, they don’t usually show up same time on PM and git releases.

17

But @elbows which branch though, the entire graphics branch or only HDRP branch?

18

I usually go for the master branch. And yes the entire graphics project since the HDRP folder is not enough, you will also need to use core, shadergraph etc from the same branch.

1 Like
19

Hi,

I work all projects in Unity 2019.4.5f1, with latest HDRP for that version, will i still be able to use those projects in 2020 versions and their HDRP, or changes are radical ?

I want to get a feeling whether i should remain in 2019.4.5 or make the move to stop support for it and use 2020 only for HDRP.

i know for example that much older HDRP or DOTS projects are completely broken now and nothing works out of the box, is it for example anything similar between the 2019 and 2020 HDRP versions or is now a more concrete and stable foundation, so working in 2019.4.5 means will just play in 2020 and latest HDRPs ?

Thanks

20

Hi, HDRP have been out of preview in late 19.3. So starting from here, we guarantee data migration created with base HDRP. So if you use a non modified version of HDRP, it is safe to move to 2020.0.

If you have fork/change HDRP or use asset store plugin, then it may require some adaptation based on the following guidelines:

1 Like