DCS Control 0.5.6 preview

DCS Control runs DLSS 5, frame generation and Quad Views foveated rendering together in VR (Pimax), set up and launched with one button, and makes DCS faster for every pilot (engine CPU optimizations, monitor or any headset).

New in 0.5.6:

• One-file setup. DcsControl-0.5.6-preview-Setup.exe: choose the install folder (it shows the space needed and free) and the Start menu / desktop shortcuts, and it installs for your Windows user without administrator rights. WebView2 and the Visual C++ runtime come from Microsoft when missing; an installed copy is updated in place and a failed update rolls back.
• Uninstall from Settings → Apps with its own window: it can put DCS back to stock first and, only if you tick it, delete your profiles and settings.
• Updates inside the app. DCS Control tells you when a newer release is out (Overview banner; turn it off on the Diagnostics page), shows what's new, then downloads the setup, checks its signature and installs it. After an update, What's new opens once.
  • From this version on, updates arrive this way. Coming from 0.5.5 or earlier, install 0.5.6 once with the setup (or the ZIP).

Also in 0.5.5:

• Terrain prefetch fix inside Engine Optimizations. It runs inside the engine optimizations module and has its own switch on that page, no longer tied to CPU Boost. It counts in the headset panel's Engine line.
• Nothing in DCS's install folder without DLSS 5. Optimizations only no longer adds dxgi.dll/dxgi2.dll to DCS's bin, so there is no Windows permission prompt under Program Files and no new DLLs for the antivirus.
  • Updating is automatic: the first Launch DCS removes the old files (or puts your own dxgi.dll back) and turns the new fix on.
• ReShade (or another dxgi.dll mod) keeps working with DLSS 5. The app names it in Checks and asks once before Launch DCS. Keep it working loads it after the DLSS 5 loader; Set it aside keeps it off. It is backed up either way and Back to stock DCS puts it back.

Also in 0.5.4: works on many more PCs, plus a large bug-fixing round.

• DCS under Program Files works. The app asks Windows once for permission to write where it needs to, instead of stopping with "Access to the path … is denied". If an antivirus or Windows Security's Controlled folder access is what blocks the write, the app says so.
• AMD and Intel graphics: DLSS 5 and NVIDIA frame generation are refused with a clear message, and frame generation starts as FidelityFX.
• Pimax without eye tracking gets a fixed focus area; a desktop Tobii eye tracker is no longer mistaken for the headset's.
• Finding DCS:
  • Saved Games: the folder DCS really uses, DCS or DCS.openbeta.
  • Standalone installs: also found through Eagle Dynamics' registry entry.
  • Pimax Play: found when installed outside Program Files.
  • Saved Games on OneDrive works.
  • Paths with accented letters work.
• CPU Boost keeps a core pinning you set yourself (Process Lasso) and is safer on small CPUs.
• Pupil shift:
  • With DCS's custom IPD on, it now actually reaches DCS: the layer applies the same IPD itself.
  • Canted headset views no longer shift both pupils towards the nose.
  • The page explains what it corrects and what not.
• Stability:
  • Frame generation: fixes for a thread-safety issue with DCS's D3D11 context, a long GPU stall, a removed device, and a possible crash at exit.
  • Engine optimizations: start/shutdown races, leaks and log paths fixed. On AMD drivers without D3D11 command lists, the multi-threaded shadows and G-buffer are reported as not supported.
• Smaller interface fixes:
  • decimal comma accepted;
  • shortcuts work on AZERTY and similar layouts;
  • Windows high contrast supported;
  • no timeout while a Windows prompt is open.
    Full list in docs/RELEASE_NOTES.md.

Earlier:

• 0.5.3: Diagnostics page and diagnostic package.
• 0.5.2: Pupil shift, engine status in the headset, refresh rate read from Pimax Play.

DCS VR Control is now DCS Control. It is no longer only for VR: the CPU optimizations are for every pilot, on a monitor or with any headset. The VR features remain for Pimax headsets.

Early beta. Flown mostly on one PC so far (Pimax Crystal Super at 90 Hz, RTX 5090, Ryzen 7 9800X3D, DCS 2.9 Steam, single player). Expect rough edges and please report what you find.

For every pilot (monitor or any headset)

