Maniphest T48028

GPU Compute in Cycles is broken on AMD stable drivers and Blender stable release
Closed, Archived
Actions

Assigned To
Thomas Dinges (dingto)
Authored By
Adrian (afl_ext)
Apr 1 2016, 12:45 PM
Tags
  • BF Blender
Subscribers
Adrian (afl_ext)
Jeffrey Engelstad (jaxom)
Mauro Castaldi (kastaldi)
Mischa Alff (MrAster)
Stefan Wojtyna (StefanW)
Thomas Dinges (dingto)
Vuk Gardašević (lijenstina)

Description

System Information
Windows 10 x64 Pro
Radeon R9 380 4G

Blender Version
Broken: 2.76b
Worked: On AMD drivers from last year

I have already reported this bug in the past, but it was ignored because AMd drivers were not stable then.
Now it happens on certified stable driver release, and on blender stable release.
The problem is: If you use GPU compute on AMD GPU with Cycles, the sampling is broken and results in visible horizonral artifacts instead of normal noise.

Exact steps for others to reproduce the error
I attach the simplified project here, just hit F12 to render again with AMD:

bug.blend502 KBDownload

Here is also the errornous render result:

Please don't say again that you don't care, apparently a lot of people use their AMDs to render things and WONT want to downgrade drivers.

Thank you.

Related Objects

Mentioned Here
rBf337feaf5a1d: BLender 2.76: We go 'b' series now
rB22a2853b5d56: Blender 2.77: Point submodules to an updated hashes
rB29bb10ee964a: Fix transform center2d for 2d views
rBf185effa1507: Buildbot: Explicitly disable tests on all platforms

Event Timeline

Adrian (afl_ext) created this task.Apr 1 2016, 12:45 PM
Adrian (afl_ext) raised the priority of this task from to 90.
Adrian (afl_ext) updated the task description.
Adrian (afl_ext) added a project: BF Blender.
Adrian (afl_ext) edited a custom field.
Adrian (afl_ext) added a subscriber: Adrian (afl_ext).
Mischa Alff (MrAster) added a subscriber: Mischa Alff (MrAster).Apr 1 2016, 2:33 PM

I get the same issue on Windows 8.1 x86-64, AMD Radeon R7 200 series with latest AMD drivers, and Blender 2.76b.

Adrian (afl_ext) added a comment.Apr 1 2016, 2:43 PM

I also tested 2.77 f185eff build version and it's still the same

Thomas Dinges (dingto) added a subscriber: Thomas Dinges (dingto).Apr 1 2016, 8:25 PM

Can you both confirm, that 2.76 is broken too?

Because in that case, I doubt it is Cycles fault. Blender 2.76b is several months old, and we did not get such reports back then. Which means, the issue is in the driver, and yes we cannot fix that.

Thomas Dinges (dingto) merged a task: T48031: Blender AMD viewport and render bug..Apr 1 2016, 8:25 PM
Thomas Dinges (dingto) added a subscriber: Stefan Wojtyna (StefanW).
Stefan Wojtyna (StefanW) added a comment.Apr 1 2016, 9:12 PM

I tested it on version 2.76 and 2.76b
So probably there's something with the latest AMD Driver :/

Adrian (afl_ext) added a comment.Apr 1 2016, 9:18 PM

Please consider that AMD won't give a damn about such issue. Maybe there is easy workaround? It looks like compute work group X dimension is read incorrectly. I'm not familiar with Cycles code to test solutions.

Thomas Dinges (dingto) lowered the priority of this task from 90 to Low.EditedApr 1 2016, 9:27 PM

Maybe there is a workaround, but such Driver issues are very difficult and time consuming to find. Time we should spend on other things. If AMD cannot get their act together, that is unfortunate for both developers and users, but that is simply not fixable from our side.

For now, I suggest to downgrade the driver and test an older one.

