DCS now supports OpenXR natively

[Zebra1-1]

On 1/15/2024 at 12:55 AM, Aussie Pilot said:

Do we still need to force enable openXR in DCS now since 2.9 with an edited exe?

This thread is a year old now and with 31 pages I don't have the time to wade through them all. I have a quest 2 VR headset.

I'm kind of under the impression that DCS is running openXR all the time now and doesn't need enabling, but being new to all this, it gets a bit confusing.

Cheers, A.P.

You do not if you are using MT.

ST, yes. 

[jungleboy123]

sorry, stupid question. I have Pico 4 and Quest 3. In Pico 4 OpenXR just works straight from launching in Virtual Desktop. In Quest 3 i have no idea. How can i know if OpenXR is working?

[Qcumber]

6 hours ago, jungleboy123 said:

sorry, stupid question. I have Pico 4 and Quest 3. In Pico 4 OpenXR just works straight from launching in Virtual Desktop. In Quest 3 i have no idea. How can i know if OpenXR is working?

In the oculus app settings there is an option to make oculus the default for open xr. Oculus should then run open xr if you start DCS from the MT folder without any force settings (which you might have read about in older threads). 

[jungleboy123]

6 hours ago, Qcumber said:

In the oculus app settings there is an option to make oculus the default for open xr. Oculus should then run open xr if you start DCS from the MT folder without any force settings (which you might have read about in older threads). 

Thank you. It looks like VD was set as the current runtime and i was running Quest 3 in DCS all this time probably in some other mode unless it used oculus OpenXR.

Sorry, you might be able to help with these questions too. Will try to explain:

1. How can i switch between the OpenXR profiles. Some days i use Quest 3, sometimes Pico 4 via VD. I want it to point to the correct launch.
2. Pico 4 i am now trying the new Pico Connect beta. I have applied the additional hack to give godlike resolution. When i launch in SteamVR via MT, the game only displays in 2D TV screen mode.

Thanks.

Edited April 4, 2024 by jungleboy123

[Phantom711]

@jungleboy123

1. As you might have noticed, only one program at a time (i.e. VD, Oculus, SteamVR) can be the OpenXR runtime. So you have to go into the settings of the respective program and select it as the active OpenXR runtime.

To save you from the hassle there are tools like XR-picker, which let you select that from outside the respective software.

https://github.com/rpavlik/xr-picker/releases
 

2. As mentioned…did you have SteamVR selected as your OpenXR runtime?

[jungleboy123]

12 minutes ago, Phantom711 said:

@jungleboy123

1. As you might have noticed, only one program at a time (i.e. VD, Oculus, SteamVR) can be the OpenXR runtime. So you have to go into the settings of the respective program and select it as the active OpenXR runtime.

To save you from the hassle there are tools like XR-picker, which let you select that from outside the respective software.

https://github.com/rpavlik/xr-picker/releases
 

2. As mentioned…did you have SteamVR selected as your OpenXR runtime?

Thanks.

For 2. I think @Qcumber and your answer to 1 just made me realised the default runtime was set to VD. I need to try to set it to steamVR then relaunch the game. Will report back after that's done.

 

[Qcumber]

3 hours ago, jungleboy123 said:

Thank you. It looks like VD was set as the current runtime and i was running Quest 3 in DCS all this time probably in some other mode unless it used oculus OpenXR.

Sorry, you might be able to help with these questions too. Will try to explain:

1. How can i switch between the OpenXR profiles. Some days i use Quest 3, sometimes Pico 4 via VD. I want it to point to the correct launch.
2. Pico 4 i am now trying the new Pico Connect beta. I have applied the additional hack to give godlike resolution. When i launch in SteamVR via MT, the game only displays in 2D TV screen mode.

Thanks.

 

In VD it should select VDXR automatically. To change back to oculus runtime you need to click the "default XR" box in settings. I switch between Pico 4 and quest pro so am used to doing it. 

[jungleboy123]

5 hours ago, Qcumber said:

In VD it should select VDXR automatically. To change back to oculus runtime you need to click the "default XR" box in settings. I switch between Pico 4 and quest pro so am used to doing it. 

Thanks, working now!

[koen330]

OpenXR 1.1 is out.

Is this something we can update ourself, or has this to be implemented by DCS or VR headset manufacturers?

[mbucchia]

2 hours ago, koen330 said:

OpenXR 1.1 is out.

Is this something we can update ourself, or has this to be implemented by DCS or VR headset manufacturers?

The news you've seen is about the OpenXR _standard_ being updated to 1.1.

This is similar to something like "a new version of DirectX was released" - with either new or more integrated capabilities.

Vendors will start rolling out new OpenXR runtimes - integrated to their platform - similar to how drivers would be updated for new DirectX version.

Application developers (such as ED) have the opportunity to start using these new capabilities by writing new code. It's not likely to start happening before the roll-out phase above is in motion (which it isn't really today).

End-to-end, a majority of the things announced for 1.1 were already possible in 1.0, such as the quad views foveated rendering that DCS already implements today. They are now more standard and slightly easier to use, but they still require efforts both on the platform vendors to implement (eg: Meta, the most important vendor, does not support quad views foveated rendering in 1.0 and there is no evidence yet that they will in 1.1) and the app developers to utilize (and thankfully ED does support quad views foveated rendering, if the platform supports it).

[Dodge]

