Artefacts when rendering with the GPU in Blender 2.90.2 and 2.83 release #77095
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
48 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#77095
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: Win 10 pro 64-bit
Processor: Ryzen 2700X
Graphics card: ASRock Radeon RX 580 Phantom Gaming X OC 8GB
RAM: 32 GB
Blender Version
Broken: 2.90.2 / 2.83.17
Worked: 2.82a
Bisecting shows
394a1373a0as the cause.Short description of error
When i am rendering using Cycles engine weird artefacts like in the image below are also rendered
Exact steps for others to reproduce the error
There are not specific steps , every image i try to render has the same outcome
Added subscriber: @p_one_snake
#81502 was marked as duplicate of this issue
#79025 was marked as duplicate of this issue
#78496 was marked as duplicate of this issue
#78249 was marked as duplicate of this issue
#77979 was marked as duplicate of this issue
#78063 was marked as duplicate of this issue
#77986 was marked as duplicate of this issue
#77972 was marked as duplicate of this issue
#77917 was marked as duplicate of this issue
#77769 was marked as duplicate of this issue
#77718 was marked as duplicate of this issue
#77482 was marked as duplicate of this issue
#77454 was marked as duplicate of this issue
#77412 was marked as duplicate of this issue
#77361 was marked as duplicate of this issue
#77343 was marked as duplicate of this issue
#77334 was marked as duplicate of this issue
#77321 was marked as duplicate of this issue
#77322 was marked as duplicate of this issue
#77319 was marked as duplicate of this issue
Added subscriber: @Alaska
Changed status from 'Needs Triage' to: 'Needs User Info'
A clean install of the latest AMD GPU drivers? https://www.amd.com/en/support
Unfortunately same result
Are you running any sort of overclock? If so, are you able to disable it?
Are you also able to test with factory defaults? Select from the top of Blender
File -> Defaults -> Load Factory Settingsand see if the issue persists.Assuming that doesn't work, are you also able to provide full system information? This can be done by selecting from the top of Blender
Help -> Save System Infoand uploading the file here.Are you also able to run Blender with debug options?
CMDand open the applicationCommand prompt--debug-cyclesand pressEnter.It looks like my problem is bigger than i anticipated , it isn't only the final render , the render view is messed up as well
I will answer the questions in order
My graphics card runs in stock settings.
I loaded the factory settings but it wasn't effective
Here you have the system info you asked for
system-info.txt
The debug results are here
Debug.txt
Changed status from 'Needs User Info' to: 'Needs Triage'
That is quite odd. Looking over your system information and the debug file, nothing stands out to me as the cause of the issue. This will most likely need to be investigated by someone with better knowledge than I do.
I'm kind of suspicious this may be a hardware failure. You could test this by underclocking your GPU and GPU memory. However, even then it's not certain that it will clarify things.
I wish you luck in getting this sorted. And hopefully it isn't some hardware failure.
Thanks but i am more inclined to believe that is a compatibility issue between newer versions of Blender and my graphics card , the older versions are not displaying this artefacts , i guess this will be sorted out in future versions , have a nice day !
Have a nice day
Sorry, I completely forgot about the working on 2.82a. Sometimes working on many different reports can cause them to blend together slightly.
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Strange that this works with previous versions of Blender.
I have the equivalent GPU from the previous gen (rx 480), but I cannot reproduce the problem.
I noticed however that your installed driver is a newer version than the one installed here.
Operating system: Windows-10-10.0.18941 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13586 Core Profile Context 19.50.01.05 26.20.15001.5006
Added subscriber: @Gromovsky
I have exactly the same problem in 2.83-2.9 with any drivers.
I also have rx 580. I wrote about this in this post:
https://blenderartists.org/t/very-slow-gpu-rendering-in-cycles-opencl-blender-2-81/1186239/132
https://blenderartists.org/t/very-slow-gpu-rendering-in-cycles-opencl-blender-2-81/1186239/120
My computer configuration:
CPU ryzen 2600
RAM: 16GB
GPU: rx 580 XFX 8gb
Windows 10 LTSC 1809
I recently did a clean install of the system to check for problems - the problem remains
@Gromovsky, can you provide the
system-info.txt(Help -> Save System Info) to we see if it is the same driver version?:4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017Added subscriber: @iss
Similar GPU here as well, can not reproduce. I have seen some reports for RX 580 that I could not reproduce.
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61
Adding bisect info from user
@ompaduon blender-coders channel:with the commit right before
394a1373a0it's okayi'll do a build with
394a1373a0as wellsymptoms include artifacting, image burn and computer hard locks
the gpu is at fault
windows 10, ryzen2700x, rx580
amd driver version is reccomended 20.4.2
@Germano Cavalcante
Yes there he is
system-info.txt
Added subscriber: @Germano
Removed subscriber: @Germano
Closed as duplicate of #77319
Changed status from 'Duplicate' to: 'Needs User Info'
Added subscriber: @SherlockXGP44
Added subscriber: @bobharlinton
Added subscriber: @radcatradcat
Artefacts when rendering with the GPU in Blender 2.90.2to Artefacts when rendering with the GPU in Blender 2.90.2 and 2.83 releaseAdded subscriber: @makoto3d
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
I filed the same report, AMD RX480, Latest drivers, the problem only appeared when tried to use 2.83, I tried with stock settings and with my personal clocks and nothing has changed. 2.82a works just fine.
I can reproduce it, I open a default scene, try to render the cube, sometimes the render comes out glitchy and with artifacts, and sometimes my computer freezes and have to force a shutdown.
Is anyone here willing to bisect versions of Blender to find the culprit?
To do this, you will need to setup a Blender build environment following this guide: https://wiki.blender.org/wiki/Building_Blender
Following that, switch to the Blender 2.83 branch using the command
git checkout blender-v2.83-releaseAfter that, start the bisecting process by running these commands:
git bisect startgit bisect bad HEADgit bisect good de0de9381d9b(This build is a few months old. I chose it simply so a large range of builds will be tested)makeThen test the Blender version. If you experience issues, use the command
git bisect badthenmakeand test again.If you don't have issues with a specific version, use
git bisect goodthenmakeand test until you get a specific commit.Added subscriber: @EAW
@Alaska It has already been done, it is commit
394a1373a0.I'll try tomorrow
@makoto3d
No need, as @EAW pointed out, the commit has been identified.
Added subscriber: @TNose007
Added subscriber: @volto
Added subscriber: @CustosLux
I have the same exact issues, the glitches even looks the same in my system! also older versions of blender seems to be working properly.
Added subscriber: @ompadu
Added subscriber: @higgsas
Added subscriber: @zonaweb
Added subscriber: @GeekyStudios
Similar Issues on RX 480 8GB on 2.83 Steam. Vertical line artifacts. Intel Denoiser in composite completely destroys the image.
Render:
Denoise output:
Issue does not exist when I use 2.82.
Added subscriber: @DragnautTheWick
Glad people are looking into this.
I have a Radeon RX 570 and this exact same issue occurs.
This issue is in Blender 2.83.0 and June 5's Blender 2.90.0. This issue is not in Blender 2.81.16
Added subscriber: @DM3NT3D
Added subscriber: @theburgman21
Hello there, I'm having the same issue on an Asrock RX 570 on an i7 6700K system with 32GB of ram. running Blender version 2.83.0
Find pictures attached
Hope it gets fixed
Thanks
CPU only:
OPENCL CPU+GPU:
OPENCL GPU only:
Edit:
I can confirm this error is new to Blender 2.83.0 (Doesn't reproduce on 2.82.7). Using latest AMD drivers (20.5.1)
Added subscriber: @Sbotkin
This comment was removed by @Sbotkin
Has anyone tried rolling their drivers back? @mano-wii’s Driver looks to be the one from December of 2019, and he has no issues. And @mano-wii and @iss, have you tried upgrading your drivers to see if you can reproduce the issue?
Just to contribute:
GPU: RX570
CPU: I7 770k.
Fresh windows install, latest AMD Driver, version 20.5.1 from 25/05/2020.
Artifacts in Blender 2.83, using cycles.
Everything ok in Blender 2.82a.
The issue is reproducing on the 20.4 version of drivers.
On older drivers is hard to reproduce, sometimes it does that lines thing, sometimes it does not, but for sure the PC CRASHES when doing the final render even of a simple cube, maybe it can do 1 frame but high chance the next frame crashes everything.
System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13572 Core Profile Context 19.11.3 26.20.13031.18002
With this machine, it seems I can't reproduce it in the viewport today, but every render (of the default startup scene) crashes the pc instantly.
just crashed 3 times and rebooted 3 times, it rendered 3 good frames of a simple plane and then the artifact started to show up.
rx 480, 19.11 driver
Added subscriber: @kulius
I have the exact same issue in Blender 2.83, rendering using an RX480 8GB with the latest 20.5.1 drivers.
It seems that the periodic stripes are not the only artifacts occuring, differently-colored reflections are also apparent on some surfaces as you can see in the image.
Added subscriber: @Akshat_42
I am also suffering from the same problem while rendering in cycles using both 2.83 and 2.90. I have a msi armor radeon rx570 8GB version and a ryzen 5 3600. The render shows small lines which are even more exagerrated to holes by the denoise compositing node. I tried it with the CPU and didn't had any problens. I tried underclocking and overclocking the gpu, I reinstalled the drivers but the problems were still there .
Before denoise (gpu compute)
With denoice (gpu compute)
(System Info)
system-info.txt
(Debug Info)
Debug Info.txt
Hope this gets fixed soon and I will have to rollback to 2.82a.
Added subscriber: @Reprevise
Added subscriber: @ramanamono
{F8606708}I get the same artifacting and often also system crashes.
I installed blender 2.83 installer on windows 10 version 1909
GPU XFX RX 580 4GB tested with driver 20.4.2 and 20.5.1
CPU Ryzen 5 1600 (orginal version)
With Blender version 2.82 I do not have this issue, now testing it with portable zip version.
So this is a all Polaris issue or only certain onces
Added subscriber: @Kjngo
Added subscriber: @jeanpal86
Same weird lines on a clean install of 2.83
Cpu: i7 8700k
Gpu: Asus Dual rx580 w/ 20.5.1 drivers
Using ProRender Radeon instead of Cycles, hopefully could be solved soon!
Added subscriber: @yangshuzhan
I previously wrote in here about this issue. I've made some progress. The rendering errors I had before are gone.
Before, I was using an Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, but have since switched to a AMD Ryzen 5 3600 CPU. I have kept the same GPU (Radeon RX 570) between exchanging my computer parts.
It is also worth mentioning, however, that I have also gotten a new motherboard-- I used to have some Gigabyte board and now have an Asus B450-F Gaming Board-- and I also got 16 GB of DDR4 memory instead of 16 GB of DDR3.
Sorry if too many factors have changed that would make this development less useful, but I thought it important to mention it.
Added subscriber: @nil99normal
Added subscriber: @Ritsumei
I have the same problem with Cycles in 2.83 version.
GPU: AMD Radeon RX 590, not overclocked. Latest drivers
CPU: AMD Ryzen 3700x
Blender 2.82 worked well.
Added subscriber: @GrimMask
I'm having the same problem with Cycles in 2.38 \
GPU: AMD Radeon RX 570 - not overclocked, latest drivers
CPU: AMD Ryzen 2700x
I just updated my Radeon software version to 20.5.1 and immediately noticed the artifacts. Before the update there were none.
It appears to only be an issue with the GPU, as when i render in hybrid, only some tiles contain the "artifacts"
When I render with the 570 alone, all tiles are corrupted with the "artifacts"
I'm a complete novice with blender, and don't know if this input helps, but I figured it couldn't hurt.
Added subscriber: @geoser
I got the same issue with both Blender 2.83/2.9a and Radeon RX580 with 20.4.2 driver and with the latest optional driver version as well.
Interesting that I solved it by increasing tile size to 512x512. I'm still not sure if it would work on all scenes.
Based on the view of the artifacts I suppose that the issue might be related to some precision of floating number calculations. And it can be corresponded to the tile size as well.
I read your comment So i test it for my self increasing the tile size to 512x512 and it dose reduce or sometimes gets rid of the line but there is still those other artifacts remaining.
Are you rendering GPU only? If you are rendering mixed CPU+GPU because the tiles are so big (512x512) you might not get any rendered on the GPU. I have tried rendering the bmw scene with 128x128, 256x256, 512x512 and 1024x1024 bucket size, GPU only and the artefacting is still there.
This was on a RX580.
I did it with GPU Only at 128, then 192 up to 512x512 any Higher will be Blue Screen of Death lol on my RX 570 4GB but the Artifacts are still there but slightly reduced it's like a bluish color noise, at 512x512 lines are mostly or almost gone but there still artifacts but even at 512x i would get blue screen i usually render at 128 or 192 Max tile size
It was GPU only. Thank you for your recheck, it seems the solution works only for very limited set of scenarios. Anyways I ended up with installing a previous driver from here , particularly version 20.2.2, and the artifacts are gone with any tile size.
I have tested with the 20.2.2 driver as well. The artifacts are gone on my end too.(rx580, ryzen 2700x, win10). I used to get artifacting with the 20.4.2 driver.
If the solution is blacklisting opencl 2.0 and falling back to 1.2, maybe it should be for the gpu/driver version combo? And maybe with giving the user a warning at "Settings/System/Cycles Render Devices/OpenCL" about the driver? Similar to the "No compatible GPUs..." at "Settings/System/Cycles Render Devices/CUDA".
Is there a contact between the Blender Foundation and the AMD people? Maybe they can help with the driver.
I had an automatic update, but I'm still not able to reproduce the problem either in the viewport or in the render (OpenCL).
Another possibility may be that my monitor is connected directly to the HDMI output of the GPU. (who knows)
Operating system: Windows-10-10.0.18941 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.19.02 27.20.1019.2002
Added subscriber: @AranMoreno
I´m also having the same problem with an AMD rx 590, and also crashes a lot when rendering on the gpu with openCL.
Added subscriber: @Werk
RX 580 ... ver 2.83..
Could everyone who reproduces the bug provide the
system-info.txt(generated inHelp -> Save System Info)?This will allow me to organize the description and can help to better identify what causes the problem.
system-info.txt
system info.zip
Here @mano-wii this one is while using a rx590
Here @mano-wii .system-info.txt
Here you go sir. Thanks! system-info.txt
system-info.txt
system-info.txt
There you go
system-info.txt
To me It is clear that the problem is in the driver.
A newer driver is available. Go there to install -> https://www.amd.com/en/support
Removed subscriber: @kulius
Added subscriber: @kulius
I have the most recent one, I´ll try to downgrade to their "recommended one" to see if fixes anything.
BUT He is working fine in version 2.82..
Here is my system-info.txt :
system-info.txt
Can you link what driver to download, because to my knowledge and as the the driver update tool says, I have the latest version. Or do you mean we have to wait till a new version gets released?
But if it is a driver issue, who is to report it to AMD then? Should we all report to AMD?
This makes no sense for two things.
First i already have the latest (both beta and WHQL both tested) drivers installed
And second this issue cannot be replicated in the previous version of Blender, even with this new drivers!!
This is the driver I was ussing before I downloaded 2.83. It was working fine in 2.82a
This comment was removed by @AranMoreno
Added subscriber: @Alirion-2
Same Problem here with 2.83 / 2.90 on a RX 480 8 GB - Win 10 - Tested Driver's 20.5.1 / 20.4.2
2.82 works flawlessly - no Issues at all. 2.83 causes Complete GPU Lockups / TDR's and thoose Artifacts as seen above - on some scenes its worse than on others. However i suspect it has something to do with the Wavefront or memory termination in relation to how Textures are stored in OpenCL 2.0. as the lines/artifacts appear pretty much exactly at 64px from eachother ( reflections and glossy etc. get influenced from this ofc. ) also tehy seemingly have random values ( different colors depending on usage / iteration ) which leads me to think theres somewhere a termination error or pointer starting too early - also the GPU crash leads to a Memory Access Violation regarding to the GPU Debugger.
I had the lastest driver, and also I downgraded to the recommended one, nothing seems to fix it, does anyone have a download link to the 2.82a? since Tomas seems to not have the bug on that one, every time I try to download 2.82 it redirects to 2.83 on the blender site, and the one on here https://download.blender.org/release/ doesn´t seem to be 2.83a and it has the same bugs.
I also have more details of the bug, it seems to happen only on certain view angles. It´s more obvius when facing towars x or y, anything on between doesn't happens as much.
I let my computer (Windows-10) do an automatic update and it installed this driver version for my
Radeon (TM) RX 480:4.5.13596 Core Profile Context 20.10.19.02 27.20.1019.2002From what I understand if the "Context" number is higher then the driver is more recent.
20.10.19.02 27.20.1019.2002>20.5.1 27.20.1017.1011But it seems that the driver available on the website is 20.5.1. So they will still update there.
Now for the questions of why it works in 2.82:
For better performance. Blender 2.83 now uses OpenCL C 2.0 see
394a1373a0https://download.blender.org/release/Blender2.82/
The issue seems to be worst now, at least for me.
Before I was able to render at least, and now the whole sistem freezes to black screen or blinking screen and I have to reboot my machine.
I tried to remove all drivers using amd clean tool, an then later, used only the windows update driver. Same problem. Then I've installed Radeon Software and the recomended driver, 20.4.2, same result: Artifacts.
Looking for openCl Bugs over the internet, seems that something documented at AMD Comunity Forum, but I'm not a Developer related to Graphic cards thing things, like blender developers are, so I Cannot say if it's related to blender problem.
One thing I would like to ask is:
as it is a major problem on latest blender release for ADM users (at least the videocards listed), Is it possible let the users choose between OpenCL 1.0 and OpenCl 2.0?
Sorry If I'm suggesting something out of reality.
So far it's only been a problem of the Polaris cards? RDNA is working fine? a month ago the seemed to have the same problem even on blender 2.82. This is my first amd card and probably the last since this. https://blender.stackexchange.com/questions/175770/cycles-gpu-opencl-render-has-square-white-artifacts-and-strange-lines-on-an-amd
Removed subscriber: @geoser
I've reported this to AMD. It's been a month since this bug was found.
Added subscriber: @SickadtSteve
RDNA uses a newer OpenCL Stack, however this is a Cycles problem. as Radeonprorender, Luxcorerender and all my other OpenCL Apps are running totally fine, stable and performant. Bugs happen and with enough reports they eventually get fixed - besides not even all addons are running in 2.83 yet so. Eh! if your on the bleeding Edge then expect bugs. The only shame is that this did not get properly tested for an "LTS" Release.
I discovered another bug that might be related to this one since it shows an OpenCl error, on 2.90 while being on render view, just go to the "view object types" menu and hide Mesh, it will corrupt the render view with an error message that can bee seen on the second screenshot. Something similar happens on blender 2.82 but no error message comes up, on 2.83 will crash with no warning.
Added subscriber: @ankitm
If you still need it: system-info.txt
Added subscriber: @brecht
Thanks all for the system info, it seems this is about RX 4xx and 5xx cards specifically. I've committed a workaround for those based on the info.
The latest 2.90 builds on https://builder.blender.org/download/ have the fix, please let me know if this solves the problem since I don't have this hardware to confirm myself.
I confirm. The freezes and the atifacts are gone now.
RX570 here.
I confirm.
GPU RX590. Works well
yes,I GOOD ,RX580
I also confirm. RX 590. The problem is gone.
Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
Thanks, I'll consider this resolved then. Hopefully in the future AMD can provide a driver fix for this, so we can remove our workaround.
Artifacts are gone on rx 590.
They forget they older cards very quickly, I reported the bug to them, hopefully many people will do the same to make enough noise to fix the problem, but it feels improbable coming from Amd, there a are many problems with Polaris reported on their forums, and never gets fixed, I haven't seen a rx 590 patch note in a while, and it was the most recent Polaris card.
It works on my RX580, but for some reason my Ryzen 1600 renders a lot faster, and I'm not sure if that's normal.
I also noticed that, gpu render seems slower.
Tested blender-2.90.0-6899cb3c073e-windows64, rx580 , problem still remains.
Could you upload your system-info.txt please?
The Artifacts are Gone in Blender 2.90 Alpha Works Great
no More Artifact
Here is My System Info: system-info.txt
Does this workaround is planned to go to LTS 2.83?
Yes, it will be added to 2.83 LTS.
Changed status from 'Resolved' to: 'Confirmed'
Re-opening to investigate performance.
It works for me too but render time more than double, maybe there is some setting in 2.9 to speed it up...
Enabling OpenCl and use it only with the cpu with no gpu has any benefits than using none?
Can confirm that GPU crashes have stopped when using GPU to render on Cycles, but performance is still worse than CPU.
Using default cube on a metallic plane render times:
CPU: 00:40.93
GPU: 00:57:51When rendering a personal project of mine, the results are much worse:CPU: 0:49:09
GPU: 1:10:08.61
All results were captured using
system-info.txt
Just for Help
RX570
Core i7 7770k
At least for me, the render times are equal. Both rendered with Cycles and GPU.
2.82a: 13:34:33
2.90 (with the fix): 13:17:22
.
Same file rendered
RX 580 8Gb 20.5.1 drivers
GPU BMW scene 240x180 tiles:
6899cb3c07GPU Class scene 256x256 tiles
6899cb3c072.3 version with artifact was almost twice as fast, but I guess its only because of artifacts
2.3 with artifacts
2.9
No it's faster because it's using OpenCL 2.x and older versions are using OpenCL 1.x. I guess with the latest 2.9 build, it is switched again to OpenCL 1.x for Polaris GPUs.
Hopefully this is a temporary workaround and the much faster OpenCL 2.x gets fixed for Polaris GPUs.
I've rolled back my AMD drivers to older versions which seems to be working just fine. IMO i prefer to keep my drivers outdated (haven't notice a difference in performance) and use blender 2.83 with openCL 2.x
Which version did you downgraded to?
Version 20.2.2 WHQL seems to be working just fine! as said by other users in this post.
I am using a RX 480.
You can find it here .
I confirm, rolling back to 20.1.3 with an rx 590 fixed the artifacts and crashes for me, from 20.2.2 and up the bug appears with rx 590, I think Opencl 2.0 shouldn't be disabled for rx 4xx, 5xx cards, rolling back the drivers seems much better workaround and we can use the benefits of opencl 2.0 in newer blender versions, and let´s inform amd and wait for a fix. @brecht
Render times for scenes with artifacts in 2.83 are meaningless and not useful for comparison. Comparing between CPU and GPU also doesn't tell us if there is a performance regression or just possible room for future optimization.
The useful times to compare are with a previously working Blender version.
I agree. I've been testing some of my scenes and i'm getting lots of performance enhances in 2.83 with OpenCL 2.x
I have been testing all drivers for rx 590 and this is what I found.
20.5.1 ❌ artifacts
20.4.2 ❌ artifacts
20.4.1 ❌ artifacts
20.3.1 ❌ artifacts
20.2.2 ✔ no problems
20.1.3 ✔ no problems
20.1.1 ✔ no problems
All drivers from 20.2.2 and prior will fix the artifacts, 20.2.2 is the last recommended driver by amd, is not that old, we shouldn´t have problems rolling back to that version, at least for a while.
I almost sure that it will be the same case for rx 580, 570 and below.
Thank you for sharing your findings. Have you found any issue in 20.2.2? Weird if you do since i am unable to find any issues with those drivers in my RX 480.
My bad, it was 20.2.2, it works fine.
Awesome! so it seems to be an AMD side issue, sadly i feel that this is not gonna be fixed any time soon from AMD since this is old hardware :/ Still i'm gonna report this and hope for the best.
Maybe is an error that was there and was only detectable with blender 2.83, and since it came up just recently, there wasn't a way to let amd know before, their drivers are shared between Polaris and most recent rdna, I think we still have a big chance to get noticed.
Added subscriber: @rhuanhianc
I am using a RX 480 and Driver 20.2.2 WHQL
Test 2.83 05:32.86
Test 2.90.0-6899cb3c073 05:48.15
Test 2.82a 05:49.79
not tested on updated drivers because they are locking my pc
I Tested my Project and these are the Results for Each Versions:BenchMark blender.txt
and a Screenshot of the Drivers for GPU:
I can confirm the issue is no longer present on an RX 570 AMD driver 20.5.1
GPU: AMD RX 580
AMD Driver version: 20.2.2
Blender version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash:
211b6c29f7, type: ReleasePlatform: Windows
With the 20.2.2 AMD driver, everything works fine, performance is great, a lot better than on the "fixed" 2.90 release. Maybe until AMD fixes this issue, there could be two Blender versions, one with the fix, and one without it.
of course the 2.83 LTS is the one with the Artifacts
Grabbed 20.2.2 now and it indeed perfroms fine on that and FAST ( using teh OpenCL 2.0 Build ). i have made a Report to the Driver Team pointing to this Thread. What strikes me a bit odd is that every other Software ( uncluding RPR which uses OpenCL 2.0 also ) runs fine even with 20.5.2. The Performance of Cycles on OpenCL 2.0 is awesome now tho. Will continue testing on Linux.
Added subscriber: @Assasinatorczar
@Alaska downgrade to driver 20.2.2, the bug is not there.
Added subscriber: @ZeeKhar
I confirm it work on RX 480 graphic card.
GPU: AMD RX 480
AMD Driver version: 20.5.1
version: 2.90.0 Alpha, branch: master, commit date: 2020-06-19 23:28, hash:
874af5301c, type: Releasebuild date: 2020-06-19, 22:40:03
platform: Windows
Downgrading the graphics card drivers is no an option for me, buttons on other software disappear on the tabs like Adobe and some other giltches...
20.2.2 is working bad for you? I´m also using the adobe suite and I have not seen problems. The only thing we can do is keep sending error reports and wait, I also created a post on their forums but no attetion from them https://community.amd.com/message/2982927
Added subscriber: @colesdav-1
I had GUI glitches as well immediately after downgrading. Buttons and text missing in my case. It fixed itself after a computer restart. Maybe try a clean driver reinstall?
Downgrade driver to 20.2.2 does not work for me. Still getting random freezes
Did you made a clean install? I still had some issues until I uninstalled the graphics driver with ddu uninstaller, also I don´t know which graphics card do you have, maybe is different.
Guys if you still have issues with drivers, i recommend using AMD PRO drivers, they are specifically designed to be stable and have the best performance for design workloads.
I use some of the features inside the Adrenalin drivers so i'm sticking with 20.2.2 at the moment but i've tested the PRO Drivers and they work like a charm. No issues, problems or inestability this far. And my performance is the same, even at games! So if you're not using some features incorporated in the Adrelanin drivers i suggests to switch to PRO drivers.
Removed subscriber: @Reprevise
Added subscriber: @Wekita
I just thought I would weigh in on this discussion since I'm having the same problems myself. I have both 2.79 and 2.83 Installed on my machine, and I'm running a RX550 on an older FX4300 CPU with 16gig DDR3 1600mhz ram. ( surprisingly capable machine ) However, every time I try to render cycles, mostly with the preview render as I never get to a full render, blender hangs up, computer crashes and restarts. I've tried AMD Drivers 20.1.3, 20.2.2, as suggested, and am now currently running 20.5.1 and all give the same results. Except 20.5.1, I get a BSOD from that driver version. I've tested cycles in 2.79 and no problems. Everything renders fine. In fact 2.79 seems to render better in cycles than 2.82 did. Which also didn't have this problem. So my guess is there's some bad bug's in 2.83 cycles engine. I hope this gets fixed soon, This has stopped my project in its tracks because I can't use cycles and I don't want to go back to 2.82. I don't know how to do a dump file so I can't give any more information than that. - Oh, and there are no PRO drivers for my card.
Thank You for your attention.
Thank you. I've Installed here PRO Drivers for my RX570 And now everything seems to work smooth again. I'm new to AMD world, I didn't knew about PRO Drivers.
Added subscriber: @farhad995
I also switched to the Pro driver (20.Q2.1) for RX 580 and works, no artifacts and really fast too. More than twice as fast as blender 2.82 in some scenes.
So OpenCL 2.x works fine on Polaris. I hope the workaround to switch back to OpenCL 1.x is not going to be implemented in the 2.83 LTS, or at least a switch to choose between the versions.
Or maybe recommend that the Pro driver should be used for Blender.
The bug is gone in 1.83.1, but I guess it's due blocking opencl 2.0 for polaris cards right?
Hopefully not! if they did that i will have to stick with 2.83.0 i really get used to this performance boost.
This issue was referenced by blender/cycles@3f8e42c268
This issue was referenced by
2822744b0bThis issue was referenced by
2d8c59ccb9Added subscriber: @BeatBreakerS
I'm able to render with GPU now on 1.83.1, but viewport cycles is giving me the following artifacts on GPU mode, CPU cycles runs fine.
Also if we try to switch out of GPU cycles via going to CPU or Eevee blender gets huge ram and CPU usage then just freezes.
system-info.txt
Massive performance regression between 2.83.0LTS and 2.83.1LTS,
With the bmw27_gpu demo file render time goes from 182sec to 270sec (not counting kernel compilation).
windows 10 2004, RX 580 4GB and Ryzen 1600
GPU driver: Radeon pro driver enterprise 20.q2
It makes RX 580 completely useless for rendering as my CPU is faster than my RX 580 graphics card with the new 2.83.1LTS maintenance update.
Changed status from 'Confirmed' to: 'Resolved'
Added subscriber: @T-hamma-T
Added subscriber: @Arturo-5
Using Pro Driver 20.Q2.1 with RX 470. No artifacts, but I experiment random freezes after some graphic corruption on screen. Long renders have a higher possibility to cause the problem. I don't remember having this problem on Blender versions previous to 2.83. by the way, on all versions I see a much higher GPU memory consumption when rendering using OpenCL. On my other computer CUDA takes one third that memory.
Both 2.83 and 2.83.1 have random freezes, although 2.83 renders much faster. Haven't tested 2.90.
I also tested 20.2.2 drivers and also had random freezes with no artifacts on 2.83 and up
I'm currently rendering a big image using 2.82.7 and everything is going ok after 40 minutes.
So, for me, the conclussion is that there is something wrong both in blender (2.83 and up) and AMD GPU Drivers,
AMD's prorender doesn't have any artifact. I think the problem is not about drivers. By the way , this bug is not resolved yet.
Well, looks like I'll be stuck on 2.82 for awhile longer. This is Blender 2.83.2 running on a FX-4300 CPU with a RX-550 Graphics card, Windows 10 2004, GPU Driver Version 20.5.1.
Rendering with CPU only seems fine, but awfully slow ( 15+ Min. 1080p ) even compared to 2.82 which is a bit faster. But as soon as I switch to GPU ( OpenCL ) Render, this happens...
I think it's safe to say cycles is really broken.
Have you tried using AMD PRO DRIVERS instead? Devs seems to have applied a fix to enable OpenCL ONLY if you're using AMD PRO DRIVERS (this only applies for Polaris GPU's)
I don't think there are any Pro drivers for my card. ( RX-550 ) I looked and couldn't find them online.
Oh, wow just checked w/ GPU Z and it says Polaris 21. Revision FF ( Whatever that means ). Ok, so how do I find Pro drivers for this thing ?
Update Well, don't I feel like a dummy. I just found it. I'll try it out and update this thread when I'm done.
Update 2 NOPE! Blender Hung, crashed, and the computer went black and restarted. I'm telling ya'll, I'm cursed. If there's a worst case scenario for anything, it will happen to me.
Oh, but the new Pro driver does great with ver-2.82 though. Awesome results. 1080p under 5 min. That's good for this old machine.
Sorry for the late response. Here is a download link for the latest AMD pro driver. https:*www.amd.com/en/support/kb/release-notes/rn-pro-win-20-q2-1
I would suggest to perform a clean installation using AMD cleanup utility or DDU.
If you look up your Card using AMD’s driver search on their website, it is the third driver listed. Clicking on the
release noteslink leads you to a page that only lists the compatible Pro GPUs (at least on mobile that is). I know I found this confusing. There is another link that is hard to find, that takes you to the longer pdf version of the release notes. It lists theRX500series as compatible on page 13.https://drivers.amd.com/relnotes/amd-radeon-pro-software-for-enterprise-20.Q2.1.pdf
AMD fixed the bug!, at least on my rx 590 while running the new driver ver. 20.70.1, tested on blender 2.83.0, so @brecht theres is no need to keep the workaround of not using opencl 2.0 for polaris cards.
I'll try running the new drivers and blender 2.83 before the polaris blacklist. Will report later, hopefully they revert this change.
@AranMoreno I am glad to hear that it is fixed for you. @brecht has set this workaround to only affect OpenCL drivers 3075.12 and lower. Can you upload your system-info-txt file to show the OpenCL driver that the AMD driver 20.70.1 has? I don’t have the hardware to check it myself.
system-info.txt
Open CL is now 3110.7 on 20.70.1, It is definitely solved in rx 590 and rx 580, I am not sure in other rx 5xx or rx 4xx. So we are using all the capabilities of Opencl 2.0 if we are using a driver higher than 3075.12? @EAW
@makoto3d The change to only affect OpenCL drivers 3705.12 and lower is in Blender LTS 2.83.2. Download it here. It was added in
2822744b0bThank you for confirming!
Assuming I am reading the patches correctly: If you are using Blender 2.83.2, and have your GPU selected as the render device, then yes the OpenCL 2.0 kernels will be built and used for Cycles.
Just and update... Just tried out the radeon 20.7.1 driver and still crashes on my RX550. Even Pro driver doesn't work. My computer locks up, crashes and restarts. I can render CPU, but its terribly slow. I even ran a few bench test's on my GPU just to see if maybe there was something wrong with my card, ( GPU Caps Viewer ) but there wasn't any problems as far as I can tell. All my games and graphics software run fine too. Just thought I'd let ya'll know.
This comment was removed by @AranMoreno
Did you tried a clean driver install with DDU unistaller?
After figuring out what DDU was, I downloaded it and used it to reinstall my driver. RESULTS: The first attempt to render my test scene Blender crashed, But not my computer this time. ( YAH! ) 2nd time was successful however I did get a few white dots in the render. So I tweaked a few settings and and 3rd time I got a good render at 1080p and in ~3 min. Really Cool. Less than half the time as in 2.82. So next I tried the classic BMW render. I only sat through about 8 min. of but stopped the render because it was estimating 30 min. render. Too long. But what it had rendered out at that point looked good. No artifacts.
I'm no programmer, but I would recommend going over the render code one good time to make sure everything is correct. But that's just me. Hopefully this problem is fixed. I'll know after using it a few days.
Now if only I can fix my view port problem and things will be perfect. I do thank ya'll for your time and help.
20.7.1 seems to have fixed most of the stuff - altho there's some memory corruption going on ( random pixel sampling / crashing / video corruption ) if out of core rendering is used with blender 2.83.2 on Polaris / Win10.
Your file consumes a lot of video memory?
Added subscriber: @raindance
Can confirm that the 2020.5.1-june10 driver works on my Radeon RX 590. No artifacts.
Odd that it did not work for AranMoreno though. Maybe the issue is more than just GPU-related?
Can confirm that with the new AMD Drivers it works wonderfull, now my RX 480 renders even 2% faster than my i7 6700k.
I use that AMD radeon software 20.7.2 ,on blender 2.83，look like everything is fine。Im RX 580
RX470 Using 20.7.2 Drivers (after DDU)
No artifacts (dots)
Still random crashes on 2.83.2 and 2.90. Maybe a bit more stable.
With 2.83.2 I managed to finish a 5m render. Then it froze the next time.
On 2.90 it completed a render but one of the buckets had half the bright. The next time it froze while showing a similar artifact on a different bucket.
2.82 is still perfectly stable
Added subscriber: @(Deleted)
Blender 2.83.1 - 2.83.3; OS Windows 10 1909; graphics card AMD RX460 2GB VRAM, drivers Adrenalin 20.7.2 (also tested 20.7.0, 20.7.1, and 19.12.1) installed after DDU.
Viewport rendering on mildly complex scenes doesn't work: it can't get past the first sample, UI elements disappear, and doing anything that starts a new render freezes Blender (you must force close it). For some reason, switching to CPU rendering during a GPU viewport rendering doesn't freeze Blender. Using a render border (CTRL+B) is considered as simplifying the scene.
Normal rendering works (even without tiles, on the same scene that viewport rendering crashes on), but during rendering drivers sometimes randomly crash: this causes a black screen, after which all Blender window become white and you must force close it.
Added subscriber: @TashaSkyUp
blender 2.83.3 + 5700xt + amd driver 20.7.2 = crash on changing to cycles. (after about 1 minute wait)
Added subscriber: @EAMMN
Same here, but with RX 580, and with AMD driver 20.4.2 artifacts appears. However, both driver versions seems to be working fine in Blender 2.82.7
I'm also still having problems with crashes with 2.83.3 & 2.9 Beta on my RX 550. ( Driver version 20.7.2 ) Been having this from the beginning. I had to disable GPU rendering all together because of it. CPU rendering is real slow and heats up my CPU.
Is this a Blender problem or a Driver problem ? Does anyone know ? Radeon cards seem to be the hardest hit by this.
Where is 2.82.7 ? I didn't even know there was one...
Added subscriber: @Insertcoin.tv
We tested lot of drivers, Radeon Pro Duo 32gb polaris + 580, and while 2.82 is ok, from 2.83+ to 2.90, we got random crash and instability, not usable for us sadly.
We must work with 2.82 atm.
This comment was removed by @Wekita
Removed subscriber: @TNose007
Update Note: Running Blender 2.83.4 under Windows 10 using the AMD Drivers 20.7.2 on RX 480 8 GB seems to work with optimizations. I get no crashes so far ( 1 day ) - viewport 1 sample stop bug is gone. rendering so far works fine ( out of core wont work anymore but for now its fine ). So far also no lockups / hard crashes anymore for me.
Heads up Devs and Thanks <3 !
RX470 4GB, 20.7.2 Drivers, Blender 2.83.4. Blender can't even finish one single bucket with GPU. It hangs forever and sometimes corrupts video. 2.82 is OK.
I did that. And I've just done it again. Same result. By the way, when GPU is undervolted (I use to keep it undervolted to lower temperatures) it freezes almost instantly. With default voltage values I managed to render the default cube scene 2 times at 400%. Then I thought the problem was the undervolting configuration, but then I tried with a relatively heavy scene and it froze again, graphic corruption, etc. I noted that it had to compile some aditional kernels which were not needed to render the default cube scene.
I've just tested the same scene with 2.82 and everything was fine.
It catches my attention the high memory consumption when rendering with OpenCL. I managed to render this scene on a 950GTX GPU with 2GB taking just 1,5GB. With OpenCL it takes almost 100% of my 4GB RX470.
I think a lot of optimization is needed here.
Same result with 20.8.1 drivers.
I'm starting to assume that this issue will never be addressed. So ok, probably I will never enjoy the extra performance derived from using OpenCL 2.0. That's 'ok' for me, but I don't want to stick forever with Blender 2.82. Is there any way to configure latest Blender versions to fall back to OpenCL 1.2?
On the other hand, probably I will never acquire another AMD GPU, It's not the first time I feel abandoned in relation with drivers compatibilty or some obscure issue. It's a pity, I really love Wattman and its posibilities.
Ok - i noticed one thing that is STILL a Problem and could be what plagues your Project Files. When using bigger Projects that use like all of the Vram there's massive Adress error's until it goes out of vmem range and this leads to bad pixels -> crash. This especially happens when another program or Blenders Viewport via OpenGL is reserving GPUMemory. So there's something flunky still and due to that there is no out of core currently running some older Projects may crash or dont render at all. I can replicate this using the Cosmos Laundromat Production Benchmark - Or a medium sized file and a game or 3D App next to it. First corruption happens and then bam -> adios GPU driver sys. So there IS still something very wonky in the way cycles adresses memory it seems as RPR for example nor Lux have ANY issues like this. Ill do a quick linux test now to see what happens there when filling up the vmem. But i suspect it has something to do with the order buffers are reserved in windows vs in linux ( top to bottom register/adressing or bottom to top ).
ok using the amdgpu-pro drivers v 20.20 under linux does seem to have no isssues in that Regard whatsoever. Using the 20.20 drivers under linux seems to have still the same adress issues ( altho i dont have the same debugging on linux going i believe its not a problem there but i yet have to work a bit more with it - fresh install ). Under linux filling the vmem party with an OpenGL context and then using cycles does only lead to a CL_Adress error ( basically out of memory ) but no crash or corruption. Under windows it looks like part of the other applications context memory or sometimes even the display buffer memory is overwritten by cycles data ( judging from some of the artifacting as they look like parts of buffers or texturwe snippeds shortly before the system locks up and restarts the gpu subsys. This STILL is present in 2.83.4 <- LTS
Still with 20.8.1 drivers I noticed some differences (between AMD and nVidia) using BlendLuxCore 2.4. Although the render looks good, some materials have radically different colors. On my AMD the upholstery of a chair renders green and with nVidia (2 different cards) renders red. There are some other materials presenting this issue apart from the fact that the image renders a bit darker. I've used Hallbench example scene. It could be a Lux's bug.
Apart from that I hadn't any issue related to video corruption or freezing using Lux. I thing it uses OpenCL 1.2.
PBR_Shaders_crash.blend This Scene/Material for example renders in final and crashes in Viewport. On Win 10 / Driver 20.7.2 Blender 2.83.4
This is an issue with the volume absorption node. I get the same error in a new file with simple principled shader, transmission turned up and volume absorption added. Driver 20.7.1 Blender 2.83.4 - LTS
This though seems like a separate issue that isn't related to the artifacts this thread was made for. Maybe I'm wrong, but I don't think it would hurt reporting this separately.
Removed subscriber: @Insertcoin.tv
Removed subscriber: @SherlockXGP44
Added subscribers: @AIMI-SAYO, @ismapic, @PANCHO7532
Added subscriber: @moybit
happens to my old RX 580 SP, RX 5600, RX 5700 XT
its an AMD driver issue
nothing you can do
No theres somethign wonky in the cycles implementation. i ve been thru many drivers now and all that i get working on teh Opencl 2.0 code have that. Also it seems to be fixed by teh daily build for rendering but not for viewport. If driver related i am asking myself why radeonprorender , luxrender etc. dont have crashes like that or artifacts etc. Its definitivelyl somethign cycles does - i mean it crashed very occasionally in Opencl 1 even - The Volume implementation never really got fully fixed i feel. Apart from Volumes the latest daily seems to run fine for now - will report back once i have tested it a bit more than just a day.
Added subscriber: @nerdPower
I have tried tons of stuff, but I still cannot get it to work. I am using an RX580. I just can't get my renders to work! It looks like I will have to use cpu. Sigh
Edit: After installing version 20.12.1 of the drivers, it works!!!
Edit: Except only in render window, not viewport :(