Blender 3.2/Blender 3.1 - Incorrect render of barcelone scene with BVH2 #96165

Closed
opened 2022-03-04 14:30:29 +01:00 by Nikita Sirgienko · 16 comments

System Information
Operating system: Windows 10/Windows 11
Graphics card: AMD RX 6600 XT, NVIDIA RTX 3070

Blender Version
Broken: reproduced stably for few weeks on latest commits on Blender 3.1 Beta (769ae5c866, blender-v3.1-release, 2022-03-03) and Blender 3.2 Alpha (5eaeb9bd0d, master, 2022-03-04)
Worked: unknown, possible Blender 2.93.8 LTS

Short description of error
GPU rendering backends that make use of BVH2 don't render the pabellon/barcelone scene properly - there are artifacts in GPU render for CUDA and HIP, which are not presented with CPU/Embree or Optix rendering.

Rendered image for visual confirmation:
CPU/Embree - correct:
pabellon_quality_problem_cpu.png

Optix (NVIDIA 3070) - correct (with the exception of the water):
pabellon_quality_problem_optix.png

CUDA (NVIDIA 3070) - incorrect:
pabellon_quality_problem_cuda.png

HIP (RX 6600 XT) - incorrect:
pabellon_quality_problem_hip.png

Exact steps for others to reproduce the error

  1. Get Blender 3.1 Beta or Blender 3.2 Alpha from official blender site (https://builder.blender.org/download/daily/)
  2. Get pabellon demo scenes from official blender site (https://download.blender.org/demo/test/pabellon_barcelona_v1.scene_.zip)
  3. Unzip the archive with scene and textures and open .blend file using Blender 3.1 Beta or Blender 3.2 Alpha binary
  4. Run CPU (or Optix) render and remember how correct result should look like
  5. Run GPU render (CUDA or HIP) and confirm differences from CPU render
**System Information** Operating system: Windows 10/Windows 11 Graphics card: AMD RX 6600 XT, NVIDIA RTX 3070 **Blender Version** Broken: reproduced stably for few weeks on latest commits on Blender 3.1 Beta (769ae5c866f32d7a224c141ed4e3e899a54ec150, blender-v3.1-release, 2022-03-03) and Blender 3.2 Alpha (5eaeb9bd0d4d21ab89f5519bba716c5aedc715fc, master, 2022-03-04) Worked: unknown, possible Blender 2.93.8 LTS **Short description of error** GPU rendering backends that make use of BVH2 don't render the pabellon/barcelone scene properly - there are artifacts in GPU render for CUDA and HIP, which are not presented with CPU/Embree or Optix rendering. Rendered image for visual confirmation: CPU/Embree - correct: ![pabellon_quality_problem_cpu.png](https://archive.blender.org/developer/F12897100/pabellon_quality_problem_cpu.png) Optix (NVIDIA 3070) - correct (with the exception of the water): ![pabellon_quality_problem_optix.png](https://archive.blender.org/developer/F12897120/pabellon_quality_problem_optix.png) CUDA (NVIDIA 3070) - incorrect: ![pabellon_quality_problem_cuda.png](https://archive.blender.org/developer/F12897102/pabellon_quality_problem_cuda.png) HIP (RX 6600 XT) - incorrect: ![pabellon_quality_problem_hip.png](https://archive.blender.org/developer/F12897105/pabellon_quality_problem_hip.png) **Exact steps for others to reproduce the error** 1. Get Blender 3.1 Beta or Blender 3.2 Alpha from official blender site (https://builder.blender.org/download/daily/) 2. Get pabellon demo scenes from official blender site (https://download.blender.org/demo/test/pabellon_barcelona_v1.scene_.zip) 3. Unzip the archive with scene and textures and open .blend file using Blender 3.1 Beta or Blender 3.2 Alpha binary 4. Run CPU (or Optix) render and remember how correct result should look like 5. Run GPU render (CUDA or HIP) and confirm differences from CPU render
Author
Member

Added subscriber: @Sirgienko

Added subscriber: @Sirgienko
Member

Added subscriber: @Stefan_Werner

Added subscriber: @Stefan_Werner
Member

Increasing the number of transparent render bounces makes CPU and GPU renders match again.

Increasing the number of transparent render bounces makes CPU and GPU renders match again.

Added subscriber: @Sergey

Added subscriber: @Sergey

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

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

Can confirm the issue.
Also reproducible on 3.0 so it is not really a stopper for 3.1, but still rather annoying issue.

Can confirm the issue. Also reproducible on 3.0 so it is not really a stopper for 3.1, but still rather annoying issue.
Author
Member

I have rechecked 3.0.1 and indeed it haven't' work there: I have got a misclick when I have tested it first time, so I have run CPU test instead of CUDA.
I have updated description accordingly.

I have rechecked 3.0.1 and indeed it haven't' work there: I have got a misclick when I have tested it first time, so I have run CPU test instead of CUDA. I have updated description accordingly.

@Sirgienko, One thing I forgot to mention in the previous reply. Shouldn't CUDA and Hip labels in the report say "Incorrect"?

@Sirgienko, One thing I forgot to mention in the previous reply. Shouldn't CUDA and Hip labels in the report say "Incorrect"?
Author
Member

In #96165#1317127, @Sergey wrote:
@Sirgienko, One thing I forgot to mention in the previous reply. Shouldn't CUDA and Hip labels in the report say "Incorrect"?

Yes, they should actually be "incorrect", yes. I have fixed it.

> In #96165#1317127, @Sergey wrote: > @Sirgienko, One thing I forgot to mention in the previous reply. Shouldn't CUDA and Hip labels in the report say "Incorrect"? Yes, they should actually be "incorrect", yes. I have fixed it.
Member

Added subscriber: @LazyDodo

Added subscriber: @LazyDodo
Member

The water in the optix render seems problematic as well, cuda and hip are pretty close to CPU there but not optix.

The water in the optix render seems problematic as well, cuda and hip are pretty close to CPU there but not optix.
Alaska changed title from Blender 3.2/Blender 3.1 - Incorrect CUDA/HIP render of barcelone scene to Blender 3.2/Blender 3.1 - Incorrect render of barcelone scene with BVH2 2022-03-04 23:14:09 +01:00
Member

Added subscriber: @Alaska

Added subscriber: @Alaska
Member

I just thought I would add an extra thing here. The issue isn't caused by the CUDA/HIP rendering backends, it's caused by BVH2 used by those backends. Hence it is also reproducible on the CPU if you change the backend to BVH2.

If you look at the scene from a different angle, you will notice that transparent objects, like the tree leaves, are much brighter when using BVH2 compared to other BVH's. This might be causing the issue you're experiencing. And if that's the case, then this report is quite similar to #95462 (Partly transparent objects appear to glow in the dark when HDRI environment lighting is present (BVH2/Some GPU rendering backends))

I just thought I would add an extra thing here. The issue isn't caused by the CUDA/HIP rendering backends, it's caused by BVH2 used by those backends. Hence it is also reproducible on the CPU if you change the backend to BVH2. If you look at the scene from a different angle, you will notice that transparent objects, like the tree leaves, are much brighter when using BVH2 compared to other BVH's. This might be causing the issue you're experiencing. And if that's the case, then this report is quite similar to #95462 (Partly transparent objects appear to glow in the dark when HDRI environment lighting is present (BVH2/Some GPU rendering backends))
Contributor

Added subscriber: @Raimund58

Added subscriber: @Raimund58

This issue was referenced by 04e89c5b06

This issue was referenced by 04e89c5b06739a9a507942e2a9c67fb59b975600

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Sergey Sharybin self-assigned this 2022-03-09 10:39:08 +01:00
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
7 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#96165
No description provided.