Eevee anti-aliasing artifacts on Intel HD Graphics 620 #55205
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#55205
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
Windows 10, Intel HD Graphics 620
Blender Version
Broken: Blender 2.80
41cba97( Date 2018-05-17 02:04 )Short description of error
When Eevee in Rendered mode, when the image is static and tries to anti-alias, issues appear around certain zones of the objects ( where the anti-aliasing would be taking place ) like small randomly coloured rectangles. It's as if those areas of the screen are getting rendered in an incorrect texture format.
When actively rotating the scene, no issues show and Eevee looks great. It's only when the scene is static that the issues appear.
The issue happened with the default ( latest ) Windows 10 driver, and also with the latest one installed from their website ( Driver Date: 16/05/2018, Driver Version 24.20.100.6094 ).
Added subscriber: @MalDuffin
A bit more info - the same thing is shown when in Edit mode.
Also, when you first switch over to rendered view, the initial viewport is a bit whacky looking, until the first refresh.
Added subscriber: @LazyDodo
Changed status from 'Open' to: 'Archived'
Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.
Ah, no probs :) I had raised another bug before I read this. Where is the best way to report issues like this? I know the Intel graphics chipsets aren't as powerful as NVidia / ATI, but they are more common.
you can't report issues currently, there's just too many problems, answering 50 tickets a day about the things we already know are broken is just too time intensive, once it stabilizes out we'll open the tracker for bug reports, but there's no timeline on that currently.
Gotcha :)