Camera.state ​

Contract 2.0.0 · package sha256 a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e · generated from configurator-runtime.d.ts by services/onsite-scripter/scripts/build-contract-docs.mjs; edit the source, not this file.

Property of Camera · stable · since 2.0.0 · called as session.camera.state

readonly state: CameraState;

Observed: the camera as of the last drawn frame (this frame's in a 'late' hook), Frame.camera views included. Hooks read it too: in an 'update' hook and in a drag's constrain it is the last drawn frame's, since the camera has not moved yet, so a write that depends on the camera runs 'late' (Frame has no camera read). A durationMs: 0 write's value reads from when the write starts (autocommit: at the call, unless it queues behind an open transaction), frame still the last drawn one, so a read after its await is the landed view or lens; never a view write's while a Frame.camera view is held, nor a lens write's while that view carries fovDeg, since every frame then draws the hook's. Before any view write it reads the start view, { target: { x: 0, y: 0, z: 0 }, azimuthDeg: 0, polarDeg: 60, distance: 5 }, with the default lens, the runtime's and the fake's alike; no scene write moves it, so an app frames with its own view write, which the zoom limits fitted to the product then clamp.

Generic-API test (spec 3.1) ​