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>
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>
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>
63 -> 72 materials. Cobblestone uses rounded cells with sunken joints, gravel
fine Voronoi stones, plaster a soft troweled tooth; linen a coarse weave, wool
and moss a soft sheen.
Neighbouring blocks and coarser mips blended Extra's alpha into a scale that
belongs to neither tile; parallax and height-to-normal now load it at mip 0.
`ball 1.obj` and `ball_1.obj` sanitized to the same companion stem, so
exporting both into one folder overwrote each other's .mtl and textures. A
name the sanitizer changes now gets an FNV-1a hash of the original appended;
names that need no change keep their companions as before.
A pen lifts reporting no pressure, and a tap paints on that frame, so a tap
painted at full pressure. The release now keeps the pen's contact pressure (a
touch without pressure, such as a finger, starts fresh).
Browsers report pen pressure only for pens that send touch events; desktop
browsers deliver pens as a mouse, so the docs say so.
A UV tile with a lower resolution than its atlas block fills the block's
corner, so it has fewer texels per UV unit. Neighbourhood filters (blur,
sharpen, warps, bevel, glow, ...) and height-to-normal slopes used the block's
texel density for every tile, so such a tile blurred twice as wide and showed
twice as steep slopes in UV space.
TextureSet::block_scales gives each block's share; the compositor filters each
block at its tile's radius, texture export and the CPU path tracer scale the
slope by it, and the display packs it into the Extra texture's alpha for the
viewport and GPU path tracer shaders (parallax too).
Found while testing crates/formats/src/mesh_import/obj.rs:77 (model.name passed to raw.polygon); stem fallback in mesh_import/mod.rs `read`
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Found while testing crates/formats/src/mesh_export.rs:24
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The 2D view painted at full pressure whatever the pen reported; it now reads
the same touch force as the 3D view. Docs say where pen pressure works today
(Windows Ink and the browser) and that Linux and macOS pens arrive as a mouse
until the windowing layer reports them.
Found while testing crates/formats/src/mesh_import/ply.rs:164 (nverts is set at line 140)
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>