This guide assumes you have already have Steamplay/Proton installed with all of the prerequisites and such, as well as Space Engineers, and winetricks. If not, you can check around the internet for guides that can explain it much better than I can!
NOTE: Space Engineers and presumable many other proton games will fail with a 'too many files open' error as seen here: #35 while using OpenRC instead of systemd. The solution is to increase your file limits(the specific solution is in the original post of the issue linked previously).
Note: Ensure you have proton setup and configured prorperly. You can find more information here: https://github.com/ValveSoftware/Proton/wiki and https://github.com/ValveSoftware/Proton/wiki/Requirements
This java program simply requires Java 7 or later. This should be standard on most modern Linux systems. If it is not you can search the internet for a specific guide on how to install it for your particular Linux distribution.
Download this pre-compiled jar file:
If you would like to look at the source code or compile it yourself it is in this repository as Source-PatchGUI.java
Simply double click it and it should open. The program should be fairly intuitive and has a built-in help feature.
IF YOU CAN NOT START THE PatcherGUI.jar, because computers… THEN CONTINUE.
Some distros special circumstances do not allow you to simply double click the jar and have it run.
On some Distros and Desktop Environments you can simply right click on the PatcherGUI.jar file, then click properties > Permissions and ensure the check box: Is executable is marked.
You can open your terminal/console of choice and cd into the directory where the PatcherGUI.jar file is located, and run 'sudo chmod a+x PatcherGUI.jar'
Using your favorite terminal/console program, cd into the directory and run 'java -jar PatcherGUI.jar'
This will create the wineprefix and modify the config file for you. If you want you can scroll down and find the manual instruction on what this patcher automates.
Backup any save data, blueprints, ETC... Then verify the integrity of your game files in Steam.
Ensure prerequisites are installed and up to date.
Wine(5.0 or higher... although the newest version is recommended). Find out more at winehq: https://wiki.winehq.org/Download
Winetricks: from here https://wiki.winehq.org/Winetricks then:
sudo winetricks --self-update
Download(Save to downloads) this python script:
Run this script with
python3 autoprefix-patcher.py
Note: The script will ask you if it needs help, so make sure you read what it says! It can apply another fix for one of the issues below(freeze at startup) and will ask you if you want to fix it.
Congratulations Space Engineers should now work properly on Linux. Have fun and enjoy!
Backup any save data, blueprints, ETC...
Then verify the integrity of your game files in Steam.
Ensure prerequisites are installed and up to date.
Wine(5.0 or higher... although the newest version is recommended). Find out more at winehq: https://wiki.winehq.org/Download
Ensure winetricks is up to date.
sudo winetricks --self-update
Ensure protontricks is up to date.
follow the instructions based on how you installed it.
Create your wine prefix with winetricks in the compatdata folder in steamapps/common/
WINEPREFIX="INSERT/DIRECTORY/TO/SPACEENGINEERS/pfx" winetricks --force -q dotnet48 vcrun2015 faudio d3dcompiler_47
Create your wine prefix using protontricks if it is already installed, or if you want to install it from the instructions .
protontricks 244850 --force -q dotnet472 vcrun2015 faudio d3dcompiler_47
Open your Space Engineers bin64 directory: usually at $HOME/.local/share/Steam/steamapps/common/SpaceEngineers/Bin64
In this folder find the file SpaceEngineers.exe.config and open it in a text editor(Gedit, Kwrite, ETC...).
You should see something like this:
Now add <gcServer enabled = "true"/> to a new line after the line that says <runtime>
It should now look like this:
Save the file and close it.
Congratulations Space Engineers should now work properly on Linux. Have fun and enjoy!
Note you may have to reapply these fixes if the game updates. It depends on if the file is changed durring the update. If you encounter issues try following these steps again.
When using the autopatcher (even sometimes when using the manual method) the game will show a splash screen and then crash.
Manually install dotnet48 into your prefix. More information can be found in step 2 of manual guide above.
Broken startup and missing videos, causing startup freeze that requires user input to get past the splash screen.
Rename the file here: "LOCATION_OF_SPACE_ENGINEERS_INSTALL/SpaceEngineers/Content/Videos/KSH.wmv to KSH.wmv.old
OR
Set Steam launch options (right click Space Engineers in Steam, click Properties, then in the General tab) to %command% -skipintro
Upon startup the game will show this error one or more times.
- Just hit no each time it appears. It should not impact the ability of the game to run.
- Run
WINEPREFIX="INSERT/DIRECTORY/TO/SPACEENGINEERS/pfx" winetricksIn the library tab of the configuration window add rundll32.exe to the New override for library box and click add. Then find it in the list below and click edit and ensure disabled is selected. (See image below:) Click apply, then close the window.
Some users report that faudio has looping sound issues.
None is known at this time. More testing is required.
While using faudio some users report crackling or popping audio.
Try adding the following to your steam launch options(right click Space Engineers in steam, click Properties, then in the General tab, click SET LAUNCH OPTIONS...) add the following in the box that appears.
A) If something is already in the box add PULSE_LATENCY_MSEC=60 after those items but before %command%
e.g. DXVK_HUD=full PULSE_LATENCY_MSEC=60 %command% Make sure you have spaces between each item.
B) If the box is empty add:
PULSE_LATENCY_MSEC=60 %command%
Then hit ok on the launch options window. If you are still experiencing issues, try modifying the value of PULSE_LATENCY_MSEC try 30, or 90 instead of 60.
When the user alt+tab from the game, the game will keep the mouse from moving to another screen or selecting other windows. It also prevents keyboard input to other windows, even if they are on the same screen, or there is only one monitor.
The known workaround causes more issues than it fixes. If you are so inclinded to try it you can find it in issue #Be warned this fix breaks other things. Try at your own risk!
Game crashes shortly after start with System.OutOfMemoryException: Array dimensions exceeded supported range. error in log.
Game sends analytics to 81.0.234.196 and 88.146.207.227 (Keen SWH analytics servers) which apparently sends back some garbage that causes the issue (unintentionally). To resolve the issue block this service via:
sudo iptables -A INPUT -s 88.146.207.227 -j DROP
The game will freeze and accept no input just after loading a world. This will also sometimes lockup the OS. This seems to only happen on the newest line of AMD graphics cards(currently tested(5700/5700XT)).
Set all ingame graphics settings to minimum. Especially Voxel Quaity, and grass density. You may wish to increase some settings, such as texure quality, but do so at your own peril, the results may be mixed.
From this issue #26
SpaceEngineers.exe refuses to die after exiting the game.
You can take a look at this script by inetknght: https://github.com/inetknght/linux-profile/blob/master/.bash/kill_space_engineers.bash
It will help eleminate those pesky zombie processes.
From this issue #33
It appears space engineers does not work when run from an NFS(Network File System.)
Do not install or run SE from an NFS.
From this issue #46
Running Space Engineers will sometimes crash at or before the main menu. This sometimes is caused by mono being used instead of DotNet, however if dotnet is used then and this issue persist, try the following fix.
In winecfg, enable 'Emulate a virtual desktop' and set your desired resolution.
From this issue #52 Dotnet4.0, a requirement for dotnet4.7.2 and dotnet4.8 fails to install on some systems in newer proton versions.
Downgrade to an older version of proton such as 4.11-13, or possibly 5.0 and install dotnet, before swithing to a newer version of proton.