Skip to content

Releases

Beta 24

Beta 24 Pre-release
Pre-release

Choose a tag to compare

@fox3-fleed-access fox3-fleed-access released this 16 Nov 17:07

Another small one, for players whose DCS is set to run as administrator.

What's new

  • "[WinError 740] The requested operation requires elevation" (#44). If your DCS is set to always run as administrator and you start the optimizer the normal way, Windows won't let it start DCS, and the test stopped with that message. The window now tells you what to do in plain words: either start the optimizer with right-click, Run as administrator, or switch that setting off for DCS. Nothing is changed on your PC by the failed try. If you could never find the Apply button (#33), this was probably why: the test never got to a result.
  • The user guide has a new troubleshooting row for this.

Also in beta 23, a few hours ago: PCs that only allow signed PowerShell scripts can start the tool (#41).

VR testers: this is a regular beta and tests on your monitor. For testing in the headset use VR test build 3. It doesn't have the plain-words message above yet, but the same two ways around it work there.

How to use it: download DCSGraphicsOptimizer.exe below, close DCS, run it, and press Test and optimize. There's nothing to install. Your settings are backed up before anything changes, and Undo puts them back.

The tool sends nothing about you or your results, so we only know how it went if you tell us: an issue here or a note in #dcs-graphics-optimizer on the Fox3 Discord. Thanks!

Beta 23

Beta 23 Pre-release
Pre-release

Choose a tag to compare

@fox3-fleed-access fox3-fleed-access released this 16 Nov 16:06

A small one, for players whose PC would not let the tool start.

What's new

  • PCs that only allow signed PowerShell scripts (#41). At startup the tool reads your hardware with a small PowerShell script. On a PC set to run signed scripts only, Windows refused it, and some of you switched script signing off to get going. You no longer have to: the reading doesn't run as a script file any more, so that setting doesn't apply. If you switched script signing off for this, you can switch it back on.
  • The user guide now explains the "DCS is taking longer than usual but is still working" message you can see when Tacview builds its terrain files the first time on a map.

VR testers: this is a regular beta and tests on your monitor. For testing in the headset, stay on VR test build 2 and ignore its "newer version" notice for now (#42). The next VR test build fixes that notice and includes the fix above.

How to use it: download DCSGraphicsOptimizer.exe below, close DCS, run it, and press Test and optimize. There's nothing to install. Your settings are backed up before anything changes, and Undo puts them back.

The tool sends nothing about you or your results, so we only know how it went if you tell us: an issue here or a note in #dcs-graphics-optimizer on the Fox3 Discord. Thanks!

Beta 22

Beta 22 Pre-release
Pre-release

Choose a tag to compare

@fox3-fleed-access fox3-fleed-access released this 16 Nov 04:32

This one changes how you get feedback to us.

What's new

  • The tool no longer sends results. Earlier betas asked whether they could send anonymous test results. That's gone: beta 22 doesn't ask and sends nothing about you, your PC or your results. (It still checks GitHub once at start to see if a newer version is out.)
  • Two buttons at the bottom of the window take you to where we read everything: the issues here on GitHub and the #dcs-graphics-optimizer channel on the Fox3 Discord.
  • If a test fails, the window shows a short bit of the DCS log with your Windows user name and folder paths removed, and a Copy the failure log button. Paste it into an issue or the Discord channel and we can usually see what went wrong.

How to use it: download DCSGraphicsOptimizer.exe below, close DCS, run it, and press Test and optimize. There's nothing to install. Your settings are backed up before anything changes, and Undo puts them back.

Since we don't get results automatically any more, we only know how it went if you tell us. A quick "worked great" or "this looked wrong" in an issue or on Discord helps a lot, and the saved report folder is the most useful thing to attach. Thanks!

VR test build 3

VR test build 3 Pre-release
Pre-release

Choose a tag to compare

@fox3-fleed-access fox3-fleed-access released this 16 Nov 16:30

This 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.

Beta 21

Beta 21 Pre-release
Pre-release

Choose a tag to compare

@fox3-fleed-access fox3-fleed-access released this 15 Nov 21:46

A small update with fixes for reports since beta 20.

Fixes

  • "Benchmark aircraft never appeared" with Tacview (#3): the first time Tacview records on a map it builds its terrain files, and that can freeze DCS for several minutes right after the test mission starts. The test used to run out of time while that happened. It now waits for DCS to come back and carries on.
  • Older PCs rated as "not in our table yet" (#38): more older graphics cards and processors are in the table now, including the GTX 980 and 970 (desktop and laptop) and the i7-6700 family, so their rating isn't a guess any more.
  • Processor wording (#36): the processor line no longer talks about "single-thread speed", which made it sound as if the tool assumed the old single-threaded DCS. Multithreaded DCS is what gets tested.

How to use it: download DCSGraphicsOptimizer.exe below, close DCS, run it, and press Test and optimize. There's nothing to install. Your settings are backed up before anything changes, and Undo puts them back.

If you're on an older copy, the window will tell you a newer one is out (beta 18 and newer). If a test fails, the window can send us an anonymized bit of the DCS log, which is how we found the Tacview one. Thanks!

Beta 20

Beta 20 Pre-release
Pre-release

Choose a tag to compare

@fox3-fleed-access fox3-fleed-access released this 15 Nov 17:29

This one comes out early because a lot of you hit the "mission never started" problem with beta 18 today. It also brings everything from beta 19, which we skipped so you get the newest build straight away.

Fixes

  • "Mission never started" (#29): DCS won't host the test mission until it has finished signing in to multiplayer, and the test sometimes asked too early and gave up. It now waits for DCS to sign in and tries again.
  • Steam (#27): DCS is now started the way Steam starts it, so the "launch with custom arguments" box shouldn't appear any more. If Steam isn't open, the tool asks you to open it first.
  • Moved or linked Saved Games folder: on some PCs the test refused its own mission because DCS and the tool spelled the folder path differently. It now runs.

VR

  • Pick your headset: if the tool can't tell which headset you have, you can pick it from a list under the profile name. The list now includes Quest 3, 3S, 2 and Pro, Pico 4 and 4 Ultra, Reverb G2, Index, Varjo Aero and Bigscreen Beyond 2, alongside the Pimax headsets.
  • Frame rate first: in a headset the recommendation aims for the highest refresh rate your headset can really hold, instead of settling for half rate to gain picture.
  • The headset software's home screen (for example the Mixed Reality portal) no longer counts as "another program using the graphics card".
  • This regular beta still tests on the monitor. Testing inside the headset is in the VR test builds for now (see #10 if you'd like to help).

Also new: a Windows sound when a test starts and when it ends.

How to use it: download DCSGraphicsOptimizer.exe below, close DCS, run it, and press Test and optimize. Your settings are backed up before anything changes, and Undo puts them back.

If a test fails, the window can send us an anonymized bit of the DCS log. Those logs are how we found today's fixes, so thank you!

Beta 18

Beta 18 Pre-release
Pre-release

Choose a tag to compare

@fox3-fleed-access fox3-fleed-access released this 15 Nov 14:04

Betas 16 and 17 were tested but never released, so this one brings everything from them. If you're on beta 15 or older, this is the one to grab.

Fixes

  • "Benchmark aircraft never appeared" (#3): your failure logs showed two more causes. Some add-ons get in the way of how the test finds its aircraft, and sometimes DCS stayed at the menu after the test had already finished. Both are handled now, so those runs count instead of failing.
  • Endless "DCS start was interrupted and will start again" (#17): if DCS closes straight away twice, the test now stops and tells you what to check instead of trying again and again. When Steam or the updater restarts DCS, the test follows along.
  • PCs with lots of add-ons (#17): setting up the test mission can take DCS a few minutes on these PCs. The test now waits for it instead of giving up seconds too early.
  • Wide multi-screen setups (#7): pictures spread over several screens (for example with exported MFDs) get a fair frame-rate goal instead of always being graded against 120 FPS.
  • Scorecard before the test (#25): the score shown before you test is now judged against the goal a Balanced test would aim for on your PC, so it should be much closer to what the test then measures.

New

  • The window tells you when a newer version is out, with a button to the download page. To check, it looks at this project's list of releases when it opens; nothing about you or your PC is sent.
  • The version you're running is shown at the bottom of the window.
  • The user guide has a "Removing it" section listing every file the tool leaves behind (#18).

How to use it: download DCSGraphicsOptimizer.exe below, close DCS, run it, and press Test and optimize. Your settings are backed up before anything changes, and Undo puts them back.

If a test fails, the window can send us an anonymized bit of the DCS log, which really helps. Thanks to everyone who sent theirs!

VR test build 2

VR test build 2 Pre-release
Pre-release

Choose a tag to compare

@fox3-fleed-access fox3-fleed-access released this 15 Nov 14:32

This 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.

VR test build 1 (for VR volunteers)

Pre-release

Choose a tag to compare

@fox3-fleed-access fox3-fleed-access released this 15 Nov 06:35

This is a test version for the VR volunteers. If you fly on a monitor, please use the regular beta instead.

What's different: 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 or SteamVR), 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.
  • 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.

DCS Graphics Optimizer 0.1.0-beta.15

Pre-release

Choose a tag to compare

@fox3-fleed-access fox3-fleed-access released this 14 Nov 16:00

Changes since beta 14:

  • Failure logs, anonymized. When a test fails, the tool makes a short extract of DCS's log (the benchmark's own lines, DCS's errors and warnings, and the end of the log). Your Windows user name and folder paths are replaced by <USER>, <SAVED> and <DCS>, and lines that mention logins, passwords, tokens, serials or e-mail addresses are left out. If you share test results, the extract is sent automatically and the window shows exactly what was sent. If you do not, nothing is sent; the window offers a Send this failure log button with a preview. This lets us fix failures like #3 without asking each of you for a file.

Everything from beta 14 is included: Balanced / Quality / Smoothness choice, the "benchmark aircraft never appeared" fix, the VR warning before Apply, and more.

Signed by Fox3 Managed Solutions Inc.
SHA-256: 265f3db44fadac2fdc8d63bb99d3dc54d76c1a2974898abde6532f74287d3b3b