MagicD3VIL
Published
Works absolutely fine out of the box, just install and run with proton 5+.
Works out of the box with Proton 5, no problems at all
Runs out of the box (tested with Proton 5.13). Slight performance issues when entering a new area before everything loads (amdgpu).
Game experience stutters when entering a new area before all of the textures manage to load for that area.
Experienced no problems at all with newest Proton. The performance was indistinguishable from Windows running the game on the same machine.
You have to build mesa from git (version 21.0) otherwise the textures won't work as stated in the Proton 5.13-4 release changelog.
If you don't mind going through the setup process before playing the game, the result is quite enjoyable.
protontricks 223750 vcrun2017 corefonts xact d3dcompiler_43
The mouse capture after alt-tabbing from fullscreen works kinda weird. If you use the windowed mode and you set it to your native resolution, it will turn into borderless fullscreen, so I recommend using that option.
Summary
- After the initial steps in the section below, I was able to play the game with no problems at all. I did a few training missions, the game recognized my HOTAS automatically and the performance was indistinguishable from running on Windows.
Additional steps after the installation
- Select "
openbeta" in the Betas section of the game's properties menu. - Select "
Proton 4.11" in the Compatibility section of the game's properties menu. - Run the game once to create the WINEPREFIX required for the next step (the game will crash, that's ok).
- Install Protontricks (you'll need to have Python3) using "
pip install protontricks". - Use the command "
protontricks 223750 vcrun2017 corefonts xact d3dcompiler_43" to install the required files for the game. - Lastly, you will need to CD to the root of the game's installation directory and make a symbolic link to the file "
webrtc_plugin.dll" in the "bin" folder by using this console command:ln -s ./bin/webrtc_plugin.dll ./webrtc_plugin.dll
If you don't do this, the game will launch but you'll be stuck on a black screen.
Additional notes
- Do not press the F10 key while in-game, I suggest rebinding any action using this key to something else. It's a known bug and pressing this key will crash the game.
- If the game crashes while playing, you will need to go to the WINEPREFIX of your DCS World (usually your Steam root folder and then "
./steamapps/compatdata/223750/") and delete this file:./pfx/drive_c/windows/system32/lsteamclient.dll
If the game crashed and this file is present when you'll try to launch the game again, you will receive an error message and the game won't start.
- The game worked with my Thrustmaster T.Flight Hotas One out of the box which is a nice plus.
Made for DCS World Steam Edition [openbeta] Version: 2.5.6.59398
Music sometimes didn't play
Doesn't work with Proton 5.13. You have to manually set it to use Proton 5.0-10
With a few initial setup steps runs without any issues with performance on par with the native version.
6.1-GE-2 GloriousEggroll
Things I did before launching the game:
- I used command
protontricks -c 'wine64 uninstaller' 359320 - I installed custom
wine-mono version 6.1.0_ED(https://github.com/redmcg/wine-mono/wiki#install-custom-version) - I used custom
Proton-6.1-GE-2(https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/6.1-GE-2)
My Thrustmaster T-FLIGHT HOTAS ONE worked out of the box.
With a few initial setup steps runs without any issues with performance on par with the native version.
6.1-GE-2 GloriousEggroll
custom mono
These were my pre-launch steps to get the game working:
- I downloaded a custom Mono .msi installer from here: https://github.com/redmcg/wine-mono/releases/tag/wine-mono-6.1.1_ED
- I ran
protontricks -c 'wine64 uninstaller' 359320and uninstalled the current version of Mono and installed the custom Mono from the previous step - I downloaded and selected Proton 6.1-GE-2 as my Proton version (https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/6.1-GE-2)
- Profit
As a nice bonus, my Thrustmaster T-FLIGHT HOTAS ONE worked out of the box.
On the first launch, the intro cinematic won't play properly, but after changing to the correct resolution in the main menu, the cinematic works.
Fullscreen and alt-tabbing worked correctly. However, sometimes after alt-tabbing the game stops registering some keys. This is a game-related bug and not related to Proton. To fix this, you need to quicksave by pressing Alt+S.
Runs like native. It's free so give it a shot
The game works best for me in the borderless window mode
Saberclaw
For this test, I used an older model racing wheel Microsoft SideWinder Force Feedback. The wheel worked out of the box but for some reason even after setting in-game the wheel deadzone settings to 0 the wheel still had forced ~10% deadzone in the center and the force feedback was not working.
How I fixed deadzone and force feedback issue
- I installed the "
linuxconsoletools" package so I could use the "evdev-joystick" command. - I've set the wheel deadzone to 0 using
sudo evdev-joystick --evdev /dev/input/by-id/usb-Microsoft_SideWinder_Force_Feedback_Wheel__USB_-event-joystick --deadzone 0
"--evdev" selects the device you want to edit and "--deadzone" sets the deadzone. To list the devices you can edit you can use "sudo evdev-joystick --listdevs" command.
3. Now I don't know if it was thanks to installing the "linuxconsoletools" package or thanks to editing the deadzone but either way my force feedback is working now after doing the steps above.
Force Feedback did not work for me out of the box
For this test, I used an older model racing wheel Microsoft SideWinder Force Feedback. The wheel worked out of the box but for some reason even after setting the wheel deadzone to 0 in the in-game settings the wheel still had forced ~10% deadzone in the center. The force feedback was also not functional.
How I fixed deadzone and force feedback issue
- I installed the "
linuxconsoletools" package so I could use the "evdev-joystick" command. - I've set the wheel deadzone to 0 using
sudo evdev-joystick --evdev /dev/input/by-id/usb-Microsoft_SideWinder_Force_Feedback_Wheel__USB_-event-joystick --deadzone 0
"--evdev" selects the device you want to edit and "--deadzone" sets the deadzone. To list the devices you can edit you can use "sudo evdev-joystick --listdevs" command.
Additional notes
- I need to run the
uvdev-joystickcommand every time after plugging the wheel into the computer and before starting the game. Otherwise, the wheel will have the default center deadzone and the force feedback won't work. - I made this shell script for launching the game. If you'll use it, forget to edit it so it's corresponding to your setup:
#!/bin/sh
sudo evdev-joystick --e /dev/input/by-id/usb-Microsoft_SideWinder_Force_Feedback_Wheel__USB_-event-joystick --d 0
steam steam://rungameid/378860
exit
stranglevk 60 %command% -vulkan -USEALLAVAILABLECORES -cpuLoadRebalancing -ignorepipelinecache
I use Strange (stranglevk) as a frame limiter of choice but it is not necessary
5.21-GE-1 GloriousEggroll
The background music stopped playing when I clicked or alt-tabbed out of the game and didn't continue when I got back to the game.
5.21-GE-1 GloriousEggroll
Pre-launch tweaks
- I used Proton 5.21 GloriousEggroll: https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.21-GE-1
- I used the SpaceEngineers Linux Patcher: https://github.com/Linux74656/SpaceEngineersLinuxPatches/blob/master/PatcherGUI.jar (without it the game would crash on the splash screen)
I saw some floating grass here and there, not sure if it's Proton related. I resolved it by turning off the grass completely in the settings. The game looks better without it anyway.
5.21-GE-1 GloriousEggroll
Custom Proton 5.21-GE-1 GloriousEggroll
SpaceEngineersLinuxPatches https://github.com/Linux74656/SpaceEngineersLinuxPatches/blob/master/PatcherGUI.jar
I saw some floating grass here and there. I resolved it by turning off the grass completely in the settings. The game looks better without it anyway.
5.21-GE-1 GloriousEggroll
Custom Proton 5.21-GE-1 https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.21-GE-1
I saw some floating grass here and there. I resolved it by turning off the grass completely in the settings. The game looks better without it anyway.
Right now you will need to download the SpaceEngineersLinuxPatches from Github. Just download and run the PatcherGUI.jar and let it do its thing. Without it, the game will crash after the splash screen. https://github.com/Linux74656/SpaceEngineersLinuxPatches
PS: Mods, please stop removing the SpaceEngineersLinuxPatches from my Proton Report... the game won't launch without it!
gamemoderun %command% -nosteam
Some particle effect is not compiled correctly, so sometimes you can see a few small black squares floating in space. However, it is not frequent and noticeable.
Out of the box, the game kept crashing on startup with the Native version. That was because the game requires older libraries that my system does not have. I fixed this issue by forcing Steam Linux Runtime in the "Properties -> Compatibility" tab. After that, the game runs flawlessly.
The -nosteam launch option is for people who want to log in with their Gaijin account instead of their Steam account
I haven't tried native version but Proton runs great as with most Unity games
