jurinko

If you use openxr toolkit, switch off turbo mode.

You need so start dcs from desktop icon, then using steamvr works.

I have excellent experience with the latest driver from Match 19. Rtx 4080.

Never assume malice if incompetence is the clue. or Never assume software failure if forgotten cable got into fan blades happened to me as well.

I had g2 and now q3, so I know what 90hz looks like and I could not stand 60hz for a second. 72hz is so much better than 60hz that I do not recognize it at all. In the link menu, if I concentrate on it, yes there is distant shimmer and 90hz is solid, but ingame i do not feel it.

You csn set steamvr as your openxr runtime and start dcs from desktop icon. For me, steamvr runs even better than with oculus/openxr.

Install the Skatezillas DCS updater and run it in VR OFF mode.

With virtual desktop running you see your desktop like in a cinema and by single click you get into VD settings, or start/switch off SteamVR, or switch between desktop and VR. DCS is started by clicking the desktop icon with the tracking tool. With Oculus link, i can use tracker or fingers first, but then I can use only mouse (after the quest link starts). With v63 bs I cannot start DCS by the VR icon, but have to peer outside headset and start it from the normal desktop or from Steam.

To be absolutely honest, i just wanted to mess with it to try something else, after getting excellent results with cable link. And kids complained wifi in their room is poor, so now they have dedicated 2.4G channel and I have 5G. VD is also a backup for situations like it is now.

I got Q3/4080 working in Virtual desktop (with 40euro wifi router). I wanted to get rid of the V62/63 drama and run DCS in OpenXR, but alas, it still runs better with SteamVR, Turbo on, HEVC-10bit or AV1 codec. It runs slightly worse with HEVC-10bit, Turbo OFF, VRDX runtime - here and there slight soft stutter. I am definitely spoiled. Simplicity of life with VD is nice, everyhing is made with Q3 on and the tracker/fingers, no swearing and peering through the slot around my nose at the keyboard. Q3 is, after much fiddling after G2, a great upgrade.

There is a procedure how to do it in Bignewy's thread about using oculus runtime. You uninstall oculus software, reinstall, snooze update, click off auto update, make a copy of the folder, delete some folders, get it updated, replace the oculus folder with the old one, run installer for repair and you have v62 not updating itself. It worked for me but the performance is better with v63 using steamvr as openxr runtime so i reverted everything back and at 3am i went to bed satisfied i have the best option on.

Now I can run DCS with v63/Quest 3, starting it from the desktop icon or from Steam shortcut. I set SteamVR as OpenXR runtime and in game OpenXR toolkit still works. Strange is, now Turbo mode causes terrible stutter and DCS runs smoothly without it, before Turbo mode smoothed things out.

The force_oculus_VR trick does not work for me either (Quest 3). I can run DCS using SteamVR as OpenXR runtime and start it manually from Steam as non-Steam game. Since the OXR toolkit does not work now, I had to change the resolution in the headset settings (changing the PD in game or resolution in SteamVR settings does not work). No turbo mode, but it looks it does not need one (runs smoothly). Probably Turbo fixes some OpenXR deficiency. When first computers appeared, it seemed to me a magic I never could understand. And so here we are

If I force oculus and still can open the openxr toolkit menu in game, am I running in openxr or in native oculus api?

We can always get hotfix if v63 goes stable. That --force oculus vr thing does not work though.