white artifacts in EEVEE #86578

New Issue

guang liang chen · 2021-03-15T11:44:17+01:00

guang liang chen commented

2021-03-15 11:44:17 +01:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 670/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67

Blender Version
Broken: version: 2.92, 2.93.0 Alpha, branch: master, commit date: 2021-03-14 22:11, hash: 070010e203
Worked: 2.91

Short description of error
White NaN pixels appearing when using EEVEE. It's less apparent in the viewport than in renders as the number of artifacts depends on the number of samples.

spekles in eevee.blend

Exact steps for others to reproduce the error
Open the attached file, switch to viewport rendering, hit F12.

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 670/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67 **Blender Version** Broken: version: 2.92, 2.93.0 Alpha, branch: master, commit date: 2021-03-14 22:11, hash: `070010e203` Worked: 2.91 **Short description of error** White NaN pixels appearing when using EEVEE. It's less apparent in the viewport than in renders as the number of artifacts depends on the number of samples. ![error.jpg](https://archive.blender.org/developer/F9892502/error.jpg) [spekles in eevee.blend](https://archive.blender.org/developer/F9892506/spekles_in__eevee.blend) **Exact steps for others to reproduce the error** Open the attached file, switch to viewport rendering, hit F12.

guang liang chen commented

2021-03-15 11:44:17 +01:00

Added subscriber: @imdjs

blender-admin commented

2021-03-15 11:44:17 +01:00

#88643 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#87412 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#87391 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#87248 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#86752 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#86795 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#86681 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#87233 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#87202 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#87072 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#87059 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#87024 was marked as duplicate of this issue

blender-admin commented

2021-03-15 11:44:17 +01:00

#86855 was marked as duplicate of this issue

Philipp Oeser changed title from ~~got white spekles in EEVEE(blender2.92 2.93)~~ to white artifacts in EEVEE

2021-03-15 15:14:06 +01:00

Philipp Oeser commented

2021-03-15 15:14:06 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser commented

2021-03-15 15:17:12 +01:00

Added subscribers: @fclem, @lichtwerk

Philipp Oeser commented

2021-03-15 15:17:12 +01:00

This works for me in 2.92 though, only seeing those in 2.93

**System Information**
Operating system: Linux-5.10.19-200.fc33.x86_64-x86_64-with-glibc2.32 64 Bits
Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01
version: 2.93.0 Alpha, branch: master, commit date: 2021-03-15 12:31, hash: `rBab6e67767e73`

In contrast to similar reports we had recently, these dont seem related to screen space reflections.

CC @fclem

This works for me in 2.92 though, only seeing those in 2.93 ``` **System Information** Operating system: Linux-5.10.19-200.fc33.x86_64-x86_64-with-glibc2.32 64 Bits Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01 version: 2.93.0 Alpha, branch: master, commit date: 2021-03-15 12:31, hash: `rBab6e67767e73` ``` In contrast to similar reports we had recently, these dont seem related to screen space reflections. CC @fclem

Clément Foucault commented

2021-03-15 15:54:29 +01:00

I cannot repro here (AMD + Linux) Will test on another config.

I did must have done it commented

2021-03-16 02:35:29 +01:00

Added subscriber: @leonardos

I did must have done it commented

2021-03-16 02:35:29 +01:00

cant reproduce win 10 + amd 2.93

Spencer Singer commented

2021-03-16 03:21:51 +01:00

Added subscriber: @MLSpence

Evan Wilson commented

2021-03-18 20:01:41 +01:00

Added subscriber: @EAW

Evan Wilson commented

2021-03-18 20:01:41 +01:00

I can reproduce as I have a NVIDIA GPU.
Some observations:

The nan pixels are in the diffuse direct pass.
They go away when I turn off the Subdivision surface modifier, which makes me wonder if that is part of the issue. I'll see if the other reports all have subdivision surface modifiers as well.

Tested using:
version: 2.93.0 Alpha, branch: master, commit date: 2021-03-18 17:07, hash: b1150fa1f5, type: Release
OS: Windows-10-10.0.19041.630-SP0 64 Bits
GPU: GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35
CPU: i7-950 @3.07 GHz SSE2 SSE3 SSE41
RAM: 8.00 GB

