Elite dangerous steam linux

How to install and play Elite Dangerous on Linux

There are video games that have literally made the history of video games: Arkanoid, Galaga, Donkey Kong, Super Mario, R-Type, just to name a few. There are video games that, beyond their beauty, have conquered millions of players: PUBG, Fortnite, Destiny to stay in recent times. There are video games that have gone beyond the concept of video games: Flight Simulator, SimCity, Civilization, Age of Empires, and we stop there.

Elite Dangerous, like all episodes of the Elite saga, is part of all these fields and has rightfully acquired a golden place in the history of video games. It is not just a video game, but a real scientific simulator that responds to all the laws of physics and science. Space, the galaxies, are his playing field, the spaceships his characters, the pilots his players. Elite Dangerous offers the opportunity to fulfill the dreams of those who grew up watching science fiction and marveling at the starry sky.

Unfortunately, Elite Dangerous doesn’t have a Linux version yet, and still had significant issues with Wine. But things are changing (actually, they have already changed!) thanks to Steam, Proton, and some tricks to apply.

Play Elite Dangerous on your Linux. Hassle-free and fast

Enough with dual-booting, slow emulators, launch errors, and all the flaws that have characterized trying to play Elite Dangerous on Linux so far. Today, thanks to all the work done by the Steam team and their Proton, with just a few clicks and some terminal commands, we can play Elite Dangerous and have an incredible gaming experience.

So, let’s see how to install and play Elite Dangerous on Linux.

1- Install Steam on your Linux distro

For Debian (like Mint and Ubuntu) based distro, easy peasy double click on the .deb file that you can get here: https://steamcdn-a.akamaihd.net/client/installer/steam.deb.

For Fedora, on the Software Repositories , ensure to enable the RPM Fusion Nonfree – Steam repo and digit in a terminal:

$ sudo dnf install steam

For openSUSE, just click on the 1-Click Install for your version on this page: https://software.opensuse.org/package/steam.

2- Enable Proton on Steam

On the Steam client, on the upper-left corner click on Steam and then Settings . On the Settings window, click on Steam Play and ensure to check the Enable Steam Play for supported files and Enable Steam Play for all other titles checkboxes. Also, select the Proton version (we suggest you use the latest if you don’t have issues) you want to use from the drop-down menu. Lastly, restart the Steam client.

3- Buy and install Elite Dangerous on Steam

On the Steam client, buy and install the Elite Dangerous game. You can also start with the link from the Steam website: https://store.steampowered.com/app/359320/Elite_Dangerous/.

Wait until the game is fully installed, restart the Steam client and do all the updates if presents.

You will see the game load and the Steam client show you that it is active. But, in truth, you won’t be able to play the game and you won’t even see a picture of Elite Dangerous.

Don’t worry, close the game, close the Steam client and go on.

4- Install Protontricks for your distribution

You can use pipx to install the latest version of Protontricks. pipx requires Python 3.6 or newer, and you will need to install pip, setuptools and virtualenv first. Install the correct packages depending on your distribution.

For Debian based:

$ sudo apt install python3-pip python3-setuptools python3-venv

For Fedora:

$ sudo dnf install python3-pip python3-setuptools python3-libs

For openSUSE:

$ sudo zypper in python3-pip python3-setuptools python3-libs

After installing pip and virtualenv, run the following commands to install pipx for the current user.

$ python3 -m pip install —user pipx
$

Close and reopen your terminal. After that, you can install protontricks.

$ pipx install protontricks

To upgrade to the latest release:

$ pipx upgrade protontricks

5- Use Protontricks to make Elite Dangerous working on Linux

As suggested above, make sure you have tried to launch the game at least once, and have protontricks set up before getting the dotnet framework.

Open a terminal window and digit:

$ protontricks 359320 -q dotnet472 win7

Wait until the installation process has been terminated and close the terminal window.

6- Launch Elite Dangerous inside Steam

Open the Steam client again, and click PLAY on the Elite Dangerous game.

If the game crashes on the first launch, this is normal. Click on PLAY again and you will see that everything will be fine this time.

So, in the end, have a nice journey Commander!

Источник

Elite dangerous steam linux

1,785	уникальных посетителей
33	добавили в избранное

This should be obvious, but expect no support from anyone if you have issues using this (hopefully temporary) method.

For now you should only use this method for yourself using your own commander, in solo mode only.

* 2019 july 4th : no more need for so many manual actions ; one protontricks command and you’re good to go.

* 2018 December 18th (minor) : note added on current debian testing nvidia-driver 390.87-4 state (crashes on client startup).

* 2018 December 15th (minor) : notes about winbind, vulkaninfo and compatibility.d/ location.

* 2018 December 13th : post 3.3 ED patch deployment — dotnet45 and vcrun2017 now required. Possible registry entries editing required to bypass the client CRC error («Login failure, use the launcher»).

As of now (july 4th 2019), one single protontricks command is enough to get ED up & running :

Get winetricks and protontricks (if you’re going to ask «how? where. «, just stop reading this, this isn’t for you.)

wine 4.x from your distribution’s packages should be enough (i used 4.0-2 from debian testing this time).

The instructions below are now deprecated, I keep them here, just in case somebody finds it interesting/useful.

A few things are required to get Elite Dangerous running on your favorite Operating System :

— ultra-fresh graphics driver (i use NVidia Beta 415.18.02) : https://developer.nvidia.com/vulkan-driver [«Developer Beta Driver Downloads» section]

