LOD popin is bad

[Alienhead]

I've been gone for a weeks worth of updates, this bug wasn't happening a week ago so it started somewhere between last week and yesterdays updates.

Horrible looking LOD pop in on terrain mesh layers.  I guess it's on mesh layers only, could be something else because some of that pop in isnt LOD anyways.

 

 

 

 

 

[Alienhead]

I'm no longer certain its the LOD causing this, all over my map I have weird occurrences like this popping up.

[Alienhead]

Editor mode VS Run mode

 

( editor mode )

( run mode ) 

This is clearly not right, and could be related?

 

[Alienhead]

Upon further investigation it may have something to do with normal maps as the pop seems to only be occuring with mesh mats using a normal map.

[Josh]

That does not look like what we commonly call "LOD popping". It looks more like a problem with the way the compute shader is writing memory...

[klepto2]

just a hint, i get these artifacts only when i use the bloom posteffect. 

[Josh]

@klepto2 thinks this is being caused by NAN values outputted by the shader, which then get amplified in the bloom blur.

[Josh]

@Alienhead You can add this to the very end of the main function in Shaders/PBR/Fragment.glsl:

    //Check for NAN values
    if (isnan(outColor[0].r) || isnan(outColor[0].g) || isnan(outColor[0].b) || isnan(outColor[0].a) )
    {
        outColor[0] = vec4(1,0,1,1);
    }

This will provide a visual cue if the outputted color is a NAN value.

I have tried this on an AMD card but I do not have any scene that produces this problem.

[Josh]

This issue may have been solved by adding checks for NAN in the bloom shader, or other checks. Is this still occuring?

[Alienhead]

I have not seen this bug in many many months now.