OptiX GPU rendering artifacts with large plane #85078
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
13 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#85078
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:Ubuntu 20.04.1 LTS
Graphics card:NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER]
Blender Version
Broken: 2.92.0 Beta 'c2e6969c56ef
Worked: 2.91.0 Beta #f923b6faa9f4
Short description of error
Incorrect GPU rendering with CYCLES of large unsubdivided Planes
Exact steps for others to reproduce the error
Delete Cube
Add Plane
Scale 500 on X and Y plane
Switch on GPU rendering
Switch on cycles rendering
Render
Added subscriber: @Cagey
#81566 was marked as duplicate of this issue
#91613 was marked as duplicate of this issue
#91570 was marked as duplicate of this issue
#89351 was marked as duplicate of this issue
#87606 was marked as duplicate of this issue
Blocky GPU rendering with Cyclesto Blocky GPU rendering with Cycles OptiX CPU + GPUChanged status from 'Needs Triage' to: 'Confirmed'
Blocky GPU rendering with Cycles OptiX CPU + GPUto OptiX GPU rendering artifacts with large planeAdded subscribers: @pmoursnv, @brecht
I initially though this was a CPU + GPU rendering issue, but it's a precision issue with OptiX and large planes.
We have a
ray_offsetfunction to avoid self-intersections, but I guess OptiX triangle intersection has larger error for this case than Embree's and our own triangle intersection.Yeah, things get funky with OptiX when intersecting objects with huge scaling. There's another report on this here too: #81566.
To solve this we could introduce some logic that detects and skips self-intersections when they happen (e.g. by keeping track of the last hit and checking if the new hit point is behind that based on the ray direction) or something along those lines.
Added subscriber: @Alaska
I believe I reported a similar issue to this report and #81566 in #75636 . In that task @brecht suggested D6250: Fix #43835, #54284: Cycles with no ray offsetting could resolve the issue. Is this still the case?
Added subscriber: @Stefan_Werner
Yes, that patch would likely help. Still this report can be kept open since the OptiX case is a bit different than the CPU one.
Added subscribers: @Renderbicks, @mano-wii
Added subscribers: @Arcomade, @Blendify, @Zandman
Added subscribers: @PabloCio, @ThomasDinges, @PeterBaintner
Please merge this latest bug report with Blender 3.0 Alpha and Cycles X (master branch): https://developer.blender.org/T91613
Added subscribers: @01Beaker, @Raimund58
Added subscriber: @SteffenD
Added subscriber: @costa
Is this still happening with latest Blender 3.x?
Changed status from 'Confirmed' to: 'Archived'
It is no longer happening in Blender 3.3.1 (Win11, GTX1080)
It's happening but on a bigger scale
Changed status from 'Archived' to: 'Confirmed'
Re-opening then. Thanks for thecking. @costa Can you please upload a blend with a larger plane that has the issue now? Easier to confirm. :)
Scaled the plane two times with 500.
![2022-11-25 16_31_24-Blender_ [C__Users_raimund.klink_Downloads_artifacts.blend].png](https://archive.blender.org/developer/F13968493/2022-11-25_16_31_24-Blender___C__Users_raimund.klink_Downloads_artifacts.blend_.png)
![2022-11-25 16_32_31-Blender_ [C__Users_raimund.klink_Downloads_artifacts.blend].png](https://archive.blender.org/developer/F13968497/2022-11-25_16_32_31-Blender___C__Users_raimund.klink_Downloads_artifacts.blend_.png)
![2022-11-25 16_33_17-Blender_ [C__Users_raimund.klink_Downloads_artifacts.blend].png](https://archive.blender.org/developer/F13968504/2022-11-25_16_33_17-Blender___C__Users_raimund.klink_Downloads_artifacts.blend_.png)
![2022-11-25 16_29_08-Blender [C__Users_raimund.klink_Downloads_artifacts.blend].png](https://archive.blender.org/developer/F13968486/2022-11-25_16_29_08-Blender__C__Users_raimund.klink_Downloads_artifacts.blend_.png)
![2022-11-25 16_37_36-Blender_ [C__Users_raimund.klink_Downloads_artifacts.blend].png](https://archive.blender.org/developer/F13968514/2022-11-25_16_37_36-Blender___C__Users_raimund.klink_Downloads_artifacts.blend_.png)
artifacts.blend
CYCLES (Optix)
CYCLES (Cuda)
CYCLES (CPU)
EEVEE
Workbench
I do not think at that point this can really be considered a bug but more just a working limitation of Blender.
See the manual: https://docs.blender.org/manual/en/latest/advanced/limits.html
Changed status from 'Confirmed' to: 'Archived'
Closing then as known limitation.