haze1 Posted July 10, 2023 Posted July 10, 2023 After 4 months, I still couldn't figure out how to launch the MT client using the Oculus Quest 2 headset. Using the " --force_enable_VR" command" launches the client but still fails to recognize the headset. The Oculus software is up to date. (Oculus App Version 54.0.0.110.284 (54.0.0.110.284)
LOW_Hitman Posted July 10, 2023 Posted July 10, 2023 In your games folder there is a folder called bin-mt (...Games\DCSWorld\bin-mt - use the dcs.exe file within this folder and DCS will run in MT-Version. Right after the start you can see if its the correct version - because in MT the main menu "hanger" is darker - the lightning is darker or a litte "dark yellow" Also using a oculus quest 2 so its important (if you are using a nvidia graphicscard) to set low latency mode to ultra in the nvidia settings for best output. i9-9900K / Bios Profile XMP2 / Rog Strix Z-390F Gaming / ASUS TUF Geforce RTX 4070Ti Super / 32GB HyperX Fury 2666 / Saitek X52 HOTAS / Pico 4
BuckarooUK Posted July 12, 2023 Posted July 12, 2023 I think we have the same issue? I also have been using a Quest 2 with the regular DCS Beta standalone and the Oculus driver software. Multithread wouldn't access the hanger in which the Mig 29 sits. So I made a shortcut of the multi-thread .exe and added the force VR command. However, that takes be to a distorted menu screen upon booting up which is static (doesn't move with head movement). I've added a screenshot of the menu screen below. It's driving me nuts. Does anyone know how to solve it.
haze1 Posted July 12, 2023 Author Posted July 12, 2023 1 hour ago, BuckarooUK said: I think we have the same issue? I also have been using a Quest 2 with the regular DCS Beta standalone and the Oculus driver software. Multithread wouldn't access the hanger in which the Mig 29 sits. So I made a shortcut of the multi-thread .exe and added the force VR command. However, that takes be to a distorted menu screen upon booting up which is static (doesn't move with head movement). I've added a screenshot of the menu screen below. It's driving me nuts. Does anyone know how to solve it. exactly, it seems we have the same issue
Sprool Posted July 22, 2023 Posted July 22, 2023 I made a shortcut to DCS multithread which force-loads VR and the OpenXR toolkit, which is great for a performance boost. "E:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR Works fine as long as the Quest 2 is fired up and ready to go, I run DCS from within the Quest app, dcs appears in my games library.
thekow Posted July 22, 2023 Posted July 22, 2023 It also works for me in the above configuration, you need to make sure your oculus link is up already before launching though. IF you can afford to lose a few frames with steamVR you can run virtual desktop as well.
Tomcat388th Posted July 23, 2023 Posted July 23, 2023 My launch sequence 1 Turn on my quest 2 let it boot up to your home environment 2 I use the oculus debug tool so it gets started next. to tweak my link setting. 3 Back to the headset and turn on oculus link 4 Start DCS I use the MT exe with the force openxr and VR commands as stated above Ryzen7 5800X3D. 64 gb ram, 6950XT 16gb, Winwing Orion F18, MFG Crosswind Rudder, 42 inch lg tv, Quest PRO USN VF31 F14A AE2 1985-1989 CV 59 NAS Oceana IL ANG 183FW/170FS F16C Block 30 Big Mouth 1989-2006 Full time tech Retired E8
haze1 Posted July 29, 2023 Author Posted July 29, 2023 On 7/22/2023 at 11:15 PM, Sprool said: I made a shortcut to DCS multithread which force-loads VR and the OpenXR toolkit, which is great for a performance boost. "E:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR Works fine as long as the Quest 2 is fired up and ready to go, I run DCS from within the Quest app, dcs appears in my games library. With OpenXr downloaded, and using the "D:\dcs\bin-mt\DCS.exe --force_enable_VR --force_OpenXR" command it is still not working. null
Sprool Posted July 29, 2023 Posted July 29, 2023 you should have speech marks after .exe and not after OpenXR "E:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR
haze1 Posted July 30, 2023 Author Posted July 30, 2023 11 hours ago, Sprool said: you should have speech marks after .exe and not after OpenXR "E:\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR It doesn't let me do that. After I click to apply, and check the properties after, the speech marks are missing.
Sprool Posted July 30, 2023 Posted July 30, 2023 8 hours ago, haze1 said: It doesn't let me do that. After I click to apply, and check the properties after, the speech marks are missing. strange, works ok on my pc
haze1 Posted July 30, 2023 Author Posted July 30, 2023 1 hour ago, Sprool said: strange, works ok on my pc It does accept speech marks at "Start in", but when I try to add them to "Target", it just deletes them and highlights the text in the box. null
Sprool Posted July 31, 2023 Posted July 31, 2023 When I create a new shortcut by dragging existing one to my desktop for example, I just add the extra text to the properties that already exist, and in Target there are already speech marks there around the text so you just add the --force_enable_VR and so on. You just add a space and 2 dashes or minus signs then the rest of the text. If you are still struggling then can you launch DCS from within your VR headset in 'my apps' or 'Library'? Thats what I end up doing most of the time.
Recommended Posts