CameraLimits.minAzimuthDeg ​

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 CameraLimits · stable · since 2.0.0

ts
minAzimuthDeg?: number | null;

Degrees. The azimuth limits are the arc from minAzimuthDeg counter-clockwise to maxAzimuthDeg; an unset end is −180 (min) or 180 (max). The merged ends must satisfy 0 ≤ max − min ≤ 360, else the call rejects HoloInputError('invalid-input'): 150 to 210 lies behind the product, equal ends lock the azimuth, 360 apart frees it. A view outside the arc lands at its nearer end round the circle, and a move inside a narrower arc turns the way that stays inside it, more than half a turn if it must.

Default: unchanged

Generic-API test (spec 3.1) ​

Rule Result
1. Neutral name pass: minAzimuthDeg names no product
2. A precedent pass: Babylon.js ArcRotateCamera lowerAlphaLimit, upperAlphaLimit, panning (row G7)
3. Two apps, or labs pass: 26 apps (ledger: app-4f16d2f6da, app-b362a81c85, app-f9a32142f1, app-fc07850558, app-fc306ec3dc, app-fd09090420; fleet cross-check: app-04c2774145, app-37356bf09f, app-378d190f1b, app-4762caacdc, app-4f16d2f6da, app-4fd23bc869, app-510d750508, app-59c5b5751e and 18 more)
4. The cheaper fix first decided per need in Appendix B: rows G7 at tier stable (a member only where no rule, data, asset or app code serves the need)