Depth Sensing broken?

[FrostKiwi]

I observe neither being able to run https://github.com/pmndrs/xr/tree/main/examples/stage nor even a basic test scene with depthSensing: true. Launching that scene in AR on a Quest 3 v81.1034 leaves the scene fully empty, nothing initializing. No errors, no hands, no 3D models, just nothing.

Here comes the interesting part, the already built online demo, there it's fine: https://pmndrs.github.io/xr/examples/stage/

So I would assume, that this is an HTTPS not trusted thing. But I doubled checked that.

• On localhost
• with ADB reverse
• deployed on a real domain with a real valid Certificate and no certificate trust issues

If I build https://github.com/pmndrs/xr/tree/main/examples/stage and run it locally or deploy it: truning depth-sensing true, breaks the WebXR scene completely once entering immersive-ar. I'm at a loss as to what is going on.

Here I deployed the same https://github.com/pmndrs/xr/tree/main/examples/stage demo myself: https://demo.frost.kiwi <-- this doesn't work, even though no errors are thrown.

Can someone else reproduce this? Build the stage example in this repo with latest versions of everything, launch npx vite and confirm it not working a Quest 3 v81.1034?

[FrostKiwi]

Figured out that specifically ThreeJS v0.179.0 is at fault and reported it in mrdoob/three.js#32155

I checked the version of the online demos: https://pmndrs.github.io/xr/examples/stage/ was built with ThreeJS r173 and I built https://demo.frost.kiwi/ with ThreeJS r180.

Looking at release notes, I suspect

• WebGLRenderer
  • Improve reversed depth buffer support

or

• WebXRManager
  • Set glBinding separately from layer creation.
  • Disable left eye layer for right eye camera and vice versa.