Great to hear from you. I can’t believe people complained about the UX, I think it’s perfect for what it does.
1 Like
@mbucchia Sorry to ping you, but I am hoping you can help me out.
I am very upset today 
I have not been on my Sim PC for a few days, so when I booted up today I had the VD update come through. I have literally spent 6 months (no joke) dialling in settings and last time I was on the PC, I finally settled on settings that worked really great everywhere (basically swapped back to DLSS instead of TAA, with CAS scaling, 85% FOV and set 4128x4322 for my Quest 3).
Now, since the update I have this awful phasing of like 10 seconds absolutely fine, then 4 seconds of a double-image redrawing very fast, so it looks out of focus. It comes and goes and I cannot find where or why this has started.
I was using OXRTK but tried without just now and it’s the same (maybe slightly less often) but I have never had it do this before in this way.
Thing is without OXTRK to boost the resolution and reduce the FOV, it looks really low res for me now (using DLSS Quality and Godlike). Unreadable fonts in cockpit etc.
I can turn resolution down or use FSR and put scaling up there, so my GPU is not at 100%, but with my previous settings it seems now the GPU is working more than before in same scenario (where I would have had 85% usage it is now 100%). I can see my target fps (36) is maintained even when this is happening. Even at 60% GPU it happens. It’s something else deeper down making it happen since this update. What can I do?
Is it possible to go BACK to the previous version of VD?
I highly doubt your issue is related to Virtual Desktop. The latest version of Virtual Desktop changed mostly things related to the multimonitor desktop mode and nothing should be affecting the VR experience. There is also nothing that broke OpenXR Toolkit. If you take a look at thia thread, people claim it is Quest Link that broke it.
You can download older builds from GitHub if you want to check: Releases · guygodin/VirtualDesktop · GitHub
But again your issue seems completely different from what is discussed in this thread. As always: step 1) if follow the troubleshooting guide on OpenXR Toolkit website to clear your settings. This fixes most issues.
Thanks for the quick response.
But the update is the only thing that changed on my system since a few days ago when it was running beautifully.
I will try older version. Are those from GitHub compatible with Quest 3? (I bought it from the Meta store).
Will also try reset TK setting. Thanks.
Yes they are the same releases you used before. You can join the Discord to ask support for installing older releases, i normally dont deal with that.
Still, doing a full reset of OpenXR Toolkit is the #1 thing to try
1 Like
Would just like to report that Quest 3 Link (wired) is working fine with OXRTK on my side. Non-test channel.
VRPerfkit may be an option when Oculus v68 arrives 
1 Like
Does it have turbo mode, eye tracking, and post processing?
EDIT: doesn’t look like it =(
Vrperfkit wont work with MSFS since its an OpenVR mod and MSFS is an OpenXR application.
Your only realistic option to keep using the (unsupported) OpenXR Toolkit is likely to use VDXR (and therefore Virtual Desktop), even though my overall recommendation is to not use OpenXR Toolkit at all.
1 Like
But it says Oculus runtime is supported? Or does it mean OpenVR via Oculus somehow?
“Oculus runtime” = Oculus VR (OVR) legacy API, not OpenXR
1 Like
Thanks for linking this, really insightful! Hadn’t seen it before.
FWIW I broke my rule and spent a few minutes looking at this. My findings are here: RIP OpenXR Toolkit : r/oculus (reddit.com)
Bottom-line: 100% a Meta bug, and an absolutely rookie bug.
11 Likes
You have served us so well mbucchia - hopefully they will fix it. I still use OXRTK and would hate to give it up. Thanks as always!!
1 Like
I have v68.0.0.388 on my Quest3 and OXRTK is working OK with MSFS (and DCS) ???
While investigating last night I discovered there are 2 levels of PTC:
-
PTC on the Quest itself (activated via phone app)
-
PTC on the PC side (activated via Beta tab in the Quest PC app)
The latter is what matters here. It will bump your Meta OpenXR runtime from version 1.99 to 1.100 (the bogus one). You can see that version number in the OpenXR Toolkit log file or a tool like OpenXR Explorer.
OK, mbucchia, if I download the PTC PC Oculus app, I see the issue - but just with Airlink/Link. If I use Virtual Desktop, I still can use OXRTK - I guess because it has it’s own runtime.
Yes that’s what i had mentioned a few messages above:
I have to agree. VDXR is the way 
I’ve made the switch from Quest Link to Virtual Desktop / VDXR with all my sims and am pleased with how they all perform (except X-Plane 12 which is a nightmare with both Link and VD).
Hi everyone, long-time reader, first-time poster here.
I’m trying to figure out how to remove the FOV overlay on a Quest3 when using VXDR. I used to achieve this by using Oculus Debug Tool and Oculus Mirror, which has been my go-to streaming setup.
I know OpenXR has a “remove HAM” option, but it doesn’t seem to make any difference. Additionally, I’ve noticed that if the Oculus Mirror app is not the active window, the frame rate drops to below 5fps, which is a significant issue for streaming.
Any suggestions on how I can mirror exactly what I’m seeing on the Quest3 for streaming purposes would be greatly appreciated. I’ve read some articles on using the development app and using ADB to stream… not sure if that’s a possible route.
Thanks in advance!