Gaussian XR rendering glitches with Meta Quest Link caused by Asynchronous Spacewarp (ASW) — solution included

[tiem2scam-cmd]

Running on Meta Quest 3 or Pro results in this glitching regardless of settings, both on BiRP and URP (D3D12 Multi-pass). This is using Meta Quest Link, that is, the hardware being used to render is the computer's, not the headset, so I'm effectively using the headset as a display.
Non XR rendering works completely fine, including the Unity editor view when using the headset (the mirroring pass).
Only happens when the gaussians are visible from the camera view, regular meshes work fine.

I've tried multiple fixes to no avail. Any idea why this happens?
Thanks in advance!

[tiem2scam-cmd]

Solved! Posting the solution here in case anyone has the same issue:

It's a frame synthesis feature causing this problem on Oculus/Meta devices: Asynchronous Spacewarp. Whenever the app can't sustain the headset's target framerate, it triggers and creates glitched "in between" frames, because I guess the Gaussian rendering doesn't provide enough info (probably depth) for ASW to create proper frames.

Someone can correct me if I'm wrong, but there seems to be no way of turning this off in the new Meta apps, so you have to boot up the legacy Oculus Debug Tool exe from the folder Meta Horizon\Support\oculus-diagnostics or use the shortcut ctrl+numpad1.

[wuyize25]

Thanks a lot for sharing the solution and the detailed steps!

[nhghieu22-pixel]

Have you ever tried to export your app to run directly on Meta Quest 3 @tiem2scam-cmd ?
I tried and nothing appear on my headset ! I am trying to fix this, but has no idea.