• Engine Optimizations: a small module DCS loads by itself from Saved Games takes CPU work off DCS's render and model threads (multi-threaded G-buffer and shadows, faster culling, leaner memory and state handling) with exactly the same image. About +50-60 % FPS depending on the scene and p95 −34 % at a busy VR airfield when DCS is CPU-bound (image verified identical pixel by pixel; with everything on, the GPU becomes the limit). Once applied it stays on every time DCS starts, also from Steam or a desktop shortcut.
• CPU Boost (optional): DCS priority and core placement from DCS's own CPU ranking, plus a fix for DCS's terrain prefetch loop (≈1.7 cores freed in traces). The prefetch fix now also works when DCS starts from Steam.
• Free VRAM (optional): close VRAM-hungry apps before the flight and reopen them after.
• Optimizations only: for a monitor or any other headset. DCS runs exactly as you set it up; no OpenXR runtime, layer or VR option is touched.

For Pimax headsets

• Foveated rendering: bundled Quad-Views-Foveated (eye-tracked); the focus area follows your Pimax Play settings (Quick/Fine). Keep Quad Views on in Pimax Play.
• DLSS-NR ("DLSS 5") on the focus area only, through a modified Cheeky Foveated DLSS, with an optional smaller central area and an in-flight on/off hotkey. Bring your own nvngx_dlssnr.dll (tested 310.8); the app keeps a verified copy.
• Frame generation: OFXR (djules75 fork + DCS pacing patches). Auto 2×/3×, in-headset diagnostic panel with optional VRAM counter and Engine and Pupil shift lines.

One-click Launch DCS and Back to stock DCS (every file and setting the app touched goes back).

Download

• DcsControl-0.5.6-preview-Setup.exe (recommended): double-click it and follow the window. Windows 10 or 11, 64-bit (tested on 11). Windows may say the publisher is unknown: choose More info → Run anyway.
• DcsControl-0.5.6-preview-win-x64.zip: the same app as a portable folder (self-contained .NET). Unzip it anywhere and double-click DcsControl.exe; keep the files folder next to it.
• DcsControl-0.5.6-preview-sources.zip: complete corresponding source, including the modified OFXR (LGPL-3.0) and Cheeky (GPL-3.0) components.
• .sha256 files: checksums; .sig files: the release signatures the in-app updater checks.

Please note

• Single player only so far: the app places a dxgi.dll loader (and optionally dxgi2.dll) in DCS's bin folder and, with Engine Optimizations, a hook in Saved Games\DCS\Scripts. Multiplayer and integrity checks are untested; use Back to stock DCS before joining a server or updating DCS.
• Start the app from the Start menu, the desktop or Explorer.
• Frame generation adds latency, especially in 3×.

See the README and docs/USER_GUIDE.md. Support: https://ko-fi.com/nigos

DCS Control 0.5.5 preview

DCS Control runs DLSS 5, frame generation and Quad Views foveated rendering together in VR (Pimax), set up and launched with one button, and makes DCS faster for every pilot (engine CPU optimizations, monitor or any headset).

New in 0.5.5:

• Terrain prefetch fix inside Engine Optimizations. It runs inside the engine optimizations module and has its own switch on that page, no longer tied to CPU Boost. It counts in the headset panel's Engine line.
• Nothing in DCS's install folder without DLSS 5. Optimizations only no longer adds dxgi.dll/dxgi2.dll to DCS's bin, so there is no Windows permission prompt under Program Files and no new DLLs for the antivirus.
  • Updating is automatic: the first Launch DCS removes the old files (or puts your own dxgi.dll back) and turns the new fix on.
• ReShade (or another dxgi.dll mod) keeps working with DLSS 5. The app names it in Checks and asks once before Launch DCS. Keep it working loads it after the DLSS 5 loader; Set it aside keeps it off. It is backed up either way and Back to stock DCS puts it back.

Also in 0.5.4: works on many more PCs, plus a large bug-fixing round.

• DCS under Program Files works. The app asks Windows once for permission to write where it needs to, instead of stopping with "Access to the path … is denied". If an antivirus or Windows Security's Controlled folder access is what blocks the write, the app says so.
• AMD and Intel graphics: DLSS 5 and NVIDIA frame generation are refused with a clear message, and frame generation starts as FidelityFX.
• Pimax without eye tracking gets a fixed focus area; a desktop Tobii eye tracker is no longer mistaken for the headset's.
• Finding DCS:
  • Saved Games: the folder DCS really uses, DCS or DCS.openbeta.
  • Standalone installs: also found through Eagle Dynamics' registry entry.
  • Pimax Play: found when installed outside Program Files.
  • Saved Games on OneDrive works.
  • Paths with accented letters work.
• CPU Boost keeps a core pinning you set yourself (Process Lasso) and is safer on small CPUs.
• Pupil shift:
  • With DCS's custom IPD on, it now actually reaches DCS: the layer applies the same IPD itself.
  • Canted headset views no longer shift both pupils towards the nose.
  • The page explains what it corrects and what not.
