AMD GPU + Cycles + Branched Path Tracing + Reflective Caustics = Render Tiles Bug #72864

Closed
opened 2020-01-03 07:27:51 +01:00 by RJ Nievera · 16 comments

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: f1aa4d18d4
Worked: (optional)

Short description of error
AMD GPU + Cycles + Branched Path Tracing + Reflective Caustics = Render Tiles Bug

Exact steps for others to reproduce the error

  1. Have an AMD GPU
  2. Have multiple glossy / reflective objects
  3. Have an HDR environment
  4. Have Reflective Caustics On
  5. Have Branched Path Tracing On
  6. Render with Cycles Hybrid Tiled ( CPU + GPU )

*Unchecking Reflective Caustics will make error tiles disappear.

Tested on:
R9 380X - bug present
RX 480 - bug present
RX 580 - bug present
Firepro M6100 - bug present
GTX 960M - no bug
*all on Windows 10 64bit

AMD Drivers:
Adrenalin 19.10.1 to 19.12.2
Enterprise 19.Q4.1

renderBug.png

cycles_cuda_opencl_test2.blend

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: `f1aa4d18d4` Worked: (optional) **Short description of error** AMD GPU + Cycles + Branched Path Tracing + Reflective Caustics = Render Tiles Bug **Exact steps for others to reproduce the error** 1. Have an AMD GPU 2. Have multiple glossy / reflective objects 3. Have an HDR environment 4. Have Reflective Caustics On 5. Have Branched Path Tracing On 6. Render with Cycles Hybrid Tiled ( CPU + GPU ) *Unchecking Reflective Caustics will make error tiles disappear. Tested on: R9 380X - bug present RX 480 - bug present RX 580 - bug present Firepro M6100 - bug present GTX 960M - no bug *all on Windows 10 64bit AMD Drivers: Adrenalin 19.10.1 to 19.12.2 Enterprise 19.Q4.1 ![renderBug.png](https://archive.blender.org/developer/F8257537/renderBug.png) [cycles_cuda_opencl_test2.blend](https://archive.blender.org/developer/F8257543/cycles_cuda_opencl_test2.blend)
Author

Added subscriber: @rjnievera

Added subscriber: @rjnievera

#80700 was marked as duplicate of this issue

#80700 was marked as duplicate of this issue

#70501 was marked as duplicate of this issue

#70501 was marked as duplicate of this issue
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

I can reproduce the artifacts on an AMD Radeon RX 5700 on Windows. However, the artifact pattern looks different to yours. Furthermore, when I render the image twice, I get exactly the same result. Do you get different results on different AMD GPUs?

untitled.png

I can reproduce the artifacts on an AMD Radeon RX 5700 on Windows. However, the artifact pattern looks different to yours. Furthermore, when I render the image twice, I get exactly the same result. Do you get different results on different AMD GPUs? ![untitled.png](https://archive.blender.org/developer/F8277705/untitled.png)

Added subscriber: @mont29

Added subscriber: @mont29

This might actually be more like known limitation (afaik, AMD OpenCL is still lagging behind…), but let’s #Cycles team decide here.

This might actually be more like known limitation (afaik, AMD OpenCL is still lagging behind…), but let’s #Cycles team decide here.
Author

Subsequent renders on the same scene/frame produces different artifact patterns. This was on an RX 480.

renderBug RX 480 01.png

renderBug RX 480 02.png

Subsequent renders on the same scene/frame produces different artifact patterns. This was on an RX 480. ![renderBug RX 480 01.png](https://archive.blender.org/developer/F8281167/renderBug_RX_480_01.png) ![renderBug RX 480 02.png](https://archive.blender.org/developer/F8281169/renderBug_RX_480_02.png)

Added subscriber: @cr00k

Added subscriber: @cr00k

I can confirm the same issue using Radeon VII and Threadripper 2950x in Windows 10, blender 2.82.7. AMD Radeon driver 19.10.1 and latest 20.4.1.

Workaround is to select only one OpenCL Render Device (Edit > Preferences > System). Either GPU or CPU. I found out that the final render is slightly different using only GPU (darker) or only CPU > hence, mixing both CPU and GPU results in tiles (every time different "tiling" result, due to slightly different sampling).

Hope it helps.

Here are some examples from the legendary donut tutorial :)

Only GPU
onlyGPU.png

Only CPU
onlyCPU.png

Both
bothGPU-CPU_v2.png
bothGPU-CPU_v1.png

I can confirm the same issue using Radeon VII and Threadripper 2950x in Windows 10, blender 2.82.7. AMD Radeon driver 19.10.1 and latest 20.4.1. Workaround is to select only one OpenCL Render Device (Edit > Preferences > System). Either GPU or CPU. I found out that the final render is slightly different using only GPU (darker) or only CPU > hence, mixing both CPU and GPU results in tiles (every time different "tiling" result, due to slightly different sampling). Hope it helps. Here are some examples from the legendary donut tutorial :) Only GPU ![onlyGPU.png](https://archive.blender.org/developer/F8485591/onlyGPU.png) Only CPU ![onlyCPU.png](https://archive.blender.org/developer/F8485594/onlyCPU.png) Both ![bothGPU-CPU_v2.png](https://archive.blender.org/developer/F8485592/bothGPU-CPU_v2.png) ![bothGPU-CPU_v1.png](https://archive.blender.org/developer/F8485595/bothGPU-CPU_v1.png)
Added subscribers: @ColeMorris, @brecht, @zaster, @atomedia, @AaronSmithey, @mano-wii

The issue here is that data allocated by closure_alloc_extra is not being properly copied in split/kernel_branched.h.

This is rather tricky since this data contains pointers which would also need to be remapped, or removed so that we don't need to remap them.

The issue here is that data allocated by `closure_alloc_extra` is not being properly copied in `split/kernel_branched.h`. This is rather tricky since this data contains pointers which would also need to be remapped, or removed so that we don't need to remap them.

Added subscriber: @BlackYps

Added subscriber: @BlackYps

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'

OpenCL and branched path tracing were removed in Blender 3.0, the new unified CUDA/HIP kernels will not have this problem.

OpenCL and branched path tracing were removed in Blender 3.0, the new unified CUDA/HIP kernels will not have this problem.
Sign in to join this conversation.
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
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#72864
No description provided.