I can reproduce as I have a NVIDIA GPU. Some observations: - The nan pixels are in the diffuse direct pass. - They go away when I turn off the Subdivision surface modifier, which makes me wonder if that is part of the issue. I'll see if the other reports all have subdivision surface modifiers as well. ``` ``` --- Tested using: version: 2.93.0 Alpha, branch: master, commit date: 2021-03-18 17:07, hash: b1150fa1f5a5, type: Release OS: Windows-10-10.0.19041.630-SP0 64 Bits GPU: GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35 CPU: i7-950 @3.07 GHz SSE2 SSE3 SSE41 RAM: 8.00 GB

Giampaolo commented

2021-03-22 13:50:44 +01:00

Added subscriber: @joaulo

Balázs Gyutai commented

2021-03-23 13:16:36 +01:00

Added subscriber: @BalazsGyutai

Falk David commented

2021-03-24 11:07:26 +01:00

Added subscribers: @Gandarufu, @PratikPB2123

Jeran commented

2021-03-24 16:23:14 +01:00

Added subscriber: @TheJeran

Spencer Singer commented

2021-03-26 17:20:51 +01:00

i was able to reproduce this in the viewport, so i believe this isn't just a render image only thing. It also happened more often when I turned on "High Quality Normals" in the performance settings.

