Installing EVE on Linux: Difference between revisions

 

== Options to run a client on Linux ==

=== New launcher ===  

Some basics about the parts & process:

Installation starts with an installer, always found on [https://www.eveonline.com/download this] page or direct [https://launcher.ccpgames.com/eve-online/release/win32/x64/eve-online-latest+Setup.exe link]. Steam and Lutris can manage the dependencies & installation and subsequent updates.

The [https://github.com/Squirrel/Squirrel.Windows Squirrel] installer is used to install & update the launcher

The launcher downloads the client.  

The Launcher launches the client.  

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.

The current(as of December 2023) launcher & Linux unofficial channel on discord: [https://discord.com/channels/940573867192221696/1096046348421312574 Official EVE Online Discord server, new launcher channel, linux thread]

Thread on the EVE Forums: [https://forums.eveonline.com/t/recap-of-vanguard-on-linux-after-first-strike/432438 EVE Forums] Below from an excellent write up from Katrina Bekers:

* Use Steam, by opting-in the Beta branch and the code “TheInvitation” (case sensitive), installing the launcher from Steam, bypassing Squirrel altogether.

*  Manually extract the launcher package (“nupkg”, which is just a zip archive), and put it where it can be correctly run by WINE/Proton. Use this URL, modifying the version number adequately: https://launcher.ccpgames.com/eve-online/release/win32/x64/eve-online-1.1.0-full.nupkg

* Use [[Linux#Lutris|Lutris]], which implements a workaround for the “run as Administrator” default behavior in WINE/Proton, thus letting Squirrel do its job, see [https://lutris.net/games/eve-online/ install notes].

* Get the Squirrel installer and modify the Setup file with a binary editor so that the check for Administrator is reversed, and the installer proceeds if the user has Administrator privileges. smurftek: If you want to use the beta launcher under wine / proton without going through steam or having to change a bunch of settings, edit the binary and at address 00407436 replace it with “b8 01 00 00 00” and presto the launcher will work anywhere.

 

* Use Steam

 

 

 

 

=== Steam ===

https://www.protondb.com/app/8500

[https://lutris.net/ Lutris] is a gaming platform for Linux. It offers Wine builds that are pre-configured for specific games, and allows for a graphical installation of various games and applications. Those that are unable to use the methods above, or are weary on the process, may find this solution more viable.

 

 

 

 

 

 

 

 

 

 

 

 

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}}

#: {{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.

# Add symbolic links to the libraries in the launcher's folder

#: {{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.

# Insert the following text and then save it:

#: {{code|sudo ln -s {{Color|green|/Path/To/Wrapper/}}evewrapper.sh /usr/bin/evelauncher}}

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.

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.

Your EVE launcher shortcut may fail with the following message:

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" "$@"}}

==== 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" "$@"}}

: '''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.