Intel HD graphics: Changing Roughness Value to 0 causes mesh to be black #88754

Closed
opened 2021-06-02 21:09:31 +02:00 by Kurtdzn · 54 comments

System Information
Operating system: Windows 10 Pro
Graphics card: Intel® HD Graphics 500 "Integrated Graphics"

Blender Version
Broken: 2.93, 02-Jun-2021 14:22
Worked: 2.92, 25-Feb-2021 12:03

Short description of error
When sliding the roughness slider all the way to 0 causes it to be all black (only in eevee)Normal.png

Bug.png
Materials being affected:

  • Anisotropic BSDF
  • Glass BSDF
  • Glossy BSDF
  • Hair BSDF (Exception as it bugs with any value)
  • Principled BSDF

Exact steps for others to reproduce the error

  1. Add any material listed above
  2. Set the roughness slider to 0 (Except for the Hair BSDF)
    Report.blend
**System Information** Operating system: Windows 10 Pro Graphics card: Intel® HD Graphics 500 "Integrated Graphics" **Blender Version** Broken: 2.93, 02-Jun-2021 14:22 Worked: 2.92, 25-Feb-2021 12:03 **Short description of error** When sliding the roughness slider all the way to 0 causes it to be all black (only in eevee)![Normal.png](https://archive.blender.org/developer/F10154646/Normal.png) ![Bug.png](https://archive.blender.org/developer/F10154648/Bug.png) Materials being affected: - Anisotropic BSDF - Glass BSDF - Glossy BSDF - Hair BSDF (Exception as it bugs with any value) - Principled BSDF **Exact steps for others to reproduce the error** 1. Add any material listed above 2. Set the roughness slider to 0 (Except for the Hair BSDF) [Report.blend](https://archive.blender.org/developer/F10154650/Report.blend)
Author

Added subscriber: @Kxrtdzn

Added subscriber: @Kxrtdzn

#91466 was marked as duplicate of this issue

#91466 was marked as duplicate of this issue

#89947 was marked as duplicate of this issue

#89947 was marked as duplicate of this issue

#89628 was marked as duplicate of this issue

#89628 was marked as duplicate of this issue

#89569 was marked as duplicate of this issue

#89569 was marked as duplicate of this issue

#89550 was marked as duplicate of this issue

#89550 was marked as duplicate of this issue

#89132 was marked as duplicate of this issue

#89132 was marked as duplicate of this issue

#89107 was marked as duplicate of this issue

#89107 was marked as duplicate of this issue

#89042 was marked as duplicate of this issue

#89042 was marked as duplicate of this issue

#88866 was marked as duplicate of this issue

#88866 was marked as duplicate of this issue
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Cannot reproduce here (still looks like the first picture in 2.93 on my side -- not like the second)

**System Information**
Operating system: Linux-5.11.16-200.fc33.x86_64-x86_64-with-glibc2.32 64 Bits
Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.67
version: 2.93.0, branch: master, commit date: 2021-06-02 11:21, hash: `rB84da05a8b806`
Cannot reproduce here (still looks like the first picture in 2.93 on my side -- not like the second) ``` **System Information** Operating system: Linux-5.11.16-200.fc33.x86_64-x86_64-with-glibc2.32 64 Bits Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.67 version: 2.93.0, branch: master, commit date: 2021-06-02 11:21, hash: `rB84da05a8b806` ```
Member

Added subscribers: @ghost653, @PratikPB2123, @Koopa512, @Mets

Added subscribers: @ghost653, @PratikPB2123, @Koopa512, @Mets

to be precise, from my testing it is any value below exactly 0.00372662150766700484526283698727411319850943982601165771484375 (it's probably infinite, but cut off due to the limit of 64 decimal digits)
specs and OS: Ubuntu 20.10 64 bit with everything up to date, Intel core i5 5200u, no dedicated GPU and 8GB of DDR3 RAM
seems to be also the case in Cycles Viewport

to be precise, from my testing it is any value below exactly 0.00372662150766700484526283698727411319850943982601165771484375 (it's probably infinite, but cut off due to the limit of 64 decimal digits) specs and OS: Ubuntu 20.10 64 bit with everything up to date, Intel core i5 5200u, no dedicated GPU and 8GB of DDR3 RAM seems to be also the case in Cycles Viewport
Member

Added subscriber: @McClure

Added subscriber: @McClure
Pratik Borhade changed title from Changing Roughness Value to 0 causes any mesh to be black (EEVEE) to Changing Roughness Value to 0 causes any mesh to be black 2021-06-11 19:38:46 +02:00

Added subscriber: @PrototypeNM1

Added subscriber: @PrototypeNM1

Couldn't recreate on an Intel UHD Graphics 620.

Couldn't recreate on an Intel UHD Graphics 620.

Removed subscriber: @PrototypeNM1

Removed subscriber: @PrototypeNM1
Member

Added subscriber: @bilgi

Added subscriber: @bilgi
Ankit Meel changed title from Changing Roughness Value to 0 causes any mesh to be black to Intel HD graphics: Changing Roughness Value to 0 causes mesh to be black 2021-06-18 21:12:09 +02:00
Member

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

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

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

While we don't have the hardware in triaging team, there are multiple reports, easy to redo steps and working version.

While we don't have the hardware in triaging team, there are multiple reports, easy to redo steps and working version.
Member

Added subscribers: @cagram, @Zandman

Added subscribers: @cagram, @Zandman
Member

Added subscriber: @afeso

Added subscriber: @afeso

Added subscriber: @jgilhutton

Added subscriber: @jgilhutton

In #88754#1173383, @Koopa512 wrote:
to be precise, from my testing it is any value below exactly 0.00372662150766700484526283698727411319850943982601165771484375 (it's probably infinite, but cut off due to the limit of 64 decimal digits)
specs and OS: Ubuntu 20.10 64 bit with everything up to date, Intel core i5 5200u, no dedicated GPU and 8GB of DDR3 RAM
seems to be also the case in Cycles Viewport

I only got to 0.003726621 manually. But I have this same problem.
Can confirm for Blender versions 2.93, 2.93.1 & 3.0.0
09flu1veih771.mp4

> In #88754#1173383, @Koopa512 wrote: > to be precise, from my testing it is any value below exactly 0.00372662150766700484526283698727411319850943982601165771484375 (it's probably infinite, but cut off due to the limit of 64 decimal digits) > specs and OS: Ubuntu 20.10 64 bit with everything up to date, Intel core i5 5200u, no dedicated GPU and 8GB of DDR3 RAM > seems to be also the case in Cycles Viewport I only got to 0.003726621 manually. But I have this same problem. Can confirm for Blender versions 2.93, 2.93.1 & 3.0.0 [09flu1veih771.mp4](https://archive.blender.org/developer/F10207059/09flu1veih771.mp4)

Any of the following combinations results in a completely shadeless material:

Captura de pantalla (114).png

Any of the following combinations results in a completely shadeless material: ![Captura de pantalla (114).png](https://archive.blender.org/developer/F10207061/Captura_de_pantalla__114_.png)
Member

Removed subscriber: @Mets

Removed subscriber: @Mets

Added subscriber: @pafurijaz-4

Added subscriber: @pafurijaz-4

Added subscriber: @scaled

Added subscriber: @scaled

Linux version of Blender also affected. HD Graphics 520, Debian 11, drivers: Mesa 20.3.4.

Linux version of Blender also affected. HD Graphics 520, Debian 11, drivers: Mesa 20.3.4.

Added subscriber: @EliteArmedForce

Added subscriber: @EliteArmedForce

I can confirm this issue. I have been facing this issue for the past month or so.

Affected Blender version:Linux (Ubuntu 20.04.2) with Blender v2.93, v2.93.1 and 3.00

I thought this bug was unique to me so, I tried getting help by posting in [Reddit ]] and [ https:*blender.stackexchange.com/q/228640/120919 | blender.stackexchange . (post links contains detailed images of the issue respectively)

I tried on both windows 10 and Ubuntu 20.04 lts
Specs: (laptop)
OS: Windows 10 64 bit & Ubuntu 20.04 LTS
CPU: Intel i5-4210U
RAM: 12 GB
Display Drivers: Intel HD Graphics 4400 and AMD Radeon HD 8500M

I can confirm this issue. I have been facing this issue for the past month or so. Affected Blender version:Linux (Ubuntu 20.04.2) with Blender v2.93, v2.93.1 and 3.00 I thought this bug was unique to me so, I tried getting help by posting in [Reddit ]] and [[ https:*blender.stackexchange.com/q/228640/120919 | blender.stackexchange ](https:*www.reddit.com/r/blender/comments/o5rl1n/hdri_sphere_appears_black/?utm_source=share&utm_medium=web2x&context=3). (post links contains detailed images of the issue respectively) I tried on both windows 10 and Ubuntu 20.04 lts Specs: (laptop) OS: Windows 10 64 bit & Ubuntu 20.04 LTS CPU: Intel i5-4210U RAM: 12 GB Display Drivers: Intel HD Graphics 4400 and AMD Radeon HD 8500M

Also, forgot to mention, if you turn on Ambient Occulution, it don't became pure black, but reflection still missing. And in some models reflections was broken after update.

Expected:
изображение.png

Roughness = 0, AO is on
изображение.png

Roughness = 0.01, AO is on
изображение.png

Also, forgot to mention, if you turn on Ambient Occulution, it don't became pure black, but reflection still missing. And in some models reflections was broken after update. Expected: ![изображение.png](https://archive.blender.org/developer/F10215806/изображение.png) Roughness = 0, AO is on ![изображение.png](https://archive.blender.org/developer/F10215808/изображение.png) Roughness = 0.01, AO is on ![изображение.png](https://archive.blender.org/developer/F10215810/изображение.png)

Added subscriber: @Flolfy

Added subscriber: @Flolfy

Inocent question here: Anybody knows which is usually the timespan of fixing these kind of issues?
I'm asking this in order to organize the production of our projects. Right now, we can not use any version above 2.92 because of this problem, and we were counting on using the new depth of field options available on 2.93.
I ask without the intention of being rude or unpolite. I just want to have certain amount of information so I can avoid asking about this in the future and also so I can be able to schedule the projects.
Thanks!

Inocent question here: Anybody knows which is usually the timespan of fixing these kind of issues? I'm asking this in order to organize the production of our projects. Right now, we can not use any version above 2.92 because of this problem, and we were counting on using the new depth of field options available on 2.93. I ask without the intention of being rude or unpolite. I just want to have certain amount of information so I can avoid asking about this in the future and also so I can be able to schedule the projects. Thanks!
Member

Will dare setting to High prio since it is a regression.

Will dare setting to High prio since it is a regression.
Member

Added subscriber: @LilyArlatto

Added subscriber: @LilyArlatto

0.0047 roughness value seems to be as low as I can go before this happens to me.

0.0047 roughness value seems to be as low as I can go before this happens to me.

This comment was removed by @jgilhutton

*This comment was removed by @jgilhutton*

This problem is not present on eevee-dof-refactor-blender-2.93.0-5db9a008b95a-linux64 nor blender-2.93.0-175325ebdb5b-linux64.
Any InteHD user who wants to try 2.93 depth of field implementation could use that version of Blender.
Also, maybe this information helps to rule out some things.

This problem is not present on **eevee-dof-refactor-blender-2.93.0-5db9a008b95a-linux64** nor **blender-2.93.0-175325ebdb5b-linux64**. Any InteHD user who wants to try 2.93 depth of field implementation could use that version of Blender. Also, maybe this information helps to rule out some things.

Added subscriber: @kurocle

Added subscriber: @kurocle

Added subscriber: @Capt.price

Added subscriber: @Capt.price

The roughness value of 0.0037267 is normal for me, but it gets pitch black when reduced to 0.0037266. Running Intel Graphics 620 and Blender 2.93.3
System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 27.20.100.8681
Blender Version
Broken: version: 2.93.3, branch: master, commit date: 2021-08-17 18:30, hash: 8b80d19f36
Worked: (newest version of Blender that worked as expected)

The roughness value of 0.0037267 is normal for me, but it gets pitch black when reduced to 0.0037266. Running Intel Graphics 620 and Blender 2.93.3 **System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 27.20.100.8681 **Blender Version** Broken: version: 2.93.3, branch: master, commit date: 2021-08-17 18:30, hash: `8b80d19f36` Worked: (newest version of Blender that worked as expected)
Contributor

Added subscriber: @Jake-Faulkner

Added subscriber: @Jake-Faulkner
Jake self-assigned this 2021-08-29 03:17:00 +02:00
Contributor

Seems to have appeared in blender/blender-staging@64d96f68d6

Seems to have appeared in blender/blender-staging@64d96f68d6

Added subscriber: @jpbruyere

Added subscriber: @jpbruyere
Member

Added subscriber: @Rodrigo_S.T

Added subscriber: @Rodrigo_S.T

Added subscriber: @maxwxyz

Added subscriber: @maxwxyz

Can confirm on current Blender version on Windows.
Also, the Sky Texture is not displaying in Eevee.
Blender Error.png

Can confirm on current Blender version on Windows. Also, the Sky Texture is not displaying in Eevee. ![Blender Error.png](https://archive.blender.org/developer/F10516208/Blender_Error.png)

Added subscriber: @Wovchick

Added subscriber: @Wovchick

This issue was referenced by 651f1b5cf9

This issue was referenced by 651f1b5cf9f67fb3cdec486985d68eda6adf75a6

This issue was referenced by 4c156cba21

This issue was referenced by 4c156cba21f7ada1057ca91360bc0a6d48962fb5
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Sign in to join this conversation.
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
23 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#88754
No description provided.