— wine staging — see below

— winbind installed & running (on the «host» part) when you want to play the game (sorry about that, not liking those things either ; i personally disabled it on all runlevels, manually starting the service when needed)

some coffee, tea, cigarette or any (legal) recreational stuff plus some time (some downloads are quite heavy)

For example, i downloaded NVIDIA-Linux-x86_64-415.18.02.run

Back to console, uninstall (purge) your current, deprecated nvidia-driver package and all «*nvidia*» packages matching your current nvidia-driver package version.

You can use something like this to retrieve that list :

Uninstall those packages manually or use dpkg and awk

Still in console, run the nvidia driver you manually downloaded as root.

once installed, restart your x server (xdm, slim, gdm, whatever)

running nvidia-settings will allow you to confirm the upgrade :

you also have to install some vulkan libraries & tools :

wine-staging is required

I’m now using wine-4.0-rc1 (Staging)

first uninstall (purge) your wine debian packages :

then install wine from winehq repository :

again, a recent version of this tool is required (the use of winetricks is one of the reasons we upgraded wine for).

Proton 3.16-4 Beta was patched by redmcg ( github.com/redmcg ) for Elite Dangerous support ; we’ll add it to your steam installation.

/.steam/compatibilitytools.d/ # you must use

/.local/share/Steam/compatibilitytools.d/ # once you extracted this tarball you can check if it worked as expected # using steam steamplay settings (see following screenshot) : # «Proton 3.16-4 Beta ED» (note the «ED») should be listed there. # if in doubt, create one directory, and create a symlink for the other mkdir $HOME/.steam/compatibilitytools.d wget «https://github.com/redmcg/wine/releases/download/ED_Proton_3.16-4_Beta/Proton_3.16-4_Beta_ED.tar.gz» -O $HOME/Proton_3.16-4_Beta_ED.tar.gz cd $HOME/.steam/compatibilitytools.d/ tar zxvf $HOME/Proton_3.16-4_Beta_ED.tar.gz

Now, RESTART STEAM

Open steam settings, select «Steam Play» tab, and chose Proton 3.16-4 Beta ED
(note the «ED» part)

disable ESYNC : edit user_settings.py so it looks like this :

Back to the steam client, hit Play on Elite Dangerous, to ensure the WINEPREFIX directory structure is created (game will not start, or not in good shape at this point).

You can instead manually create compatdata/359320/pfx/ if you know its desired location (i ended up doing this to restart from scratch after some failures while putting this guide together).

We’ll install dotnet45 and vcrun2017 into ED’s WINEPREFIX :

Note that i entirely removed the compatdata/359320/ directory, prior to executing those commands, finally starting steam.

I also had vcrun2012 installed using winetricks (should not be required anymore, to be confirmed).

we’ll now inject dxvk’s modified DLL files into ED’s WINEPREFIX :

if you get the login failure error dialog once you hit play on EDLauncher, you have to update a registry key for MachineGuid, the one that’s used by the client (wine32 uses one MachineGuid value to start the launcher and wine64 another for the app initially) :

/.steam/compatibilitytools.d/Proton\ 3.16-4\ Beta\ ED/dist/bin/wine64 regedit

— Navigate to HKLM/Software/Microsoft/Cryptography

— Copy Value for MachineGuid key

— Navigate to HKLM/Software/Wow6432Node/Microsoft/Cryptography

on the Audio tab, set all i/o devices to pulseaudio (with wine staging you can now use your audio devices directly, haven’t tried that yet).

set mode to Windows 7 ; this is required and has to be run as the last wine action you’ll take.

If you don’t use pulseaudio, well . you should 🙂

we do not need any custom launch options anymore.

you should now be able to play ED by hitting the play button on your steam application.
(You may get two rundll32 errors, just continue)

I personally had to switch the Mouse pointer rendering mode in game settings from os cursor to ‘ ‘ otherwise mouse cursor would be semi-hidden while on dark backgrounds.

I first lowered all video features/settings to their minimal values and slowly increased them ; i play at 60 fps using this setup :

Debian GNU/Linux stretch 9.6 (stable flavor)
Linux 4.9.0
intel core i7-2600K cpu @3.40GHz
16GB RAM
GeForce GTX 1050 Ti (4GB)
Nvidia proprietary drivers 415.18.02 (it just works so i did not upgrade it recently, especially seeing some reports of problems from users using later versions).

Mose of those commands could be rewritten in a more compact form, or even scripted to semi-automate the whole thing, just requiring you to confirm dotnet and VCredist installations.

Such a script could probably also «guess» where your Elite installation is, thus not requiring you to edit the script once, but .. as you can see i did not take the time to do it this time.

I may consider doing it if the process changes too often.

For the record, packaged nvidia-driver 390.87-4 (from debian testing) crashes on gane client startup during shaders preparation, while manually installed (binary installer) 415.18.02 works perfectly at 60fps all settings maxed out.

Thanks to following teams and individuals for making this possible ; we’re getting really close to get «transparent» support for GNU/Linux for everybody without the need for manual actions :

— Graphics card manufacturers (i can only speak for NVidia, as i don’t use AMD gfx cards anymore)

— redmcg ( github.com/redmcg ) for his wine fork and active contribution

— Valve/Steam for providing a GNU/Linux steam client & integrating wine/proton into it

I’ll update this section slowly, but here are some of the sources used to put this together :

Источник