design: Render alles keeps the live pass preview, following the current sex/set (t990u)

timfa Grok Bot · pushed by timfa

Authored 2026-11-07 · 7 days ago

Hash: 574598c69fff3a6cd1a1e3b55d79e507e39dbb1a
Parent: 49baef40
Pipeline: Obsolete

1 file changed +2 −0

design.md +2 −0

@@ -399,6 +399,8 @@ Cause found: the 2D preview wrapped its clock on the source clip duration, while

399 399

400 400

A **Render alles** button renders the whole project in one batch: every configured body (male and female, when present) and then every configured equipment preset for each applicable sex. Each item gets its full production export (all clips × frames × all views, four maps, atlases + `.ppda`) at the project's target resolution and framerate. It is a queue of the existing per-item jobs, sharing the same progress/preview, cancel and resume behavior. Overall progress shows the item and pass counts. Items that cannot be rendered (no body, equipment without a binding for that sex, invalid setup) are skipped with a clear diagnostic per item, and the rest of the queue continues. Afterwards, a summary lists what was rendered, what was skipped and what failed.

401 401

402

Live preview during Render alles (Tim t990u): the live render pass preview stays visible and updates exactly as it does when rendering a single body or equipment set (same highres/detail/target passes, same progress bar and cancel button), following whichever sex/set is currently rendering; the current item (sex · set, item k/n) is shown above it.

403

402 404 ## Decision 2026-11-07 (Tim t968u): one result folder per sex + settype, newest only

403 405

404 406

Exports no longer pile up as `renders/run-<id>/` folders. Each result lives in `renders/<sex>-<settype>-atlas/` and holds only the newest complete render (loose PNGs, atlases, `.ppda`, manifests). A new render is built in a temporary in-progress folder inside `renders/` (also used for resume). Only after it is fully complete and verified is the previous `<sex>-<settype>-atlas/` removed and the new folder renamed into place. A crash or cancel therefore never loses the last good result, and an unfinished run can still be resumed. Older `run-*` folders from earlier versions are not deleted automatically; the 2D preview ignores them with a notice. The 2D preview and **Render alles** use these fixed folders.

@@ -399,6 +399,8 @@ Cause found: the 2D preview wrapped its clock on the source clip duration, while

399

400

A **Render alles** button renders the whole project in one batch: every configured body (male and female, when present) and then every configured equipment preset for each applicable sex. Each item gets its full production export (all clips × frames × all views, four maps, atlases + `.ppda`) at the project's target resolution and framerate. It is a queue of the existing per-item jobs, sharing the same progress/preview, cancel and resume behavior. Overall progress shows the item and pass counts. Items that cannot be rendered (no body, equipment without a binding for that sex, invalid setup) are skipped with a clear diagnostic per item, and the rest of the queue continues. Afterwards, a summary lists what was rendered, what was skipped and what failed.

400

A **Render alles** button renders the whole project in one batch: every configured body (male and female, when present) and then every configured equipment preset for each applicable sex. Each item gets its full production export (all clips × frames × all views, four maps, atlases + `.ppda`) at the project's target resolution and framerate. It is a queue of the existing per-item jobs, sharing the same progress/preview, cancel and resume behavior. Overall progress shows the item and pass counts. Items that cannot be rendered (no body, equipment without a binding for that sex, invalid setup) are skipped with a clear diagnostic per item, and the rest of the queue continues. Afterwards, a summary lists what was rendered, what was skipped and what failed.

401

402

Live preview during Render alles (Tim t990u): the live render pass preview stays visible and updates exactly as it does when rendering a single body or equipment set (same highres/detail/target passes, same progress bar and cancel button), following whichever sex/set is currently rendering; the current item (sex · set, item k/n) is shown above it.

403

402## Decision 2026-11-07 (Tim t968u): one result folder per sex + settype, newest only

404## Decision 2026-11-07 (Tim t968u): one result folder per sex + settype, newest only

403

405

404

Exports no longer pile up as `renders/run-<id>/` folders. Each result lives in `renders/<sex>-<settype>-atlas/` and holds only the newest complete render (loose PNGs, atlases, `.ppda`, manifests). A new render is built in a temporary in-progress folder inside `renders/` (also used for resume). Only after it is fully complete and verified is the previous `<sex>-<settype>-atlas/` removed and the new folder renamed into place. A crash or cancel therefore never loses the last good result, and an unfinished run can still be resumed. Older `run-*` folders from earlier versions are not deleted automatically; the 2D preview ignores them with a notice. The 2D preview and **Render alles** use these fixed folders.

406

Exports no longer pile up as `renders/run-<id>/` folders. Each result lives in `renders/<sex>-<settype>-atlas/` and holds only the newest complete render (loose PNGs, atlases, `.ppda`, manifests). A new render is built in a temporary in-progress folder inside `renders/` (also used for resume). Only after it is fully complete and verified is the previous `<sex>-<settype>-atlas/` removed and the new folder renamed into place. A crash or cancel therefore never loses the last good result, and an unfinished run can still be resumed. Older `run-*` folders from earlier versions are not deleted automatically; the 2D preview ignores them with a notice. The 2D preview and **Render alles** use these fixed folders.