Starting DCS with the quest pro

[markturner1960]

While i try and track down the cause of my crashes / freezes in the headset since the patch on Friday, I have been wondering whats the best way to run DCS....I am talking about runtimes and shortcuts etc and Steam VR

What do most QP users use? 

Is there any mileage in using SteamVR and if so, how would you set this up?

Currently, I am using the Oculus runtime, and my old shortcut with the force enable VR use open XR addition. I still have open XR performance tools available using this. 

Is there any other methods of starting / running DCS through the QP I can try, to see if they run without crashing? 

[slughead]

1 hour ago, markturner1960 said:

how would you set this up?

Have you tried these instructions?

 

Have you tried both the single thread and multithreaded binaries?

[markturner1960]

Thanks, I did see those but was still a little unclear:

I have Oculus set as the runtime in my oculus software. What was unclear was wether I still had to use the amended shortcut to start either of the binaries (MT orST) 

Also, if you want OpenXR performance tools to be available and active, how should this be done? 

Conversely, how would run in OpenXR without the toolkit being available and active?

I think its pretty clear in the linked instrcutions how to run using steamVR, I was more interested in wether this was worthwhile, what do the majority of users here do and why? 

Up until recently, it was accepted knowledge that using OpenXr was better than SteamVr, however, since DCS now supports openXR natively, I have heard people saying that SteamVR gives a better result. I wondered if there was any more detailed information on this or wether it was purely anecdotal....

 

Thanks!

[markturner1960]

Hi, OK, I have completed a complete re install of windows and DCS. Touchwood, so far, its all running OK. 

To start DCS, I am simply clicking the shortcut to the updater .exe that DCS placed on my desktop. 

I have set Oculus as the OpenXR runtime in Oculus home. 

If I look in my DCS log file, it says: VISUALIZER (Main): LAUNCH IN VR OculusRift: OculusRift : Oculus Rift S

Does this mean I am running OpenXR ? 

If I want to run DCS MT, I can simply make a shortcut to that .exe, but do either of these need an appended line added to run DCS in native open XR? 

And what is the difference between how its running now, using the Oculus openXR runtime and forcing openXR via the amended shortcut? Are they not the same thing? 

[Sile]

I think at the moment things are different for ST and MT.

- ST needs the --force_OpenXR Parameter in the shortcut if u want to use OpenXR API.
   Otherwise ST defaults to Oculus API. More here but i fear that's not true/updated for the current MT Client anymore.
- MT defaults to OpenXR API. No Parameter needed.

In the log you should see OpenXR somewhere in that line. So i think you are not running OpenXR, see above - ST needs startup parameter.
This is what i get in MT Client Log: "VISUALIZER (Main): LAUNCH IN VR OpenXR: Meta Quest Pro"

With OpenXR API you can set either SteamVR (in it's Settings -> OpenXR) or Oculus ( in Oculus home) as OpenXR Runtime. Try what works best for you.

And yes. You can simply make a shortcut to the .exe in "bin-mt". But I would just copy the ST Shortcut, rename it and change "bin" to "bin-mt" in both relevant fields. And add the parameter for OpenXR, if desired.

Edited June 14, 2023 by Sile

[markturner1960]

Thanks, following the above, I can confirm that I have the same line entry as you, VISUALIZER (Main): LAUNCH IN VR OpenXR: Meta Quest Pro for both MT & ST options. I dont use steamVR, so set the runtime in the oculus software. 

Thanks again