Hint for VR in AR WebXR sessions.

[AdaRoseCannon]

/facetoface This came up in today's call (4/3/25). There have been experiences in the wild want to run almost entirely in VR then occasionally use the AR pass through features. Currently this results in large power and performance requirements as the AR systems are active but not being utilised. Should we have a new session type or an API to quickly allow switching between AR and VR?

[cabanier]

The proposal is to have a switch to disable calculation of the AR passthrough so sessions can seamlessly switch between VR and AR.

[m-blix]

What would this look like in code, Something like the below? I would think we would want a promise as operation to enable/disable could take a while.

session.toggleAR().then((enabled) => {
  console.log('enabled?', enabled)
})

[cabanier]

What would this look like in code, Something like the below? I would think we would want a promise as operation to enable/disable could take a while.

session.toggleAR().then((enabled) => {
console.log('enabled?', enabled)
})

It could be something in the renderstate. That way it's easy to read and write and it's well defined when it's applied.