Reporting for loader failures — the aggregate view, as distinct from the
per-node logging in nodes/load-leaf-error-dispatch.ts.
Exists because loadScene structurally cannot throw on ordinary leaf-local
failures: loadLeafNode catches their LoaderErrors and returns null so the
rest of the scene still builds. That is the right behavior, but it meant a
scene whose every node failed resolved normally and logged an unconditional
"Scene loaded successfully" — a green log over an empty viewport, which is
what made a real data bug (a WASM trap in the gsplat projection kernel) look
like a mystery. Container-wide archive faults remain fatal and bypass this
aggregate.
Reporting for loader failures — the aggregate view, as distinct from the per-node logging in
nodes/load-leaf-error-dispatch.ts.Exists because
loadScenestructurally cannot throw on ordinary leaf-local failures:loadLeafNodecatches theirLoaderErrors and returns null so the rest of the scene still builds. That is the right behavior, but it meant a scene whose every node failed resolved normally and logged an unconditional "Scene loaded successfully" — a green log over an empty viewport, which is what made a real data bug (a WASM trap in the gsplat projection kernel) look like a mystery. Container-wide archive faults remain fatal and bypass this aggregate.