THREE.JS / SOURCE PROMOTION

AR hit test

Source-shaped study of the pinned webxr_ar_hittest example: ARButton, the required hit-test feature, two select controllers, a matrix-driven ring reticle, and cylinder placement from the first hit result.

InitializingPreparing renderer

Preparing the transparent WebGL2 AR scene and hit-test lifecycle...

backend
-
controllers
-
reticle
-
placements
-
feature
-
source
-
frames
-
sample
-
AR entry pointhit-test
AR capability-

The AR button requests the exact required hit-test feature. Desktop QA uses a synthetic reticle adapter; native viewer-space hit sources and real-world poses require an AR-capable device.

Synthetic hit-test adapterdesktop fallback

Synthetic select mirrors the official reticle.matrix.decompose path. It is not evidence of native camera passthrough, viewer-space hit-test negotiation, or whole-example fidelity.

Runtime stateRUNNING

The source requests a viewer reference space, stores one hit-test source, reads the first result each frame, and clears it on session end.