Interface: WebXRRuntimeAdapterOptions
Defined in: service-framework-three/src/webxr-runtime-adapter.ts:80
Properties
| Property | Modifier | Type | Description | Defined in |
|---|---|---|---|---|
host? | readonly | AnimationLoopHostLike | The renderer, or anything else with setAnimationLoop. Given one, the adapter owns the loop: WebXRRuntimeAdapter.start binds it and each callback becomes a frame. Omit it to drive frames yourself with WebXRRuntimeAdapter.emitFrame. | service-framework-three/src/webxr-runtime-adapter.ts:95 |
scheduler? | readonly | IScheduler | Given a scheduler, each owned frame also emits the renderTick channel with source: "three", exactly as ThreeRenderLoopBridge does, so an app needs one loop owner rather than two. | service-framework-three/src/webxr-runtime-adapter.ts:101 |
sessionInit? | readonly | (mode: SessionMode) => unknown | Supplies the XRSessionInit for a mode - required and optional features. Called once per request; the default sends no init at all. | service-framework-three/src/webxr-runtime-adapter.ts:106 |
xr | readonly | WebXRManagerLike | renderer.xr - the renderer's WebXR manager. | service-framework-three/src/webxr-runtime-adapter.ts:82 |
xrSystem? | readonly | WebXRSystemLike | null | navigator.xr. Defaults to the global when omitted, and to null where there is no global, which is what a Node test sees. A null system reports every session request as "unsupported". | service-framework-three/src/webxr-runtime-adapter.ts:88 |