Hold Out does not hold out Collection Hierarchy #110720

New Issue

Open

opened 2023-08-02 15:55:21 +02:00 by rohan stevenson · 4 comments

rohan stevenson commented

2023-08-02 15:55:21 +02:00

System Information
Operating system: Linux-5.19.0-50-generic-x86_64-with-glibc2.35 64 Bits, X11 UI
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03

Blender Version
Broken: version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc
Worked: (newest version of Blender that worked as expected)

Short description of error
Nested collections do not get held out if only the top level collection is held out.

Exact steps for others to reproduce the error

Note attached blend file.

Note the foreground collection with 2 subjects in it. When holding out the foreground, the nested collections (collections held within the "Foreground" collection) are not held out.

**System Information** Operating system: Linux-5.19.0-50-generic-x86_64-with-glibc2.35 64 Bits, X11 UI Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03 **Blender Version** Broken: version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: `8bda729ef4dc` Worked: (newest version of Blender that worked as expected) **Short description of error** Nested collections do not get held out if only the top level collection is held out. **Exact steps for others to reproduce the error** Note attached blend file. ![image](/attachments/e453b65a-4da1-4952-abc5-d1f9f0119b3a) Note the foreground collection with 2 subjects in it. When holding out the foreground, the nested collections (collections held within the "Foreground" collection) are not held out.

58 KiB

Screenshot from 2023-08-02 14-52-36.png

58 KiB

Render Layer Tests.blend

149 KiB

Screenshot from 2023-08-02 14-52-36.png

rohan stevenson added the

labels 2023-08-02 15:55:22 +02:00

YimingWu commented

2023-08-02 16:20:02 +02:00

Member

This is probably by design. But the documentation certainly should clarify on this.

This is probably by design. But the [documentation](https://docs.blender.org/manual/en/latest/scene_layout/collections/collections.html) certainly should clarify on this.

YimingWu added

Render & Cycles

Render Pipeline

EEVEE & Viewport

and removed

labels 2023-08-02 16:20:33 +02:00

rohan stevenson commented

2023-08-02 18:00:44 +02:00

Author

This is probably by design. But the documentation certainly should clarify on this.

Well it makes no sense if it is by design. Collections are a way to organise complex scenes, so it makes sense that the hierarchy of the collection nesting should be followed by the hold out function.

If part of a collection would need to be rendered while the rest of the collection was to be held out, then the user would create a new collection and move that part above the original collections hierarchy.

This has all the appearance of a bug to me.

> This is probably by design. But the [documentation](https://docs.blender.org/manual/en/latest/scene_layout/collections/collections.html) certainly should clarify on this. Well it makes no sense if it is by design. Collections are a way to organise complex scenes, so it makes sense that the hierarchy of the collection nesting should be followed by the hold out function. If part of a collection would need to be rendered while the rest of the collection was to be held out, then the user would create a new collection and move that part above the original collections hierarchy. This has all the appearance of a bug to me.

YimingWu commented

2023-08-04 06:40:05 +02:00

Member

@rohan.stevenson Yeah I agree.

I do have a confusion here as well... If I have an object that's in collection A and B, and if I set A as hold out, and B is normal, what would the renderer do in this case? (Or what is expected)

@rohan.stevenson Yeah I agree. I do have a confusion here as well... If I have an object that's in collection A and B, and if I set A as hold out, and B is normal, what would the renderer do in this case? (Or what is expected)

rohan stevenson commented

2023-08-05 18:21:33 +02:00

Author

....additionally, if you turn OFF a collection, it turns off all the collections that reside within that collection, and if you turn it back on, they all turn back on. The holdout function should be consistent with that behaviour.

WRT to your question, if you set A to hold out and B to render, then A should be held out and B should render. BUT - if you set that COLLECTION to hold out, everything within that collection should hold out, until you turn it back on. Once it is back on, the previous state (A to hold out B to render) should be remembered.

I would have thought this was obvious. The hierarchy should always be observed.

What is even the point of having a hold out option for a collection, if collections within that collection do not get held out? (unless you manually set them to hold out). Plus it is not consistent with turning collections on or off.

I have a complex scene with 3 layers of audience characters and it is a nightmare trying to work out whether something has been held out or not.

....additionally, if you turn OFF a collection, it turns off all the collections that reside within that collection, and if you turn it back on, they all turn back on. The holdout function should be consistent with that behaviour. WRT to your question, if you set A to hold out and B to render, then A should be held out and B should render. BUT - if you set that COLLECTION to hold out, everything within that collection should hold out, until you turn it back on. Once it is back on, the previous state (A to hold out B to render) should be remembered. I would have thought this was obvious. The hierarchy should always be observed. What is even the point of having a hold out option for a collection, if collections within that collection do not get held out? (unless you manually set them to hold out). Plus it is not consistent with turning collections on or off. I have a complex scene with 3 layers of audience characters and it is a nightmare trying to work out whether something has been held out or not.

rohan stevenson referenced this issue

2023-08-11 10:16:46 +02:00

Objects do not retain View State when turning Collections Off then back On #87111

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

2 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#110720

No description provided.