DCS on linux - Revision history

0nn0 at 20:08, 9 March 2026

2026-03-09T20:08:30Z

0nn0 at 19:52, 9 March 2026

2026-03-09T19:52:29Z

0nn0 at 19:51, 9 March 2026

2026-03-09T19:51:27Z

0nn0 at 18:59, 9 March 2026

2026-03-09T18:59:14Z

0nn0 at 18:48, 9 March 2026

2026-03-09T18:48:13Z

0nn0 at 19:20, 27 February 2025

2025-02-27T19:20:45Z

0nn0 at 19:17, 27 February 2025

2025-02-27T19:17:39Z

0nn0 at 18:57, 27 February 2025

2025-02-27T18:57:09Z

0nn0 at 18:49, 27 February 2025

2025-02-27T18:49:06Z

0nn0 at 18:11, 27 February 2025

2025-02-27T18:11:54Z

@@ Line 102: / Line 102: @@
 '''Q:''' ''I have The AH-64 module, but DCS crashes when I try to fly it''
-'''A:''' This is probably due to your prefix missing a certain font, called Segoe UI Symbol and should be in the seguisym.ttf file. You can try finding it online and then you need to drop it in ''/drive_c/windows/Fonts/'' within your prefix.
+'''A:''' This is probably due to your prefix missing a certain font, called Segoe UI Symbol and should be in the seguisym.ttf file. You can try finding it online and then you need to drop it in ''/drive_c/windows/Fonts/'' within your prefix. Technically this is piracy, but ED is the one at fault. They should have used their own font instead of using a proprietary Microsoft font which they haven't even properly licensed.
 '''Q:''' ''My screen is flashing black every couple of frames.''

@@ Line 102: / Line 102: @@
 '''Q:''' ''I have The AH-64 module, but DCS crashes when I try to fly it''
-'''A:''' This is probably due to your prefix missing a certain font, called '''Segoe UI Symbol'''. You can try finding it online and then you need to drop it in ''/drive_c/windows/Fonts/'' within your prefix
+'''A:''' This is probably due to your prefix missing a certain font, called Segoe UI Symbol and should be in the seguisym.ttf file. You can try finding it online and then you need to drop it in ''/drive_c/windows/Fonts/'' within your prefix.
 '''Q:''' ''My screen is flashing black every couple of frames.''

← Older revision		Revision as of 19:51, 9 March 2026
Line 98:		Line 98:

	'''A:''' This is a known problem, but there is a fix (seemingly only for X11 users). You have to add the following to your launch parameters <pre style="color: red">WINE_SIMULATE_WRITECOPY=1 %command%</pre>		'''A:''' This is a known problem, but there is a fix (seemingly only for X11 users). You have to add the following to your launch parameters <pre style="color: red">WINE_SIMULATE_WRITECOPY=1 %command%</pre>
		+
		+
		+	'''Q:''' ''I have The AH-64 module, but DCS crashes when I try to fly it''
		+
		+	'''A:''' This is probably due to your prefix missing a certain font, called '''Segoe UI Symbol'''. You can try finding it online and then you need to drop it in ''/drive_c/windows/Fonts/'' within your prefix

	'''Q:''' ''My screen is flashing black every couple of frames.''		'''Q:''' ''My screen is flashing black every couple of frames.''

@@ Line 129: / Line 129: @@
 ==SRS==
