Open bug report

Linked-view candidate hardcodes sensor.glb instead of the scene manifest filename

John Lauer ·

Adom 2D Board development candidate 0.5.0, feature/depth-lab-placement; native KiCad 10.0.6; Linux/WSL2. This affects the local linked-view candidate, not the released 2D-only workflow.

Loading a second board with scene.json declaring file: carrier.glb fails with ERROR: No such file or directory (os error 2). Both configure_scene and the browser importer hardcoded sensor.glb despite the manifest file field.

Expected: use the validated manifest filename for the board asset, while restricting served files to that board and explicitly declared LOD assets. Preserve compatibility for old manifests without a file field.

Attached is the local correction: use the declared GLB filename (legacy fallback sensor.glb), reject path traversal/separators/non-GLB names, hash the selected file, and have the browser import it. Native layer and PCB hashes remain mandatory. This is source work, not an installable release claim.

Validation: the new carrier loads from carrier.glb; the isolated browser reports 20/20 bodies, 41 scene meshes, no browser exceptions, matching source hashes and a paused idle renderer. Existing single-board resource guards remain. The screenshot shows the actual native linked view. Native underside silk contrast is a separate open rendering concern; do not claim this filename fix addresses it.

carrier-linked

carrier-scene-filename.patch

0 Replies

Log in to reply.