Keyframe on renderlayer enable toggle does not evaluate during animation render #39940

New Issue

Warren Bahler · 2014-04-28T19:23:03+02:00

Warren Bahler commented

2014-04-28 19:23:03 +02:00

System Information
Win 7 and Ubuntu 13.4

Blender Version
Broken: 2.7 f93bc76
Worked: 2.69

using cycles

If I keyframe the "enable/disable render layer" toggle, It will work correctly during timeline playback. But if I render an animation sequence, the keyframed toggle will not evaluate.

Exact steps for others to reproduce the error

Open the attached file. Scrub the timeline and note that the render layer "monkey" is keyframed to turn on on frame 3.
Press CTRL F12 to render animation, note that the keyframe does not evaluate and blender only renders the "Cube" layer.

Also,during rendering, if you switch to another properties editor tab, and then back to the renderlayers after frame three, you will see that the tick box refreshes correctly, but still does not actively render.

**System Information** Win 7 and Ubuntu 13.4 **Blender Version** Broken: 2.7 f93bc76 Worked: 2.69 using cycles If I keyframe the "enable/disable render layer" toggle, It will work correctly during timeline playback. But if I render an animation sequence, the keyframed toggle will not evaluate. **Exact steps for others to reproduce the error** 1. Open the attached file. Scrub the timeline and note that the render layer "monkey" is keyframed to turn on on frame 3. 2. Press CTRL F12 to render animation, note that the keyframe does not evaluate and blender only renders the "Cube" layer. Also,during rendering, if you switch to another properties editor tab, and then back to the renderlayers after frame three, you will see that the tick box refreshes correctly, but still does not actively render.

Warren Bahler commented

2014-04-28 19:23:03 +02:00

Changed status to: 'Open'

Warren Bahler commented

2014-04-28 19:23:03 +02:00

Added subscriber: @WarrenBahler

Warren Bahler commented

2014-04-28 19:24:33 +02:00

attached file didn't work so here it is: RndrLyrTest.blend

attached file didn't work so here it is: [RndrLyrTest.blend](https://archive.blender.org/developer/F86309/RndrLyrTest.blend)

Willi commented

2014-04-28 21:36:51 +02:00

Added subscriber: @willi-2

Willi commented

2014-04-28 21:36:51 +02:00

Have a look here: #39828

Animation of render layer is not supported (anymore).

Have a look here: #39828 Animation of render layer is not supported (anymore).

Warren Bahler commented

2014-04-28 23:21:14 +02:00

@willi-2 - actually that's a different property, I'm trying to animate the actual render layer toggle on and off - which worked in 2.69.

Lukas Tönne commented

2014-04-29 12:23:21 +02:00

Added subscriber: @LukasTonne

Lukas Tönne commented

2014-04-29 12:23:21 +02:00

I think the problem here is that render layers are copied into the renderer state data at the start of the render job:
https://developer.blender.org/diffusion/B/browse/master/source/blender/render/intern/source/pipeline.c$516

This means that, even though the anim data is correctly evaluated and updates the render layer flags in the scene render data, this has no effect on the currently running render job's layer flags.

In general this means that any animation on render layer data is effectively not supported. I can think of 2 possible "solutions":

Rebuild the render layers list of the render job for each new frame
Accept that render layer flags (and possibly other settings) cannot be animated and enforce that in the API (not so nice of course, but may be cleaner design)

I think the problem here is that render layers are copied into the renderer state data at the start of the render job: https://developer.blender.org/diffusion/B/browse/master/source/blender/render/intern/source/pipeline.c$516 This means that, even though the anim data is correctly evaluated and updates the render layer flags in the scene render data, this has no effect on the currently running render job's layer flags. In general this means that any animation on render layer data is effectively not supported. I can think of 2 possible "solutions": - Rebuild the render layers list of the render job for each new frame - Accept that render layer flags (and possibly other settings) cannot be animated and enforce that in the API (not so nice of course, but may be cleaner design)

Brecht Van Lommel was assigned by Lukas Tönne

2014-04-29 12:24:35 +02:00

blender-admin commented

2014-04-29 14:03:09 +02:00

This issue was referenced by blender/blender-addons-contrib@4ff3ebf45c

This issue was referenced by blender/blender-addons-contrib@4ff3ebf45c8b7fe6911fb40d43384dc04d7a132b

blender-admin commented

2014-04-29 14:03:09 +02:00

This issue was referenced by 4ff3ebf45c

This issue was referenced by 4ff3ebf45c8b7fe6911fb40d43384dc04d7a132b

Brecht Van Lommel commented

2014-04-29 14:03:46 +02:00