-Some have reported that SRS can work if installed via wine or proton, but there are no good guides on this which are current. Ask around to find out more.
+Some have reported that SRS can work if installed via wine or proton, but there are no good guides on this which are current. Some work is being done on scripting the installation. See the [https://github.com/ChaosRifle/DCS-on-Linux ChaosRifle git repo] for more details.
 ==Useful resources:==

@@ Line 1: / Line 1: @@
-DCS can be made to run on linux. You will need to use either wine or proton to make it work, as there is no native client. Overall it does work reasonably well. Compared to running DCS on Windows, the performance is slightly reduced, but decent. It doesn't matter if you use Gnome or KDE, but please be aware that there are many hotkeys in Gnome which use modifiers that collide with DCS default key assignments. DCS is known to run well on Ubuntu, OpenSUSE and Fedora and is likely to run well on many other distributions also.
+DCS can be made to run on linux. You will need to use either wine or proton to make it work, as there is no version of DCS that is made to run on linux natively. Overall it does work reasonably well. Compared to running DCS on Windows, the performance is slightly reduced, but decent. It doesn't matter if you use Gnome or KDE, but please be aware that there are many hotkeys in Gnome which use modifiers that collide with DCS default key assignments. DCS is known to run well on Ubuntu, OpenSUSE and Fedora and is likely to run well on many other distributions also.
 See the FAQ and external references for more info on known problems and how to fix them.
@@ Line 109: / Line 109: @@
 If you have a stand-alone HMD, like a Pico or Quest, you might want to have a look at [https://github.com/alvr-org/ALVR/wiki/Installation-guide Air Light VR (ALVR)] This tool can be used to connect to the HMD via a (wireless) network connection and presents the HMD as an OpenXR device. There are some caveats. ALVR is mostly geared towards nVidia GPUs, but AMD GPUs can be made to work. However, only the closed source drivers will work. Please check the [https://github.com/alvr-org/ALVR/wiki/Linux-Troubleshooting ALVR documentation] to see how to deal with this.
-Some if you intend to use Monado can benefit from [https://gitlab.com/gabmus/envision Envision], a tool which helps you set up a VR rendering context.
+If you use Monado, you can possibly can benefit from [https://gitlab.com/gabmus/envision Envision], a tool which helps you set up a VR rendering context.
-VR certainly is not an easy thing to get going on linux. Ask around if you need help.
+VR certainly is not an easy thing to get going on linux. It will take a fair bit of effort. Ask around if you need help.
 ==Head Tracking==
@@ Line 120: / Line 120: @@
 The most widely used program to do head tracking is opentrack. Opentrack can de made to run under Proton using the [https://github.com/markx86/opentrack-launcher Opentrack-launcher script]. This script downloads the latest version of opentrack at the time of first launch. This will opentrack run by adding a commandline option to the steam launcher. It works great for most users.
-If somehow the opentrack-launcher script doesn´t work you can also try to use a double installation. One inside the wine or proton prefix, and one outside the prefix. You then use the local loop network connection for data transfer.
+If somehow the opentrack-launcher script doesn´t work you can also try to use a double installation. One inside the wine or proton prefix, using the command line to launch the installer via wine or proton for the former, and one outside the prefix. You then use the local loop network connection for data transfer.
 Another possible option is to use a tool called [https://github.com/sonic2kk/steamtinkerlaunch SteamTinkerLaunch] to run multiple programs inside the same prefix.
@@ Line 133: / Line 133: @@
 ==Useful resources:==
-https://github.com/TheZoq2/dcs_on_linux : Git documentation for running DCS using Wine.
+https://github.com/ChaosRifle/DCS-on-Linux : Git documentation for running DCS using Wine.
 https://www.protondb.com/app/223750 : ProtonDB page for DCS.

@@ Line 11: / Line 11: @@
 ===Using Proton===
-This option requires that you have bought your DCS modules on Steam. This guide assumes an installation of Steam using the native package manager for your distribution. This option is available for most distributions. Alternatively you can use the Flatpak version of steam, but it is known to cause problems when using extra software like SRS or opentrack due to how security is managed in Flatpak.
+This option works with Standalone as well, but if you have bought your DCS modules on Steam, then it is massively easier. This guide assumes an installation of Steam using the native package manager for your distribution. This option is available for most distributions. Alternatively you can use the Flatpak version of steam, but it is known to cause problems when using extra software like SRS or opentrack due to how security is managed in Flatpak.
 At the time of writing (february 2024) the following steps are confirmed to be working on OpenSUSE Tumbleweed while using KDE and on Kubuntu 22.04.3. You might notice here that the description is basically about linux with KDE. The reason is that this is what you'll probably want to use this anyway, as there are a lot of keystrokes in DCS which interfere with Gnome's global hotkeys.

@@ Line 87: / Line 87: @@
 </pre>
-This example adds rules for multiple files in one file, matching them on vendor id and product id, setting the access to the device with MODE, setting them up as a joystick device, adding the user access tag and running the evade-joystick command using RUN for adding the device as a virtual device.
+This example adds rules for multiple devices in one file, matching them on vendor id and product id, setting the access to the device with MODE, setting them up as a joystick device, adding the user access tag and running the evade-joystick command using RUN for adding the device as a virtual device.
 You can also add calibration data and other options. For a more elaborate explanations or help, try searching the web or asking around.

@@ Line 95: / Line 95: @@
 '''A:''' You can get help/support for running DCS on linux on [https://old.reddit.com/r/hoggit r/hoggit] and on the [https://matrix.to/#/#dcs-on-linux:matrix.org DCS on Linux matrix channel]. Please note that this is on a best effort basis. In the end you still have to fix it yourself, but others might come up with suggestions you had not thought of.(..yet)
-'''Q:''' ''I have The F-4E module, but it Jester seems to be borked''
+'''Q:''' ''I have The F-4E module, but certain features, like the wheel for Jester and the sketch on the canopy are borked''
-'''A:''' This is a known problem, but there is a fix (for X11 users). You have to add the following to your launch parameters <pre style="color: red">WINE_SIMULATE_WRITECOPY=1 %command%</pre>
+'''A:''' This is a known problem, but there is a fix (seemingly only for X11 users). You have to add the following to your launch parameters <pre style="color: red">WINE_SIMULATE_WRITECOPY=1 %command%</pre>
 '''Q:''' ''My screen is flashing black every couple of frames.''

@@ Line 5: / Line 5: @@
 ==Setting Up DCS==
 ===Using Wine===
-You can check out [https://github.com/TheZoq2/dcs_on_linux TheZoq2's guide] or [https://github.com/budderpard/DCS_Standalone_on_linux/blob/master/README.md#Vr-References Budderball's guide]for tips and tricks for running DCS Standalone on linux.
+You can check out [https://github.com/TheZoq2/dcs_on_linux TheZoq2's guide] or [https://github.com/budderpard/DCS_Standalone_on_linux/blob/master/README.md#Vr-References Budderball's guide] for tips and tricks for running DCS Standalone on linux.
 You can also try to use Lutris to make installation easier. See: https://lutris.net/games/dcs-world/ Please note that scripts tend to get out of date over time.