Vuk Gardašević (lijenstina) added a subscriber: Vuk Gardašević (lijenstina).Apr 1 2016, 9:27 PM

Tested the same file on Linux and Windows. Same machine, dual boot.
R7 360, X3 455 8 gig ram

Linux:
Xubuntu 15.10 Driver Packaging Version 15.201.1151-150908a-188977E
Blender Build 2683dd8

Windows 7 64-bit
Driver Packaging Version - 16.15-160307a-300321E
Blender Build 29bb10e

Windows has installed the non-WHQL 16.3 driver from 09.03. The horizontal lines are very noticable in the render preview/render on lower samples; after a while they clean up, but still can be noticed. First image is after 5 samples, the second one after 144.

Linux (Older) Driver, on the other hand, doesn't have that problem. Even on lower samples.

Adrian (afl_ext) added a comment.Apr 1 2016, 9:42 PM

I fired a ticket to AMD support but well, I can only expect that if stars constellation is fortunate I will see the fix in next year :)

Jeffrey Engelstad (jaxom) added a subscriber: Jeffrey Engelstad (jaxom).Apr 2 2016, 3:55 AM

Just tested on
blender-2.77-f185eff-win64
Windows 10
AMD 7970 6gb
AMD Driver 16.3.2

GPU Render no settings changed.
No artifacts in the render other then normal noise.

Adrian (afl_ext) added a comment.Apr 2 2016, 11:17 AM
In T48028#367886, @Jeffrey Engelstad (jaxom) wrote:

Just tested on
blender-2.77-f185eff-win64
Windows 10
AMD 7970 6gb
AMD Driver 16.3.2

GPU Render no settings changed.
No artifacts in the render other then normal noise.

Are you completely sure you have GPU compute enabled? I tested exactly this driver version, on the same os and the same Blender version, and got the bug.

Mauro Castaldi (kastaldi) added a subscriber: Mauro Castaldi (kastaldi).Apr 2 2016, 10:05 PM

Same issue on

Blender 2.76b build f337fea
Blender 2.77 build 22a2853

AMD R9 390 NITRO 8 mb,
AMD Crimson driver version 16.3.2
Driver Packaging Version 16.15.2211-160321a-300865C

O/S Windows 10 64 bit

Does anyone know the latest working AMD drivers version ?

Adrian (afl_ext) added a comment.Apr 2 2016, 10:46 PM
In T48028#367934, @Mauro Castaldi (kastaldi) wrote:

Same issue on

Blender 2.76b build f337fea
Blender 2.77 build 22a2853

AMD R9 390 NITRO 8 mb,
AMD Crimson driver version 16.3.2
Driver Packaging Version 16.15.2211-160321a-300865C

O/S Windows 10 64 bit

Does anyone know the latest working AMD drivers version ?

http://support.amd.com/en-us/kb-articles/Pages/AMD-Radeon-Software-Crimson-Edition-16.1-Hotfix-Release-Notes.aspx
This is the latest version working, I use it now and it works.
Keep in mind that cleaning up after Crimson drver is PITA, be sure to uninstall it via control panel and then switch the driver in device manager to something older, so installer won't spot new driver already in place.

Jeffrey Engelstad (jaxom) added a comment.Apr 3 2016, 12:46 AM

Adrian.

Yes I am positive I am Using GPU Render on my system.
User preferences OpenCL Device is set to (Tahiti)
and your default settings in the file you submitted has the Render settings of supported and GPU Compute.
Works fine on my system. it may be a Problem with the new AMD GPU's as I see you have the R9.

Mauro Castaldi (kastaldi) added a comment.Apr 3 2016, 10:47 AM

Adrian thank you, 16.1 Crimson drivers work like a charm.

Thomas Dinges (dingto) changed the task status from Unknown Status to Archived.Apr 3 2016, 10:54 AM
Thomas Dinges (dingto) claimed this task.

Closing this then, as it is a driver issue, and that is simply not fixable by us.