Development linked-board import needs primitive budgets, streaming LOD and idle render control
Environment at incident: adom-2dboard 0.5.0 development candidate, branch feature/depth-lab-placement; Adom Babylon 9 viewer package 0.2.0; Hydrogen 1.0.316 (development build 9ddcc472ed3ade811ae52126edd4e1fe60da871a-dirty); Adom Bridge 2.1.95; adom-cli 0.5.16; Windows host with WSL2 workspace. Bridge is now 2.1.96 after the restart; this is not the incident version.
The linked 2D/3D board development candidate imported a native KiCad GLB without a primitive/resource preflight. That file contains 79 mesh definitions but 11,943 primitives. The live Babylon scene reported 11,953 meshes and approximately 10.93 fps. The recorder was confirmed off. The user reported a frozen Hydrogen and had to restart it. The large static primitive count is evidence of excessive rendering work; it is not proof of a memory leak or a complete root-cause diagnosis.
I introduced this unbounded import in the development integration. It must not be presented as a regression in the released 2D-only app. The attached source checkpoint screenshot is from before remediation; do not reopen the original scene to reproduce on a user's shared desktop.
Required app behavior:
- Inspect actual primitive instances and decoded buffers before opening large native exports; return actionable AI hints and refuse loads beyond explicit budgets.
- Batch compatible static board/copper geometry without changing native manufacturing files or reference identity.
- Consume hash-pinned, reviewed wiki component GLBs so approved MPN artwork carries through to the board.
- Load super-low components first, fetch higher detail by projected size, share repeated geometry, use hysteresis and bounded concurrency, and dispose inactive detail. Hiding meshes alone does not release them.
- Stop idle and hidden render loops. Expose resource counters and distinguish estimates from measured GPU allocation.
- Validate repeated zoom and unload/reload cycles in an isolated renderer before showing the repaired candidate on the shared desktop.
Current local remediation: old 11,943-primitive file is refused at startup with scene_budget_exceeded; exact native-board batching produces a 20-primitive base; four LOD candidates exist for 13 component types. A streaming static-component implementation is under isolated browser tests. Full visual/native seating, hardware GPU memory and motion/LED state qualification remain pending. Shared guidance is published in adom/adom-wiki-skillpack 0.8.7, skill wiki-component-lod.

0 Replies
Log in to reply.