• Stability:
  • Frame generation: fixes for a thread-safety issue with DCS's D3D11 context, a long GPU stall, a removed device, and a possible crash at exit.
  • Engine optimizations: start/shutdown races, leaks and log paths fixed. On AMD drivers without D3D11 command lists, the multi-threaded shadows and G-buffer are reported as not supported.
• Smaller interface fixes:
  • decimal comma accepted;
  • shortcuts work on AZERTY and similar layouts;
  • Windows high contrast supported;
  • no timeout while a Windows prompt is open.
    Full list in docs/RELEASE_NOTES.md.

Earlier:

• 0.5.3: Diagnostics page and diagnostic package.
• 0.5.2: Pupil shift, engine status in the headset, refresh rate read from Pimax Play.

DCS VR Control is now DCS Control. It is no longer only for VR: the CPU optimizations are for every pilot, on a monitor or with any headset. The VR features remain for Pimax headsets.

Early beta. Flown mostly on one PC so far (Pimax Crystal Super at 90 Hz, RTX 5090, Ryzen 7 9800X3D, DCS 2.9 Steam, single player). Expect rough edges and please report what you find.

For every pilot (monitor or any headset)

• Engine Optimizations: a small module DCS loads by itself from Saved Games takes CPU work off DCS's render and model threads (multi-threaded G-buffer and shadows, faster culling, leaner memory and state handling) with exactly the same image. About +50-60 % FPS depending on the scene and p95 −34 % at a busy VR airfield when DCS is CPU-bound (image verified identical pixel by pixel; with everything on, the GPU becomes the limit). Once applied it stays on every time DCS starts, also from Steam or a desktop shortcut.
• CPU Boost (optional): DCS priority and core placement from DCS's own CPU ranking, plus a fix for DCS's terrain prefetch loop (≈1.7 cores freed in traces). The prefetch fix now also works when DCS starts from Steam.
• Free VRAM (optional): close VRAM-hungry apps before the flight and reopen them after.
• Optimizations only: for a monitor or any other headset. DCS runs exactly as you set it up; no OpenXR runtime, layer or VR option is touched.

For Pimax headsets

• Foveated rendering: bundled Quad-Views-Foveated (eye-tracked); the focus area follows your Pimax Play settings (Quick/Fine). Keep Quad Views on in Pimax Play.
• DLSS-NR ("DLSS 5") on the focus area only, through a modified Cheeky Foveated DLSS, with an optional smaller central area and an in-flight on/off hotkey. Bring your own nvngx_dlssnr.dll (tested 310.8); the app keeps a verified copy.
• Frame generation: OFXR (djules75 fork + DCS pacing patches). Auto 2×/3×, in-headset diagnostic panel with optional VRAM counter and Engine and Pupil shift lines.

One-click Launch DCS and Back to stock DCS (every file and setting the app touched goes back).

Download

• DcsControl-0.5.5-preview-win-x64.zip: the app (self-contained .NET). Unzip it anywhere: inside are only DcsControl.exe, Install DCS Control.cmd, README.txt and a files folder that stays next to the exe. Double-click DcsControl.exe; Install DCS Control.cmd adds it to the Start menu (and replaces an earlier DCS VR Control install; your backups and profiles are kept). Windows 10 or 11, 64-bit (tested on 11). Needs the Microsoft Edge WebView2 Runtime, which the installer adds if missing.
• DcsControl-0.5.5-preview-sources.zip: complete corresponding source, including the modified OFXR (LGPL-3.0) and Cheeky (GPL-3.0) components.

Please note

• Single player only so far: the app places a dxgi.dll loader (and optionally dxgi2.dll) in DCS's bin folder and, with Engine Optimizations, a hook in Saved Games\DCS\Scripts. Multiplayer and integrity checks are untested; use Back to stock DCS before joining a server or updating DCS.
• Start the app from the Start menu or Explorer.
• Frame generation adds latency, especially in 3×.

See the README and docs/USER_GUIDE.md. Support: https://ko-fi.com/nigos

DCS Control 0.5.4 preview

DCS Control runs DLSS 5, frame generation and Quad Views foveated rendering together in VR (Pimax), set up and launched with one button, and makes DCS faster for every pilot (engine CPU optimizations, monitor or any headset).

New in 0.5.4: works on many more PCs, plus a large bug-fixing round.

