THREE.JS / FOUNDATIONS 312
Pin the world.
A hit pose becomes an anchor, the anchor owns a tracked pose, and the scene survives drift, tracking loss, deletion, and synthetic persistence.
Desktop simulation is explicit; native AR is exposed only through the guarded button.
anchor lifecycle
A synthetic persistent handle is application-level evidence, not device persistence. Native button clicks are intentionally excluded from QA.
synthetic world
Hit source: floor · revision 0. Create a hit anchor, then move the source to see attached pose updates.
- mode
- desktop
- feature plan
- progressive
- tracked anchors
- 0
- visible anchors
- 0
- pose revisions
- 0
- persistent handles
- 0
- selected
- —
- anchor space
- none
- hit result
- none
- native support
- probing
- draw calls
- 0
- frame samples
- 0
A native XRAnchor exposes an XRSpace; the desktop record labels its simulated equivalent.
Loss hides locatable content without silently deleting the application record.
Persistent handles are synthetic until a real XR session proves requestPersistentHandle/restorePersistentAnchor.
No anchor events yet.
Desktop simulation is deterministic · real AR requires a compatible device · no native session is inferred from the simulation
Inspect session feature negotiation →LAB 312 / XR ANCHOR OWNERSHIP