[Solved] [HDRP] Random black flickering | 2018.2.1

Hey there,

I sincerely hope, this has not been posted yet, but at least I was unable to find anything similiar.
We are currently working with HDRP and everything went fine so far. Expected behaviour.
There is just 1 strange issue we are facing.

Sometimes the screen (or some materials) flicker black. Randomly. Just a millisec. Not view angle dependent. We also deactivated all PostFX. No changes. Tried different shaders. No changes.

Does anyone have any clue, where this is coming from?

Any help is greatly appreciated.

 

try to off some features from HDRenderPipeline settings at Light Loop Settings

 

Hey peter,

thanks for your hint. Could you also tell me where to find those settings?
Seems like I am unable to locate them. Nothing in SRP Debug window at least.

Thanks again!

---

Oh nevermind. I found it Going to investigate on this

 

Well nothing. All enabled, All disabled. No difference

 

Tried to off all features available. No difference.
But it has to do something with the lights. If I disable Lightin in SceneView everything's fine.

 

Well it's strange sometimes... Just opened this thread after 2 days of searching and 30minutes later got the solution.

Disabling the contact shadows of our Main Directional Light helped

 

Yeah it's all WIP so you'll get this sort of problem...

 

Unfortunately I have the same problem and this didn't fix the problem Anyone who knows the solution?

 

i've got the same problem... flickering randomly even in the scene. annoying.

 

Also have this problem HDRP Unity 2019.30f3. Scene flickers to total black seemingly randomly

 

I've had this problem. For me it was one specific model that caused the flickering after a Unity and HDRP upgrade. No guarantees it will solve it for you, It but it might be worth checking by disabling objects to see if you can identify which object could be causing this. When I found the object that caused it for me, reimporting the model was enough to fix it.

 

Its still exists in 2019.3.0f6 with HDRP 7.1.8. I got black frames.

 

I was getting lots of black frames and found out some causes.

- Cause 1: objects with scale 0. If an object has any of its scales set to 0, it's quite probable that the screen will flicker in black when it is being rendered.

- Cause 2: certain normal maps. Some normal maps that I downloaded from the internets where causing this flicker. Quite interestingly, it also depended on the scale! The same model, at scale 1, had no errors. For reasons, I use the model at scale 0.064, which caused tremendous flickering.

- Cause 3: certain normal maps + distortion. At scale 1, this does not cause flickers, but black squares, being it angle dependent. At scale 0.064, the flicker covers the whole screen.

We've solved each case differently:

- Cause 1: avoid objects getting scale 0.
- Cause 2: using a different normal map.
- Cause 3: not using distortion - for now.

Hope it helps.

 

We have problems with flashing black polygons when they are duplicate. We check the geometry for duplicate polygons (especially CAD data (especially CATIA)).

 

Why this thread mark as solved? It not solved at all! In my case black squares or flickering caused by planar reflection. No workaround, only disable it.

 

Just noticed the same problem. I have a Radeon Pro Vega on a bootcamped Mac. What card do you have? Maybe its a driver issue...

 

iSpiegelball I hardly doubt it. I have gtx-1650 and Windows 7

 

this bug is still exists in 2019.3.4f1 with hdrp on all hardware

 

I solved the problem for myself by disabling the static batching that was enabled on some objects.

 

I can confirm this as well. I have to say that this is really annoying.

 

Yep, I've encountered this after porting my (semi-large) project to the HDRP from the built-in renderer.
(Unity 2019.3.7f1 / HDRP 7.1.3)

Tried disabling lighting settings in the HDRP pipeline asset, w/o any luck. As well as shadows / contact shadows.
And objects with distortion applied to them.

I guess its object related, alas, I can't pinpoint which one it is yet.

If anyone else have suggestions how to find out what's causing these artifacts, please share them.

Edit: Found some normal maps that are causing this issue. Not sure how to replace them though. Or how to even debug what's wrong with them.

 

