diamond26

@Steel JawWhat do you mean OTT doesn’t see MT? Those two are not related. OTT works as before when Link or Airlink is used. OTT is not relevant only when Virtual Desktop is used.

Quest2 is using a proximity sensor to wake up the headset when you put it on your head. DCS with MT crashes every time I put the headset down. Disabling the proximity sensor (using Meta Quest Developer Hub) eliminates the problem. The proximity sensor was never an issue with previous versions

I can confirm I had the same issue with Quest2 and motion blur on in MT

Based on a very helpful response from Special K in ED's Disocrd I found out that there is a "Hide control stick" option in Game options which was enabled by default. Unticking this brought back the stick in both F-18 and F-86

Since the introduction of the 2.8.2.35759 I noticed a very strange behavior when I use OpenXR (in both 2D or VR). The flight stick in F-86 and F-18 is not visible. And for F-18 there is a binding to bring it back, but for F-86 there is none. This behavior appears only with OpenXR. I have tried it on 2 different computers, same result. When I use Opencomposite OpenXR or normal OpenVR runtime everything work as expected. Any ideas or at least a key binding to make stick visible in F-86? PS. I have tried full repair, no mods to no avail.

I have noticed that for Quest2, Turbo ON works with all ASW different settings. I have no impact on CPU temperatures because of rebar

Just a note on the use of ASW in Q2. The GPU usage is lower whenever I use 45 forced or locked compared to ASW disabled. (rebar is enabled)

One more thing to try is to reduce the FOV in OTT (or ODT) to a value below 1, like 0.8 or 0.9 and see how much you gain. In my case up to 0.75 is not so visible in the headset but has a great impact in FPS

Oculus has to be set as active OpenXR runtime in oculus app to work properly with native OpenXR DCS. The switch I mentioned is this "C:\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR. Note the space after .exe"

Quest2 can run both OpenVR and OpenXR without additional SW. With the latest patch if you do not add any switches to DCS.exe then it will run OpenVR (like it was all the time before 2.8.2). If you use the switch for OpenXR then it will run DCS OpenXR. With the latter you will have the option to use OpenXR toolkit to enable additional functions like upscaling or sharpening, color saturation etc. Hope that helps

these are my results on three different options (DCS OpenXR, Opencomposite OpenXR, Vrperfkit). No Upscaling, Turbo mode on in OXRTK. Test with F18 low level free flight over Persian Gulf. i7 12700K/ 3080 12Gb/32gb RAM 3600 End result: DCS OpenXR works better PS. Now I wish Skatezilla's App was able to launch directly the DCS OpenXR option so I can use different settings for different use cases.

@SkateZillaGood question. Any suggestion?

As long as you choose to use Oculus as OpenXR runtime in the oculus app, everything else stays as before. https://forum.dcs.world/topic/318004-dcs-now-supports-openxr-natively/?do=findComment&comment=5138982

Quest2 works just fine (OpenXR is enabled as default runtime in Oculus app).

Quest2 works in my case, but I had OpenXRtookit installed and used previously with Opencomposite. Now I have two options in OpenXR toolkit for DCS

You are welcome. The whole idea for steamVR API use is to trick the system that SteamVR is used so Opencomposite can take over and use their own dll. So in reality no SteamVR is used.

are you following the steps shown in the attached image there is no need for that if you follow the system-wide installation of the Opencomposite. This is only needed if you do a per-game installation

The trick is to launch the game using right click on VD streamer icon and launch game option. Then you use the shortcut MoleUK mentions in his first post

It's an interesting case this one. I've only tested VD with my gaming Laptop (i79750, RTX 2060) due to connectivity issues with PC. In my case the picture clarity in VD was lacking compared to both Link and Airlink despite trrying the highest resolution possible. It had a blurry filter. FPS wasn't better when used the Ultra resoloution which is close to full resolution I use in Oculus for Link and Airlink

For what is worth I have similar experience with Quest2 using OpenXR toolkit in the sense that override option behaves better than scaling for the exact same resolutions.

Thank you @AlaskanGrizzly for the update. Works perfectly with F1 now!

There is a caveat in the details of turbo mode from mbucchia page which may explain what you see and feel: Any statistics or performance measuring tool might now present incorrect data

As @5ephir0thsaid. The only comparison maybe between OpenXR (especially because of OpenXR toolkit options) and VRPerfkit

I run a session with my gaming laptop with ASW lock on 30 (@72hz this is 24FPS locked) and while the flight was smoother than ASW OFF or ON, the artifacts in HMD and very close objects were annoying.

In my case that is only visible if the FPS is lower than the 50%. I can see that with my gaming laptop (RTX 2060, image below). In my PC rig where I'm always above 50% of the designated hz setting I don't see ghosting on anything on HMD (like numbers not being clear for example) null