Maniphest T39828

Incorrect render layer visibility display for animated render layers
Closed, Resolved
Actions

Assigned To
Bastien Montagne (mont29)
Authored By
Willi (willi)
Apr 21 2014, 2:43 PM
Tags
  • Animation & Rigging
  • BF Blender
Subscribers
Bastien Montagne (mont29)
Brecht Van Lommel (brecht)
Campbell Barton (campbellbarton)
Sergey Sharybin (sergey)
Willi (willi)

Description

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:


Actually, only layer 2 is visible.

Exact steps for others to reproduce the error

  1. Open attached file: At frame 0, only render layer 1 is visible. At frame 1, only render layer 2 is visible.
  2. 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.blend58 KBDownload

Revisions and Commits

rB Blender
rB14ab812da55a Fix T39828: Incorrect render layer visibility display for animated render…
rBAC Blender Add-ons Contrib
rBAC14ab812da55a Fix T39828: Incorrect render layer visibility display for animated render…

Event Timeline

Willi (willi) created this task.Apr 21 2014, 2:43 PM
Willi (willi) raised the priority of this task from to 90.
Willi (willi) updated the task description.
Willi (willi) added projects: BF Blender, User Interface.
Willi (willi) edited a custom field.
Willi (willi) added a subscriber: Willi (willi).
Bastien Montagne (mont29) added subscribers: Brecht Van Lommel (brecht), Campbell Barton (campbellbarton), Sergey Sharybin (sergey), Bastien Montagne (mont29).Apr 21 2014, 8:38 PM

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

Bastien Montagne (mont29) lowered the priority of this task from 90 to Normal.Apr 21 2014, 8:38 PM
Sergey Sharybin (sergey) added a comment.Apr 21 2014, 8:43 PM

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

Brecht Van Lommel (brecht) edited projects, added Animation & Rigging; removed User Interface.Apr 22 2014, 12:24 AM
Brecht Van Lommel (brecht) added a comment.Apr 22 2014, 12:30 AM

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.

Sergey Sharybin (sergey) added a comment.Apr 22 2014, 8:04 AM

@Brecht Van Lommel (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?

Willi (willi) added a comment.Apr 22 2014, 11:46 AM

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.

Brecht Van Lommel (brecht) added a comment.Apr 22 2014, 1:23 PM

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

Bastien Montagne (mont29) claimed this task.Apr 23 2014, 4:23 PM
Bastien Montagne (mont29) edited this Maniphest Task.Apr 23 2014, 4:23 PM
Bastien Montagne (mont29) changed the task status from Unknown Status to Resolved.Apr 23 2014, 4:23 PM

Closed by commit rB14ab812da55a.

Bastien Montagne (mont29) edited this Maniphest Task.May 12 2014, 4:49 PM