wrong Zdepth data in Cycles #32351

Closed
opened 2012-08-18 00:36:19 +02:00 by Sam Vila · 10 comments

%%%In the attached file you can see that after rendering a couple of frames there's a flickering on the zdepth channel when it's rendering with cycles, if you switch to the blender internal render it's completely fine. The problem is only with the zdepth channel in cycles

More information:

http://www.youtube.com/watch?v=SScHpL7dsQU

http://blenderartists.org/forum/showthread.php?263721-Depth-of-field-flickering%%%

%%%In the attached file you can see that after rendering a couple of frames there's a flickering on the zdepth channel when it's rendering with cycles, if you switch to the blender internal render it's completely fine. The problem is only with the zdepth channel in cycles More information: http://www.youtube.com/watch?v=SScHpL7dsQU http://blenderartists.org/forum/showthread.php?263721-Depth-of-field-flickering%%%
Author

Changed status to: 'Open'

Changed status to: 'Open'

%%%It's a precision issue, where in one pixel a ray manages to slip through between two triangles. Usually you wouldn't notice this and the Z Depth channel itself does not flicker, but in this case the Normalize node is used, which is sensitive to changes in a single pixel. I'll see if I can fix this precision issue, but in general I'd suggest to not use the Normalize node for this kind of setup, in this simple scene it works but in general it can give issues even if tiny object move in/out of the camera view.%%%

%%%It's a precision issue, where in one pixel a ray manages to slip through between two triangles. Usually you wouldn't notice this and the Z Depth channel itself does not flicker, but in this case the Normalize node is used, which is sensitive to changes in a single pixel. I'll see if I can fix this precision issue, but in general I'd suggest to not use the Normalize node for this kind of setup, in this simple scene it works but in general it can give issues even if tiny object move in/out of the camera view.%%%
Author

%%%I also tried with a different setup for export the depth pass data into a bitmap file with the same results. What I did was to use a map value with a color ramp the problem is that all the data comming from the depth channel in cycles is corrupt or something so the values "dance" and produce this flickering thing. With Blender internal is fine. Do you suggest another way to export the depth pass?%%%

%%%I also tried with a different setup for export the depth pass data into a bitmap file with the same results. What I did was to use a map value with a color ramp the problem is that all the data comming from the depth channel in cycles is corrupt or something so the values "dance" and produce this flickering thing. With Blender internal is fine. Do you suggest another way to export the depth pass?%%%

%%%I'm quite sure there is no flickering as long as you do not use the Normalize node, I tested it here and it works fine.%%%

%%%I'm quite sure there is no flickering as long as you do not use the Normalize node, I tested it here and it works fine.%%%
Author

%%%I'm checking this more in deep, doing some extra test, I'll provide additional information tomorrow or so, thanks Brecht.%%%

%%%I'm checking this more in deep, doing some extra test, I'll provide additional information tomorrow or so, thanks Brecht.%%%

%%%Any news here? Otherwise I suggest to close and maybe mark as ToDo. %%%

%%%Any news here? Otherwise I suggest to close and maybe mark as ToDo. %%%
Author

%%%I did a few more tests and I think the only problem is with the depth values in cycles when using the normalize option. This is something that really confusse me a lot, the fact that some channels (vector channel, depth, normals...) looks completely different from Blender Internal to Cycles. IMO it should look exactly the same all the channels. So I think is more a ToDo list than something to just ignore.%%%

%%%I did a few more tests and I think the only problem is with the depth values in cycles when using the normalize option. This is something that really confusse me a lot, the fact that some channels (vector channel, depth, normals...) looks completely different from Blender Internal to Cycles. IMO it should look exactly the same all the channels. So I think is more a ToDo list than something to just ignore.%%%

%%%Yes, will make this a todo. Improving raytracing precision is a nice thing to work on but we'll never get it 100% anyway, due to float precision.%%%

%%%Yes, will make this a todo. Improving raytracing precision is a nice thing to work on but we'll never get it 100% anyway, due to float precision.%%%

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

%%%I can confirm this problem. I did not know the normalize node was at fault, but it is my preferred way to render out a depth pass as a png.%%%

%%%I can confirm this problem. I did not know the normalize node was at fault, but it is my preferred way to render out a depth pass as a png.%%%
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
4 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#32351
No description provided.