Collections visibility settings - Design Task #53493
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
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#53493
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?
Problem
There are few scenarios to consider when thinking about the collection options:
Instanced group
Dupli vertices
Support simulation objects
Reference objects
Invisible to the camera
Light that contributes to the scene but is not visible
Proposed solution
Groups
There is still one scenario where the visibility control for render and viewport may be required: group instancing.
When you instance a group and have a highpoly object to be used for the final render, but also a lowpoly to be used only for the viewport.
For this case (group collections) we will implement a viewport and render collection options.
Example of solution applied to the presented problems
See the scenarios above and their respective image for reference.
Collection override for workspace "Only Render"
Use object duplicator visibility option to hide duplicator
Separate simulation support objects from the rest of the simulation
Different collections
Disable camera ray visibility for the wall objects
Changed status to: 'Open'
Added subscriber: @dfelinto
Collection Settings - Proposalto Collections visibility settingsCollections visibility settingsto Collections visibility settings - Design TaskAdded subscriber: @spockTheGray-4
Added subscriber: @TysonTom
This comment was removed by @TysonTom
Added subscriber: @ideasman42
Added subscriber: @mont29
Overall looks sensible to me…
Some questions/remarks:
"Only Render" means the object participates to render result (be it cycles, eevee, etc.), but not the overlays in 3DViewport, right? So int the end, per object, we'd have an absolute ON/OFF status (from 'compilation' of enabled/disabled flags from all collections an object lays in), and an "Only Render" option that sort of amends the ON status, if I understood correctly?
So only #5 (the invisble-to-camera one) actually needs a custom, specific flag & handling?
About #3: Not sure we need two collections for the physics in fact… Wouldn’t that collection layout do the expected work? That way, we can still use a single collection for a whole simulation (as far as simulation code is concerned).
One collection gathering all objects involved in simulation, both visible and invisible ones, set todisabled**. This is the collection you feed to simulator.
One collection gathering all visible objects involved in simulation, set toenabled**.
Added subscriber: @fsiddi
@mont29:
Correct. Exactly how we do in 2.79.
We will have no built-in "only render" option, but let users add a dynamic override for this if they need this granular control per collection.
I'm not talking about a new flag here. Instead, talking about sticking to what we already have (per-object engine specific camera ray visibility control). Eevee can use that as well if we want.
There is more than one way to skin a cat. IF users want to have a single collection for the entire simulation, what you propose is perfectly sound. Otherwise they can go with what I suggest. But I will update the task to include your idea.
Removed subscriber: @TysonTom
Added subscribers: @pablovazquez, @PawelLyczkowski-1
Added subscriber: @antoniov
Changed status from 'Open' to: 'Archived'