Repository navigation
VR test build 3
Pre-releaseThis is the third 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 2
- PCs that only allow signed PowerShell scripts can now start the tool (#41). Nothing needs to be switched off, and if you switched script signing off for this, you can switch it back on.
- The "newer version" notice now only tells you about a newer VR test build (#42). In build 2 it pointed at the regular beta, which tests on the monitor.
- Everything from the regular betas 20 to 23: the test waits when Tacview is building its terrain files, moved or linked Saved Games folders, more older graphics cards and processors in the rating table, and clearer wording on the processor line.
- The tool no longer sends results. It doesn't ask and sends nothing about you, your PC or your results. If a test fails, the window shows a short bit of the DCS log with your user name and folder paths removed, and a Copy the failure log button so you can paste it to us.
Not in this build yet: picking the refresh rate you actually play at, for example a Quest 3 at 72 Hz (#40). That's next.
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
Tell us in an issue here or in #dcs-graphics-optimizer on the Fox3 Discord. Since the tool sends nothing, that's the only way we hear how it went.
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.