CPU and GPU tiles do not have the same light rendering #91570

Closed
opened 2021-09-21 14:47:16 +02:00 by Pablo · 15 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68
Graphics card: NVIDIA GeForce GTX 1060
CPU : AMD 5900X

Blender Version
Broken: version: 2.93.4, branch: master, commit date: 2021-08-31 09:23, hash: b7205031ce
Worked: (newest version of Blender that worked as expected)

Short description of error
When I run a CPU+GPU render I sometimes get a bug on the final tile render.
It happens randomly on my projects and the only solution to avoid this problem is to render only on the GPU or CPU.
According to my tests, this does not come from the denoiser, addon...

If I open a new blender with a cube, a plane, and a similar texture sky the problem does not appear, if I import in addition the same scene FBX, still no problem. But if the bug appears in one of my projects while before all work correctly then it is impossible to make it disappear.

Exact steps for others to reproduce the error
210526P VILLA ROQUES 01.blend
No_Bug_Tiles_CPU+GPU_FBX_IMPORT.png

No_Bug_Tiles_CPU+GPU.png
Bug_Tiles_CPU+GPU.png

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68 Graphics card: NVIDIA GeForce GTX 1060 CPU : AMD 5900X **Blender Version** Broken: version: 2.93.4, branch: master, commit date: 2021-08-31 09:23, hash: `b7205031ce` Worked: (newest version of Blender that worked as expected) **Short description of error** When I run a CPU+GPU render I sometimes get a bug on the final tile render. It happens randomly on my projects and the only solution to avoid this problem is to render only on the GPU or CPU. According to my tests, this does not come from the denoiser, addon... If I open a new blender with a cube, a plane, and a similar texture sky the problem does not appear, if I import in addition the same scene FBX, still no problem. But if the bug appears in one of my projects while before all work correctly then it is impossible to make it disappear. **Exact steps for others to reproduce the error** [210526P VILLA ROQUES 01.blend](https://archive.blender.org/developer/F10527416/210526P_VILLA_ROQUES_01.blend) ![No_Bug_Tiles_CPU+GPU_FBX_IMPORT.png](https://archive.blender.org/developer/F10527642/No_Bug_Tiles_CPU_GPU_FBX_IMPORT.png) ![No_Bug_Tiles_CPU+GPU.png](https://archive.blender.org/developer/F10527641/No_Bug_Tiles_CPU_GPU.png) ![Bug_Tiles_CPU+GPU.png](https://archive.blender.org/developer/F10527406/Bug_Tiles_CPU_GPU.png)
Author

Added subscriber: @PabloCio

Added subscriber: @PabloCio

Added subscriber: @PeterBaintner

Added subscriber: @PeterBaintner

Cannot confirm:

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41
Amd Ryzen 3900x

Blender Version
2.93.4, branch: master, commit date: 2021-08-31 09:23, hash: b7205031ce

From what I saw, have you tried updating your graphics card driver?

Cannot confirm: **System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41 Amd Ryzen 3900x **Blender Version** 2.93.4, branch: master, commit date: 2021-08-31 09:23, hash: `b7205031ce` From what I saw, have you tried updating your graphics card driver?

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

Does the issue happen with master? Cycles-X was merged today 0803119725, maybe that fixes your issues?

Does the issue happen with master? Cycles-X was merged today 08031197250aeecbaca3803254e6f25b8c7b7b37, maybe that fixes your issues?
Author

In #91570#1223057, @PeterBaintner wrote:
Cannot confirm:

From what I saw, have you tried updating your graphics card driver?

I just installed the latest GPU driver and I still have the same problem.

> In #91570#1223057, @PeterBaintner wrote: > Cannot confirm: > > From what I saw, have you tried updating your graphics card driver? I just installed the latest GPU driver and I still have the same problem.
Author

In #91570#1223075, @ThomasDinges wrote:
Does the issue happen with master? Cycles-X was merged today 0803119725, maybe that fixes your issues?

I did not try, Cycle-X is not stable enough for my intensive use.

> In #91570#1223075, @ThomasDinges wrote: > Does the issue happen with master? Cycles-X was merged today 08031197250aeecbaca3803254e6f25b8c7b7b37, maybe that fixes your issues? I did not try, Cycle-X is not stable enough for my intensive use.
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

@PabloCio Cycle-X is now in Blender 3.0 Alpha and reflects the latest official version of Cycles.
It is helpful for developers to test if the latest Alpha contains the bug that you are experiencing.

You can download the latest alpha version here: https://builder.blender.org/download/daily/

@PabloCio Cycle-X is now in Blender 3.0 Alpha and reflects the latest official version of Cycles. It is helpful for developers to test if the latest Alpha contains the bug that you are experiencing. You can download the latest alpha version here: https://builder.blender.org/download/daily/
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Related report: #89351, #85078

Judging by these reports it looks to be an issue with large objects, try to scale your whole scene down to see if that fixes the issue.

Related report: #89351, #85078 Judging by these reports it looks to be an issue with large objects, try to scale your whole scene down to see if that fixes the issue.

Closed as duplicate of #89351

Closed as duplicate of #89351

Closed as duplicate of #85078

Closed as duplicate of #85078

Added subscriber: @brecht

Added subscriber: @brecht

The issue here is the large plane. The simple solution is to subdivide large planes a few times. Scaling down the scene should not be needed.

The issue here is the large plane. The simple solution is to subdivide large planes a few times. Scaling down the scene should not be needed.
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
5 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#91570
No description provided.