Glitches on Eevee with Intel HD620 #70870
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#70870
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?
this is the system info generated by blender 2.81nafter loading factory settings
this is the rendered cube
Broken: 2.81 from oct 16 and before
Worked: 2.8
The Eevee rendering shows a lot of missing pixels, some greyed out , some transparent. Workbench and Cycles don´t have the problem.
With brand new installed 2.81, first opening, selecting general, F12 to render: missing or grey displayed parts of the cube. Also happens with more complex models and also in 2.82 while it worked well in 2.8 .
system-info.txt
Added subscriber: @noiling
#70877 was marked as duplicate of this issue
Added subscriber: @Mets
Please provide some more basic info by going to Help->Report a Bug in Blender's interface, then paste the detected OS, GPU and Blender version details into your report.
Also a screenshot or full render showing the problem could be helpful (on the default cube in the default scene would be perfect, perhaps even do File->Defaults->Load Factory Settings first).
This comment was removed by @noiling
I´m a little bit unsure if i had to put the requested information into the original task, as done, or as a coment, so I repeat it here:
system-info.txt
Added subscriber: @mano-wii
There are already newer graphics drivers for your Intel:
https://downloadcenter.intel.com/product/126789/Intel-UHD-Graphics-620
If you can, install the latest version and tell us if the issue is fixed.
Added subscriber: @ConsUme
eevee doesn´t work on blender 2.81to Glitches on Eevee with Intel HD620On my end it still doesn't work. But thank you for pointing out about the drivers.
Hey Paul Try using a blend file from 2.80,We have the same problem except mine has those glitch alias effects, it was merged.
This happens when I load up a blend file made in 2.80 in 2.81
Note: there is some minor "scanline" effects on a face perpendicular of the sun lighting on the cube in the viewport. if I port the 2.8 startup file to 2.81 (The glitch alias effects still gone).
Edit: Welp just for curiosity sake, mine is almost the exact same when rendered the default cube while not using a ported 2.80 startup file. so it is the same problem as paul whoever merged this was correct in their assumption
But the default cube ported from 2.80
Yes, I came across this 2.80 to 2.81 thing by loading up an earlier blend file before even using the rendered view.
I have installed the new graphics driver and the problem has gone, in 2.81 at least. I will check 2.82.
This comment was removed by @ConsUme
I'm going to update you guys my latest debug logs Including both standard start-up cube and a startup cubed saved in 2.80 and loaded up in 2.8,1 no updating drivers did not fix this.
2.81 standard.
blender_system_info.txt
blender_debug_output.txt
2.80 loaded into 2.81
blender_system_info.txt
blender_debug_output.txt
@ConsUme, some settings in the viewport may be disabled when importing a scene from an earlier version. But it's hard to tell which setting is causing the issue.
The version of your installed graphics driver is
23.20.16.4973
, but there is already the26.20.100.7323
.@noiling reported that by updating the driver the problem is fixed.
Could you update the graphics driver too?
Did you check my recent system information/Debug info, I did already update my drivers.
Edit: wait... What? It's still saying i'm still have the old drivers?
Edit 2: Soo, um real quick can you point me to the drivers for Dell OEM Intel hd620, I apperently cannot use Intels own updators, and had to use Dells one and, it apparntly didn't update.
Update: well I'm shit outta luck, unless there is a way to force upgrade. Intel software won't allow me to update, and they say I need to use ones on Dells website, but they only had the old 23.20.16.4973 driver.
Well, fuck...
Update 2: Looks like I have a way.
Might report back tommorow however.
You can close thread, now more mad at Dell than anything.
Changed status from 'Open' to: 'Resolved'
Ok I'll close this one.
Feel free to create another report or reopen this if you cannot resolve it even updating the driver.