So, it seems like in HDRP Lit does normalize the input normal map without suppressing potential NaN's.
(Judging by this shadergraph post, https://forum.unity.com/threads/mod...fter-adding-a-normal-map.822486/#post-5450790 which probably means default shaders do the same)

Question is, how to find and test existing normal maps against zero / NaNs?
Unpacking normals in C# in my attempts just result in -inf, -inf results (e.g. DXT5).
But most likely I'm doing it wrong.

Stop NaNs are enabled in the pipeline asset settings, but I think those are for post processing only.

 

That's nice to know. Thanks.

However, how do I fix normal map caused NaN's?
I'm 100% sure that it is caused by one. Because removing it also removes the flickering.
And the Stop NaN's in this case does nothing.

Do I need to rebake / modify it somehow?

Any suggestions would be great, because I'm not artist and I don't have the sources either.

I was thinking about it, but it seems like its just plain easier to just suppress it via custom shader.
Because there's like a ton of art that probably have 0,0,0 normals out there.

 

Seb, mine flickers like crazy whenever I select something with a mesh renderer (the scene view). I've tried the debug view for NaN, but I don't observe any red dots. Also, if i select anything that has lightmaps, the meshrender's lightmap section opens and closes indefinitely, and the scene view flickers like crazy.

Any idea on the underlying issue?

 

Edit: Okay, the issue that somehow imported normals on the model get messed up.
Setting Normals to Calculate and Tangents -> Calculate Mikktspace instead of Import solves the issue.

Edit 2: Most of those models are generated with RealtimeCSG, setting every one of them to Calculate instead of Import solved my flickering issue. I've made an issue for that on the RealtimeCSG github.

Tried making today a shader that replaces zero vector normals with 0.001;
And it didn't worked either. It seems like there's an internal issue after normals being assigned to the surface data.

Here's normal map example:
[Redacted]

That also got me thinking whether it can be caused by the model itself somehow;

There's also a different case of the flickering, but it doesn't show up in the NanTracker debug as red pixels.
Need to investigate those as well. It could be light max count reaching, but I'm not sure about that.

 

Hello Guys! I'll leave this comment here since I had the same problem and I found another "solution".

For me, the problem was that I had a tree that I had exported from SpeedTree. I followed all the instructions to import a tree from SpeedTree to Unity HDRP, that I found on the SpeedTree documentation page, but whenever I placed the tree in my scene I had this weird flickering.

After reading your comments I realized it was my post-processing that was making the flickering, more specifically the Bloom, so I turned it off and the problem was solved, it is a little shame to not have a little bloom but it's better than to have a flickering scene. I hope this helps someone is a similar situation in the future!

 

I solved this by unchecking Post Processing Profile -> Screen Space Reflections.

The problem came specifically in Basic Unity 3D Project not in HDRP. This caused the flickering of shadows with Direction Light and Post Processing Effects when the mouse was moved in the editor or the camera rotated in the runtime.

 

So for me it seems like it disappears when i switch off my Bloom. However, I'm curious to know if there is a way around this without switching off Bloom?

Also I should add that this only occurs when using a specific material created in shader graph. On that shader if I turned down the normals strength all the way to zero - the flickering also disappears

 

In my case with HDRP 10.2.0, the flashes were caused by the Temporal Accumulation setting of the Ambient Occlusion being disabled, after switching it back on (or after disabling the Ambient Occlusion all together) there's no more flickering of the lights in the scene view.

To be precise, my flashing problem was happening when selecting a gameobject with a mesh renderer or a material and moving the cursor over the fields in the inspector.

 

Normally, NaN and bloom usually causes this weird problem, but the other causes of the black flickering problem, mentioned by the others were really interesting to read.

 

For me, it was indeed materials made in Amplify Shader. All I had to do is have NaN off and it fixed it for me. I have no idea how to fix the actual issue myself...

 

Get this ugly flickering on 2019.4.10. Was caused by one of ProBuilder meshes after edge dividing and face extruding.

 

Glad to hear that solved it.

Interesting.

 

F***ing NaNs.

 

Actually I found out later by accident that the "normal map intensity" in the amplify shader causes those NaNs. I forget about it them someone reminds me years later. It looks like it's safer to have a value of "1" in HDRP normal maps intensity. Even today there are probably still asset store publishers that have this issue in their asset packs and they don't know it.

 

guys, I found how to solve it, I saw that my unityhub account was auto log out, so when I login back, click some update in the hub, woala, it's fixed ^^

 

Problem: objects appear to flash black when moving in the game view only.
This occurred only in the "game" window but not in the editor window. (runtime and editing) While using unity 2022.1.12f1. HDRP outdoors.

Problem was caused when deleting a Decal Object that caused the renderer to default to the Deferred renderer in the pipeline settings.

Took some fiddling around before realizing what had occurred.
Seems like there's a few things the user can do to trigger this, not just deleting a decal prefab.

To be clear, the solution for my issue in HDRP 2022.1.12f1 was fixed by toggling the renderer from Deferred to Forward then playing the scene.

an error message for when the renderer changes like this would be great.