Page MenuHome

LookDev with environment texture starts washed out, until viewport moves
Closed, ResolvedPublic

Description

Operating system: Kubuntu 18.10, 4.18.0-20-generic #21-Ubuntu SMP Mon May 6 18:45:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Graphics card: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
Broken: 2.80, 9efe117535c6 Dec 2019-05-20 16:16

When an environment texture is used, LookDev often starts with the environment texture apparently "whitened"; it's as if all pixel values are bumped up a bit. This disappears when the viewport is rotated.

  • remove profile directory, start blender
  • go to "world" tab, click the small circle button next to "Color", choose Environment Texture
  • click "Open image." button, navigate to <blender directory>/2.80/datafiles/sutdiolights/world/night.exr
  • change to LookDev shading
  • use drop-down menu next to shading buttons to change display settings, enable "Scene World"
  • observe that the world is whitish/grey
  • use MMB to rotate viewport
  • observe that the world is immediately shown correctly when movement happens

This seems to happen the first time the world texture is shown, but in my experience it happens other times as well (not sure what triggers it.) It can be annoying when changing in to LookDev because it requires "jiggling" the view to get it to display properly.

Event Timeline

-I can confirm that problem with the build 2.80.71

This seems like a more general problem than just with the environment. I can basically repro the problem whenever Eevee needs to recompile its shaders due to a change in the node graph.

The shader recompile happens correctly but the viewport only "half" refreshes, leaving a whitish/whashed-out image in the viewport.

This is most easily seen when using Node Wrangler and using its quick view functionality to view each node individually. As you view each node for the first time the viewport is left in the half-finished state. Upon viewing them again things work correctly.

It also happens when opening the default scene and clicking the Shading workspace for the first time.

Sebastian Parborg (zeddb) triaged this task as Needs Information from User priority.

I can't seem to reproduce this on my end.

Is this still and issue with the latest beta?

Thanks -- yes, just confirmed it with d93a7290e506.

Yes, still repros here too on 04c54dec445

Here's a gif showing the issue (occurs on both my AMD and nVidia):

And here's a sample .blend:

Sebastian Parborg (zeddb) raised the priority of this task from Needs Information from User to Confirmed, Medium.

I can reproduce this around 15% of the time I swap surface output in that file.