Starting with VR - Checking my understanding

[FZ1FZ1]

Hi folks,

Apologies, I know you’ve heard this a zillion times before, but I’m brand new to VR.  I have a Quest 3 and a non-Steam version of DCS running on a Windows 11 PC.

I’ve watched lots of YouTube vids and read many posts on various forums.  After getting overwhelmed with conflicting advice/instructions regarding  different bits of software/options, etc, I’ve spent some time trying to un-confuse myself. I think I now have a basic level of understanding of what I need to do to get started. 

Rather than me just posting a “What do I do?” request, I’d just like to check my understanding so far, based on the statements below.  I’d really appreciate it please, if someone could confirm that I’ve got these 4 statements correct.  If I haven’t, please could you point me in the right direction (in simple terms!)

Thanks in advance.

 

1. To get the PC and headset talking to each other, I can use either Virtual Desktop OR Oculus Link (Air or Cable versions)

 

2. I have a choice of middleware (APIs?) 

     a. Use the Oculus protocol built into DCS by starting it with the   --force_oculusVR   qualifier   OR

     b.  I can install the OpenXR toolkit and start DCS with the   --force_OpenXR   qualifier

 

3.  Using the OpenXR option gives more flexibility relating to optional in-game mods, than using the OculusVR option

 

4. I do not need to worry about SteamVR,  OpenComposite or Windows Mixed Reality with my setup.

 

[av8orDave]

36 minutes ago, FZ1FZ1 said:

Hi folks,

Apologies, I know you’ve heard this a zillion times before, but I’m brand new to VR.  I have a Quest 3 and a non-Steam version of DCS running on a Windows 11 PC.

I’ve watched lots of YouTube vids and read many posts on various forums.  After getting overwhelmed with conflicting advice/instructions regarding  different bits of software/options, etc, I’ve spent some time trying to un-confuse myself. I think I now have a basic level of understanding of what I need to do to get started. 

Rather than me just posting a “What do I do?” request, I’d just like to check my understanding so far, based on the statements below.  I’d really appreciate it please, if someone could confirm that I’ve got these 4 statements correct.  If I haven’t, please could you point me in the right direction (in simple terms!)

Thanks in advance.

 

1. To get the PC and headset talking to each other, I can use either Virtual Desktop OR Oculus Link (Air or Cable versions)

 

2. I have a choice of middleware (APIs?) 

     a. Use the Oculus protocol built into DCS by starting it with the   --force_oculusVR   qualifier   OR

     b.  I can install the OpenXR toolkit and start DCS with the   --force_OpenXR   qualifier

 

3.  Using the OpenXR option gives more flexibility relating to optional in-game mods, than using the OculusVR option

 

4. I do not need to worry about SteamVR,  OpenComposite or Windows Mixed Reality with my setup.

 

Nice work, I'd give you about a 90% on the test, not bad for a first try!

Seriously though, you've got it mostly correct. Some notes:

1) You can use Virtual Desktop, Oculus Link, or AirLink. As a general rule, Link refers to the cabled setup, while AirLink refers to Oculus's wireless option.

2) If you are using the Multithread version of DCS, OpenXR is native, and you don't need to use an argument. OpenXR Toolkit is a seperate software that gives additional options in-game. Your only other option is SteamVR.

3) With a Quest, you'll be using Oculus unless you use Virtual Desktop. OpenXR Toolkit is just additional software that adds additional features / options.

4) Correct.

Edited March 11, 2024 by davidrbarnette

[Qcumber]

41 minutes ago, FZ1FZ1 said:

1. To get the PC and headset talking to each other, I can use either Virtual Desktop OR Oculus Link (Air or Cable versions)

Yes. That's right although there are some issues with oculus working since the recent update. Once this is sorted by DCS then either are viable options. Although with oculus I would advise a cable (you can get a 3rd party cable for a lot less than meta charge). VD also requires a dedicated router connected to your pc via ethernet so there is an additional cost involved. There is also steam link which is "free" ( I say this because it still requires a decent WiFi connection or usb cable, so has some hidden costs). 

2. I have a choice of middleware (APIs?) 

     a. Use the Oculus protocol built into DCS by starting it with the   --force_oculusVR   qualifier   OR

     b.  I can install the OpenXR toolkit and start DCS with the   --force_OpenXR   qualifier

DCS uses open XR API as native so just stick with this. You don't need to "force" it anymore. Open XR toolkit is an add on that gives you some tweaking options. It more "icing in the cake". 

3.  Using the OpenXR option gives more flexibility relating to optional in-game mods, than using the OculusVR option

Yes. 

4. I do not need to worry about SteamVR,  OpenComposite or Windows Mixed Reality with my setup.

No. You do not need any of these unless you try using steam link then you will need steam VR. 

Simultaneous reply with davidrbarnette. Please see my comments interspersed above. 

Edited March 11, 2024 by Qcumber

[FZ1FZ1]

Thanks very much for the speedy replies guys, they are much appreciated.

It's good to know that I'm on the right track and thanks for keeping your corrections/advice to words of one syllable for me! 

 

@davidrbarnette

@Qcumber

Edited March 11, 2024 by FZ1FZ1

[Lange_666]

There's a problem with the latest Oculus software (v63) which causes DCS to crash.
 

Using Virtual Desktop instead should be fine from what i read.
If you are still on V62 of the Oculus app you can block it from updating this way:

 

[Mk1_Trebuchet]

You feel like you're finding conflicting information because you probably are....  sort of.   Always check the date on info posts, the whole VR thing is moving so fast that changes to hardware and software are practically constant.  But just beware, once you're set in VR it's really hard to go back.  

[FZ1FZ1]

Thanks folks!

 

@Lange_666 - Thanks for the heads-up. Being a cautious soul, I always set any software I install to prevent auto-update, so I'm still on V62 on the headset.  I thought that I'd checked a "no auto update" option on the PC app, but I'll check again and if not, I'll use the workaround you linked to

 

@Mk1_Trebuchet - Yes, I've been checking source dates, but with my lack of knowledge of the tech, it's difficult to know which technologies have been superseded/side-lined and which are still viable.  Having now got it working, I can definitely see the addictive potential! 

 

A quick update:

• I've now got VR working reliably (i.e. I can fire-it up repeatedly, not just by luck or accident!) albeit with some stutters and freezing.
• My next step is to revisit the most recent optimisation videos/postings and try the different performance improvement suggestions.
• Playing with Link vs. Virtual Desktop is another step to try, because I can now revert to a working setup if it all turns to poop!
• I have an unused WiFi-6 router from a recent ISP upgrade, so I'll set that up as an access point to improve wireless performance (my current WiFi hub is 4 brick walls away from the headset).

 

Thanks to all for the help.  I'm still cr4p at flying in DCS, but at least crashing and/or ejecting is more impressive in VR!  

 

Edited March 13, 2024 by FZ1FZ1