Scene view turns white

[sniffle63]

Hello, using HDRP is proving to be quite difficult because of how slow the scene view is to respond and how often it just all together breaks.

I’ll do something simple like hit control z to undo a change on the inspector and my screen will turn white and the only way I have found to fix it is by closing and reopening unity.

Another issue is how turning the scene view lighting on and off or scene view post-processing on or off or changing any value on a shader causes a long recompiling of the shader process where everything in the scene is broken until it’s done. Makes working with it very difficult, reminds me of the '90s

[UnityLighting]

You must set up exposure value properly.
Here you can learn how to set up exposure and HDRP light’s settings easily:

HDRP Basics

Hi I Want to share the basics of the HDRP settings tutorials and tips here The main purpose is the workflow to comes from Built-in pipeline to the HDRP I will update the topic Built-In <=> HDRP HDRP Default Profile HDRP Complete Profile Guide HDRP quick start scene light setup: [HDRP Quick Start Guide For Beginners Unity 2020 LTS] Unity 2021.2 HDRP Realtime GI HDRP Lighting Box LIt 7104130–846985–HDRP_Default_Profile.unitypackage (3.36 KB)

[pierred_unity]

@aliyeredon2

You must set up exposure value properly.
Here you can learn how to set up exposure and HDRP light’s settings easily:
https://discussions.unity.com/t/838833

No, the white screen he’s referring to is related to the “ctrl+z” bug that happened on older versions of HDRP. It only happens once per session.

@sniffle63 , you don’t need to restart the editor actually, you just need to hit this button, as a much faster workaround:

[sniffle63]

@pierred_unity

No, the white screen he’s referring to is related to the “ctrl+z” bug that happened on older versions of HDRP. It only happens once per session.

@sniffle63 , you don’t need to restart the editor actually, you just need to hit this button, as a much faster workaround:

Thank you for the suggested fix but clicking that causes all of the shaders to recompile, which arguably is not faster than reopening unity tbh. (and I’m on a nvme 2.0 drive)

Also, you said it’s on an older version of HDRP but I am on 10.5.1, is this an older version?

[sniffle63]

btw, using control z is not the only thing that causes it. That’s just the latest thing that caused it that made me want to post a post. It has been caused by quite a few things, usually, just during normal workflow it will eventually happen.

And if not this issue then the scene will just be completely unviewable for 90% of the time I’m in the editor because it’s constantly recompiling and I cant see anything and as soon as it’s done (after 1-5 minutes sometimes, if I’m lucky enough for it to complete at all majority of the time it just stops halfway through leaving me with a broken scene) I then need to make another change because im in dev and probably have 100+ changes to make but after each variable change I have to wait for everything to recompile. Its crazy really.

Even an option for making batch changes before the recompile isnt taht useful because I need to be able to dev in realtime instead of feeling like im back in a old model editing program having to render the scene to see my changes.

Hell if I was using baked lights it would make more sense because it would be rebaking the lightmaps, but this feels worse and more time consuming then even waiting on that

[italhaali88]

@pierred_unity

No, the white screen he’s referring to is related to the “ctrl+z” bug that happened on older versions of HDRP. It only happens once per session.

@sniffle63 , you don’t need to restart the editor actually, you just need to hit this button, as a much faster workaround:

This works actually
Thank you