EEVEE Next: Lamps except the Sun turns the model dark (does not catch any light) with Intel UHD 620 #120273
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
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#120273
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.22631-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 25.20.100.6444
Blender Version
Broken: version: 4.2.0 Alpha, branch: main, commit date: 2024-03-08 00:32, hash:
6dffc162c7b9
Worked: (newest version of Blender that worked as expected)
Short description of error
In EEVEE Next, the model does not catch any light in Render mode.
It turns completely dark.
This is how it looks in EEVEE:
...and this is how the same model looks in EEVEE Next:
Exact steps for others to reproduce the error
The model looks total dark. (Does not catch any light)
blender_debug_output.txt
I have used the model provided in this follow-along tutorial:
https://www.youtube.com/watch?v=ZeKodExfp_4
(The link is provided in the Description)
This may be an issue with the integrated GPU "Intel(R) UHD Graphics 620"
I don't have similar hardware to test, so before forwarding to the developers, it would be useful to have some information available:
blender_debug_gpu.cmd
. This will start Blender in debug mode and create log files).Also please check if this issue is not one of those that have already been reported:
#118790: EEVEE-NEXT : AREA LIGHT : VOLUME PROBE : Baking Not works correctly with area light and many light (After verification)
#119259: EEVEE-NEXT : AREA LIGHT : SHADOW BROKEN WHEN USING AREA LIGHT
No, my issue is about the visibility of the object itself, not about baking or shadows.
So it is not a duplicate.
With EEVEE Next, the object remains dark with all lights except Sun.
This is how the object appears with EEVEE Next with Sun:
The sample file is attached.
I'll try with a UHD620 device
Can't reproduce the problem on the Surface Pro 6 on either linux or windows. Could you check and make sure that you have your graphics driver up to date?
I updated the GPU driver, but the problem in Blender remains.
During the updating process, I did see some anomaly, as follows:
My Device Manager reported that the graphic drivers are the latest.
But I did find an updated driver for the combination of {Win 11, UHD 620, and 8th Gen Intel i3}.
This page says that the updated driver is dated 1st Feb 2024.
I installed that and restarted the laptop.
Now the Device Manager shows the latest driver version, but the date is 13 Nov 2023!
(Probably the difference in the dates is because the driver exe contains multiple drivers for different families of GPU.)
I hope that everything is in order!
Earlier, I had reported a bug (#114597) that my laptop "almost" freezes when I switch to EEVEE Next and render mode.
It turned out that EEVEE Next was not tuned for low-end GPUs such as UHD 620.
Could this be a similar issue with UHD 620?
@raindrops hi, best to update drivers from the website (or use Intel® Driver & Support Assistant)
Device manager always shows current driver as latest.
@raindrops, could you also provide debug-logs?
Please open Blender's installation directory and double click on the
blender_debug_gpu.cmd
. This will start Blender in debug mode and create log files.Try to reproduce the error again.
Then close Blender
The Windows Explorer should open and show you up to two files, a debug log and the system information.
Add them to your bug report by clicking on the upload button below or via drag and drop..
I also have the same issue and can confirm is not present in Linux (ubuntu)
If someone wants it, I have some debug logs as I have a similar system
ERROR (gpu.debug): EEVEE > negZ_view > Deferred.Opaque > Shading > DoubleSided > MADefault Surfa > MADefault Surfa : Error has been generated. GL error GL_INVALID_OPERATION in BindImageTextures: (ID: 4095530478) internal format of texture 3 is not supported
In EEVEE Next, the model turns dark (does not catch any light) in Render modeto EEVEE Next: Lamps except the Sun turns the model dark (does not catch any light) with Intel UHD 620Thank you for providing the blender_debug_output.txt file. I have updated the bug report description and confirmed the issue.
Indeed, from the information provided by @raindrops and @Dr.CGI, it appears that there is a consistent issue with the UHD 620 GPU.
@fclem ^
The
--debug-gpu
output contain quite a lot of GL errors about invalid format. The same formats are working in other shaders. I believe this is a driver bug since it doesn't appear on Linux as reported by @Dr.CGI . We will report upstream. I don't know if we can find a workaround.Unable to reproduce with
7b7e9f224c
026f8e8bdf
I will try to boot windows on the last system. Will take me some time as the battery are failing.
Finaly got a stacktrace (default cube, eevee-next, render shading mode)
The incorrect textures can be solved by
When starting blender with
--debug-gpu
it reports about missing resources, which aren't missing. This driver is quite bad.but nonetheless got all lights working
Might be related to #107642
What I found so far is that the driver report support for an extension, which is failing. I will disable the extension for UHD/Windows. Linux drivers are better supported and work as expected.
@raindrops In a hour a Blender version can be downloaded at https://builder.blender.org/download/patch/PR121062/ which might solve this specific issue. Can you test if it fixes this specific issue.
I detected more issues with this driver which I am looking into. These will be handled one by one in their own reports.
I have downloaded the patch version, but it keeps crashing as soon as I switch to EEVEE Next in Rendered mode.
(I was facing the same issue in earlier version of Blender also, and have already raised a bug: #120669)
Unless that bug is resolved, I won't be able to test this patch.
In other words, we have to treat bug#120669 as blocker for this one.
Good to see that you have the same issues as I faced yesterday. This will take some time to work around all the driver bugs. :-(