feat(render): the Cesium renderer can run an application's camera controller

createCesiumRendererPlugin({cameraController}) (render/cesium/plugin) puts
the camera port on the shared camera controller over a native camera on
Cesium's (controlledCamera.js): poses written exactly, out of any lookAt
transform, the vertical field of view as Cesium's wide-side fov and kept
on a resize. Cesium's own controls hold their input off and their
collision off while it drives; the controller runs before and after the
preUpdate listeners, and what it throws is reported. A followed item's
position is where its GPU icon set draws it (drawnPosition), and the
input port's camera holds are the controller's.

The conformance harness, given a controller, steps a virtual clock 1/60 s
a frame for ticks and pointer events, so flights and pointer scripts are
compared frame by frame.
This commit is contained in:
Sameh Khamis committed 2026-11-12 11:41:54 -08:00
1 parent 1a7ef7fc7a
commit aa58886e40
11 files changed
+826 -36

No files matched your search

+10
View File
@@ -0,0 +1,10 @@
/**
* @module render/cesium/plugin
* @description The Cesium renderer plugin made with options, for an
* application that hands it something of its own: `cameraController`, the
* shared camera controller's factory, which then drives Cesium's camera
* and takes the user's input in place of Cesium's own controls
* (`controlledCamera.js`). Without options it is the default plugin the
* application scene loads (`application.js`).
*/
export { createCesiumRendererPlugin } from './appRenderer.js';