- Cesium's own tweens (its flights) step on the renderer's clock, so the
flight traces compare frame by frame; dispose gives the scene its own
clock back.
- moveStart and moveEnd are measured each tick on that clock, by the
shared move detection, a change of the field of view or aspect
included; Cesium's own events timed them by the system clock.
- A follow of a drawn item tracks where the draw port draws it.
- Pick rays are summed from the eye's axes: Cesium's lose about 1e-9 of
direction at a near plane of 0.1 m. Ellipsoid picks and the view
rectangle use them; a canvas with no size has none, as in Cesium.
- The harness always runs the virtual clock and claims 120 checks: 119
pass on the page and query.heights skips. The five pointer traces
need a camera controller there, and are recorded from Cesium's own
controller in Node.
- The package boundaries list the cesium plugin export and the modules
its groups now import.
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.