Board viewer: budget, toggle and preserve the LED spot lights that component GLBs now carry
John Lauer's LED component GLBs (adom/ncd0402g1, adom/ncd0402b1) carry a real KHR_lights_punctual spot light and named switch groups: Adom.LED.State holds the emissive lens skin and the light, Adom.LaserEtch.MPN holds the part number, each with extras.adomRole. He verified them in the Hydrogen WebView2 Babylon 9.5 scene: the light casts onto a matte receiver and goes away when the state group is disabled, and the MPN toggles independently. Details and the follow-up on budgeting are on https://wiki.adom.inc/adom/adom-step2glb/issues/17; the engine/viewer split is written up in https://github.com/adom-inc/service-occt/blob/main/docs/led-spotlights-design.md.
The engine side is done: service-step2glb 1.3.2 and step2glb 0.13.2 preserve the lights and the state groups through the molecule optimize, plain convert, the web LOD and anchor-glb, and refuse a job if a count changes. So the files arriving at the viewer will carry the lights. What is left is the viewer's, and that is this issue:
- Light budget and culling. Babylon materials default to maxSimultaneousLights = 4; a board with forty lit LEDs cannot light every receiver with every LED. Pick the N nearest or brightest active LED lights per frame or per material and let the rest stay emissive-only. Clustered lighting (the ClusteredLightContainer symbol exists in 9.5) is the right long-term tool, but it needs a benchmark before it is promised; the symbol being present is not proof it is active.
- No per-LED shadows by default. One shadow generator per spot light does not scale.
- Visibility toggles by state-root name. Expose the groups the viewer finds by name (Adom.LED.State, Adom.LaserEtch.MPN, and the existing Adom.HeatsinkVias / Adom.SolderBalls / Adom.LaserEtch) as toggles per instance and per role, and persist the chosen state where the viewer persists anything else. setEnabled(false) on the group root is the whole mechanism.
- No rescaling of light range or intensity. glTF light range is metres and intensity candela; they do not follow a node matrix. A viewer that rescales a model to fit the screen must leave the lights alone or divide the scale back out, or a 15 mm range becomes 15 m.
- Per-placement light instances. A board that references one LED GLB many times must instance the light per placement, or every LED switches together.
Nothing here asks for the viewer to create lights of its own; the reference files carry them. The datasheet-angle cone, the display gain and the units are all in the file's extras and in the convention document under review on the same #17 thread.