Layer rows are 48 points tall with alternating shades, hover, an accent edge on the selected
row and a divider under each layer. Each row shows its content thumbnail (the layer's own result
in the displayed channel) and its mask thumbnail, each selectable on its own; a subtitle names
the layer type and effect count; blend mode and opacity stack on the right. Effects hang under
their layer on tree lines in "Content effects" and "Mask effects" groups that fold without
touching the document, each with a thumbnail of the stack up to and including it (a hidden
effect shows what it bypasses, struck through). Folder contents indent with lines.
Paint and fill thumbnails show their own coverage over a checkerboard; folders composite their
children. Every size derives from layer_panel::layer_preview_size, so a preview size setting
plugs in there. New strings are translated in every shipped language.
The compositor renders a one-layer cut of the stack at 64 px (content in a channel, mask, or
the stack up to an effect); the engine keeps an immutable snapshot, a worker thread, an LRU
cache and stale-result rejection.
Saved cameras (Project.cameras) already act as bookmarks; add camera.bookmark1..9 commands,
a short viewport glide when going to a camera from the UI, a test and a control-protocol section.
Use the UI control height for high-poly and cage file buttons and their row-width reservations. Cover smaller and larger control sizes in the bake UI regression test.
Use theme control heights for toolbar, path, asset, property, bake and browser export controls. Keep width calculations in sync with the rendered controls and verify narrow toolbars at three theme sizes.
Keep mode buttons accessible while view controls join the scrolling strip when space is tight. Respect the remaining clip width, simplify the layout, translate view hints, and add toolbar interaction and visual checks.
The Painting, Bake and Render buttons move from the left tool shelf to the
right end of the top bar, which now shows in every mode. The view and mode
buttons keep their place; the tool controls scroll in their own strip with
arrow buttons and the horizontal wheel instead of drawing over them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Upstream removed bake/maps.rs, engine/tests/auto_rebake.rs and read_skew
(moved elsewhere); take the deletions. Convert two new chunks_exact uses in
bake/test/setting.rs.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Use slice fill in the particles test (manual_slice_fill) and
AtomicUsize::try_update, the renamed fetch_update, in the connection
limiter. Both are behaviour-neutral.
Refs #233
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Clippy 1.99 flags chunks_exact and chunks_exact_mut with a constant
chunk size (chunks_exact_to_as_chunks). Switch those call sites to
as_chunks / as_chunks_mut. Behaviour is unchanged: the trailing partial
chunk was already dropped.
Fixes#233
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Review point: with no worker thread the fallback built a whole in-memory zip per
entry; it now writes each entry straight into the file like the serial writer,
and the test covers that path.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The generator panel had level, softness and noise but no way to lift or lower the finished mask. The new offset is added to the result and clamped to 0..1. The thresholding now lives in Generator::shape, shared by the compositor and the preview.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The secondary-ray maps now start from 64 rays reaching a tenth of the
bounding-box diagonal (was 32 rays and a quarter), the defaults common to
mesh-map bakers. Occlusion falls off linearly with the hit distance instead
of with its square, on the CPU and in the GPU shader, so a hit halfway to the
max distance counts half. Thickness keeps its 0.1 reach and also gets 64 rays;
bent normals still share the occlusion rays.
Tests: a floor under a ceiling at half the max distance bakes 0.5 occlusion
(0.25 with the squared falloff), and the default ray settings.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Opening a project file stops at 8 GiB of decompressed data (MAX_TOTAL), but
saving had no matching check, so a too big project saved fine and then failed
to open. Saving now counts the bytes the loader would count and refuses before
the temporary file is created, with an error that names the size and the limit;
the existing file stays as it was. The limit itself is unchanged. A test checks
that the count equals what load counts for a real file.
Fixes#215. Refs #200
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Saving compressed every zip entry one after the other with deflate level 6 on a
single thread; the baked maps were about three quarters of the time. The entries
are independent, so native builds now compress them on up to 8 worker threads
(one core is left to the UI) and copy the finished entries into the file in the
original order with raw_copy_file. Entry names, order, methods, CRCs and sizes
are unchanged, the format is unchanged, older versions open the files.
Memory stays bounded: a worker only starts an entry while the estimated size of
the entries started and not yet written is under 3 GiB, and baked maps and pixel
tiles stream into the compressor instead of building a raw copy first. wasm and
single-core machines keep the serial writer. The atomic tmp + fsync + rename
path is unchanged.
Refs #200, fixes#214
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Replace the per-vertex mesh curvature with short ray rings around each
texel, so triangle size no longer decides the result: walls beside the
point (concave), hard edges (convex), the spread of the smooth normals and
true curvature where shading and faces agree. A high poly uses a small
true-curvature radius, and with match by mesh name a part only reads
itself. Rays go through RayScene::closest in bounded chunks, so they run
on the GPU tracer when there is one. Ray is laid out as the shader reads
it and uploads without a copy. Output stays 0..1 with 0.5 flat;
curvatureStrength and curvature_from_normal keep their meaning.
Clean-room implementation.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>