Cycles volume shader position vector bleeds from objects behind #89814
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#89814
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.11.0-7614-generic-x86_64-with-glibc2.32 64 Bits
Graphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01
Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-07-11 05:31, hash:
2289e26fa3Worked: unknown
Short description of error
A low percentage of rays seems to get the incorrect position information in a volumetric shader. Under specific circumstances this can cause very bright unwanted artifacts around an objects outline.
Exact steps for others to reproduce the error
Turn on viewport rendering on following file:
volume_shader_position.blend
After a few hundred samples a bunch of pixels should show the artifacts.
Added subscriber: @SimonThommes
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Needs User Info'
@SimonThommes : do you think this could be the same as {#86742}?
Closed as duplicate of #86742
@lichtwerk This does seem to me like the same issue. I can also confirm that this increases with distance from the world origin, which makes sense as it's most likely a precision error.
I did already poke Brecht about it in person, as this is an issue we are running into in production at the studio and he mentioned he might have an idea how to identify these faulty rays.
But yes, these two tasks can probably be merged afaict.
Added subscriber: @brecht
@SimonThommes, unfortunately I don't have a quick solution for this issue, it's quite complicated to improve ray-tracing precision to avoid this.
@brecht Ah okay, thanks for looking into it! I'll try to cheat my way around it for Sprite Fright then, as this is quite a niche issue and probably shouldn't have priority otherwise.
Added subscriber: @Tetrino
Just want to say I am glad that people who have more working knowledge with Blender have seen this issue and have a more technical background for the causes. Love this community.