• DCS under Program Files works. The app asks Windows once for permission to write where it needs to, instead of stopping with "Access to the path … is denied". If an antivirus or Windows Security's Controlled folder access is what blocks the write, the app says so.
• AMD and Intel graphics: DLSS 5 and NVIDIA frame generation are refused with a clear message, and frame generation starts as FidelityFX.
• Pimax without eye tracking gets a fixed focus area; a desktop Tobii eye tracker is no longer mistaken for the headset's.
• Finding DCS:
  • Saved Games: the folder DCS really uses, DCS or DCS.openbeta.
  • Standalone installs: also found through Eagle Dynamics' registry entry.
  • Pimax Play: found when installed outside Program Files.
  • Saved Games on OneDrive works.
  • Paths with accented letters work.
• CPU Boost keeps a core pinning you set yourself (Process Lasso) and is safer on small CPUs.
• Pupil shift:
  • With DCS's custom IPD on, it now actually reaches DCS: the layer applies the same IPD itself.
  • Canted headset views no longer shift both pupils towards the nose.
  • The page explains what it corrects and what not.
• Stability:
  • Frame generation: fixes for a thread-safety issue with DCS's D3D11 context, a long GPU stall, a removed device, and a possible crash at exit.
  • Engine optimizations: start/shutdown races, leaks and log paths fixed. On AMD drivers without D3D11 command lists, the multi-threaded shadows and G-buffer are reported as not supported.
• Smaller interface fixes:
  • decimal comma accepted;
  • shortcuts work on AZERTY and similar layouts;
  • Windows high contrast supported;
  • no timeout while a Windows prompt is open.
    Full list in docs/RELEASE_NOTES.md.

Earlier:

• 0.5.3: Diagnostics page and diagnostic package.
• 0.5.2: Pupil shift, engine status in the headset, refresh rate read from Pimax Play.

DCS VR Control is now DCS Control. It is no longer only for VR: the CPU optimizations are for every pilot, on a monitor or with any headset. The VR features remain for Pimax headsets.

Early beta. Flown mostly on one PC so far (Pimax Crystal Super at 90 Hz, RTX 5090, Ryzen 7 9800X3D, DCS 2.9 Steam, single player). Expect rough edges and please report what you find.

For every pilot (monitor or any headset)

• Engine Optimizations: a small module DCS loads by itself from Saved Games takes CPU work off DCS's render and model threads (multi-threaded G-buffer and shadows, faster culling, leaner memory and state handling) with exactly the same image. About +50-60 % FPS depending on the scene and p95 −34 % at a busy VR airfield when DCS is CPU-bound (image verified identical pixel by pixel; with everything on, the GPU becomes the limit). Once applied it stays on every time DCS starts, also from Steam or a desktop shortcut.
• CPU Boost (optional): DCS priority and core placement from DCS's own CPU ranking, plus a fix for DCS's terrain prefetch loop (≈1.7 cores freed in traces). The prefetch fix now also works when DCS starts from Steam.
• Free VRAM (optional): close VRAM-hungry apps before the flight and reopen them after.
• Optimizations only: for a monitor or any other headset. DCS runs exactly as you set it up; no OpenXR runtime, layer or VR option is touched.

For Pimax headsets

• Foveated rendering: bundled Quad-Views-Foveated (eye-tracked); the focus area follows your Pimax Play settings (Quick/Fine). Keep Quad Views on in Pimax Play.
• DLSS-NR ("DLSS 5") on the focus area only, through a modified Cheeky Foveated DLSS, with an optional smaller central area and an in-flight on/off hotkey. Bring your own nvngx_dlssnr.dll (tested 310.8); the app keeps a verified copy.
• Frame generation: OFXR (djules75 fork + DCS pacing patches). Auto 2×/3×, in-headset diagnostic panel with optional VRAM counter and Engine and Pupil shift lines.

One-click Launch DCS and Back to stock DCS (every file and setting the app touched goes back).

Download

• DcsControl-0.5.4-preview-win-x64.zip: the app (self-contained .NET). Unzip it anywhere: inside are only DcsControl.exe, Install DCS Control.cmd, README.txt and a files folder that stays next to the exe. Double-click DcsControl.exe; Install DCS Control.cmd adds it to the Start menu (and replaces an earlier DCS VR Control install; your backups and profiles are kept). Windows 10 or 11, 64-bit (tested on 11). Needs the Microsoft Edge WebView2 Runtime, which the installer adds if missing.
• DcsControl-0.5.4-preview-sources.zip: complete corresponding source, including the modified OFXR (LGPL-3.0) and Cheeky (GPL-3.0) components.

Please note

• Single player only so far: the app places a dxgi.dll loader (and optionally dxgi2.dll) in DCS's bin folder and, with Engine Optimizations, a hook in Saved Games\DCS\Scripts. Multiplayer and integrity checks are untested; use Back to stock DCS before joining a server or updating DCS.
• Start the app from the Start menu or Explorer.
• Frame generation adds latency, especially in 3×.

