Holdout function not working properly #73309
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#73309
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: WINDOWS 10
Graphics card: NVIDIA RTX 2060ti
Blender Version
Broken: (Blender v. 2.81a)
Worked: (Worked only on blender 2.79b)
Short description of error
When you want to render some layers with holdout and when combine it into photoshop or node editor, there are 1px gap between two layers, and everything looks like have line around objects. It seems that object rendered with holdout function is 1 px smaller. If I need to change only one object color I can not render it with holdout alone, I need to re-render all the scene. With shadow catcher is the same, you can not render shadow in different layer and holdout all objects in it, they will not stick nicely in composer.
Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).
Added subscriber: @indijus
Added subscriber: @JacquesLucke
Changed status from 'Needs Triage' to: 'Needs User Info'
Please provide an as-simple-as-possible .blend file that allows us to reproduce the issue more easily.
Also try the latest builds from the buildbot, please. https://builder.blender.org/download/
simple scene.blend If you want to holdout shadow in one layer and hold out the bed in another layer, after combining they have 1px line around the bed and the shadow. Maybe it is anti aliasing problems. If you need to tweak shadow or change shadow color, you should render it without background, because holdout bed from shadow will not work. But if shadow is with background and not transparent as shadow catch I will not able to manipulate shadows different from the bed
How can you call a scene with 473 MB "simple" :D
Please try to reproduce this in a much smaller file, preferably starting from a new empty file.
Otherwise debugging this issue becomes much harder.
Is this only related to cycles?
The main problem is when you holdout some object it makes jittering around the object cutting. When you want to combine shadow with holdout object you will get 1px strokes around any object if it is contain transparent layer. I posted it to blender artist group on Facebook and people tested it a lot, and everybody have the same problem. If you want to work with layers you can not use holdout button because it will cut object without anti aliasing and in post production objects not sticking nicely together. I do not work with eevee so I got this only on Cycles. tested beta versions it is the same. It is like on older blender 2.79 when you tried to use ID object index or material ant they do not contained anti aliasing. Cryptomatte not working for such situation if you want to render only one object with different patterns and cut out everything what is not important for rendering. You can render shadow in another pass layer, object in another ( In old 2.79 way layering), but you can not holdout perfectly shadow or object. So I do not understand why it is such function at all in layers menu. To look throw objects maybe in viewport, because in rendering it is not working, no anti aliasing and so much jittering around cutted objects in transparent backgrounds. I am not programmer so it is hard to explain it correctly but maybe someone will understand it :)
Added subscriber: @dfelinto
Changed status from 'Needs User Info' to: 'Archived'
@indijus thanks for the report. But we have not the resources to debug production files.
Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.
If you manage to isolate the issue and simplify the file further, please submit as a new bug report.
Added subscriber: @stanland
Hi,
I have the same problem. I made a very simple blend and photoshop file to test this issue. I think this problem is related to antialiasing.
HOLDOUT_TEST.blend