HDRP 5.7.2 to HDRP 6.9.2 (Unity Upgrade)

Hi there,

I require to upgrade our large project

I have been prolonging this upgrade for a long time because of this issue, as i did testing last year in september.

My findings can also be found on this thread : Upgraded Project from 2019.1.0f2 to 2019.2.3f1 - Performance/FPS Drop by 30-50FPS

i have a major performance drop when upgrading my project from 2019.1.14f to 2019.2.10f1, and i belive it is due to the fact that once you go to 2019.2.1 the HDRP package must be upgraded, which unity automaticly does from 5.7.2 → 6.9.0 when upgrading the projects unity versions from 2019.1.14 to 2019.2.10

This is a major frame drop in performance and ive been trying to find where its comming from.

None of the assets have changed, nor textures, shaders, or anything else.

Only the unity version and hdrp packages.

i notice a 20FPS drop in unity editor, which translates to a 40-50 FPS drop in a stand alone, and this makes our project unplayable.

I have tried going through the HDRP debugging windows, disabling shadows and different rendering settings one at a time to see the impact, to no success.

My next move is to completely re-create the HDRP pipleline script resource in hopes that it will have some effect

Does any one have any suggestions…

My last thread from September went without a reply, and i really wish a unity dev/rep would chime in

Thanks in advance

here are some comparison screen shots,

Has any one had these issues before?


I have no insights into the SRPs but 2019.2 is no longer supported so there is a chance that this is a bug that would never get fixed.

I’d make a backup of the project and just jump ahead to 2019.4 just to see if the issue persists there.

Also, the chances of the right people seeing this post increase if you place it in the Graphics/HDRP subforum and or tag it with hdrp
Edit: added the tag for you.

That said, it does look a bit weird that the drop seems to come entirely from RenderPipelineManager.DoRenderingLoop_Internal suddenly getting a self time of 33ms. I’d maybe check how that looks like in timeline view and if this couldn’t be down to VSync or something. Also, profiler screenshots from this occurring on a device and with the Scripting category not toggled of in the CPU Usage chart might provide further info. :slight_smile:

THANK YOU. i will run the test after work with the mentioned profiler settings and provide screenshots for both @)!(>@> and @)!(>$

1 Like