Understand level scope in renders and production outputs
Learn how renders respect the level scope you fire them from while production outputs always cover the full design.
A render fired while you are in Room or Floor view normally contains only what was visible at that moment - hidden levels and hidden layers are excluded from the rendered scene.
Outputs are the exception: they are required to see the whole design. While an output is being produced, all layers and levels are temporarily switched on, so the output includes hidden rooms, floors and layers regardless of the view you fired it from. This applies to every output, including those that run their own layer, level or elevation filtering.
Production outputs (cutting lists, schedules, board layouts, and other manufacturing outputs) always cover the entire design regardless of the view you were in when you generated them. They turn all layers on and ignore level scoping for the duration of the output, then restore the view's hiding afterwards. This is a required behaviour for outputs, not an optional setting.
If a render is missing rooms or floors, re-fire it from a wider level (Floor or World).
If an output includes items you had hidden on screen, that is by design: outputs are always generated from the full design, not from the current on-screen visibility. Hiding layers or levels only affects what you see while designing; it does not remove anything from a render, cutlist, schedule or other output.
System layers cannot be created, only custom ones.
When an output (render, cutlist, schedule, board layout, quotation) is generated, the system temporarily shows the whole design so nothing hidden is left out of the result. This is automatic and always on for outputs — you do not need to (and cannot) turn it on yourself. While an output is being produced, the current view's layer/level hiding is suspended, and afterwards your previous view state is restored exactly as it was.
Because of this, a render or output that appears to be missing rooms, floors or hidden items is not caused by the output path skipping hidden geometry; it reflects the view state that was captured when the render was fired. To reproduce a render faithfully, the same viewing mode, target level and design version must be used.