A first bonfire from one image
Can a reference image become a useful village prop? A local TripoSR test produced a bonfire draft with a stone ring and logs, ready for a separate cleanup review.
Full entry & measurements
TripoSR is installed in an isolated local Python 3.11 environment. The official source at 107cefdc244c39106fa830359024f6a2f1c78871 and cached official weights generated and reloaded two real 64-grid CPU GLBs on Apple M1 / 16 GB: an official sample and the first Habitat bonfire. The bonfire was measured on 15 October 2026 at 25.156 seconds including warm imports/preprocessing/export, excluding setup/downloads; its upstream inference stage took 10.554 seconds. Its independently reloaded mesh has 2,591 vertices and 5,140 triangles, finite vertices and valid indices, but is not watertight. These are one-run draft measurements, not an ETA or game-ready acceptance. The generated input concept and actual raw-mesh CPU preview preserve separate provenance and individual privacy reviews. Visual inspection shows a recognizable ring and logs with softened details; Blender cleanup and unseen-surface checks remain pending. The native build used an already installed SDK process-locally after the default SDK linker failed; an initial sandbox run failed on OpenMP shared memory, then an approved local run succeeded. No MPS acceleration, texture bake, higher grid, OBJ, Blender cleanup or Unity import is claimed. A reusable habitat-triposr-assets skill was created only after successful generation, installed in personal skills, and passed the skill validator. docs/triposr.md preserves repeatable invocation, exact source/model revisions, input prompt and limits. Next: review the raw prop in a separate Blender file and decide cleanup; animated flames remain a separate effect and Unity replacement requires its own authorization. No Unity/Blender/site layout or resident behavior was changed.