Collections won't be rendered despite being checked for render #61483

Closed
opened 2019-02-12 21:14:35 +01:00 by seeyalater · 12 comments

System Information
Operating system: Windows 7 SP1
Graphics card: Nvidia GTX 1050 Ti

Blender Version
Broken: 2.8 Beta, d3870471eed7, 2019-02-12
Worked: (optional): 2.8 Beta about a month ago (sorry I deleted that version so I can't check the exact version)

Short description of error
If I use collection instances, and the original instanced collections are turned off for rendering, the instanced collections will be invisible too.

Exact steps for others to reproduce the error
1.) Create a collection inside the scene collection. Make a table with a glass on it (or anything, the point is to have multiple objects in the collection).
2.) Turn off render visibility for this collection.
3.) Create another collection in the scene collection, eg: Restaurant. Inside this collection add the "table" collection instance multiple times. Keep the Restaurant collection and all instanced collections visible in it for render.
4.) Render scene.
5.) Nothing will show up. Only if you turn on the visibility for the original table collection is when the instances will appear.

I'm pretty sure this is not a normal behaviour, I don't recall this happening before, and this could be solved with groups and layers in Blender 2.79.
This is literally the reason why I registered on this site, I hope this is helpful information and will be fixed soon.

**System Information** Operating system: Windows 7 SP1 Graphics card: Nvidia GTX 1050 Ti **Blender Version** Broken: 2.8 Beta, d3870471eed7, 2019-02-12 Worked: (optional): 2.8 Beta about a month ago (sorry I deleted that version so I can't check the exact version) **Short description of error** If I use collection instances, and the original instanced collections are turned off for rendering, the instanced collections will be invisible too. **Exact steps for others to reproduce the error** 1.) Create a collection inside the scene collection. Make a table with a glass on it (or anything, the point is to have multiple objects in the collection). 2.) Turn off render visibility for this collection. 3.) Create another collection in the scene collection, eg: Restaurant. Inside this collection add the "table" collection instance multiple times. Keep the Restaurant collection and all instanced collections visible in it for render. 4.) Render scene. 5.) Nothing will show up. Only if you turn on the visibility for the original table collection is when the instances will appear. I'm pretty sure this is not a normal behaviour, I don't recall this happening before, and this could be solved with groups and layers in Blender 2.79. This is literally the reason why I registered on this site, I hope this is helpful information and will be fixed soon.
Author

Added subscriber: @ohmyblender

Added subscriber: @ohmyblender

Added subscriber: @StephenSwaney

Added subscriber: @StephenSwaney

Do you have a .blend showing the problem?

Do you have a .blend showing the problem?
Author

In #61483#619432, @StephenSwaney wrote:
Do you have a .blend showing the problem?

Sure. I can't share the original project, but I easily reproduced the problem with the steps I provided. Here is the Blender file. Just try to render it first and there won't be any tables visible. Btw now I'm using the latest Blender build (I downloaded it after I wrote the bug report) Broken blender 2.8 collections.blend

> In #61483#619432, @StephenSwaney wrote: > Do you have a .blend showing the problem? Sure. I can't share the original project, but I easily reproduced the problem with the steps I provided. Here is the Blender file. Just try to render it first and there won't be any tables visible. Btw now I'm using the latest Blender build (I downloaded it after I wrote the bug report) [Broken blender 2.8 collections.blend](https://archive.blender.org/developer/F6598985/Broken_blender_2.8_collections.blend)

Added subscriber: @AlexeyShefer

Added subscriber: @AlexeyShefer

Closed as duplicate of #62214

Closed as duplicate of #62214

Added subscriber: @ZedDB

Added subscriber: @ZedDB

As explained in #62214, you should use View Layer -> Set Exclude to do this.

As explained in #62214, you should use ` View Layer -> Set Exclude` to do this.
Author

In #61483#634425, @ZedDB wrote:
As explained in #62214, you should use View Layer -> Set Exclude to do this.

1.) If this isn't a bug then what's the point of having the eye and the camera icon if they don't work for instanced collections? This is totally inconsistent in the UI.
2.) Why isn't this working with instanced collections if it works with everything else (objects and normal collections) and this is literally the point of having camera and eye icons in the outliner?
3.) I couldn't find that option under the view layer tab and last time when I looked up view layers months ago for something else, they said they only work with Cycles not Eevee and I'm using Eevee.

> In #61483#634425, @ZedDB wrote: > As explained in #62214, you should use ` View Layer -> Set Exclude` to do this. 1.) If this isn't a bug then what's the point of having the eye and the camera icon if they don't work for instanced collections? This is totally inconsistent in the UI. 2.) Why isn't this working with instanced collections if it works with everything else (objects and normal collections) and this is literally the point of having camera and eye icons in the outliner? 3.) I couldn't find that option under the view layer tab and last time when I looked up view layers months ago for something else, they said they only work with Cycles not Eevee and I'm using Eevee.

Added subscriber: @mont29

Added subscriber: @mont29

The first two questions is for @mont29

3: right click the collection go to View Layer -> Set Exclude.

The first two questions is for @mont29 3: right click the collection go to View Layer -> Set Exclude.
Author

In #61483#635791, @ZedDB wrote:
The first two questions is for @mont29

3: right click the collection go to View Layer -> Set Exclude.

Oh ok, thank you.

> In #61483#635791, @ZedDB wrote: > The first two questions is for @mont29 > > 3: right click the collection go to View Layer -> Set Exclude. Oh ok, thank you.
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#61483
No description provided.