See the README and docs/USER_GUIDE.md. Support: https://ko-fi.com/nigos

DCS Control 0.5.3 preview

New in 0.5.3:

• Diagnostics page. If the headset panel says "DLSS 5: ON but not applied", the page reads the last DCS session and explains why in plain words, with what to check.
• Diagnostic package. One click saves a ZIP with what is needed to understand a problem: the app's report and the logs and settings of DCS, DLSS 5, frame generation, Quad Views, Pupil shift, the engine optimizations, CPU Boost and Pimax Play or SteamVR.
  • Only text files.
  • Your Windows user name, PC name and e-mail addresses are removed, and so are the account tokens, account ids and headset serial number found in Pimax's logs.
  • Attach it to your report.
• Fixes:
  • The refresh rate read from Pimax Play ignores seconds with missed frames.
  • Pupil shift no longer holds a lock while the frame is submitted, and the in-flight switch beep no longer causes a hitch.
  • Smaller interface fixes.

New in 0.5.2:

• Pupil shift (experimental).
• Engine and Pupil shift status in the headset panel.
• Refresh rate read from Pimax Play.
• Engine optimizations active in scenes with many views.

DCS VR Control is now DCS Control. It is no longer only for VR: the CPU optimizations are for every pilot, on a monitor or with any headset. The VR features remain for Pimax headsets.

Early beta. Flown mostly on one PC so far (Pimax Crystal Super at 90 Hz, RTX 5090, Ryzen 7 9800X3D, DCS 2.9 Steam, single player). Expect rough edges and please report what you find.

For every pilot (monitor or any headset)

• Engine Optimizations: a small module DCS loads by itself from Saved Games takes CPU work off DCS's render and model threads (multi-threaded G-buffer and shadows, faster culling, leaner memory and state handling) with exactly the same image. About +50-60 % FPS depending on the scene and p95 −34 % at a busy VR airfield when DCS is CPU-bound (image verified identical pixel by pixel; with everything on, the GPU becomes the limit). Once applied it stays on every time DCS starts, also from Steam or a desktop shortcut.
• CPU Boost (optional): DCS priority and core placement from DCS's own CPU ranking, plus a fix for DCS's terrain prefetch loop (≈1.7 cores freed in traces). The prefetch fix now also works when DCS starts from Steam.
• Free VRAM (optional): close VRAM-hungry apps before the flight and reopen them after.
• Optimizations only: for a monitor or any other headset. DCS runs exactly as you set it up; no OpenXR runtime, layer or VR option is touched.

For Pimax headsets

• Foveated rendering: bundled Quad-Views-Foveated (eye-tracked); the focus area follows your Pimax Play settings (Quick/Fine). Keep Quad Views on in Pimax Play.
• DLSS-NR ("DLSS 5") on the focus area only, through a modified Cheeky Foveated DLSS, with an optional smaller central area and an in-flight on/off hotkey. Bring your own nvngx_dlssnr.dll (tested 310.8); the app keeps a verified copy.
• Frame generation: OFXR (djules75 fork + DCS pacing patches). Auto 2×/3×, in-headset diagnostic panel with optional VRAM counter and Engine and Pupil shift lines.

One-click Launch DCS and Back to stock DCS (every file and setting the app touched goes back).

Download

• DcsControl-0.5.3-preview-win-x64.zip: the app (self-contained .NET). Unzip it anywhere: inside are only DcsControl.exe, Install DCS Control.cmd, README.txt and a files folder that stays next to the exe. Double-click DcsControl.exe; Install DCS Control.cmd adds it to the Start menu (and replaces an earlier DCS VR Control install; your backups and profiles are kept). Windows 10 or 11, 64-bit (tested on 11). Needs the Microsoft Edge WebView2 Runtime, which the installer adds if missing.
• DcsControl-0.5.3-preview-sources.zip: complete corresponding source, including the modified OFXR (LGPL-3.0) and Cheeky (GPL-3.0) components.

Please note

• Single player only so far: the app places a dxgi.dll loader (and optionally dxgi2.dll) in DCS's bin folder and, with Engine Optimizations, a hook in Saved Games\DCS\Scripts. Multiplayer and integrity checks are untested; use Back to stock DCS before joining a server or updating DCS.
• Start the app from the Start menu or Explorer.
• Frame generation adds latency, especially in 3×.

See the README and docs/USER_GUIDE.md. Support: https://ko-fi.com/nigos

DCS Control 0.5.2 preview

