Incorrect render layer visibility display for animated render layers #39828

Closed
opened 2014-04-21 14:43:16 +02:00 by Willi · 13 comments

System Information
Win7/64, AMD HD 6850

Blender Version
since 2.57b

Short description of error
When navigating forward from a key frame for visibility of render layers to another key frame, the display does not match the actual values:
Bild_309.JPG
Actually, only layer 2 is visible.

Exact steps for others to reproduce the error

  • Open attached file: At frame 0, only render layer 1 is visible. At frame 1, only render layer 2 is visible.
  • If you navigate from frame 0 to frame 1, the display (as shown in screenshot) incorrectly indicates both render layers are visible, whereas, when navigating from frame 2 to frame 1, display is correct.

RenderLayers.blend

**System Information** Win7/64, AMD HD 6850 **Blender Version** since 2.57b **Short description of error** When navigating forward from a key frame for visibility of render layers to another key frame, the display does not match the actual values: ![Bild_309.JPG](https://archive.blender.org/developer/F85515/Bild_309.JPG) Actually, only layer 2 is visible. **Exact steps for others to reproduce the error** - Open attached file: At frame 0, only render layer 1 is visible. At frame 1, only render layer 2 is visible. - If you navigate from frame 0 to frame 1, the display (as shown in screenshot) incorrectly indicates both render layers are visible, whereas, when navigating from frame 2 to frame 1, display is correct. [RenderLayers.blend](https://archive.blender.org/developer/F85517/RenderLayers.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @willi-2

Added subscriber: @willi-2

Added subscribers: @brecht, @ideasman42, @Sergey, @mont29

Added subscribers: @brecht, @ideasman42, @Sergey, @mont29

Iirc, this should not be animatable? Brecht, Campbell, Sergey, can you confirm?

Iirc, this should not be animatable? Brecht, Campbell, Sergey, can you confirm?

From my understanding the things they shouldn't be animatable. But i might be wrong.

From my understanding the things they shouldn't be animatable. But i might be wrong.

We disabled animation of scene layers because it gave dependency graph issues I think. This render layer value should not suffer from that particular problem.

I think the problem here is the way this RNA property interacts with the animation system. Because it's not allowed to have zero layers enabled, the f-curve that disables the first layer will be ignored when going from frame 0 to 1. That's a tricky issue as well though.

We disabled animation of scene layers because it gave dependency graph issues I think. This render layer value should not suffer from that particular problem. I think the problem here is the way this RNA property interacts with the animation system. Because it's not allowed to have zero layers enabled, the f-curve that disables the first layer will be ignored when going from frame 0 to 1. That's a tricky issue as well though.

@brecht, it doesn't seem render engine supports changes in render layers visibility. Here's a sample file which is free from the mentioned bug in animation but which fails to render animation{F85610}.

AFAIR, this bits are copied into Render and not being updated. We could support this, but isn't it a TODO and meanwhile marking layers as non-animatable is ok-ish thing?

@brecht, it doesn't seem render engine supports changes in render layers visibility. Here's a sample file which is free from the mentioned bug in animation but which fails to render animation{[F85610](https://archive.blender.org/developer/F85610/render-layer-visibility.blend)}. AFAIR, this bits are copied into Render and not being updated. We could support this, but isn't it a TODO and meanwhile marking layers as non-animatable is ok-ish thing?
Author

I see. I'll keep layer 20 visible all the time. Should be a temporary workaround. Not essential for me anyway, so I'll do it differently if you decide to drop animatability of render layers.
Thanks.

I see. I'll keep layer 20 visible all the time. Should be a temporary workaround. Not essential for me anyway, so I'll do it differently if you decide to drop animatability of render layers. Thanks.

I'm OK with this being marked non-animatable for now.

I'm OK with this being marked non-animatable for now.

This issue was referenced by blender/blender-addons-contrib@14ab812da5

This issue was referenced by blender/blender-addons-contrib@14ab812da55ad08bc00f90fe0b9efa91c60daa71

This issue was referenced by 14ab812da5

This issue was referenced by 14ab812da55ad08bc00f90fe0b9efa91c60daa71
Bastien Montagne self-assigned this 2014-04-23 16:23:04 +02:00

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Closed by commit 14ab812da5.

Closed by commit 14ab812da5.
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
5 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#39828
No description provided.