Blender Auto Save Timer Limits During Playback and Long Renders
0 reputation · 22 Jan 2021, 06:15 UTC
0 reputation · 22 Jan 2021, 06:15 UTC
Blender's Auto Save, present since 2.80 and active in current releases, writes a timed copy of the working scene to the system's temporary directory. The interval is configured in Preferences under Save & Load, and File > Recover > Auto Save exposes the last write after a crash. What the feature does not document is how the timer behaves while the interface is busy.
During animation playback or timeline scrubbing, the interface stays busy with frame evaluation. It is unclear whether a pending Auto Save write pauses, defers until playback stops, or is skipped for that interval entirely. The same ambiguity applies to long-running operations such as a render or an active transform, where event processing is limited. No preference or release note states when such a pause takes effect, and the preferences expose no record of deferred or skipped intervals.
Version assumption: Blender 2.80 and later; the timer interaction should be confirmed on the specific release in use.
34775 reputation · 22 Jan 2021, 13:27 UTC
The Auto Save timer does not pause during playback or rendering. Instead, the timer continues to fire on real‑time intervals, but the actual write operation runs as a modal operator that only executes when Blender’s event loop is idle. Consequently, any pending Auto Save is deferred until playback stops or the render yields control back to the main loop. Long‑running operations such as a full animation render behave the same way: the save occurs after the render finishes or at a yield point, not during active frame evaluation.
Blender’s event loop processes modal operators (including the Auto Save write) only when it is not busy evaluating frames, scrubbing the timeline, or executing a render. The timer itself is not suspended; it simply queues a save request that waits for the next idle pass. There is no evidence that intervals are skipped or that the timer resets. The deferral boundary is the next iteration of the main loop where no modal operator holds control—typically after playback stops or when a render engine yields (e.g., between tiles or frames).
.blend1 files. Note whether they appear during playback or only after it stops.--debug or open the scripting console to observe timer operator calls and compare timestamps with playback/render periods.What Blender version and render engine (Eevee, Cycles, Workbench) are you using? Some engines yield control differently between tiles or frames, which changes when the deferred Auto Save can execute.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.