New in 0.5.2:

• Pupil shift (experimental, eye-tracked Quad Views): when your eyes turn, each pupil moves a few millimetres, but DCS renders from fixed eye points, so near objects shift slightly against far ones as you look around. A new OpenXR layer renders each eye from where its pupil is, then hands the headset its own poses back. No GPU cost, off by default, not yet confirmed in flight; it has its own page and an in-flight switch (Ctrl+Shift+F10) to compare.
• Engine status in the headset: the diagnostic panel says whether all the engine optimizations are working, only some, none, or that you switched them off, and shows Pupil shift's state.
• Refresh rate read from Pimax Play as it runs (SteamVR on Sboys); no need to set it by hand.
• Engine Optimizations: they no longer sit idle in scenes with many views (the F-4), and the multi-threaded G-buffer covers 99.8-100 % of its passes there (22-33 % before).

Also in 0.5.1: a sturdier multi-threaded G-buffer, faster multi-threaded shadows, CPU Boost that follows DCS's own launcher, a working uninstall and a clearer interface.

DCS VR Control is now DCS Control. It is no longer only for VR: the CPU optimizations are for every pilot, on a monitor or with any headset. The VR features remain for Pimax headsets.

Early beta. Flown mostly on one PC so far (Pimax Crystal Super at 90 Hz, RTX 5090, Ryzen 7 9800X3D, DCS 2.9 Steam, single player). Expect rough edges and please report what you find.

For every pilot (monitor or any headset)

• Engine Optimizations: a small module DCS loads by itself from Saved Games takes CPU work off DCS's render and model threads (multi-threaded G-buffer and shadows, faster culling, leaner memory and state handling) with exactly the same image. About +50-60 % FPS depending on the scene and p95 −34 % at a busy VR airfield when DCS is CPU-bound (image verified identical pixel by pixel; with everything on, the GPU becomes the limit). Once applied it stays on every time DCS starts, also from Steam or a desktop shortcut.
• CPU Boost (optional): DCS priority and core placement from DCS's own CPU ranking, plus a fix for DCS's terrain prefetch loop (≈1.7 cores freed in traces). The prefetch fix now also works when DCS starts from Steam.
• Free VRAM (optional): close VRAM-hungry apps before the flight and reopen them after.
• Optimizations only: for a monitor or any other headset. DCS runs exactly as you set it up; no OpenXR runtime, layer or VR option is touched.

For Pimax headsets

• Foveated rendering: bundled Quad-Views-Foveated (eye-tracked); the focus area follows your Pimax Play settings (Quick/Fine). Keep Quad Views on in Pimax Play.
• DLSS-NR ("DLSS 5") on the focus area only, through a modified Cheeky Foveated DLSS, with an optional smaller central area and an in-flight on/off hotkey. Bring your own nvngx_dlssnr.dll (tested 310.8); the app keeps a verified copy.
• Frame generation: OFXR (djules75 fork + DCS pacing patches). Auto 2×/3×, in-headset diagnostic panel with optional VRAM counter and Engine and Pupil shift lines.

One-click Launch DCS and Back to stock DCS (every file and setting the app touched goes back).

Download

• DcsControl-0.5.2-preview-win-x64.zip: the app (self-contained .NET). Unzip it anywhere: inside are only DcsControl.exe, Install DCS Control.cmd, README.txt and a files folder that stays next to the exe. Double-click DcsControl.exe; Install DCS Control.cmd adds it to the Start menu (and replaces an earlier DCS VR Control install; your backups and profiles are kept). Windows 10 or 11, 64-bit (tested on 11). Needs the Microsoft Edge WebView2 Runtime, which the installer adds if missing.
• DcsControl-0.5.2-preview-sources.zip: complete corresponding source, including the modified OFXR (LGPL-3.0) and Cheeky (GPL-3.0) components.

Please note

• Single player only so far: the app places a dxgi.dll loader (and optionally dxgi2.dll) in DCS's bin folder and, with Engine Optimizations, a hook in Saved Games\DCS\Scripts. Multiplayer and integrity checks are untested; use Back to stock DCS before joining a server or updating DCS.
• Start the app from the Start menu or Explorer.
• Frame generation adds latency, especially in 3×.

See the README and docs/USER_GUIDE.md. Support: https://ko-fi.com/nigos

DCS Control 0.5.1 preview

New in 0.5.1: a sturdier multi-threaded G-buffer (a fault turns it off for the session instead of crashing DCS, and it now works correctly in the cockpit view), faster multi-threaded shadows, CPU Boost that follows DCS's own launcher, a working uninstall from the installed copy, and a reorganized, clearer interface.