i was able to reproduce this in the viewport, ![image.png](https://archive.blender.org/developer/F9910781/image.png) so i believe this isn't just a render image only thing. It also happened more often when I turned on "High Quality Normals" in the performance settings.

Luca Knoblich commented

2021-03-26 20:24:51 +01:00

Added subscriber: @sgds

Carlos commented

2021-03-27 11:24:25 +01:00

Added subscriber: @carlos13eab

piero commented

2021-03-28 19:31:38 +02:00

Added subscriber: @pietrodichito

Pratik Borhade commented

2021-03-30 09:06:59 +02:00

Added subscriber: @borschberry

Luca Knoblich commented

2021-03-30 19:41:19 +02:00

I only had this problem in 2.93 but now it just happend in 2.91 as well (Evee, Viewport&Render):

I updated my nvidia drivers but it did not help.

Update: Turning down specular completely in the principled shader solved it.

I only had this problem in 2.93 but now it just happend in 2.91 as well (Evee, Viewport&Render): ![blender_WhiteDots_01.png](https://archive.blender.org/developer/F9914797/blender_WhiteDots_01.png) I updated my nvidia drivers but it did not help. Update: Turning down specular completely in the principled shader solved it.

Falk David commented

2021-03-30 20:43:35 +02:00

Added subscriber: @TheCrowdedOne

Jon Henry M. Faltis 9077149 commented

2021-03-30 21:01:18 +02:00

Added subscriber: @geocentric_wage

Gandalf Bartholomäus commented

2021-03-30 21:24:14 +02:00

I can confirm that it happens in Eevee-renders in 2.91 as well.

Falk David commented

2021-03-31 08:50:03 +02:00

Added subscriber: @AmirShehata

Yomom commented

2021-04-01 12:09:32 +02:00

I've tried this, doesnt seem to be anything to do with screen space refractions, volumes or anything like that, they appear as samples progress. This doesnt happen to me in Blender 2.92 but happens in 2.93. I really hope this will be an EZ fix, because 2.93 got some amazing eevee updates i need to get my hands on.

Corey Reading commented

2021-04-01 16:34:40 +02:00

Added subscriber: @cocoreysa

Corey Reading commented

2021-04-01 16:34:40 +02:00

Here's my example of this, It stops/moves when I disconnect the normal from the materials. Using Blender 2.93 that was released on the 31st of March (I have an Nvidia 1080)

Here's an example of the it effecting the Bloom.

Here's my example of this, It stops/moves when I disconnect the normal from the materials. Using Blender 2.93 that was released on the 31st of March (I have an Nvidia 1080) ![Overlay2.png](https://archive.blender.org/developer/F9916989/Overlay2.png) Here's an example of the it effecting the Bloom. ![Overlay1.png](https://archive.blender.org/developer/F9916991/Overlay1.png)

Corey Reading commented

2021-04-02 01:02:59 +02:00

I've recreated the effect in the file below, just hit render and you should be able to see. (in 2.93 released on April 1st)

FresnelBug293.blend

I've recreated the effect in the file below, just hit render and you should be able to see. (in 2.93 released on April 1st) [FresnelBug293.blend](https://archive.blender.org/developer/F9917293/FresnelBug293.blend)

Evan Wilson commented

2021-04-02 01:35:38 +02:00

In #86578#1136836, @MLSpence wrote:
i was able to reproduce this in the viewport, so i believe this isn't just a render image only thing.

I hadn’t noticed that the report said it only occurred in the render. As I can confirm that it occurs in the viewport as well, I’ll update the report.

> In #86578#1136836, @MLSpence wrote: > i was able to reproduce this in the viewport, so i believe this isn't just a render image only thing. I hadn’t noticed that the report said it only occurred in the render. As I can confirm that it occurs in the viewport as well, I’ll update the report.

Andres Stephens commented

2021-04-02 01:55:15 +02:00

Added subscriber: @AndresStephens

Andres Stephens commented

2021-04-02 01:55:15 +02:00

Can confirm. Should be a high priority bug.

Relevant tasks:

https:*developer.blender.org/T86795
https:*developer.blender.org/T86752

Can confirm. Should be a high priority bug. Relevant tasks: [https:*developer.blender.org/T86795 ](https:*developer.blender.org/T86795) [https:*developer.blender.org/T86752 ](https:*developer.blender.org/T86752)

Andres Stephens commented

2021-04-02 02:02:49 +02:00

You can see the issue happening in the Diffuse Light AOV of the Eevee render.

![bforartists_nr8bDBCsut.png](https://archive.blender.org/developer/F9917325/bforartists_nr8bDBCsut.png) You can see the issue happening in the Diffuse Light AOV of the Eevee render.

Aleksandr commented

2021-04-02 13:58:55 +02:00

Added subscriber: @viadvena

Aleksandr commented

2021-04-02 13:58:55 +02:00

System Information
Operating system: Linux-4.15.0-140-generic-x86_64-with-glibc2.27 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04

Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-04-01 21:49, hash: d91fec1a85
Worked: (newest version of Blender that worked as expected)

Same problem.

With SSR

Without SSR

**System Information** Operating system: Linux-4.15.0-140-generic-x86_64-with-glibc2.27 64 Bits Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04 **Blender Version** Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-04-01 21:49, hash: `d91fec1a85` Worked: (newest version of Blender that worked as expected) Same problem. **With SSR** ![Screenshot_20210402_145653.png](https://archive.blender.org/developer/F9917839/Screenshot_20210402_145653.png) **Without SSR** ![Screenshot_20210402_145658.png](https://archive.blender.org/developer/F9917841/Screenshot_20210402_145658.png)

Evan Wilson commented

2021-04-05 19:51:32 +02:00

Added subscriber: @Shady.Hamza

Jaggz H commented

2021-04-06 21:04:56 +02:00

Added subscriber: @jaggz

Jaggz H commented

2021-04-06 21:04:56 +02:00

As I posted in https://developer.blender.org/T87233
It's produced in a scene with geometry and no light source at all.

Can anyone confirm that it does not occur with other shader's than Principled?

It happens with different object types (I've done it with mesh and beveled curves).
It is not reliant upon subdiv modifier (although that can change the geometry, increasing or reducing its occurence).
It is not affected by specular value in my tests.
I think I've noticed it only at the edges of objects (where the normal is perpendicular to the camera/view?)
It happens with Principled Shader, and no values within the shader will stop it or affect it.
I haven't found another shader (but haven't tested much) that can cause it. If I swap principled with diffuse, it doesn't seem to happen at all.

Since its value is so extreme, I'm taking an initial wild guess that some shader calculation, with just the right circumstances, possibly a surface tangent to the view, is sending a value off to infinity (or denominator to near 0, or 0+some fudge factor).

It's just the point/points at that precise location where that value blows up (or goes to 0), and later goes through SSR, bloom, or whatever, to make it spectacular. Here it is, caused by a Curve object with Principled (later processing of SSR, Emission=10.0 makes it more visible):

As I posted in https://developer.blender.org/T87233 It's produced in a scene with geometry and no light source at all. Can anyone confirm that it does not occur with other shader's than Principled? 1. It happens with different object types (I've done it with mesh and beveled curves). 2. It is not reliant upon subdiv modifier (although that can change the geometry, increasing or reducing its occurence). 3. It is not affected by specular value in my tests. 3. I *think* I've noticed it only at the edges of objects (where the normal is perpendicular to the camera/view?) 4. It happens with Principled Shader, and no values within the shader will stop it or affect it. 5. I haven't found another shader (but haven't tested much) that can cause it. If I swap principled with diffuse, it doesn't seem to happen at all. Since its value is so extreme, I'm taking an initial wild guess that some shader calculation, with just the right circumstances, possibly a surface tangent to the view, is sending a value off to infinity (or denominator to near 0, or 0+some fudge factor). It's just the point/points at that precise location where that value blows up (or goes to 0), and later goes through SSR, bloom, or whatever, to make it spectacular. Here it is, caused by a Curve object with Principled (later processing of SSR, Emission=10.0 makes it more visible): ![Screenshot_20210406_114713.png](https://archive.blender.org/developer/F9922110/Screenshot_20210406_114713.png)

Daniel Salazar commented

2021-04-07 09:25:42 +02:00

Added subscriber: @zanqdo

Daniel Salazar commented

2021-04-07 09:25:42 +02:00

I've created a possibly related report #87248

For me the problem seems to be present only when the Jitter Camera option is used

I've created a possibly related report #87248 For me the problem seems to be present only when the *Jitter Camera* option is used

Falk David commented

2021-04-07 09:46:28 +02:00

Added subscriber: @filedescriptor

Robert commented

2021-04-07 20:00:49 +02:00

Added subscriber: @Robert_B

Robert commented

2021-04-07 20:00:49 +02:00

I have the same problem. The NaN pixels are also available without SSR and jitter camera. I tested version 2.93 alpha in Windows and Linux.

I have the same problem. The NaN pixels are also available without SSR and jitter camera. I tested version 2.93 alpha in Windows and Linux. ![Car_Firefly.jpg](https://archive.blender.org/developer/F9923158/Car_Firefly.jpg)

Aleksandr commented

2021-04-07 23:08:34 +02:00

@jaggz This bug feeling good with other shaders:

And how I remember this bug was appear in previous versions of blender and it was successfully resolved. I don't know what the essence was. There was thoughts that it's all due errors in Nvidia drivers...

@jaggz This bug feeling good with other shaders: ![Screenshot_20210408_000007.png](https://archive.blender.org/developer/F9923276/Screenshot_20210408_000007.png) ![Screenshot_20210408_000020.png](https://archive.blender.org/developer/F9923277/Screenshot_20210408_000020.png) ![Screenshot_20210408_000025.png](https://archive.blender.org/developer/F9923278/Screenshot_20210408_000025.png) And how I remember this bug was appear in previous versions of blender and it was successfully resolved. I don't know what the essence was. There was thoughts that it's all due errors in Nvidia drivers...

Michael Hermann commented

2021-04-08 13:00:53 +02:00

Added subscriber: @MichaelHermann

Dalai Felinto commented

2021-04-08 14:49:39 +02:00

Added subscriber: @dfelinto

Dalai Felinto commented

2021-04-08 14:49:39 +02:00

@fclem I can reproduce it here:

Operating system: Linux-5.8.0-45-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04

Latest master. In 2.91 it was indeed working still.

@fclem I can reproduce it here: Operating system: Linux-5.8.0-45-generic-x86_64-with-glibc2.31 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04 Latest master. In 2.91 it was indeed working still.

blender-admin commented

2021-04-08 17:08:13 +02:00

This issue was referenced by 5c4d24e1fd

This issue was referenced by 5c4d24e1fd752a8a89d44d05e8e3f9b31f2d7db0

Clément Foucault commented

2021-04-08 17:10:20 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Clément Foucault closed this issue

2021-04-08 17:10:20 +02:00

Clément Foucault self-assigned this 2021-04-08 17:10:20 +02:00

Dalai Felinto commented

2021-04-08 17:23:57 +02:00

Added subscribers: @EvaVomhoff, @TimBL, @razed, @SteffenD, @VincentMaurer

Dalai Felinto commented

2021-04-08 17:25:50 +02:00

Added subscribers: @AlSande, @Firepal

Dalai Felinto commented

2021-04-08 17:29:45 +02:00

Added subscribers: @MadRabidz, @PaganHead, @TravisOBrien

Daniel Salazar commented

2021-04-09 01:37:30 +02:00

This is not over yet!

DOF BUG.blend

Ok hints on this one:

The problem seems to be related to the custom split normals AND the sharp edges (this mesh has been imported from an alembic file)
Turning off Ambient Occlusion gets rid of the problem

This is not over yet! ![image.png](https://archive.blender.org/developer/F9926333/image.png) [DOF BUG.blend](https://archive.blender.org/developer/F9926336/DOF_BUG.blend) Ok hints on this one: The problem seems to be related to the custom split normals AND the sharp edges (this mesh has been imported from an alembic file) Turning off Ambient Occlusion gets rid of the problem

Daniel Salazar commented

2021-04-09 01:39:32 +02:00

Changed status from 'Resolved' to: 'Confirmed'

Daniel Salazar reopened this issue

2021-04-09 01:39:32 +02:00

Aleksandr commented

2021-04-09 10:14:43 +02:00

@zanqdo I just tried your file. There is a problem in ultra low value for AO "Distance" in compare with the scale of the scene. So you can just increase a little bit value and it will be working perfect. So, artifacts going to appears when AO "Distance" is very low and "Auto Smooth" is enabled.

Screencast-2021-04-09_10.59.47.mp4

Screencast-2021-04-09_11.06.10.mp4

@zanqdo I just tried your file. There is a problem in ultra low value for AO "Distance" in compare with the scale of the scene. So you can just increase a little bit value and it will be working perfect. So, artifacts going to appears when AO "Distance" is very low and "Auto Smooth" is enabled. [Screencast-2021-04-09_10.59.47.mp4](https://archive.blender.org/developer/F9926601/Screencast-2021-04-09_10.59.47.mp4) [Screencast-2021-04-09_11.06.10.mp4](https://archive.blender.org/developer/F9926602/Screencast-2021-04-09_11.06.10.mp4)

Dalai Felinto commented

2021-04-09 10:42:56 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Dalai Felinto closed this issue

2021-04-09 10:42:56 +02:00

Dalai Felinto commented

2021-04-09 10:42:56 +02:00

@zanqdo if the file of this report is now working (as it is), any new issue should be then reported as a new bug. Closing it for now. Feel free to add me as a subscriber to the new report. Remember to also mention that the issue doesn't happen in 2.92 again.

@fclem FYI I can reproduce the issue with the latest file Daniel shared.

@zanqdo if the file of this report is now working (as it is), any new issue should be then reported as a new bug. Closing it for now. Feel free to add me as a subscriber to the new report. Remember to also mention that the issue doesn't happen in 2.92 again. @fclem FYI I can reproduce the issue with the latest file Daniel shared.

Daniel Salazar commented

2021-04-10 07:52:25 +02:00

@dfelinto Sure thing, will create new report now

Daniel Salazar commented

2021-04-12 03:47:45 +02:00

Added subscriber: @zrp

CRAZ commented

2021-04-12 08:38:56 +02:00

This comment was removed by @zrp

*This comment was removed by @zrp*

Falk David commented

2021-04-12 08:45:33 +02:00

Removed subscriber: @filedescriptor

Daniel Salazar commented

2021-04-12 08:50:58 +02:00

Added subscriber: @filedescriptor

Dustin Bowser commented

2021-04-16 20:13:22 +02:00

Added subscriber: @bowserlm

Dustin Bowser commented

2021-04-16 20:13:22 +02:00

I see this is marked as Resolved. I'm still getting these artifacts on the latest 2.93 Beta build from 4/15. What was the solve?

Daniel Salazar commented

2021-04-16 22:49:10 +02:00

In #86578#1147738, @bowserlm wrote:
I see this is marked as Resolved. I'm still getting these artifacts on the latest 2.93 Beta build from 4/15. What was the solve?

Can you try disabling AO? If that fixes it then it's another bug which has been also reported

> In #86578#1147738, @bowserlm wrote: > I see this is marked as Resolved. I'm still getting these artifacts on the latest 2.93 Beta build from 4/15. What was the solve? Can you try disabling AO? If that fixes it then it's another bug which has been also reported

Dustin Bowser commented

2021-04-16 23:27:00 +02:00

Yeah I tried disabling AO. Made no difference in my case. Nan pixels still there.

YAFU commented

2021-04-16 23:38:42 +02:00

Added subscriber: @YAFU

YAFU commented

2021-04-16 23:38:42 +02:00

@bowserlm, Can you reproduce the problem with the shared .blend file on the first post of the report? If not, what is the .blend file where the problem can be reproduced?

Dustin Bowser commented

2021-04-17 00:00:56 +02:00

Here's the Blend file

https://www.dropbox.com/s/7kerknfetbbrwfr/Creature.blend?dl=0

And here is what I'm seeing

https://jmp.sh/Pda1S6k

Here's the Blend file https://www.dropbox.com/s/7kerknfetbbrwfr/Creature.blend?dl=0 And here is what I'm seeing https://jmp.sh/Pda1S6k

YAFU commented

2021-04-17 00:20:32 +02:00

@bowserlm, Please, you open a new report. You do it from Blender so it collects information from your system and hardware. From Blender "Help" menu, "Report a bug". Share that .blend file and video with developers.