fix(blender-camera): accept southern origins and bound the scene read

- Join a space-separated negative latitude to --origin before parseArgs,
  so `--origin -33.86,151.21,0` works as the usage and docs show.
- Read the input through one descriptor, regular files only, at most one
  byte past the 5 MiB scene limit.
- Use geodetic ENU axes at the origin (ellipsoid normal at its lat/lon,
  raised to its height) instead of Cesium's frame at the raised point.
- Reuse the shots already resolved, serialize the sampled shot table
  directly, and drop the typeof-only export test.
- Docs: timing matches Director seeking, with the playback differences;
  add a manual OpenUSD/Blender check; shorten the overview and test list.
This commit is contained in:
German Khokhlov committed 2026-11-19 18:24:55 +04:00
1 parent 4668f26e0e
commit 235938e19b
6 files changed
+116 -66

No files matched your search

+2 -8
View File
@@ -689,14 +689,8 @@ untouched, and the shot is not rebuilt.
See [camera directions](DIRECTOR-CAMERA.md).
An opt-in offline [Blender camera bridge](BLENDER-CAMERAS.md) exports a saved
Director scene as a camera-only USD stage (`.usda`) that Blender imports
natively: Z-up meters in a local ENU frame around an explicit WGS84 ellipsoid
origin, one camera per shot with per-frame transforms, lens values in USD's
tenths of a scene unit and rational fps recorded alongside frame-number time
codes. It uses Director seek interpolation and the runtime shot timing from
`shotPresentation.js`, so registered pack holds, minimum holds and
evidence-sequence durations match playback. Implicit live flyTo paths, imagery
and geometry are outside this camera-only format.
Director scene as a camera-only USD stage (`.usda`) with Director seek
interpolation and runtime shot timing; format, units and limits are in that guide.
Realtime voice composes separate connection, response/tool, Radio handoff, input
and audio-meter, cost, viewport-context and diagnostic owners. The existing