DCS VR Control is now DCS Control. It is no longer only for VR: the CPU optimizations are for every pilot, on a monitor or with any headset. The VR features remain for Pimax headsets.

Early beta. Flown mostly on one PC so far (Pimax Crystal Super at 90 Hz, RTX 5090, Ryzen 7 9800X3D, DCS 2.9 Steam, single player). Expect rough edges and please report what you find.

For every pilot (monitor or any headset)

• Engine Optimizations: a small module DCS loads by itself from Saved Games takes CPU work off DCS's render and model threads (multi-threaded G-buffer and shadows, faster culling, leaner memory and state handling) with exactly the same image. About +50-60 % FPS depending on the scene and p95 −34 % at a busy VR airfield when DCS is CPU-bound (image verified identical pixel by pixel; with everything on, the GPU becomes the limit). Once applied it stays on every time DCS starts, also from Steam or a desktop shortcut.
• CPU Boost (optional): DCS priority and core placement from DCS's own CPU ranking, plus a fix for DCS's terrain prefetch loop (≈1.7 cores freed in traces). The prefetch fix now also works when DCS starts from Steam.
• Free VRAM (optional): close VRAM-hungry apps before the flight and reopen them after.
• Optimizations only: for a monitor or any other headset. DCS runs exactly as you set it up; no OpenXR runtime, layer or VR option is touched.

For Pimax headsets

• Foveated rendering: bundled Quad-Views-Foveated (eye-tracked); the focus area follows your Pimax Play settings (Quick/Fine). Keep Quad Views on in Pimax Play.
• DLSS-NR ("DLSS 5") on the focus area only, through a modified Cheeky Foveated DLSS, with an optional smaller central area and an in-flight on/off hotkey. Bring your own nvngx_dlssnr.dll (tested 310.8); the app keeps a verified copy.
• Frame generation: OFXR (djules75 fork + DCS pacing patches). Auto 2×/3×, in-headset diagnostic panel with optional VRAM counter.

One-click Launch DCS and Back to stock DCS (every file and setting the app touched goes back).

Download

• DcsControl-0.5.1-preview-win-x64.zip: the app (self-contained .NET). Unzip it anywhere: inside are only DcsControl.exe, Install DCS Control.cmd, README.txt and a files folder that stays next to the exe. Double-click DcsControl.exe; Install DCS Control.cmd adds it to the Start menu (and replaces an earlier DCS VR Control install; your backups and profiles are kept). Windows 10 or 11, 64-bit (tested on 11). Needs the Microsoft Edge WebView2 Runtime, which the installer adds if missing.
• DcsControl-0.5.1-preview-sources.zip: complete corresponding source, including the modified OFXR (LGPL-3.0) and Cheeky (GPL-3.0) components.

Please note

• Single player only so far: the app places a dxgi.dll loader (and optionally dxgi2.dll) in DCS's bin folder and, with Engine Optimizations, a hook in Saved Games\DCS\Scripts. Multiplayer and integrity checks are untested; use Back to stock DCS before joining a server or updating DCS.
• Start the app from the Start menu or Explorer.
• Frame generation adds latency, especially in 3×.

See the README and docs/USER_GUIDE.md. Support: https://ko-fi.com/nigos

DCS Control 0.5.0 preview

DCS VR Control is now DCS Control. It is no longer only for VR: the CPU optimizations are for every pilot, on a monitor or with any headset. The VR features remain for Pimax headsets.

Early beta. Flown mostly on one PC so far (Pimax Crystal Super at 90 Hz, RTX 5090, Ryzen 7 9800X3D, DCS 2.9 Steam, single player). Expect rough edges and please report what you find.

For every pilot (monitor or any headset)

• Engine Optimizations: a small module DCS loads by itself from Saved Games takes CPU work off DCS's render and model threads (multi-threaded G-buffer and shadows, faster culling, leaner memory and state handling) with exactly the same image. About +60 % FPS and p95 −39 % at a busy VR airfield when DCS is CPU-bound (image verified identical pixel by pixel; with everything on, the GPU becomes the limit). Once applied it stays on every time DCS starts, also from Steam or a desktop shortcut.
• CPU Boost (optional): DCS priority and core placement from DCS's own CPU ranking, plus a fix for DCS's terrain prefetch loop (≈1.7 cores freed in traces). The prefetch fix now also works when DCS starts from Steam.
• Free VRAM (optional): close VRAM-hungry apps before the flight and reopen them after.
• Optimizations only: for a monitor or any other headset. DCS runs exactly as you set it up; no OpenXR runtime, layer or VR option is touched.

