Official SRP v11 beta is available now

Just a quick question

When you say mention "graphics packages are relocating to the core of unity" Does this mean we no longer install URP/HDRP as a package after creating a new project?

 

Not sure I understand what you mean. It will be working as package like before but will be installed by default or it will be available through other menus? I mean if i started with template where should look to find source code for the pipeline.

I also have few questions about cross srp workflow because we are planning to deploy urp for mobile and hdrp for console/PC from one unity project. Does it change somehow the process of switching between SRP? Like working with lights, volume and etc?

Will be standard URP and HDRP standardized so when i switch between pipelines i do not need convert materials if i use standard shaders?

Can you also help me and answer a question about shadergraph cross pipeline shader compilation (shadergraph that works for all pipelines simultaneously)? As I know it should work but it actually breaks srp batcher so it can’t be used.

 

Is it possible to upgrade 2020.2 SRP project into 2021.1 ? Do I need to delete SRP packages in folder when opening it in 2021.1 ?

 

Is it a module that I can turn off during Editor installation, or only during project creation? Because I would never want to download HDRP with each new release. (especially since my laptop doesn't support it at more than 10 fps)

Unity Core is getting so much bigger with each tech release that for me it takes more than an hour to download and install a new version.. I'd rather download as lightweight as possible Unity Editor, and only then download all the packages I need via Package Manager.

Just looking back at previous releases:
Unity 2018.4 - 3.0 GB.
Unity 2019.4 - 6.4 GB..
Unity 2020.1 - 7.0 GB...
Unity 2020.2 - 8.7 GB....
Windows IL2CPP module enabled*

BUT, Unity 2021.1.0b5 is 4.2 GB! Is this only because of the beta?
Will this size increase even further after relocating Graphics to the core?

 

ali_mohebali
How about SRP-api updates?

 

Additional question, can this data re-structure happen or backport in 2020.2 to have less size?

 

I would like the unit to implement the incremental updates, which would just fix the bugs, and there would be no need to download the entire editor again.
It would be much better to download updates from 30mb to 100mb, than 8GB every week due to the hotfix.

 

@ali_mohebali is there any way to identify SRP versions from Graphics github repo now that the SRPs are distributed through Unity core?

PM now just reports every 11.x as 11.0 which isn't helpful at all. Github repo doesn't have any tags for any 11.x versions so I can't sync the github changes to specific editor version anymore. I did peek into library/packagecache and shipped package didn't really give me any more info, in fact changelog was dated to last year, suggesting it wasn't even updated anymore.

This is an issue now as I frankly don't know what I'm using now, what fixes are in and what are not.

 

Not only survey but overall API state. It feels like API development was abandoned half way through. Last API update was in 2019.4.11, last major update is somewhere around 2019.1

 

In HDRP 11.0, VFX graphs prefabs take 3 additional seconds to intilize when entering Play mode.
Play mode does App reload, scene is loaded and then VFX are delayed by 3 seconds. Is this known? Could you reduce that initialization?

 

One thing I did notice was that even 2021.2.0a5 and HDRP 12 still have an option and a button to check if you are on the latest HDRP version (at the top of HDRP Wizard dialog).

Since HDRP is now shipped along with Unity core, having a check for this feels frankly quite pointless.

 

As long as one can find specific HDRP releases (per Unity engine / core version) on github, it would be fine. Tags would be ideal

 

Yeah, "new features, features, features". How about usability for URP / HDRP users, and SRP-api users(your teams is api users too)? Moreover, i don't think that URP/HDRP guys are satisfied with SRP-api too, but they just find kluges and workarounds for lack of features.

Shader/materia setup: No Replacement Shader(overrideMaterial is not near a analogue)
No multi pass
Broken shader fallback
No MaterialPropertyBlock analogue

RenderTarget API: Half of api work with RenderTargetIdentifier, half with RenderTexture, and mixing different api-calls can be very hard or not even possible

CameraAdditionalData/LightAdditionalData was a nice workaround for its time, but now it's definitely time to make custom properties for standard components. And maybe not only properties, but methods as well(i.e. to setup custom per renderer data like a standard lightprobes)

 

I've been waiting for something like the Camera Sorting Layers Texture to help upgrade my 2D game to Universal Render Pipeline from Built-In. My trouble has been that the art style is heavily dependent on grab passes, for various smoke particles and overlay effects. It's great that I can use the CSL Texture so I won't have to render all of these effects on top of everything, but I was wondering if there is any way this could be expanded to cover something like a list of CSL Textures at different depths? That would really help with the process of upgrading our game without having to rearrange hundreds of scenes. I appreciate that batching these blit passes is a huge boon for performance and that we'll want to do some of that work either way, but just having the option to run several of these on top of each other would be so much more artist-friendly.

Ideally you would also be able to turn these blit passes on or off at runtime somehow? At present it looks like we are grabbing the screen regardless if anything on-screen (or even in-scene) needs it or not, but I might be mistaken.

 

How about FIXING your motion Vector Output in HDRP, as of 2020.2. nothing! This is such a basic requirement and we cannot understant how you can release a product by completely disregarding such a simple but VERY important feature, why do you guys do this? they were working fine in version up to 2020.1 and nothing in 2020.2

 

Thanks for your reply! really appreciate it and we figured out why motion vectors were not working. Due to lack of updated documentation It took us more than two weeks to solve 'well' find a workaround for this issue and now they are working perfectly and we can finaly submit the latest upgrade for CTAA which will work in all version of Unity upto the latest one.

As of HDRP 10.2 Unity introduced the experimental Render Graph system and it is ON by default in any Unity version using 10.2 and above. When it is enabled, motion vector Data is un-accessable via the standard Postprocessing pipeline method. We first seen it on in the render debug viewer (it is on by default and when it is unchecked the next time pressing play it defaults back to enabled! ) and we didn't realise there is an option to turn it off in the HDRP default settings right at the top! as soon as we disable it, bang, motion vectors working again. This setting is not available in Unity version prior to 10.2 in the Default HDRP settings.

 

I have a few questions about SRP batcher.
1. Why do meta passes break SRP batching? They don't really matter for runtime as much as I'm aware of. Makes supporting srp batcher much harder than it should be.

2. Will there be a simpler way to support custom light probes?

3. Why is UI batching not supported? When?

 

So checking out both 11 and 12 I noticed that a lot of bug fixes don't seem to make it back to previous versions. Is this just a matter of time before they are backported, or do we need to be following the latest to get bug fixes?

 

Haven't tested it outside of editor actually. At the very least if they don't affect the srp batcher at runtime, this is not reflected in the inspector. Shaders are shown as incompatible with SRP batcher and are not batched with it in play mode if the meta pass is not compatible with SRP batcher.