SHIPPED · v0.16.0
Yolo runs fix their own failed checks, and 3D films render within your free memory
Improved
Yolo runs fix failed checks themselves. A Yolo run no longer waits at a gate when a check fails. The failed shots render again, or the script goes back to fix the failed checks, up to twice before the run asks you.
The Editor says what to do when a check fails. Instead of a plain Continue, the waiting chip names the failed check and offers Retry failed shots or Send back to fix, with the full list in its tooltip.
3D shots fit your free memory. Blender shots now render only as many at once as free memory allows, so a busy computer no longer runs out of memory partway through a film.
A scene fix that runs out of time keeps its work. When a repair hits its time limit, what it already saved is still checked and kept if it passes, instead of being thrown away.
Scene thumbnails after the final render. The Editor's scene list keeps its thumbnails once the full video is done, and shots whose take is a video now show it instead of a broken image.
Clearer final-render errors. A failed step in the final mix now names the step, such as the music, the cue sheet or the dialogue.
Fixed
Blender frames stay in the production on Windows. 3D shots could write their frames to a frames folder at the root of the drive. They now stay inside the production. You can delete a stray C:\frames folder left by an earlier version.
Captions place when their subject was not measured. A caption set to avoid a subject that was never measured stopped the shot with "no boxes for overlay avoid". It now places and notes that the subject was not measured.
Caption boxes reach the final cut. A scene caption with a background box and no animation could stop the final render with "invalid type: null, expected a sequence".