|
|
| Line 4: |
Line 4: |
| === New launcher === | | === New launcher === |
| <!-- Is there a name for this new launcher? --> | | <!-- Is there a name for this new launcher? --> |
| For the Steam and Lutris setup this page assumes Linux Mint 22.2. Everything might be a bit different in your specific distro, but the setups are always very similiar. You can easily play EVE on Steam. Lutris is a bit more work but doable. Both will start the EVE launcher.<br><small>Note: By default not all game files are downloaded and the client can download when it does not have the file/part. | | For the Steam and Lutris setup this page assumes Linux Mint 22.2. Everything might be a bit different in your specific distro, but the setups are always very similiar. You can easily play EVE on Steam. Lutris is a bit more work but doable. <br><small>Note: By default not all game files are downloaded and the client can download when it does not have the file/part. |
| The launcher can download all files en cache them, update when needed and removes parts when no longer needed. This behaviour can be changed in the launcher and I recommend to do so to prevent any lag due to loading.</small> | | The launcher can download all files en cache them, update when needed and removes parts when no longer needed. This behaviour can be changed in the launcher and I recommend to do so to prevent any lag due to loading.</small> |
|
| |
|
| === Steam (recommended) === | | === Steam (recommended) === |
|
| |
|
| * Install Steam through the software manager (any distro can use this guide https://www.linuxnest.com/install-steam-on-any-linux-distro-the-complete-2025-guide/) | | * Install Steam through the software manager |
| | ** any distro can use this guide https://www.linuxnest.com/install-steam-on-any-linux-distro-the-complete-2025-guide/ |
| * Open the steam app and Install EVE Online on Steam | | * Open the steam app and Install EVE Online on Steam |
| * Right click EVE Online in steam and chose "Properties": | | * Right click EVE Online in steam and chose "Properties": |
| Line 90: |
Line 91: |
|
| |
|
| === Discord Server: EVE on Linux === | | === Discord Server: EVE on Linux === |
| Join the growing community that plays on Linux. You can find specific help there easily. | | Join the growing community that plays on Linux. You can get even ditro specific help there easily. |
|
| |
|
| https://discord.com/invite/eKMEVeC7SQ | | https://discord.com/invite/eKMEVeC7SQ |
|
| |
|
| === Roll your own === | | === EVE on Linux Resources === |
| It is certainly doable and fun to get an installer, launcher & client to run with just the parts and get it to run, if you are so inclined please link your experience here.
| |
|
| |
|
| [https://gist.github.com/arillat/2b7e519a69268f519d507d0ed50b9713 Play EVE Online on Arch Linux with WineHQ]
| | * Manage GE Proton Version: <nowiki>https://davidotek.github.io/protonup-qt/</nowiki> |
| | | * Fix audio crackling/stuttering: <nowiki>https://steamcommunity.com/sharedfiles/filedetails/?id=3214697797</nowiki> |
| == Common issues and solutions ==
| | * EVE Online Linux Forum: <nowiki>https://forums.eveonline.com/c/technology-research/linux/</nowiki> |
| | | * OBS Vk Capture Plugin: <nowiki>https://github.com/nowrep/obs-vkcapture</nowiki> |
| Depending on the hardware used changing from/to Direct3D 11/12 can have a positive or negative effect on the quality and/or performance of the game client, this also depends on the in-game graphics setting. Your mileage may vary, since you use Linux it is expected that you have more than average computer knowledge and are able to figure out what works in your specific situation.
| | * pyfa works with .appimage: <nowiki>https://github.com/pyfa-org/Pyfa/releases</nowiki> |
| | | * Hotkey Daemon (for client switching purposes): <nowiki>https://github.com/baskerville/sxhkd</nowiki> |
| We recommend to use DirectX 11 in the launcher options, this might be different on your maschine or change int the future (current Sep 2025.
| |
|
| |
|
| === Client slowing down / high CPU usage === | | === Client slowing down / high CPU usage === |
| | Behavior like lagging is reported, a solution for this behavior is to disable '''Esync''' & '''Fsync'''. In the installation steps given above we already took care of that. |
|
| |
|
| * Behavior like lagging is reported, a solution for this behavior is to disable '''Esync''' & '''Fsync'''. In the steps above we took care of that. | | * Steam: Start the launcher with the launch options |
| | | <syntaxhighlight lang="bash"> |
| Steam: Start the launcher with a custom command [https://forums.eveonline.com/t/still-anyone-using-linux/401624/63 source] | | PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 LD_PRELOAD= %command% |
| | | </syntaxhighlight> |
| Lutris: In the runner options disable '''Esync''' & '''Fsync'''
| |
| | |
| === Disk usage ===
| |
| | |
| Through steam, the launcher can run the updater normally.
| |
| | |
| On Lutris the stable, recommended version (1.9.4+ on Sep 2025) given in the installation process might change. The updater is unable to update the launcher due to a missing component in wine. [https://discord.com/channels/940573867192221696/1096046348421312574/1187888482048299108 `unimplemented function msdelta.dll.ApplyDeltaW, aborting`] This results in a ever growing squirreltemp directory. Manually cleaning is required at this point in time (January 2024). A fix for this behavior is being worked on: make the updater detect wine and do a full update.
| |
| | |
| <small> Note: [https://bugs.winehq.org/show_bug.cgi?id=56007 on the wine bugtracker] </small> | |
| | |
| <hr>
| |
| | |
| {{Cleanup| Content below should be reviewed & updated}}
| |
| | |
| == Whey back when we had a native launcher & other problems ==
| |
| While Linux is not ''officially'' supported by CCP, a side project by '''CCP Snorlax''' has yielded a native Linux application that downloads a prebundled version of [https://www.winehq.org/ Wine] (also built by CCP Snorlax) which allows Linux to run the EVE launcher more easily. The launcher requires a {{Co|yellow|'''64-bit'''}} installation of Linux, but should work with most distributions.
| |
| | |
| Alternatively, for a more visual installation and cleaner management of multiple WINEPATHs, you can use [[Linux#Lutris|Lutris]].
| |
| | |
| Native Linux launcher has been [https://forums.eveonline.com/t/linux-launcher-key-details/159751 retired]. Recommended solution for running EVE on Linux is Steam/Proton
| |
| | |
| :''Much of this guide is adapted from the official forum post by CCP Snorlax, which can be found [https://forums.eveonline.com/t/eve-launcher-for-linux/7286 here]. Questions about the information found in this article are best asked on the [https://forums.eveonline.com/c/technology-research/linux official EVE forums]''.
| |
| | |
| | |
| === Custom Launcher Shortcut === | |
| '''''(The following additional steps are not strictly necessary, but can make running the launcher more convenient through the use of a custom launcher shortcut. See the Troubleshooting section below if you encounter any issues.)'''''
| |
| [[File:Evelauncher.png|thumb|Launcher icon]]
| |
| # Create a symbolic link (symlink) to the script in the user binaries folder
| |
| #: {{code|sudo ln -s {{Color|green|/Path/To/}}evelauncher.sh /usr/bin/evelauncher}}
| |
| # And make it executable
| |
| #: {{code|sudo chmod u+x /usr/bin/evelauncher}}
| |
| # Download the icon file
| |
| #: {{code|wget <nowiki>https://wiki.eveuniversity.org/images/a/af/Evelauncher.png</nowiki>}}
| |
| # Move the icon file to the correct directory
| |
| #: {{code|sudo mv Evelauncher.png /usr/share/pixmaps/}}
| |
| # Create the launcher file with your preferred editor
| |
| #: {{code|sudo edit /usr/share/applications/eve.desktop}}
| |
| # Insert the following text and then save it:
| |
| #: {{code|1= <nowiki>[Desktop Entry]</nowiki><br>Name=EVE Online<br>Comment=EVE Online by CCP Games<br>Exec=/usr/bin/evelauncher<br>Icon=Evelauncher<br>Terminal=false<br>Type=Application<br>Categories=Game;}}
| |
| # Run the game through the newly-created launcher shortcut!
| |
| | |
| === Using a Custom Wine Version ===
| |
| The copy of wine bundled with the launcher is quite outdated, but thankfully you can use your distribution's own wine runtime instead which gives access to things like DirectX11 support.
| |
| : '''''Note:''' Make sure to untick 'Run clients with DX9' if you want to use DX11.'''''
| |
| | |
| # Open the launcher settings with the small "E" symbol in the top right, tick "Use custom Wine", and in the box below it enter the path of your wine executable, e.g.
| |
| #: {{code|/usr/bin/wine}}
| |
| # Remove EVE's existing wine and wineenv folder
| |
| #: {{code|rm -Rd ~/.eve/wineenv ~/.eve/wine}}
| |
| # Reopen the launcher and start the game as normal.
| |
| # EVE's wine prefix should rebuild itself with the custom version.
| |
| | |
| | |
| === Troubleshooting === | |
| ==== Incompatible OpenSSL library ====
| |
| The EVE launcher requires the 1.0.x version of the openssl library in order to function, however, some newer versions of Linux distributions and those that use rolling releases include the 1.1.x version by default (this will be evident by the launcher simply not appearing at all when the script is run), so some extra steps to install the older compatibility library may be necessary.
| |
| :'''Note:''' The following example is for Ubuntu - paths and package names will likely be different on other distributions.
| |
| # Download the older library from your distribution's repos
| |
| #: {{code|sudo apt-get install libssl1.0.0}}
| |
| # Add symbolic links to the libraries in the launcher's folder
| |
| #: {{code|sudo ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 {{Color|green|/Path/To/evelauncher/}}libssl.so}}
| |
| #: {{code|sudo ln -s /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 {{Color|green|/Path/To/evelauncher/}}libcrypto.so}}
| |
| | |
| | |
| This should correct the issue temporarily, but the symlinks will be removed when the launcher is updated. A solution to this is to make your own script which checks for the existence of the symlinks, remakes them if they are missing and then triggers the launcher's script.
| |
| | |
| # Create the wrapper script in your preferred editor
| |
| :'''Note:''' The wrapper script cannot be located in the launcher's own folder, or it will be deleted when the launcher updates.
| |
| #: {{code|$EDITOR {{Color|green|/Path/To/Wrapper/}}evewrapper.sh}}
| |
| # Insert the following text and then save it:
| |
| #: {{code|1= dirname={{Color|green|/Path/To/evelauncher/}}<br><br>if [ ! -e $dirname/libssl.so.1.0.0 ]; then<br> ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 $dirname/libssl.so<br>fi<br>if [ ! -e $dirname/libcrypto.so.1.0.0 ]; then<br> ln -s /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 $dirname/libcrypto.so<br>fi<br>exec $dirname/evelauncher.sh}}
| |
| # If you made a custom launcher file as above, you will need to change the path of the symlink in step 1
| |
| #: {{code|sudo ln -s {{Color|green|/Path/To/Wrapper/}}evewrapper.sh /usr/bin/evelauncher}}
| |
| | |
| | |
| ==== Qt dependencies ==== | |
| In some rare instances on Ubuntu, you may be lacking the required Qt dependencies for the launcher, This will manifest as some QT files not be located and the launcher window opening but not displaying anything.
| |
| | |
| Instructions for this install are taken from here: https://wiki.qt.io/Install_Qt_5_on_Ubuntu
| |
| | |
| # Download the installer
| |
| #: '''Note:''' These can be put wherever the user prefers, but the home directory <code>~/</code> is recommended.
| |
| #: {{code|wget http://download.qt.io/official_releases/qt/5.7/5.7.0/qt-opensource-linux-x64-5.7.0.run}}
| |
| # Adjust permissions
| |
| #: {{code|chmod +x qt-opensource-linux-x64-5.7.0.run}}
| |
| # Install QT
| |
| #: {{code|./qt-opensource-linux-x64-5.7.0.run}}
| |
| # Install g++
| |
| #: {{code|sudo apt-get install build-essential}}
| |
| # Install generic fonts
| |
| #: {{code|sudo apt-get install libfontconfig1}}
| |
| | |
| | |
| ==== Libxcb dependencies ====
| |
| Evelauncher comes with its own libxcb. In some instances it fails to find xcb in its launch directory as well as to find libxcb installed in the system. This is indicated by message in console:<br>
| |
| ''This application failed to start because it could not find or load the Qt platform plugin "xcb" in ""''
| |
| | |
| To solve this problem just delete all files located in the directory of EVE launcher, that have "libxcb" as part of their names.
| |
| :{{code|rm libxcb*}}
| |
| | |
| | |
| ==== Launcher Shortcut Issues ====
| |
| Your EVE launcher shortcut may fail with the following message:
| |
| | |
| : {{code|/bin/sh: {{Color|orange|warning}}: shell level (1000) too high, resetting to 1}}
| |
| | |
| | |
| This, and other errors, are likely due to the fact that the 'dirname' and 'pwd' commands will return the location of the soft link, not of the shell script itself. Hence, we need to use readlink to follow every symlink in the path. Make the following changes to /path/to/evelauncher/evelauncher.sh:
| |
| | |
| : {{code|1= #!/bin/sh <br>{{Color|green|2= appname="evelauncher"}}<br><br>{{Color|green|2= dirname=$(dirname "$(readlink -f "$BASH_SOURCE")")}}<br>tmp="${dirname#?}"<br><br>if [ "${dirname%$tmp}" != "/" ]; then<br>dirname="$PWD/$dirname"<br>fi<br><br>LD_LIBRARY_PATH="$dirname:$LD_LIBRARY_PATH"<br>export LD_LIBRARY_PATH<br>export QTDIR=$dirname<br>export QT_PLUGIN_PATH=$dirname/plugins<br>"$dirname/$appname" "$@"}}
| |
| : '''Note:''' The first change is necessary only if you choose to give your soft link a different name.
| |
| | |
| | |
| ==== X Server ====
| |
| If Eve Online fails to launch, try running it from the terminal. Check for the following error message:
| |
| | |
| : {{code|user@localhost > ./evelauncher.sh<br>...<br>{{Color|orange|Invalid MIT-MAGIC-COOKIE-1}} }}
| |
| | |
| As explained [https://unix.stackexchange.com/a/10126/29963 here], an X program needs (1) the address of the display (typically ":0") and (2) the password for the display. The second requirement is known as the "Magic Cookie". One workaround to sidestep this access problem is to use xhost, which is an X server access control program. Make the following changes to /path/to/evelauncher/evelauncher.sh:
| |
|
| |
|
| : {{code|1= #!/bin/sh <br>appname="evelauncher"<br><br>dirname=$(dirname "$(readlink -f "$BASH_SOURCE")")<br>tmp="${dirname#?}"<br><br>if [ "${dirname%$tmp}" != "/" ]; then<br>dirname="$PWD/$dirname"<br>fi<br><br>{{Color|green|xhost +local:}}<br><br>LD_LIBRARY_PATH="$dirname:$LD_LIBRARY_PATH"<br>export LD_LIBRARY_PATH<br>export QTDIR=$dirname<br>export QT_PLUGIN_PATH=$dirname/plugins<br>"$dirname/$appname" "$@"}} | | * Lutris: In the runner options disable '''Esync''' & '''Fsync''' |
| : '''Note:''' xhost here is granting temporary access to any local application running as the current user. It is ''not'' allowing any kind of remote access.
| | : |
|
| |
|
| [[Category:Guides]] | | [[Category:Guides]] |
| [[Category:Applications]] | | [[Category:Applications]] |
