Live repaints merged into the last step whenever its label matched, so editing the same
path again (or the same index in another sublayer) joined the earlier edit and one undo
reverted both. An edit now merges only into the step it made itself. Stored brush
settings are clamped when read, like the tool's own, since they come from the file.
A Windows release build has no console, so when the GPU could not be
set up or the app panicked, the window never showed or vanished without
a word. Such errors now also go to errors.log beside the settings and,
on the main thread, to a message box that names the log file.
Fixes#106.
Keeps both sides of the translation tables, AGENTS rules and the formats module list;
material files in the browser load before the ask-to-save step (they add a layer, not a
new project); Arabic for the eight MaterialCraft strings; menu parity regenerated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A fill channel's source menu offered a uniform value, procedurals and
anchors, but no image, so a normal or roughness map could not be put on
its channel. The menu now lists the image resources and Import..., and
an image dropped from the Assets panel onto a channel becomes its
source. The mesh map slots share the same menu and drop target.
Fixes#127.
When file.exportTextures is given a colorSpace, colour maps carry it: an ICC profile in PNG,
JPEG, TIFF and WebP, the chromaticities attribute in EXR. TGA, BMP and HDR have no place for one
and warn. Data maps and exports without a chosen space are unchanged.
The profile is a small version 2.1 matrix/curve profile written from the space's primaries
(Bradford-adapted to D50), tested against the published sRGB colorants.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The length limit cuts the longer placeholder at a different place than the tile number,
so a long template got a <UDIM> name that matched none of the files written. A name is
now kept only when putting the tile number back gives the file's own name.
- SkewMap::paint refuses a stroke whose dabs would visit more than 2^26 texels, before any
texel changes; the dab count alone didn't bound the work of a big brush on a big map.
- bake.skew.set checks the image size from its header (decode_image_within) before decoding.
- The 2D view is shown for the skew brush in bake mode only, not in rendering mode.
- Prepared::correct allows its argument count for clippy; the skew test uses its own folder.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- MaterialX export: a tiled file's <UDIM> name comes from the file plan, so a set called
cloth.1001.body keeps its name; the DirectX normal warning is raised only when a material has a
normal map.
- colorSpace that isn't a string is an error instead of the format's default.
- MaterialX import: an image that isn't a regular file is skipped with a warning (a pipe in the
folder would have blocked the read).
- Auto-rebake: remembers which inputs each map image was baked from, so undoing a rebake brings
back a map that is out of date and rebakes it; not scheduled automatically on the web build,
where a bake would run on the page's thread.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A paste into a layer of another texture set set the session's target
to the new effect, so a later stroke in the active set could commit to
it. The target now changes only for a paste into the active set. The
layer and effect row menus offered Paste effect only while a layer was
already selected, though a click selects the row first; they now check
the clipboard alone.
With an effect selected, Delete removed its whole layer and Ctrl+D
duplicated the layer. Both now act on the effect, like the clipboard
shortcuts; effect commands default to the selected effect.
An effect's context menu copies, cuts and pastes it, and Ctrl+C,
Ctrl+X and Ctrl+V act on a selected effect (pasting a copied one above
the selected effect, or on top of the selected content or mask).
Painted strokes come along, resampled to the target set; generators
and other one-stack effects go to their stack, and a fill reading an
anchor point needs one below its new layer. effect.copy, effect.cut
and effect.paste share the layer clipboard.
- core: Fill::link (MaterialLink: package resource, graph, exposed inputs, presets,
image inputs, size); BakedMap::interop_id / for_input shared mesh-map identifiers
- formats: own .mcmat reader (no MaterialCraft dependency) and 16-bit mesh-map PNGs
- engine: material.load takes .mcmat and .mcraft; material.link.set / .preset / .cook /
.saveSource; LinkJob re-cooks through materialcraft-cli at the texture set's
resolution with baked mesh maps as graph inputs; fresh resource names per cook keep
undo and the decoded-image cache consistent; packages count as used resources
- ui: linked-material section in fill properties (presets, sliders, colors, toggles,
options) cooking on a worker thread, one process per layer, stale results redone;
Open in MaterialCraft; File > Import material...; .mcmat drops; library shelf lists
.mcmat and rescans on focus; 8 new strings in every language
- tests: materialcraft_link (import, params, undo, duplicates, mesh maps, save, and a
real materialcraft-cli round trip when MATERIALCRAFT_CLI is set)
- docs: README, features, control protocol, architecture, AGENTS, ROADMAP, parity
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Committed paths are stored in a new path sublayer (EffectKind::Path) on the
layer content or mask and the sublayer is repainted from its paths whenever one
is added, edited or removed. path.edit loads a path (with its brush and
material) into the Path tool; changes repaint live as one merged undo step.
path.remove deletes one. Manual strokes are refused on path sublayers, so they
can't be painted over by accident. The sublayer properties list its paths.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The History panel lists every undone step too (dimmed, next first) and
a click on any step goes back or forward to it, the current one
highlighted. edit.undo and edit.redo take {steps?} for the same jump.
Ctrl (Cmd on macOS) + right-drag in the 3D or 2D view changes the
brush size (left/right) and hardness (up/down), Ctrl + left-drag its
flow and angle, instead of orbiting or painting. The brush cursor stays
where the drag began, with the values beside it, and the Brush
properties name the gesture.
Undoing an effect's add or duplicate took the selected effect away and
left the selection on it, so the row lost its highlight and strokes had
no target. The selection now falls back to the stack the effect was in.
After Cancel or a bake error the app re-queued the same Auto-rebake on the next frame, forever, because a set only counted as up to date after a successful bake. Session::bake_abandoned records the set being baked and the queued ones as seen; cancel_bake and the bake error paths call it. Also drops a useless into_iter() and an unreachable branch in bake.autoRebake.
Each mesh map slot of the Texture Set Settings takes an image resource:
drop one from the Assets panel on the slot, or pick it from the slot's
menu, which also clears the slot. The image is resampled to the size of
the set's other mesh maps (or its bake size), its values read as data,
a normal map in the project's normal format.
textureSet.meshMap.set {ts?, map, image} and
textureSet.meshMap.clear {ts?, map} give agents the same.
uvtiling is clamped to 0.001..=1000, the range layer.fill.projection accepts. Image files are capped by resource_cmds::MAX_BYTES instead of a second copy of the number.
The .mtlx tags colour textures with the export's colour space: srgb_texture, lin_rec709, acescg, or lin_ap0_scene for ACES2065-1 (MaterialX 1.39 has no AP0 space; the export warns). A colour map packed into one channel (L) is not converted and now says so. The $colorSpace variable's description lists every value.
Float files (EXR, HDR) hold linear values, so their colour maps are tagged lin_rec709 instead of srgb_texture. The .mtlx goes through formats::write_atomic, and a set whose name sanitises to an earlier set's file name is skipped with a warning instead of overwriting it.
Effect rows in the layer stack can be dragged within their stack (a
drop lands above the row, or below it from its lower half), and their
context menu duplicates an effect just above itself, painted pixels
included. effect.move {effect, index} and effect.duplicate {effect}
give agents the same.