WebGPU Compute into WebXR on Quest

Seems unlikely that Meta wouldn't update with Chrome flags, especially for the main browser for WebXR? Perhaps you've missed an update?

Definitely up to date on device & browser...and tried other browsers ( old Firefox & Wolvic, to no avail ).

i tried webxr-samples/webgpu above...and they did not work on my MetaQuest 3S...

Is there a forum specifically for webgpu?

Or is Meta discouraging it in favor of dedicated Meta-Store Apps? Like Apple does with AppStore vs WebApps/PWA?

So i'm building a WebGPU offScreen canvas to load into glTexture to present the WebXR camera visuals and have noticed that MetaQuest only offers the DEPTH MAP uint16 as 'gpu-optimized' depthUsage in GL as  texture.

So to use WebGPU COMPUTE on 'depth-image-of-headset' with WebXR, specifically MetaQuest devices, we have to

1) copy the depthBuffer from a GL texture back to CPU
2) then back to GPU
To show visuals, we have to
3) copy WebGPU compute results back to CPU
4) and upload to GL as a texture
5) then render into the WebXR framebuffer

lotta extra steps for 'render' and access to GPU depth...

Meta must have an experimental feature i'm missing if not a regular one?

The "MetaQuest Developer Hub", MQDH, doesn't offer much for WebXR nor does the standalone Win11 emulator.  The Chrome Plugin behaves differently ( doesn't crash on any requestXYZ api calls, unlike the devices, which hang on requestLightProbe, etc. )

i've been experimenting with putting the WebGPU left/right eye texture into a buffer for readback, and with moving the texture into an offscreen canvas but haven't found any 'fast-paths' to make this happen.

The reverse approach, coming from the WebGL texture that holds the MetaQuest 3S Depth Buffer back into WebGPU using 'writeTexture' or 'copyExternalImage' is another pathway in need of a fastpath.

Not sure what Meta's Developer Relations consider a best path??