For Pimax headsets

• Foveated rendering: bundled Quad-Views-Foveated (eye-tracked); the focus area follows your Pimax Play settings (Quick/Fine). Keep Quad Views on in Pimax Play.
• DLSS-NR ("DLSS 5") on the focus area only, through a modified Cheeky Foveated DLSS, with an optional smaller central area and an in-flight on/off hotkey. Bring your own nvngx_dlssnr.dll (tested 310.8); the app keeps a verified copy.
• Frame generation: OFXR (djules75 fork + DCS pacing patches). Auto 2×/3×, in-headset diagnostic panel with optional VRAM counter.

One-click Launch DCS and Back to stock DCS (every file and setting the app touched goes back).

Download

• DcsControl-0.5.0-preview-win-x64.zip: the app (self-contained .NET). Unzip it anywhere: inside are only DcsControl.exe, Install DCS Control.cmd, README.txt and a files folder that stays next to the exe. Double-click DcsControl.exe; Install DCS Control.cmd adds it to the Start menu (and replaces an earlier DCS VR Control install; your backups and profiles are kept). Windows 10 or 11, 64-bit (tested on 11). Needs the Microsoft Edge WebView2 Runtime, which the installer adds if missing.
• DcsControl-0.5.0-preview-sources.zip: complete corresponding source, including the modified OFXR (LGPL-3.0) and Cheeky (GPL-3.0) components.

Please note

• Single player only so far: the app places a dxgi.dll loader (and optionally dxgi2.dll) in DCS's bin folder and, with Engine Optimizations, a hook in Saved Games\DCS\Scripts. Multiplayer and integrity checks are untested; use Back to stock DCS before joining a server or updating DCS.
• Start the app from the Start menu or Explorer.
• Frame generation adds latency, especially in 3×.

See the README and docs/USER_GUIDE.md. Support: https://ko-fi.com/nigos

DCS VR Control 0.4.2-preview (early beta)

Early beta. Flown on one PC so far (Pimax Crystal Super at 90 Hz, RTX 5090, Ryzen 7 9800X3D, DCS 2.9 Steam, single player). Expect rough edges and please report what you find.

What's inside

• Foveated rendering: bundled Quad-Views-Foveated (eye-tracked); the focus area can follow your Pimax Play settings (Quick/Fine), shown exactly as Pimax Play shows them.
• DLSS-NR ("DLSS 5") on the focus area only, through a modified Cheeky Foveated DLSS, with an optional smaller central area and an in-flight on/off hotkey. Bring your own nvngx_dlssnr.dll (tested 310.8); the app keeps a verified copy.
• Frame generation: OFXR (djules75 fork + DCS pacing patches). Auto 2×/3×, smoothness buffer so 3× delivers 90 fresh frames at 30 base, in-headset diagnostic panel with optional VRAM counter.
• CPU Boost (optional): DCS priority and core placement from DCS's own CPU ranking, plus a fix for DCS's terrain prefetch loop (≈1.7 cores freed in traces; +3–5% FPS when CPU-bound).
• VRAM helpers (optional): close and reopen VRAM-hungry apps, small DCS desktop window in VR, lower monitor mode while flying.
• Engine Optimizations (optional, CPU): a module DCS loads from Saved Games that removes work from its render and model threads without changing the image: about +30 % FPS, p95 −20 to −23 %, process CPU −11 % at a busy VR airfield.
• Optimizations only (any other headset, or no VR): DCS runs as you set it up, with only Engine Optimizations, CPU Boost and Free VRAM; no OpenXR runtime, layer or VR option is touched.
• One-click Launch DCS and Back to stock DCS (every file and setting the app touched goes back).

Download

• DcsVrControl-0.4.2-preview-win-x64.zip: the app (self-contained .NET). Unzip and run DcsVrControl.exe, or run Install.cmd. Needs the Microsoft Edge WebView2 Runtime.
• DcsVrControl-0.4.2-preview-sources.zip: complete corresponding source, including the modified OFXR (LGPL-3.0) and Cheeky (GPL-3.0) components.

Please note

• Single player only so far: the app places a dxgi.dll loader (and optionally dxgi2.dll) in DCS's bin folder. Multiplayer and integrity checks are untested.
• Start the app from the Start menu or Explorer.
• Pimax Play: leave Quad Views on (the tested setup). The bundled Quad Views takes over from Pimax's own for DCS and reads your Pimax Play Quad View values; in the app select the Bundled provider for DLSS 5.
• Frame generation adds latency, especially in 3×.

See the README and docs/USER_GUIDE.md. Support: https://ko-fi.com/nigos