white artifacts in EEVEE #86578
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
29 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#86578
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Added subscriber: @imdjs
#88643 was marked as duplicate of this issue
#87412 was marked as duplicate of this issue
#87391 was marked as duplicate of this issue
#87248 was marked as duplicate of this issue
#86752 was marked as duplicate of this issue
#86795 was marked as duplicate of this issue
#86681 was marked as duplicate of this issue
#87233 was marked as duplicate of this issue
#87202 was marked as duplicate of this issue
#87072 was marked as duplicate of this issue
#87059 was marked as duplicate of this issue
#87024 was marked as duplicate of this issue
#86855 was marked as duplicate of this issue
got white spekles in EEVEE(blender2.92 2.93)to white artifacts in EEVEEChanged status from 'Needs Triage' to: 'Confirmed'
Added subscribers: @fclem, @lichtwerk
This works for me in 2.92 though, only seeing those in 2.93
In contrast to similar reports we had recently, these dont seem related to screen space reflections.
CC @fclem
I cannot repro here (AMD + Linux) Will test on another config.
Added subscriber: @leonardos
cant reproduce win 10 + amd 2.93
Added subscriber: @MLSpence
Added subscriber: @EAW
I can reproduce as I have a NVIDIA GPU.
Some observations:
Tested using:
version: 2.93.0 Alpha, branch: master, commit date: 2021-03-18 17:07, hash:
b1150fa1f5
, type: ReleaseOS: 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
Added subscriber: @joaulo
Added subscriber: @BalazsGyutai
Added subscribers: @Gandarufu, @PratikPB2123
Added subscriber: @TheJeran
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.
Added subscriber: @sgds
Added subscriber: @carlos13eab
Added subscriber: @pietrodichito
Added subscriber: @borschberry
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.
Added subscriber: @TheCrowdedOne
Added subscriber: @geocentric_wage
I can confirm that it happens in Eevee-renders in 2.91 as well.
Added subscriber: @AmirShehata
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.
Added subscriber: @cocoreysa
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.
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 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.
Added subscriber: @AndresStephens
Can confirm. Should be a high priority bug.
Relevant tasks:
https:*developer.blender.org/T86795
https:*developer.blender.org/T86752
You can see the issue happening in the Diffuse Light AOV of the Eevee render.
Added subscriber: @viadvena
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
Added subscriber: @Shady.Hamza
Added subscriber: @jaggz
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?
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):
Added subscriber: @zanqdo
I've created a possibly related report #87248
For me the problem seems to be present only when the Jitter Camera option is used
Added subscriber: @filedescriptor
Added subscriber: @Robert_B
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.
@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...
Added subscriber: @MichaelHermann
Added subscriber: @dfelinto
@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.
This issue was referenced by
5c4d24e1fd
Changed status from 'Confirmed' to: 'Resolved'
Added subscribers: @EvaVomhoff, @TimBL, @razed, @SteffenD, @VincentMaurer
Added subscribers: @AlSande, @Firepal
Added subscribers: @MadRabidz, @PaganHead, @TravisOBrien
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
Changed status from 'Resolved' to: 'Confirmed'
@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
Changed status from 'Confirmed' to: 'Resolved'
@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.
@dfelinto Sure thing, will create new report now
Added subscriber: @zrp
This comment was removed by @zrp
Removed subscriber: @filedescriptor
Added subscriber: @filedescriptor
Added subscriber: @bowserlm
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
Yeah I tried disabling AO. Made no difference in my case. Nan pixels still there.
Added subscriber: @YAFU
@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?
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
@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.
Changed status from 'Resolved' to: 'Confirmed'
Added subscriber: @brecht
We have it back (since
ba4228bcf7
)@brecht, @fclem: was there really no middleground between this and #88368?
Added subscriber: @SachaGoedegebure
This issue was referenced by
c369382977
Changed status from 'Confirmed' to: 'Resolved'