Keyframed Render Layers Don't Work as Intended #40764

New Issue

David Brennan · 2014-06-23T05:11:23+02:00

David Brennan commented

2014-06-23 05:11:23 +02:00

System Information
Operating system and graphics card

Windows 7, 64-bit
Intel i7 CPU

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional)

Blender 2.71 RC2 (and earlier versions)

Short description of error

When Render Layers have their visibility Keyframed, and then a Scene is rendered out as an animation, the Keyframed Render Layers very often will not begin rendering at the appropriate frame, or even render at all. (This only happens when it's rendered as an animation, not when a single frame is rendered.)

For instance, let's say that you have a 1,000 frame animation with two Render Layers. The second Render Layer is not needed until frame #700, and so you Keyframe it at 699 and 700 (to save render time). Well, when you return the next day to see your finished animation frames, you'll see that that second Render Layer was never included in the animation, even at frame 700 and beyond!

This has been a long-time annoyance, dating back to at least 2.68. I just created a sample .Blend of ten frames. In this sample, I noticed that the Bug does not behave entirely as described above. Here, the second Render Layer does actually appear....but still not at the appropriate points when it's been Keyframed.

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

Attached is a .Blend of just ten frames. The second Render Layer is set to begin at frame #6. However, I just rendered it out two times. Both times, it didn't begin rendering until frame #7, and one time, the second Render Layer actually rendered at frame #1, when it was disabled. So the Bug appears to behave differently each time you render it out. (For me personally, it has always behaved as described above: the Keyframed Render Layers simply never appear at all when it's render as an animation.)

RenderLayerKeyframeBug.blend

**System Information** Operating system and graphics card Windows 7, 64-bit Intel i7 CPU **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) Worked: (optional) Blender 2.71 RC2 (and earlier versions) **Short description of error** When Render Layers have their visibility Keyframed, and then a Scene is rendered out as an animation, the Keyframed Render Layers very often will not begin rendering at the appropriate frame, or even render at all. (This only happens when it's rendered as an animation, not when a single frame is rendered.) For instance, let's say that you have a 1,000 frame animation with two Render Layers. The second Render Layer is not needed until frame #700, and so you Keyframe it at 699 and 700 (to save render time). Well, when you return the next day to see your finished animation frames, you'll see that that second Render Layer was never included in the animation, even at frame 700 and beyond! This has been a long-time annoyance, dating back to at least 2.68. I just created a sample .Blend of ten frames. In this sample, I noticed that the Bug does not behave entirely as described above. Here, the second Render Layer does actually appear....but still not at the appropriate points when it's been Keyframed. **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps Attached is a .Blend of just ten frames. The second Render Layer is set to begin at frame #6. However, I just rendered it out two times. Both times, it didn't begin rendering until frame #7, and one time, the second Render Layer actually rendered at frame #1, when it was disabled. So the Bug appears to behave differently each time you render it out. (For me personally, it has always behaved as described above: the Keyframed Render Layers simply never appear at all when it's render as an animation.) [RenderLayerKeyframeBug.blend](https://archive.blender.org/developer/F95310/RenderLayerKeyframeBug.blend)

David Brennan commented

2014-06-23 05:11:23 +02:00

Changed status to: 'Open'