The map is stored as skew.bin next to the high polys and the cage. A map that fails the
baker's checks on load is skipped with a log line.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
New texturecraft_texel::ColorSpace (sRGB, Linear Rec.709, ACEScg, ACES2065-1): the matrices are
derived at first use from the published primaries and white points (BT.709, ACES S-2014-004,
SMPTE ST 2065-1) with Bradford adaptation, so nothing is copied from a colour-management
library. ExportOptions::color_space (command and dialog: `colorSpace`) converts the colour maps
on their way out; data maps (normal, height, roughness...) are never converted.
None keeps today's behaviour: sRGB in 8/16-bit files, linear Rec.709 in float files. A linear
space in an integer file is written without the sRGB curve; ACEScg and ACES2065-1 in integer
files warn that values outside 0-1 are clamped (EXR and HDR keep them). `$colorSpace` in a file
name template now also says ACEScg / ACES2065-1. The export dialog gets a Color space combo
(label translated in all ten languages).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
file.importMaterialX {path, material?, name?} reads an open_pbr_surface, standard_surface or
gltf_pbr material and adds one fill layer: image inputs (directly, through a nodegraph output
or normalmap/convert/constant nodes, with fileprefix and the first UDIM tile) become image
resources and sources, literal values become uniform sources (sRGB-tagged colours converted to
linear, colours on scalar channels averaged), the displacement shader becomes height, and the
first image's uvtiling becomes the UV projection scale. Emission follows the specifications'
defaults (off unless emission_luminance / emission is above 0).
Images are read only from the document's folder and below: a document is untrusted. Channels
the texture set lacks, unreadable images and unsupported nodes are reported in `warnings`;
nothing to import is an error. The whole import is one undo step.
Written from the ASWF MaterialX 1.39 and OpenPBR Surface specifications; the reader caps size,
depth and element count and has mutation tests. The inverse of the MaterialX export in #50.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
resource.text draws one or more lines of text, shaped with harfrust (kerning,
ligatures, joined scripts) from the font's outlines (skrifa) and filled by a
non-zero scanline rasterizer, cropped to the ink, as an image resource: white
for the brush alpha, or a color for a decal. text.fonts lists the installed
families and styles, read from each font file's name table only (246 families in
80 ms here); Ubuntu Light and Hack from the UI's built-in fonts are always there
and are the fallback in the browser.
- Properties > Alpha > Text: the text, a font and style, Use as brush alpha and
Place as decal (in the tool's base color).
- Image alphas keep their proportions (their longer side spans the stamp), so a
line of text stays a line; image thumbnails are letterboxed and show alpha.
- harfrust 0.12 and skrifa 0.44 are the versions egui already builds, so the
lockfile gains no packages.
Fixes#40
Importers fan-triangulate quads and n-gons, and the 3D and UV wireframes drew
every triangle edge, so a quad mesh showed its triangulation. Meshes now carry a
per-triangle mask of the diagonals the importer added (Mesh::diagonals), and the
wireframe leaves them out (Mesh::wire_edges), unless a UV seam split one from its
twin.
- OBJ reads polygons whole (tobj without triangulation) and fans them itself.
- OBJ, PLY and the polygon sink (FBX, COLLADA, USD, Alembic) share one fan,
RawMesh::polygon, which records the diagonals.
- The built-in meshes mark their grid quads.
- glTF and STL store triangles only, so they keep every edge.
Fixes#41
zip 9 decodes entry names on demand, so ZipArchive::file_names and ZipFile::name
return a Result. Package lookups (FBX, usdz) skip names that do not decode, and a
project entry with a bad name is a malformed project. The usdz test reads
data_start as an Option. The lockfile pins 9.0.5 rather than the two-day-old 9.2.0.
file.exportTextures takes `materialX: true` and, next to the textures, writes one
`<mesh>_<set>.mtlx` per texture set: an open_pbr_surface whose inputs read tiledimage nodes,
inside a surfacematerial. It follows the "OpenPBR (separate maps)" preset's inputs (base,
metalness, roughness, anisotropy, coat, fuzz, transmission, subsurface, emission, opacity,
normal through a normalmap node, height as a displacement shader). Colour maps are tagged
srgb_texture; data maps are linear. UDIM sets use the <UDIM> filename token. A set with no
OpenPBR map, or DirectX normals (the normalmap node reads OpenGL), is reported in `warnings`.
Written from the ASWF MaterialX 1.39 and OpenPBR Surface specifications, in pure Rust with no
MaterialX library. Engine tests cover a two-set export, UDIM and the off/warn paths.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- Godot 4 (ORM): albedo (A = opacity), orm (R AO, G roughness, B metal), normal (OpenGL),
emission, as StandardMaterial3D reads them
- OpenPBR (separate maps): one map per OpenPBR Surface input the set has, including the coat,
fuzz (sheen), anisotropy, transmission and subsurface lobes, geometry normal (OpenGL) and a
16-bit height; maps of channels a set lacks are skipped
- test: OpenPBR writes the lobe maps of a set that has them and skips them otherwise
An FBX whose base color textures are files (as most exporters write them) now keeps them: like
a loose USD layer becomes a .usdz, opening, importing or adding it as a high poly packages the
FBX with the texture files it names, so color map bakes see them and the project stores them.
- fbx:📦 a stored zip of the FBX (first) and the files found below its folder, by the
Texture's (or Video's) RelativeFilename, else its absolute FileName's file name next to it;
textures found nowhere are named in the log
- fbx::read opens such a package like the FBX (embedded content still wins)
- shared zip limits and entry reading for usdz and FBX packages (mesh_import::zip_entry)
- test: relative and file-name-only lookups, binary and ASCII, missing files warn, packages
re-import as they are, packages without an FBX or nested ones are errors
Cameras in FBX, COLLADA and USD files join the project's camera list, as glTF cameras do.
- FBX 6/7: Camera Models (looking down +X) with the lens from their Camera NodeAttribute or
the Model's own properties (focal length over film height, else FieldOfViewY /
FieldOfView; CameraProjectionType 1 = orthographic); FBX 6 Producer views skipped
- COLLADA: instance_camera in scene nodes (perspective yfov or xfov + aspect_ratio,
orthographic ymag or xmag + aspect_ratio); node transforms understand lookat
- USD: Camera prims (focalLength over verticalAperture with USD's fallbacks, orthographic
projection), through xform ops and the hierarchy
- RawCamera::placed and lens_fov shared by every reader (glTF too); an orthographic view
height follows its node's scale; at most 64 cameras per file
- tests: a camera in the FBX 7 binary/ASCII scene, a Producer view in the FBX 6 file, a
lookat camera in the COLLADA scene, a perspective and an orthographic camera in the USD scene
The UsdPreviewSurface of each exported material gets clearcoat and clearcoatRoughness from two
more UsdUVTexture maps (Clearcoat, ClearcoatRoughness; raw), rendered from the Coat weight and
Coat roughness channels, as the GLB export already carries them.
- a set without coat channels produces no coat maps; a black coat drops both maps, like a
black emissive map
- usda, usdc and usdz; File > Export mesh, file.exportMesh and the MCP mesh_export tool
- tests: the USD round trip exports a coated and an uncoated (black) material in all three
encodings
A .gltf whose buffers or images are separate files, and a loose USD layer whose
UsdPreviewSurface textures sit next to it, now open, reimport and bake as high polys with
those files, and projects keep them: `self_contained_mesh` folds a .gltf's files in as data
URIs and packages a loose layer with its textures as a .usdz, so the stored mesh imports
from its bytes alone. Only files inside the mesh's folder are read (no absolute paths, URLs
or `..` above it); missing ones are named in the log.
- formats: `self_contained_mesh`, `read_mesh_file` and `MeshFile`; `import_mesh` uses them;
the glTF reader no longer reads the disk itself; USD texture lookups go through one
`Assets` source (usdz package or loose files)
- engine: file.open, file.new, file.reimportMesh, bake.highPoly.add and bake.cage.set read
meshes this way; a failed reimport no longer leaves the session pointing at the new file
- automation: mesh_import / mesh.import read the files under the same workspace rules
- CLI `info` reports a .gltf with external buffers
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Code comments, crate descriptions, the MCP stroke schema and the Linux package descriptions
describe features in their own words instead of naming the reference application or other
vendors' products (file format names stay)
- The README follows the layout the other Crafting Apps use (VectorCraft): a look around, made
in TextureCraft, why TextureCraft, quick start with the agent setup, status, downloads per
platform, the Crafting Apps, star history, license; no trademark footer
- The detailed feature list moves to docs/features.md
- A new path-traced render of the built-in crate textured with smart materials
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Strokes pre-blend their commit while painting and recompose committed tiles at low
priority: the 8K stroke-end frame drops from 30-42 ms to 12-19 ms
- Texture set resize runs in the background (8K: 3 s to 0.5 s, UV padding map from island
borders only)
- Decal move/scale/rotate handles; FBX and USD high-poly textures for the color map;
viewport displacement from the height channel; screen-space refraction of the scene
- CI pinned to Rust 1.96.0; FreeBSD VM sized for hosted runners; release builds embed
craft-fonts; file associations for FBX, COLLADA, USD and Alembic on every platform
- README, release checklist, NOTICE and attribution brought up to date
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Baking: per-map ray settings (AO, thickness, bent normals), GPU ray-traced baking with CPU
fallback (~12x), color map from textured glTF high polys
- Files: Alembic (Ogawa) and FBX 6 import, per-tile UDIM resolution, converting a set to UV
tiles, project templates, preserving painted strokes on mesh reimport
- UI: translations (French, German, Spanish, Portuguese, Italian, Japanese, Chinese, Korean)
with a live language picker and CJK fonts, closed panels reopen where they were, viewport
texture resolution setting, frame-budgeted scene sync for 8K sets
- Web: loading screen, WebGL2 notice, app-captured shortcuts, touch navigation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Rendering mode traces on the GPU (compute shaders, ~25x the CPU tracer) with CPU fallback;
CLI/MCP render --samples uses the GPU unless --cpu
- Depth of field in the viewport and the path tracer; multiple cameras with glTF import;
transmission/IOR, coat normal and screen-space subsurface blur; exact 8-bit normal decode
- Filter library (18 filters incl. warp, color balance, gradient map, posterize, MatFinish)
with a Filters shelf tab; geometry decals; clone from the current layer; anchors inside a
content stack; instances across texture-set resolutions; drag saved smart materials
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- UV tiles: auto-detected UDIM texture sets as one atlas per set, padding kept inside tiles,
one file per tile with the $udim export token, builtin:udim_plane
- USD: usda/usdc/usdz import (Crate reader with LZ4) and export with UsdPreviewSurface
- Shader lobes: clear coat, sheen, anisotropy and subsurface scattering channels in the
viewport and the path tracer; car paint, velvet, brushed steel, skin and wax materials;
glTF clearcoat/sheen export
- Color swatch popups no longer stay open
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Compositor caches the stack below and replays what lies above the layer being painted,
also inside folders: painting under a smart material is ~10-25x faster per frame and the
stroke commit 12-30x faster, bit-identical to a full composite
- Paint shows in the frame it is drawn; parallel stamp rasterizing and stroke commit;
camera visibility reused between strokes
- 67 procedural brush alphas with an Alphas shelf tab; drag materials, smart masks and
alphas from the shelf onto the layer stack, layers and viewport
- Export output template editor: user presets with per-channel packing, converted maps,
import/export as JSON, validated at load
- Shift+right drag turns the environment; S+drag no longer orbits while moving the stencil
- Frame profiler and scripted paint test on the control channel (debug.frames, debug.paintTest)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An open-source, clean-room implementation of a Substance 3D Painter-style texturing
workflow, written in pure Rust with egui and wgpu.
- Layer stack with 32 blend modes, masks, generators, content effects and anchor points
- Painting, projection, smudge, clone, path, lasso fill, particle brush and quick mask
- 43 procedural materials, 17 smart materials and 10 smart masks
- Mesh map baking with high-poly, cage and match-by-name support
- PBR viewport with HDR environments, TAA and a path-traced Rendering mode
- glTF, FBX, COLLADA, OBJ, PLY and STL import; texture export presets; OBJ and GLB export
- Dockable Painter-style UI, shortcut editor, web build, MCP server and CLI
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>