Repository navigation
VR test build 2
Pre-releaseThis is the second test version for the VR volunteers. If you fly on a monitor, please use the regular beta instead.
What's new since VR test build 1
- Frame rate comes first. The test now aims for the highest refresh rate your headset can really hold, and never goes below the frame rate your current settings already reach. It no longer settles for half rate (where motion smoothing kicks in) to gain picture. Half rate is only used if even the lowest settings can't hold any of your headset's refresh rates, and the result says so.
- Sounds. You'll hear a Windows sound when the test starts and another when it ends (a different one if it stops with a problem), so you know when to take the headset off.
- Mixed Reality and other headset software no longer stop the test with "another program is using your graphics card". The headset's home screen is expected to use the card before DCS takes over.
What this build does: when VR is switched on in your DCS settings, the test runs in your headset instead of on the monitor, and the recommendation is made for your headset.
Before you start
- Close DCS. VR should already be switched on in DCS's own settings.
- Connect the headset and open its software (Virtual Desktop, Meta Link, Pimax Play, SteamVR or the Mixed Reality portal), so it's sitting at its home screen.
- Wear the headset during the test, or cover its sensor, so it doesn't go to sleep and pause DCS. Look straight ahead when the test starts.
- If the window can't tell which headset you have, pick it from the list under the profile name.
Then press Test and optimize. DCS starts in the headset a few times and flies a short set of scenes on its own; you don't need to touch anything. It usually takes 10 to 20 minutes.
What would help us most
- Whether the test finished, and the before and after numbers
- Whether the recommended settings feel smoother in the headset
- Anything odd: DCS opening on the monitor instead, a black headset, the test stopping
Reply on the VR thread on GitHub or on Discord. If a test fails, the window has a button to send us the log.
Your settings are backed up and put back after every run, and Undo restores what you had before applying anything. The tool doesn't change Virtual Desktop, Link or Pimax Play settings, such as their quality or refresh rate.