Files
solvecraft/docs/render-settings.md
T
selune 9e6e0b8df1 Render workspace: complete experimental ribbon, resources and effects integration (#5493) (#5494)
* wip(render): reconcile completed material and image pipeline source with 0.20 (#5493)

Source-only integration reference for staged review, not a merge-ready aggregate.
Donor: 0xlillith/solidcraft@aea20b0115.
Upstream: 858e5995d6.

Retain original CPU/material contracts and explicit GPU donor provenance in
docs/render-materials-lab.md (#2067, #2191, #2780, #3306). Preserve released
format migrations and current navigation/startup/shell behavior. New saved
records use pending descriptors. The physical-card descriptor follows the
maintainer's material-engineering-cards naming request, with a legacy-lab
format-29 regression. Replace raw new panel hosts with shared containers.

Repository checks, complete workspace/all-target Clippy, and the independent
physical/resource authoring checks pass for this source. The fresh full local
CI invocation has reached test compilation and is not yet complete. Do not
transfer donor native output or prior test totals to this integration.

Generated review screenshots, video, package ZIP and machine logs remain at
the immutable personal evidence pin. Uncommitted geometric displacement is
backed up separately, not silently included. No kernel/vendor change, direct
main write, release or independent contributor-branch rewrite.

Co-authored-by: Christian Svensson <blue@cmd.nu>

* test(cli): pin the Compact camera-sample admission diagnostic (#5493)

The bounded request still refuses 1024x1024x64 samples before host initialization and writes no output. Update only the stale expected diagnostic to the existing Compact budget wording; production limits and code are unchanged. Exact-tree CLI regression suite: 14 passed, 0 failed. The full repository gate has been invoked separately and is not yet complete.

* Normalize UI container violation paths across platforms

Report repository-relative paths with forward slashes so diagnostics and the existing nested-package regression assertions agree on Windows and Unix. Keep the container detection rules unchanged.

Validation: official ui-containers gate and all seven focused xtask tests passed; rustfmt and diff checks passed. Only xtask/dependencies were compiled; no application build or heavy tests.
(cherry picked from commit 44b58d8e10)

* fix(render): preserve camera contracts and correct acceptance regressions (#5493)

Preserve Design view.apply semantics with a separate strict Render camera command. Retain existing translations when English-only aliases collide; add material-axis entries and camera-specific pitch labels. Compare complete validated engineering cards and retain job handles before cancellation.

Focused and native acceptance is pinned to tree f8a423b21f. Full CI has been invoked separately and is not claimed green. Landing follows the render integration policy in #5493.

* fix(render): resolve showcase licence and upstream resource hygiene (#5493)

Record SychPL's explicit MIT OR Apache-2.0 grant, retaining source/model bytes and the Ubuntu lettering notice. Remove 80 absent attribution rows, personal fork records, dead delivery attributes and three fork/resource-only workflows. Existing xtask assets now performs bounded offline hash checks and rejects orphan render attribution; no parallel draft CI or package installation. Original authoring reproduction remains explicit. Scoped xtask tests, assets, Clippy, formatting and prepared SELENE validation pass; no application or renderer-wide result is inferred.

* fix(render): align saved bounds and progressive sample resolution (#5493)

Address review r4364211669/r4364211677/r4364211681/r4364211691/r4364211695. Persisted light/frame domains respect the existing 1e9 document bound; related LED/rectangle/direction cases use the same bound. Workstation primary resolve shares the 4096 admission cap and film counters use checked conversions. Exact candidate: 485 CPU render tests, 21 render document tests and strict scoped Clippy pass, including positive boundary round trips and 2048/4096 end-to-end checkpoints. No released format/migration edits, relaxed test limits or full-stack acceptance claim.

* wip(render): isolate optional resources and harden sample handling (#5493)

Review work in progress: opt-in encoded render library with reproducible runtime catalog exports; native-only robust dependency through the workspace; checked bloom slices; per-sample point-light diagnostics; independent area-light spatial/film keys. Resource-module binaries in both configurations, generation, Cargo production feature graphs and attribution checks pass. Full engine/render regression and combined acceptance are pending: do not merge this donor as a constituent or treat scoped resource proof as runtime acceptance.

* fix(gpu): preserve donor allocations through the scope-safety repair (#5722)

Port the native-validated #5723 scope-cleanup correction into the experimental donor, retaining its adaptive, volume, aging, photographic and bloom allocations. Same reverse-drain helper and regression cases; the donor combination still needs its own compile/test gate and is not covered retroactively by render-base results.

* claim: #1369

* Reject unknown pending concepts after format folding (#1369)

* test(render): close bounded sampling and bloom review regressions (#5493)

Validate the optional-resource/lighting/dependency donor at its exact tree. Required Vulkan GPU 127/0/3; CPU renderer 487/0; engine Render 72/0; document render 21/0; lean library 7/0; strict scoped Clippy, assets/layers/lists/containers and lean-engine WASM pass. Preserve original failed controller/typing attempts. This is the draft donor/disposition source, not a replacement for constituent render PRs or final main acceptance.

* wip(render): preserve stable aging target validation candidate

Exact staged source from prior review work on donor 3b892eab5e. This is a recovery/review checkpoint, NOT accepted delivery. An actual command-path regression currently fails because the selected executor refuses ordered surface aging. No assertion, capability or admission limit is weakened. Native/UI/full combination acceptance remains pending. Saved/runtime split adds one pending descriptor and retains original file scope; no main/render branch is changed.

* test(render): preserve numeric setup intent at the admitted coordinate bound

Follow up jyviko review on #5494 without weakening the corrected saved-coordinate contract. The positive clicked fixture uses 1e9 instead of inadmissible 2e9; explicit out-of-range cases still refuse, and the full saved setup round-trips through JSON and the native container. Exact-source Render workspace 95/0 and strict all-target UI Clippy pass. This does not incorporate the separately failing stable-aging candidate or claim full current-render acceptance.

* test(render): use the real GPU executor for saved aging

Move successful native cold-reopen Check/Start coverage from the CPU-backed protocol fixture into the production GPU executor tests. Verify capture-index changes preserve the stable target and that enabling aging changes both PNG and raw EXR output. Retain explicit, allocation-free refusal coverage for executors without aging support. Production capabilities and admission checks are unchanged.

* fix(render): persist stable identities for targeted aging (#5493)

Separate saved RenderBodyTarget identities from captured mesh ordinals. Reject legacy ambiguous targets, resolve Check/Start after visibility changes and preserve native reopening, copies and undo. Unsupported executors still refuse; real AMD Vulkan regression completes saved aging after reordered capture.

Source tree 6b84c8ad passes document 23, engine Render 75, GPU effects 5 and Render UI 95 with no failures; scoped strict Clippy, WASM and repository gates pass. Fresh CLI/native reopen and clean/aged GPU exports pass with identical physical totals and inspected actual images. Whole current-render integration is separate.

* fix(render): reconcile combined CPU/GPU contracts on current upstream

Unify captured resources/status and CPU-vs-GPU request schemas after the real two-parent integration; remove obsolete duplicate Vulkan selector and retain combined platform-filter regression. Deduplicate only identical or superseded test definitions, retaining the stronger card metadata and reserved-executor assertions. No assertions, admission limits or feature refusals are weakened.

All targets of render dependencies, GPU, engine, UI, CLI and native app pass cargo check with raytrace-cpu and bundled-render-library at tree c70d00d1. Native executable tests and full current-source acceptance remain pending. This is a private integration rehearsal for subsequent constituent PRs, not an aggregate official render/main merge.

* test(render): retain one complete host lifetime regression set

Deduplicate byte-identical DropProbe/task-lifetime tests and retain the adapted environment/texture ownership regressions with every assertion and complete memory estimate. Keep the registered-geometry admission regression once; only struct field order differed. Replace a one-element diagnostic loop with its equivalent block, preserving all wrap/width assertions.

Test-only integration repair. Formatting and diff checks pass; refreshed executable validation is required. No production behavior, limits, assertions or ignores changed.

* fix(doc): recognize the proven format-29 card descriptor alias

Normalize only the historical format-29 physical-material-cards spelling, and only when material-engineering-cards is registered. Admission and migration de-duplication use the same identity. Unknown concepts, wrong versions and incapable readers still refuse before mutation. Six controlled-history Rust regressions and actual CLI migration/no-clobber acceptance pass. No version, released migration or CI changes. Refs #5793, #1369, #5493.

* test(render): preserve grounding refusal before explicit instance moves

Update the two Render binding fixtures for upstream first-occurrence grounding. Verify grounded movement refuses without changing document/history, then explicitly unground through the public command before the intended move. Retain every target, resource, copy and persistence assertion. Refs #5493.

---------

Co-authored-by: Christian Svensson <blue@cmd.nu>
Co-authored-by: Victor Santos Oliveira <56417388+Vittuu@users.noreply.github.com>
Co-authored-by: cfaulkingham <colin.faulkingham@gmail.com>
2026-10-24 14:21:59 +00:00

12 KiB
Raw Blame History

Persistent render settings

Named setups save common render settings and, optionally, the complete numerical configuration of one selected image method, including an optional embedded HDR. Saving does not start a render, apply the navigation camera or require an installed CPU/GPU executor. render.preflight and render.start consume the same saved configuration and still check the current host, geometry, capabilities and memory limits.

Commands

{"command":"render.settings.set","params":{"name":"Studio","set":{"width":1600,"height":900,"exposure_ev":1.5}}}
{"command":"render.settings.get","params":{"name":"Studio"}}
{"command":"render.settings.get","params":{}}

set creates a named setup from defaults or replaces supplied top-level fields in an existing setup. A supplied camera or job replaces the whole value; it is not a recursive patch. Omitted fields retain their values. job: null explicitly clears the job and restores the legacy request protocol. Unknown fields (including camera/job fields), invalid types and invalid values fail before document mutation. A new empty set saves the defaults; setting an existing setup to identical values is a no-op, preserving redo history and revision. Each effective edit is one undo step and marks the document dirty. There is no delete or rename command in this slice.

Named get returns {name, setup} or an error for a missing name. Without a name, it returns {setups, defaults}. Reads do not evaluate the model or change history.

Field Default Saved contract
backend builtin Valid R1 backend ID, at most 64 ASCII bytes; unavailable IDs survive reopen
mode preview R1 preview / final mode; availability checked by a future render request
camera Existing Camera::default() Snapshot of target, yaw, pitch, roll, distance, fov and up; mm/radians, existing Z-up default
width, height 1024, 768 Positive, each at most 4096; product at most 4,194,304 pixels
format png R1 output format (png / exr); saving EXR does not add an encoder
exposure_ev 0 One exposure authority: raster requires 0; CPU raytrace accepts -16 through 16; GPU path accepts -32 through 32. Legacy setups retain -32 through 32.
environment_rotation 0 Legacy finite radians, magnitude at most 1,000,000. A typed job requires 0.
environment_intensity 1 Legacy finite value, 0 through 100. A typed job requires 1.
background [236, 240, 245] Three sRGB byte values; display backplate, independent of illumination
job absent Optional typed active raster, cpu_raytrace or gpu_path configuration; absent/null keeps the legacy protocol

Camera target coordinates and positive distance are bounded to magnitude 1e9 mm; angles to 1e6 radians. FOV is finite, 0 <= fov < pi; zero means orthographic in the existing camera model. Both existing camera up axes are retained. Setup names are trimmed, nonempty, at most 128 UTF-8 bytes, without control characters. A document has at most 32 setups. Validation also runs during document deserialization.

Complete numerical job intent

job is tagged by method. It saves the active method, rather than separate CPU and GPU drafts. All numbers use the existing renderer contracts: world distances are millimetres, angles are radians and light colours/radiances are linear RGB.

Method Saved fields Main limits and defaults
raster transparent_background Defaults to false; no nonzero exposure or raytrace controls
cpu_raytrace options: optional progressive, primary_samples, preset, lights, punctual_lights, area_lights, area_samples, seed, shadows, constant environment, embedded hdr Primary samples 1/4/16 (default 1); shadows true; optional progressive/lists/preset/environment/HDR absent. At most 8 directional, 8 point/spot and 4 rectangular lights; progressive has the narrower contract below.
gpu_path transparent_background, options: samples, max_depth, seed, tone_map, denoise, lens, lighting, sky environment, embedded hdr Samples 1..4096 (default 64), depth 1..16 (default 8), seed u32 (default 0), Reinhard tone map, denoise false, optional values absent

CPU preset and explicit lights are mutually exclusive. An omitted/null light list remains unspecified; lights: [] explicitly removes the default directional lights. Point lights retain their optional spot cone, its world emission axis and both half angles. Rectangular lights retain full side vectors, sample count and seed; area_samples and seed require a nonempty rectangular-light list. Area samples are 1/4/16/64. Lists are bounded while deserializing and are never truncated. The CPU constant environment retains {color, intensity} independently of the backplate. See CPU light union for the spatial and light validation contracts.

CPU progressive: {samples_per_pixel, seed} stores bounded camera accumulation using the existing CPU transport. An absent/null value preserves fixed AA; an empty object defaults to 16 samples and seed 0. Samples are 1..64 and the seed is u32. primary_samples must be 1, output is at most 1,048,576 pixels, and width × height × samples_per_pixel is at most 16,777,216. Saving checks these limits without a render host. Area/LED lights, dielectric and anisotropic-face overrides are refused in this mode; the fixed CPU route retains them. Embedded HDR and one setup exposure remain compatible. See CPU progressive sampling for reflection limits, work admission and provisional/final publication. The top-level runtime progressive: true continues to select GPU.

GPU lighting retains the complete RGB ambient radiance, optional sun and at most four rectangular lights. Omitted/null lighting keeps the renderer's legacy studio; an explicit all-zero lighting object means a black studio. Those values are not interchangeable. lens retains aperture radius and axial focus distance; nonzero aperture requires a perspective camera. An explicit zero-aperture lens remains explicit. Tone mapping and denoising retain their existing meanings and do not create new executor capabilities.

The portable procedural GPU environment is:

{"kind":"sky","gradient":{"zenith":[0.16,0.32,0.7],"horizon":[0.8,0.9,1],"ground":[0.12,0.1,0.08]},"rotation_rad":0,"intensity":1}

Gradient entries are finite linear RGB in 0..1,000,000; rotation is finite within ±1,000,000 radians; intensity is 0..100. Omitted gradient/rotation/intensity use the shown defaults. The original procedural gradient is not a calibrated atmosphere. An environment replaces the constant ambient-light term; it does not replace the display background. See environment rendering, thin lens and studio lighting.

An embedded HDR uses the separate options.hdr field and cannot coexist with a constant CPU environment or a GPU sky. It references immutable bytes in render.resources, not a file name. Saved HDR resources documents atomic file capture, CPU/GPU colour policies, strict container hydration and the offline save/reopen contract. Optional hdr absent/null means no HDR; when an HDR object is supplied, its resource and controls are required.

RenderSetup.exposure_ev is the only saved EV. CPU lowering copies it into the runtime raytrace.exposure_ev and resets the legacy common-settings EV to zero; GPU lowering uses it in JobOptions. CPU/GPU options.exposure_ev is rejected. The two legacy common environment fields must stay at 0/1 when job is present; the method's typed environment owns those values. Existing legacy values are preserved, and a conflicting conversion fails instead of clearing them.

Save, check and start

{"command":"render.settings.set","params":{"name":"CPU studio","set":{"width":1600,"height":900,"exposure_ev":1,"job":{"method":"cpu_raytrace","options":{"primary_samples":4,"preset":"warm_cool","shadows":true}}}}}
{"command":"render.preflight","params":{"setup":"CPU studio"}}
{"command":"render.start","params":{"setup":"CPU studio","replace":true}}
{"command":"render.settings.set","params":{"name":"GPU studio","set":{"width":1600,"height":900,"exposure_ev":0.5,"job":{"method":"gpu_path","options":{"samples":256,"max_depth":8,"seed":42,"tone_map":"aces_fitted","lighting":{"environment":[0.1,0.2,0.3],"area_lights":[]},"environment":{"kind":"sky","intensity":0.5}}}}}}
{"command":"render.preflight","params":{"setup":"GPU studio"}}

An inline {"settings": full_setup} has the same semantics as a saved setup name. The engine resolves the typed job before choosing CPU or GPU dispatch. A saved gpu_path method requires the gpu-path executor; another executor announcing progressive sampling cannot replace it. A missing or unsupported host blocks Check/Start while leaving the saved intent intact.

For a complete job, the only additional request field is replace. Parallel runtime controls such as progressive, integrator, raytrace, lens, environment or transparent_background fail, including explicit null/false values. They cannot silently override a setup. For legacy job absent/null, the existing runtime request API remains available; it has no inferred CPU/GPU method.

Explicit portability boundary

External HDR paths, texture maps, GPU dielectric/clear-coat/texture body bindings and CPU reflection, anisotropy, emission, surface-effect and dielectric bindings are not part of this saved job format. Their fields are rejected, even when an unsupported list is empty. Runtime requests can still use those existing features with an inline setup whose job is null. Saving a complete setup must not discard them or turn a current body name/ordinal into a persistent identity. HDR bytes are portable through render.settings.capture_hdr; portable maps and durable body/face bindings still require separate contracts. Runtime requests can reference an existing HDR resource while supplying temporary bindings, without persisting those bindings.

No captured scene revision, worker, device, image result, JobId, host availability or external path is serialized. Reproducible input configuration does not promise bit-identical pixels across devices or renderer versions.

Persistence and evaluation

Named setups live in render: {setups: {name: setup}, resources?: {sha256: resource}}; empty render state is omitted. The optional numerical job adds the render-job-intent pending format descriptor. Embedded HDR adds its own render-hdr-resources descriptor. The optional CPU sampling field adds render-cpu-progressive. No historical format number or migration step is rewritten. Older designs need no job transformation: an absent job keeps their common settings and runtime API. Pending builds without the descriptor refuse the newer design instead of silently losing its saved options. Plain JSON, design containers and document autosave snapshots carry all HDR bytes. A command-only crash replay before a new checkpoint still needs the source path recorded by capture_hdr; it must match the recorded digest. This unit does not make that journal self-contained.

The engine avoids geometry evaluation only after proving that the document differs solely in validated render settings, with unchanged active sketch and pending moves. The proof compares the complete document after normalizing the render field, so mixed geometry/appearance/placement edits take the usual conservative refresh path. It uses a document clone/comparison, not a constant-time or whole-application speedup claim. Unchanged render pointers short-circuit the check for normal modelling commands.

Render-only edits, undo/redo and checkpoint restore preserve model state, its stale marker, cached tessellation and the prepared world state. A stale live-drag result never becomes authoritative through a settings edit; the next model-reading command still settles it normally. Revision advances for consumers that track document changes. Geometry, physical materials and appearances retain their existing representations; the setup stores image configuration, not material assignments.

No new third-party dependency or asset is introduced. doc depends on the existing pure render crate for its shared camera and R1 identifiers, within the L2 → L1 rule.