Page MenuHome

Cycles renders only two frames of animation
Confirmed, NormalPublicBUG


System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59

Blender Version
Broken: version: 2.93.0, branch: master, commit date: 2021-06-02 11:21, hash: rB84da05a8b806

Short description of error
Cycles render only two frames of animation when all of these functions are enabled: Time remapping (with ratio more than 1), Motion Blur and Persistent Data.

Exact steps for others to reproduce the error
To recreate this problem you need to create animation, set time remapping with ratio more than 1 (for example 60/24), enable Motion blur and enable Persistent data, as you can see in attached file.

Event Timeline

Nikita (Kozn) updated the task description. (Show Details)

Confirmed with attached Blend file on macOS Big Sur on MacBook M1. When I manually created a new animation based on the instructions the rendering stopped at frame 5. So the position where rendering stops seems to vary.

Maybe related to T89053, as that issue also claims to be Motion Blur + Persistent Data related.

Alaska (Alaska) changed the task status from Needs Triage to Confirmed.Sat, Jun 12, 4:12 AM
Alaska (Alaska) changed the subtype of this task from "Report" to "Bug".
Alaska (Alaska) added a subscriber: Alaska (Alaska).

I can confirm this issue with Blender 2.93 release and Blender 3.0 on Linux (see information below).

I decided to bisect the issue and to see if any more information could be found out. The "culprit" commit is the introduction of Persistent Data. rB50782df42586: Render: faster animation and re-rendering with Persistent Data

I also ran Blender with the commend --debug-all and I couldn't find anything useful from it.

System Information
Operating system: Linux-5.10.0-7-amd64-x86_64-with-glibc2.31 64 Bits

Blender Version: 3.0.0 Alpha, branch: master, commit date: 2021-06-11 21:39, hash: rBd75e45d10cbf

There seems to have been some prior problems with Motion Blur and Persistent Data: T87283, though that is marked as being fixed.

This issue is different as it's the time remapping along with motion blur and persistent data that is causing the issue from the looks of it.