CUDA 10.2 and GTX 1080 render artifacts with path tracing #74423
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#74423
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: Linux-5.3.0-7629-generic-x86_64-with-Ubuntu-19.10-eoan 64 Bits
Graphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44
Blender Version
Broken: version: 2.83 (sub 6), branch: master, commit date: 2020-03-04 04:24, hash:
fb330dd110Worked: 2-3 days ago
Short description of error
One of the recent changes to Cycles has introduced a Path Tracing sampling error when using CUDA on a 1080.
It does not happen with an RTX 2080, and also not when using OptiX. It also does not occur when using BPT.
Exact steps for others to reproduce the error
Open this file and render. cycles_cuda_bug.blend
Added subscriber: @sebastian_k
#75967 was marked as duplicate of this issue
#74471 was marked as duplicate of this issue
#74464 was marked as duplicate of this issue
Added subscriber: @brecht
Changed status from 'Needs Triage' to: 'Needs User Info'
I can't reproduce this with the
3da2dc8213build from builder.blender.org/download/, using Quadro RTX 5000.I can't find a buildbot build with revision
fb330dd110, is this a custom build?Added subscriber: @machieb
Can not reproduce with blender-2.83-31aefdeec5a6 build from yesterday.
Windows 10 Pro
Geforce 1080 Ti
Geforce GTX Titan X
Driver: 440.97
Hm, that's weird. I just did a fresh build (
cd0a6ff5c4), and still have the issue. I have 3 cards, two 1080 and one 2080. I can test with both GTX cards and the issue is always there, just not with the RTX. I also have no patches or so applied.Can you test with the buildbot build, so we know if the difference is in the build or the hardware/drivers?
Added subscriber: @SteffenD
Might indeed be the 10.2 toolkit, as @SteffenD mentioned in the other report. I just tried with buildbot and that one renders without issues.
Added subscriber: @Stefan_Werner
Does not reproduce for me either with RTX Q4000, CUDA V10.2.89, gcc version 7.4.0, Nvidia drivers 440.33.01.
It's probably not CUDA 10.2 itself but something else.
@sebastian_k since you're making your own builds, do you have the time to
git bisectthe commit that introduced the bug?Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Added subscriber: @pmoursnv
It's not unusual for new CUDA toolkit versions to give us bugs like this, and us having to fix or work around it. Sometimes it's a bug in Cycles, sometimes it's a bug in CUDA.
git bisectmay reveal the issue, but to me it seems unlikely to have been a recent commit.CUDA sampling bug with Path Tracingto CUDA 10.2 and GTX 1080 render artifacts with path tracingIt looks like this is the solution. In my case removing CUDA 10.2 and installing 10.1 got rid of the artefacts.
Removed subscriber: @machieb
If 10.1 does get rid of the error, than I also think it is not a recent commit. I did install 10.2 recently, shortly before @Stefan_Werner committed the progressive multi-jitter. If thought it was because of that, but yeah, it seems more likely that the new cuda toolkit is indeed the culprit.
I plugged in my GTX 1080Ti and
git blamepoints to the commit that brought the PMJ sampler:https://developer.blender.org/rB409074aae56138f49ce078ce919a6d02e44e521e
It reproduces with the scene attached to this bug, regardless of the sampling pattern that is selected.
Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'
Hmmm... I can not reproduce this error on Linux Mint 19.3 with a GTX 1080Ti.
Both the current buildbot build and my own build (with CUDA 10.1) render properly:
I reported a bug with adaptive sampling before, but that was simply because I compiled using CUDA 10.2
Using CUDA 10.1 fixed the adaptive sampling, what version of CUDA are you building with?
Closed as duplicate of #74471
Changed status from 'Duplicate' to: 'Confirmed'
Added subscriber: @arenyart
CUDA 10.2 + PMJ commit shows the render error. CUDA 10.2 and any revision before the PMJ commit renders fine.
Reproduces with 1080Ti/CUDA 10.2 on Windows as well.
@Stefan_Werner is this something you plan to fix? I don't see anything obviously wrong in the code, so I guess it's a commenting out code until the cause is found.
If it helps and this is caused by a compiler bug, we could also consider removing CMJ sampling.
Added subscriber: @oweissbarth
This issue was referenced by blender/cycles@480f9ef4dc
This issue was referenced by
cf5147f69fChanged status from 'Confirmed' to: 'Resolved'
Added subscribers: @beroset, @Mantissa