Viewer UI

[Darithos]

Deliberately last. The CLI is still answering the questions that decide the architecture (#1, #2, #4); a UI built before those answers would be built on guesses.

Worth starting once #4 and #5 land — textures and a monster catalogue are what make a browser useful rather than a file picker.

Reference

Darithos/D3ModelViewer is the shape to follow, and about half its WPF shell transfers:

• asset browser with type-to-filter over the catalogue
• textured viewport with per-piece visibility toggles
• the four-source animation combo from Browse by monster, offering only that monster's animations #5, plus play / loop / scrub / speed
• export dialog: formats, pieces, animations, scale, output folder
• single self-contained executable, install path auto-detected

Two things this tool has that the D3 one does not

• Piece assembly (SceneAssembler) — the browser should let you tick a head, torso and legs across several files and preview the assembled character, not just one file at a time. This is the feature that prompted the whole part-selection design and it deserves to be first-class in the UI.
• A loose-file source that is not CASC — the open dialog should ask for an extracted folder, and say so clearly, rather than expecting an install path.

Caveat

D3ModelViewer is WPF and Windows-only. Core here is net8.0 and platform-neutral; keep it that way and confine the UI to its own project, so the library stays usable from the CLI on any platform.