After updating the video card drivers to 20.11.2, interface artifacts appeared. #82856
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
51 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#82856
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?
{F9329300}System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: Radeon RX 590 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003
Blender Version
Broken: version: 2.83.9, branch: master, commit date: 2020-11-11 06:30, hash:
4abfc0bcd5Worked: (newest version of Blender that worked as expected)
Short description of error
Multiple artifacts can appear [see merged reports and see below]
Exact steps for others to reproduce the error
After updating the video card drivers to 20.11.2, interface artifacts appeared
Possible workaround: downgrade GPU driver
We had more user state that enabling Render Properties > Performance > High Quality Normals avoids the drawing issues with Eevee.
Added subscriber: @aaj
#86541 was marked as duplicate of this issue
#85683 was marked as duplicate of this issue
#85408 was marked as duplicate of this issue
#85320 was marked as duplicate of this issue
#84945 was marked as duplicate of this issue
#84905 was marked as duplicate of this issue
#84904 was marked as duplicate of this issue
#84881 was marked as duplicate of this issue
#84846 was marked as duplicate of this issue
#84829 was marked as duplicate of this issue
#84727 was marked as duplicate of this issue
#84697 was marked as duplicate of this issue
#84662 was marked as duplicate of this issue
#84526 was marked as duplicate of this issue
#84533 was marked as duplicate of this issue
#84199 was marked as duplicate of this issue
#84572 was marked as duplicate of this issue
#84557 was marked as duplicate of this issue
#84497 was marked as duplicate of this issue
#84456 was marked as duplicate of this issue
#84490 was marked as duplicate of this issue
#84412 was marked as duplicate of this issue
#84378 was marked as duplicate of this issue
#84351 was marked as duplicate of this issue
#84352 was marked as duplicate of this issue
#84337 was marked as duplicate of this issue
#84311 was marked as duplicate of this issue
#84304 was marked as duplicate of this issue
#84293 was marked as duplicate of this issue
#84292 was marked as duplicate of this issue
#84285 was marked as duplicate of this issue
#84261 was marked as duplicate of this issue
#84258 was marked as duplicate of this issue
#84212 was marked as duplicate of this issue
#84186 was marked as duplicate of this issue
#84193 was marked as duplicate of this issue
#84176 was marked as duplicate of this issue
#84172 was marked as duplicate of this issue
#84138 was marked as duplicate of this issue
#84082 was marked as duplicate of this issue
#83947 was marked as duplicate of this issue
#83714 was marked as duplicate of this issue
#84069 was marked as duplicate of this issue
#84070 was marked as duplicate of this issue
#84055 was marked as duplicate of this issue
#84060 was marked as duplicate of this issue
#84048 was marked as duplicate of this issue
#84026 was marked as duplicate of this issue
#84022 was marked as duplicate of this issue
#83978 was marked as duplicate of this issue
#83994 was marked as duplicate of this issue
#84007 was marked as duplicate of this issue
#83987 was marked as duplicate of this issue
#83961 was marked as duplicate of this issue
blender/blender-addons#83958 was marked as duplicate of this issue
#83955 was marked as duplicate of this issue
blender/blender-addons#83937 was marked as duplicate of this issue
#83463 was marked as duplicate of this issue
#83881 was marked as duplicate of this issue
#83485 was marked as duplicate of this issue
#83910 was marked as duplicate of this issue
#83920 was marked as duplicate of this issue
#83841 was marked as duplicate of this issue
#83717 was marked as duplicate of this issue
#83766 was marked as duplicate of this issue
#83770 was marked as duplicate of this issue
#83742 was marked as duplicate of this issue
#83703 was marked as duplicate of this issue
#83746 was marked as duplicate of this issue
#83738 was marked as duplicate of this issue
#83641 was marked as duplicate of this issue
#83574 was marked as duplicate of this issue
#83596 was marked as duplicate of this issue
#83204 was marked as duplicate of this issue
#83543 was marked as duplicate of this issue
#83517 was marked as duplicate of this issue
#83521 was marked as duplicate of this issue
#83484 was marked as duplicate of this issue
#83259 was marked as duplicate of this issue
#83418 was marked as duplicate of this issue
#83410 was marked as duplicate of this issue
#83437 was marked as duplicate of this issue
#83438 was marked as duplicate of this issue
#83416 was marked as duplicate of this issue
#83393 was marked as duplicate of this issue
#83261 was marked as duplicate of this issue
#83194 was marked as duplicate of this issue
#83272 was marked as duplicate of this issue
#83211 was marked as duplicate of this issue
#83088 was marked as duplicate of this issue
#83086 was marked as duplicate of this issue
#83128 was marked as duplicate of this issue
#83053 was marked as duplicate of this issue
#83066 was marked as duplicate of this issue
#83016 was marked as duplicate of this issue
#82891 was marked as duplicate of this issue
#82888 was marked as duplicate of this issue
#82926 was marked as duplicate of this issue
Added subscriber: @rjg
Changed status from 'Needs Triage' to: 'Needs User Info'
We currently have two other reports that reports graphics glitches with this particular driver version #82891, #82888. Please check if a previous version of the graphics driver fixes the problem for you.
Added subscribers: @maxdemon, @lichtwerk, @Alaska, @Bodi
Added subscriber: @Alegol
Changed status from 'Needs User Info' to: 'Confirmed'
Added subscriber: @danni-4
Added subscriber: @Jeroen-Bakker
Classify add this driver to limited support.
Installed the old driver version (recommended by AMD). The problem disappeared.
Added subscriber: @BlenderMaster-2
Old driver version solve the problem for me.
Added subscriber: @gilgaMesh98
Added subscribers: @Razvan, @Raimund58
Added subscriber: @Island
Added subscriber: @SOLO444K
Added subscribers: @YuriAOF, @Kiactus
Added subscriber: @gartist41
Added subscriber: @Horkos
Added subscriber: @VestaPhoenix
Added subscriber: @American_Grayman
Added subscriber: @gsdkskhs
Added subscriber: @SmokyDVI
Added subscriber: @greydemon
Added subscribers: @vivosan, @APEC, @leomiranda518
Added subscriber: @DoctorHazard
Added subscriber: @takytube
good job everyone!
Maybe is a problem of the 500/400 series.
I have in another computer a 5700 Xt, with the latest driver release everything work fine (20.11.3)
I can't try it on my 480 now...
Anyone can try this release?
Added subscriber: @Ryujin
Removed subscriber: @vivosan
Added subscribers: @Panfranco, @Ruk1a
Added subscriber: @ODoutor
Added subscriber: @KuroChu
Removed subscriber: @Ruk1a
Removed subscriber: @American_Grayman
Added subscriber: @Ajkad
Added subscribers: @bugsheep, @chingis
Added subscriber: @jonvito
Added subscriber: @Marcelo
Same problem on 480
Added subscriber: @DoctorRyanB1
Yes, I have the 480. Problem is I have rolled back my drivers and performed a system reinstall to no effect. Not sure what the heck is going on. Also all versions of Blender is doing it.
Added subscriber: @Bigman
Update. Rolling back drivers before 20.11 does fix the Blender rendering issue for now. Now we have to hope AMD gets this fixed.
Added subscriber: @ExtremeCaliber
I tried this workaround, it worked for me.
https://blenderartists.org/t/blender-eevee-not-working-2-8-2-90-for-me/1270834/3
Removed subscriber: @Island
Added subscriber: @ALCATRANZ
Added subscribers: @earthsam, @oxfefi
We had more user state that enabling Render Properties > Performance > High Quality Normals avoids the drawing issues with Eevee.
Added subscriber: @KalleNaksi
Added subscribers: @AdriGG16_VTS, @EAW
Removed subscriber: @jonvito
Added subscriber: @recalcitrantReaper
Added subscribers: @JSpeling, @RetroVertex
The issue might be related to a driver issue when using
GL_INT_2_10_10_10_REV. The work around of enabling High quality normals would solve this for mesh rendering. When selecting High quality normalsGL_SHORTis used for tangent and normals on meshes. This still leads to rendering errors in curves and meta balls as they still use the low quality normals.See here an example the Cube is rendered correctly, but the curve and metaball is rendered incorrecly as the normals cannot be uploaded.
The work around would be to implement HQ normals for all other geometry types and automatically enable high quality normals for specific drivers and GPUs.
I am able to reproduce this issue on linux also...
#82856.blend
Added subscribers: @Realowlg, @nacioss
I have found the perfect solution.........I went and bought a NIVIDA GTX Card. Lol.
Removed subscriber: @nacioss
Added subscriber: @Wanalienc
Added subscriber: @Estefano
Added subscriber: @ShadowGaster
Added subscribers: @emmanuelbarros43, @Alirion-2
Added subscriber: @GoldWings
Added subscribers: @brick1ng5654, @ToyMaster, @user1, @mano-wii, @Attryst, @FelixKutt, @Danfer-Adrian, @Wovchick, @john-vi-cryde, @elasesinoanda, @RoyKCarollJ456, @Wynbax, @GoldyTheClown, @KenzieMac130, @HamzaYigitKultur-1, @Mefwhesk, @iss
Removed subscriber: @Kiactus
Added subscriber: @HorseGlass
Added subscriber: @BanannedDude
Added subscriber: @Khaled4te
Added subscriber: @JYoshi
Added subscriber: @chub321
Added subscriber: @dixson3
Added subscribers: @PatrickWhite, @CreatorSiSo
Added subscriber: @Zohaib
Removed subscriber: @Bodi
Added subscriber: @Valentix
Added subscriber: @Jamexx
Added subscriber: @kurisuna
Added subscriber: @DrkCrb
Added subscriber: @devsgamingzone
Added subscriber: @BykovSer
Added subscriber: @Hannah-Umit
Can someone close task #83947 as a duplicate because i cant find this task here in the close as duplicate window.
Added subscriber: @polybots
Added subscriber: @gevorgsargsian
Added subscriber: @Bobo_The_Imp
Added subscriber: @Askinperson5423
Removed subscriber: @Zohaib
@Jeroen-Bakker I see you've added me as a subscriber, if you need a tester for something just @ me with clear instructions. I've a RX 470 8gb in my system.
Added subscriber: @maSK
Added subscribers: @paracosm-1, @U32, @MCAN
Removed subscriber: @APEC
Added subscriber: @iamcapmurica
Removed subscriber: @HorseGlass
Added subscriber: @aftamat4ik
Added subscriber: @KainThornn
Added subscriber: @Mateja
Removed subscriber: @U32
Added subscriber: @JSartu
Added subscriber: @xiq
Added subscriber: @darksmokei666
Added subscriber: @AaronB-4
Added subscriber: @FancyRacoon
Removed subscriber: @DoctorHazard
Added subscribers: @Synergeia, @Defess
Added subscriber: @dgosling
Removed subscriber: @PatrickWhite
Added subscriber: @Roykz792
Added subscriber: @Streak
Added subscriber: @Balaji_X
Added subscriber: @Ali420
Added subscribers: @Raoni1212, @k3ziah
Added subscriber: @Atlas020
Added subscriber: @Brunomendesgussoni
Added subscriber: @noureldin
Bro what to do i am having serious problem in viewport
Have you tried rolling back drivers like others have suggested?
yes sir working on it but plz contact with AMD or do some tweaks its really hard working on cycles
Added subscriber: @untz_the_bard
Added subscriber: @Ixed91
Added subscriber: @ridberg
Added subscriber: @AlexanderProcenko
When this issue will be fixed? AMD say that Blender team must do patch for Blender. What say Blender team?
I updated to Blender 2.9x and my issues resolved.
{d11a87b88c4d} makes adds support for High quality normals to non-meshes (curves/metaballs/volumetrics). Next step is to auto enable high quality normals when using the mentioned platforms.
Added subscriber: @lightbl
Removed subscriber: @Raimund58
In master there is now a fix available. The fix isn't tested with an Polaris card. I can verify that the fix works later this week when I have access to the hardware.
NOTE: the detection for the work around isn't complete as we need the exact renderer that is reported by the driver. Most reports that have used the help -> report a bug menu item has been added to the detection.
@rjg: I would suggest to wait for my test and confirmation from users and after that close this ticket.
Will test with my RX 470 tomorrow, seems the buildbot hasn't built the latest yet.
How do I get this fix?
@Jeroen-Bakker Will do.
@Brunomendesgussoni The daily builds of Blender 2.92 can be downloaded from here . You will have to wait until tomorrow though, as the build bot will create the new build around midnight.
Added subscriber: @Flampcakes
rx580(20.12.1), windows 10, Blender 2.92.0 Alpha, still have issue with eevee and cycles
With high quality normals won't the render time increase?
@AlexanderProcenko Like I said, you would've had to wait until today. The current build that is now available contains the workaround. Please download and test again.
System Information
Operating system: Windows-10-10.0.10586-SP0 64 Bits
Graphics card: AMD Radeon R7 200 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.12.1 27.20.14501.28009
Blender Version
2.92.0 Alpha, branch: master, commit date: 2021-01-04 23:35, hash:
9b17e71c23AMD Radeon R7 200 here, 20.12.1, windows 10 , blender 2.92.0 Alpha- can confirm that this workaround solve this issue so far for me.
Thank you very much for helping us with this issue!
Seems fine over here.
Removed subscriber: @ExtremeCaliber
version: 2.92.0 Alpha, branch: master, commit date: 2021-01-04 23:35, hash:
9b17e71c23, type: Releasebuild date: 2021-01-04, 23:11:02
Windows 10 Pro 64 19042.685
Rx 580 8Gb
Software version: 2020.1204.0703.12704
It seems to work well.
Thanks all for testing!
It could in very complex scenes, but not sure it will be noticeable. A normal is stored in 32 bits in low quality and in 48 bits in high quality.
Added subscribers: @KetoSuuja, @filedescriptor
Added subscriber: @draegdrwg
This did not seem to fix the wireframe overlay being invisible for me in any mode other than edit (which seems to have been merged into this bug report?), in any renderer, even with high quality normals enabled.
I have previously fixed the problem by downgrading my graphics drivers.
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.12.1 27.20.14501.28009
version: 2.92.0 Alpha, branch: master, commit date: 2021-01-04 23:35, hash:
9b17e71c23Sorry, I realise this build was probably not meant to deal with this issue, just thought I'd mention.
This report has become a collection of multiple different errors introduced with the AMD drivers. As far as I can tell there are 3 categories:
Perhaps it is better to separate this ticket into 3 subtickets to be more clear?
Its a mirracle! Last alfa daily build of Blender good working on 20.12.1! rx580 I LOVE YOU!:)
@Jeroen-Bakker The Cycles OpenCL one should definitely be a separate one. I was entirely under the impression this' a viewport/EEVEE one.
edit: Aaaand I can confirm that the wireframe overlay doesn't work in object mode. Nor setting the object display to wireframe. Or switching viewport shading from solid shading to wireframe.
Toggling
Hidden Wirein overlays while in editmode does work though.@Jeroen-Bakker Huh, just enabled face normals in editmode and those aren't showing up either. I think there is a wider issue with overlays here. Still the same system with RX 470.
Yes, also on my system too. Radeon RX 580.
AMD really mucked up a lot.
Added subscriber: @hellboundkrytonite
Added subscriber: @BeastUndead
Added subscriber: @Topher50
Added subscriber: @ujjwal_singh
Added subscriber: @Ganke
Added subscriber: @A113-2
Added subscribers: @Marwan-4, @RC12
Added subscriber: @Allllffffonnnzzzzzzooooooooooooooo
Added subscriber: @olayrocx-1
Added subscriber: @adamsrib
Added subscriber: @Zoltantan
This happens to me as well ( material preview is all grey as well ).
My specs:
System Information
Operating system: Windows-10-10.0.17763-SP0 64 Bits
Graphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.12.1 27.20.14501.28009
Blender Version
Broken: version: 2.91.0, branch: master, commit date: 2020-11-25 08:34, hash:
0f45cab862Going to try 2.93.0 alpha and let you know the results
Update1
2.93.0 alpha works fine
2.92.0 Beta doesn't
Update2 - Jan 15 2021
2.93.0 alpha works fine
2.92.0 Seems to be working today,-Beta doesn't-
Added subscriber: @mondix
I had the same issue.
I downloaded 2.92 Beta today and I can confirm this is working now.
AMD Radeon RX 580 Series 8GB Sapphire
Software Version
2020.1204.0703.12704
Driver Version
20.45.01.28-201204a-361901C-RadeonSoftwareAdrenalin2020
Added subscriber: @Harukaki
Removed subscriber: @RetroVertex
Added subscriber: @whlop
Added subscriber: @matheus.orlandi
Added subscriber: @NiceClockBro
Added subscriber: @bened
Removed subscriber: @Ixed91
Blender 2.91.2
GPU- Radeon RX590
Driver - 20.11.1
When setting these parameters in the Modeling window in render mode, the system crashes.
Removed subscriber: @Hannah-Umit
Added subscriber: @Underfoxy666
Added subscriber: @Cleron
Hi, I have the same problem, but I don't know how to fix it.
@Cleron please don't claim tasks. This option is for assigning developers who will work on solving the issue.
There is already a workaround implemented in 2.92. Until it is released you can either downgrade your graphics driver to 20.11.1 or enable Render Properties > Performance > High Quality Normals, as already explained in the ticket and comments.
Hi, sorry, I didn't understand what I was doing, and thanks for the support.
Removed subscriber: @mondix
Added subscriber: @sdasdasdas
Added subscriber: @CorradoPiscitelli
Added subscribers: @Tinannic, @Diogo_Valadares
Added subscriber: @fifiamo16
Radeon Software Adrenalin 2020 Edition 21.2.2 Highlights
Fixed Issues
Objects may fail to render correctly when using EEVEE render in Blender™ on Radeon RX 400 and Radeon RX 500 series graphics products.
I will download and test, will it work?
Updated the drive 21.2.2, EEVEE now works, but in Cycles the program crashes.
Added subscriber: @Core-2
Added subscriber: @Dempred
Added subscriber: @Garek