Khronos Releases OpenXR 1.1 to Further Streamline Cross-Platform XR Development

https://www.khronos.org/openxr/
Press Release  (15 APR 2024)
Presentation Slides (PDF)

[Aapje]

The most relevant change is that they put Quad View Foveated Rendering in the standard. This can encourage games that use OpenXR to support dynamic foveated rendering (MSFS!).

[Kenan]

I'm running DCS in Multithreading Mode (using Oculus Rift S) yet, OpenXR doesn't seem to work in DCS i.e. I can't see my virtual hands?

In the VR tab I only have two options "Disable" and "Controllers", there is no "Trackers" option. This option does appear if I try to run OpenXR via Steam but even then, when selecting it, I do not see virtual hands inside the cockpit?

Are there any additional steps I should follow to have the virtual hands enabled?

Edited June 15, 2024 by Kenan

[Blinde]

I'm using Quest 3 and I'm a bit lost with these Openxr settings. What should I use with my Rtx 4070, CAS, NIS or FSR?

[speed-of-heat]

10 minutes ago, Blinde said:

I'm using Quest 3 and I'm a bit lost with these Openxr settings. What should I use with my Rtx 4070, CAS, NIS or FSR?

ultimately it's a matter of personal preference ... on a 4070 you might want to leave those settings alone for a bit and try DLSS... but try one thing at a time for a bit and see what works best for you ... 

[Blinde]

4 minutes ago, speed-of-heat said:

ultimately it's a matter of personal preference ... on a 4070 you might want to leave those settings alone for a bit and try DLSS... but try one thing at a time for a bit and see what works best for you ... 

DLSS is too blurry, even with max sharpening set in dcs settings. DLAA is better but then again it doesn't give so good fps.

[speed-of-heat]

generally people seem to think that FSR is the best of the alternatives, combined with MSAA in game I would suggest x2  and see... YMMWV

[Silver_]

DLSS gives better performance because in the end it is at the cost of losing definition and everything is blurry (small letters or distant or somewhat camouflaged planes are difficult to see).  There is a technique that consists of increasing the pixel density in DCS and using DLSS, in the end you can see better but at the cost of performance, which results in a performance similar to or less than MSAA x2 as @speed-of-heat suggested.  In the end I prefer to stay with MSAA and not waste any more time, everything looks clear and how I like it, and the performance is not that bad either.

Edited June 28, 2024 by Silver_

[WipeUout]

I avoid using DCS pixel density as the whole image gets supersampled and is a big hit on performance.

To improve clarity you may try using Quadviews to supersample the focus area and OXRTK CAS at 100% for sharpening.  Do not use DLSS performance as it will blur too much, use balance or quality.  Your gain will be reduced but with a small gain nevertheless along much better sharpness.  You can also use CAS from Quadviews but I find CAS in OXRTK to be more efficient and leave sharpening in DCS and Quadviews at 0. 

[Qcumber]

On 6/28/2024 at 8:23 AM, Blinde said:

I'm using Quest 3 and I'm a bit lost with these Openxr settings. What should I use with my Rtx 4070, CAS, NIS or FSR?

I would not bother using OXRTK. I only really use it now to adjust contrast. DLSS native version on DCS is not the most recent. You can manually install the latest DLSS version be simply replacing it in your DCS bin folder. Also try using DLSSTweaks to change the preset (F is best for me) and the multiplier. About 0.8 gives pretty good results. Much less movement blurring and sharp cockpit. Not as sharp as without DLSS but much better anti-aliasing than MSAA. 

https://www.techpowerup.com/download/nvidia-dlss-dll/

https://github.com/emoose/DLSSTweaks

 

[Blinde]

5 hours ago, Qcumber said:

I would not bother using OXRTK. I only really use it now to adjust contrast. DLSS native version on DCS is not the most recent. You can manually install the latest DLSS version be simply replacing it in your DCS bin folder. Also try using DLSSTweaks to change the preset (F is best for me) and the multiplier. About 0.8 gives pretty good results. Much less movement blurring and sharp cockpit. Not as sharp as without DLSS but much better anti-aliasing than MSAA. 

https://www.techpowerup.com/download/nvidia-dlss-dll/

https://github.com/emoose/DLSSTweaks

 

I thought dlsstweaks was broken with the latest update.

I'm using the latest dlss dll but it's still way too blurry.

[Qcumber]

1 hour ago, Blinde said:

I thought dlsstweaks was broken with the latest update.

I'm using the latest dlss dll but it's still way too blurry.

I've not used it for a few weeks. 

[sleighzy]

On 7/11/2024 at 12:35 AM, Blinde said:

I thought dlsstweaks was broken with the latest update.

I'm using the latest dlss dll but it's still way too blurry.

@Blinde, yes DCS broke this a few patches ago. See my post here however for the DLSSTweaks workaround to resolve this issue, and how you can verify that it's working: 

 

 

[WipeUout]

Anyone noticed a quadviews box in settings?  I do use quadviews and see the box is checked but shaded out as well.  Any idea what this setting is? 

[slughead]

41 minutes ago, WipeUout said:

Anyone noticed a quadviews box in settings?  I do use quadviews and see the box is checked but shaded out as well.  Any idea what this setting is? 

Yes, I noticed that, along with an eye-tracking box. I think it might just be an indication to show that they are on or off as opposed to a setting the user can make in DCS.