How to install ED on Linux using Wine [EXPERIMENTAL, NOT OFFICIALLY SUPPORTED]

It's the same steps for 4.11 (winetricks dotnet40 win7).

If you haven't already tried it, you could try deleting (and recreating) your prefix. You may also want to try a manual install of dotnet40:

I've found 4.11 to be a bit sensitive to other versions of Wine dabbling in the prefix.
Having started the client today just to test it seems to be working ok after all. The graphical garbage must have just been a glitch.

Is there any advantage in using Proton?
For me, yes. I bought ED and Horizons through steam so running it via steamplay is convenient for me.
 
Is there any advantage in using Proton?
Not if you already have it running in Wine. It does report to the developer that you are using Linux, if that's important to you (using just Wine otherwise looks just like another Windows user).

I think the stand alone launcher can be tricky to find (removed?) for new purchases too.

And you also get all the Steam features (like remote play).
 
Not if you already have it running in Wine. It does report to the developer that you are using Linux, if that's important to you (using just Wine otherwise looks just like another Windows user).

I think the stand alone launcher can be tricky to find (removed?) for new purchases too.

And you also get all the Steam features (like remote play).
I have a multiboot linux system.
On OpenSuSE, I have ED installed in the home directory. Steam is not installed on OpenSuSE.
But ED runs when I start the launcher.
On Ubuntu, the home directory is to small, so I have it installed on a separate directory (but this is not the home directory on OpenSuSE). Steam is installed on Ubuntu.
ED runs too when I start the launcher.
I wonder how Steam sees this all. It seems to know about two different locations as it mentions them in the Library Folders. But how knows Steam if I lauch ED from the OpenSuSE home directory and when I do it from Ubuntu?
 
Last edited:
Anyone running ED via Steam/Proton with a DualShock 4 controller and able to bind all buttons to game actions, including the "PS" button and touchpad click? I couldn't get it to work using Steam's controller config options, so I've been tinkering with tweaks to ds4drv to make all buttons bindable, but I wonder if someone has tread this path already.
 
Yesterday I upgraded wine to version 4.20 on OpenSuSE 15.1
Starting the launcher with:

wine64 EDLaunch.exe /novr

resulted in an error. The launch window appeared, but no 'play' button was there. In fact, there was not even room for such a button as the launcher window was smaller in the vertical dimension.

Starting the launcher with:

wine64 EDLaunch.exe /novr /steam

worked.
It surprises me, because I thought the /steam parameter had become obsolete.
 
Last edited:
I use Debian unstable and steam with the latest proton. Navi graphics all set to high and ultra. X52 pro works fully.

After following the wiki to install dotnet40, things went smooth and the game is running fine. I honestly don't know why fdev wouldn't make the effort to change the launcher to be compatible with vanilla mono... So out of the box steamplay would work. It's not like the launcher is complicated. Linux ftw
 
After following the wiki to install dotnet40, things went smooth and the game is running fine. I honestly don't know why fdev wouldn't make the effort to change the launcher to be compatible with vanilla mono... So out of the box steamplay would work. It's not like the launcher is complicated. Linux ftw
Well the good news is work has began on porting WPF in to wine-mono. Once that is complete, hopefully dotnet40 will no longer be required.

The bug report tracking this is here:

Source code is here:
 
On OpenSuSE Leap 15.1 I used to start Elite from within a bash shell.
Then I decided to make things more elegant and now I start Elite by simply pressing on an icon on the Panel at the bottom of the screen.
This icon is connected to the executable file on /home/vaessen/bin/Elite, the contents of which are:

cd /home/vaessen/Steam_oud/steamapps/common/Elite\ Dangerous
wine64 EDLaunch.exe /novr /steam

As no bash shell is opened, where does the system get its environment variables WINE and WINEPREFIX from?
How does it know that wine is installed in /home/vaessen/ed-wine, which is not a default place?
To be clear: there is no directory /home/vaessen/.wine, which would be the default wine directory.
 
Last edited:
I'm running Elite Dangerous in - wine-5.0-rc4 (Staging) - sometimes when starting the client the screen goes black then just stays black. If I have netflix running on the other monitor it runs for a bit and then stops and then in either case the monitors turn off and say "no signal" and I have to hit the reset button as the system is unresponsive.

Has anyone else experienced this? It didn't used to do it in Proton/Steamplay.
 
I'm running Elite Dangerous in - wine-5.0-rc4 (Staging) - sometimes when starting the client the screen goes black then just stays black. If I have netflix running on the other monitor it runs for a bit and then stops and then in either case the monitors turn off and say "no signal" and I have to hit the reset button as the system is unresponsive.

Has anyone else experienced this? It didn't used to do it in Proton/Steamplay.
Does not sound familiar.
 
I'm running Elite Dangerous in - wine-5.0-rc4 (Staging) - sometimes when starting the client the screen goes black then just stays black. If I have netflix running on the other monitor it runs for a bit and then stops and then in either case the monitors turn off and say "no signal" and I have to hit the reset button as the system is unresponsive.

Has anyone else experienced this? It didn't used to do it in Proton/Steamplay.
Also running wine-5.0-rc4 (Staging) in Arch.

I don't get the permanent black screen. But it's kind of a gamble as to whether the game launches or not. For me, it seems to be related to this WINE version handing over input control to the client.

In order to get the client launched fully, I have to first click on a terminal or some other app window (I have a dual-monitor layout) in order to keep the game client out of input focus. Then once it's fully up and running, is where the gamble begins.

A lot of times, when I click into the game client to give it input focus, the client immediately freezes, and then crashes with a crash report window. Other times, I get away with it and from then on can play the game and click out of and back into focus at will. I have to unfocus the game client window twice, as it seems to want to grab input focus twice (so basically I just keep clicking on a terminal window until the client is up and running.)

If I don't click out of the game client upon launching it, the screen goes black for a bit, then I get the game crash dialogue.

Also the level of success I have with starting the game depends on the desktop environment. The simpler the environment the better;

KDE Plasma - mostly fails to run
MATE desktop - more likely to run than KDE but still mostly crashes
LXDE - more likely to run but still can crash
A plain Openbox session - most success

It could be that your black screen freezes are a similar type of problem I'm encountering.

When you encounterr the black screen, do you try to alt-tab to a different window? That might bring the picture back alive.

Regds.
 
Also running wine-5.0-rc4 (Staging) in Arch.

I don't get the permanent black screen. But it's kind of a gamble as to whether the game launches or not. For me, it seems to be related to this WINE version handing over input control to the client.

In order to get the client launched fully, I have to first click on a terminal or some other app window (I have a dual-monitor layout) in order to keep the game client out of input focus. Then once it's fully up and running, is where the gamble begins.

A lot of times, when I click into the game client to give it input focus, the client immediately freezes, and then crashes with a crash report window. Other times, I get away with it and from then on can play the game and click out of and back into focus at will. I have to unfocus the game client window twice, as it seems to want to grab input focus twice (so basically I just keep clicking on a terminal window until the client is up and running.)

If I don't click out of the game client upon launching it, the screen goes black for a bit, then I get the game crash dialogue.

Also the level of success I have with starting the game depends on the desktop environment. The simpler the environment the better;

KDE Plasma - mostly fails to run
MATE desktop - more likely to run than KDE but still mostly crashes
LXDE - more likely to run but still can crash
A plain Openbox session - most success

It could be that your black screen freezes are a similar type of problem I'm encountering.

When you encounterr the black screen, do you try to alt-tab to a different window? That might bring the picture back alive.

Regds.
The system freezes completely when I get the black screen. It's just a matter of time and Alt-Tab only accelerates the time to freeze. I can't even Alt-F2

I suspect it may actually be my graphics card on it's last legs. Which is fine. I've been waiting for an excuse to buy a GTX1660ti 6gb. I can't justify the spend while my current card still works though.

Your crashes I do get. They are simple crashes that happen once in 10 starts and I just deal with it. I do send the data dump to FD. Hopefully it will somehow indicate to them that I'm a linux user and that there are more of us than they think.

I use Mint 19 with the XFCE desktop. I found that the compositing on Cinnamon was not good and used to produce blurry text that would come into focus when a mouse pointer was over quite often. If I had the "blurry desktop" then Elite would crash at every launch. I'd have to reboot a few times to get a stable desktop and then Elite would launch. This could again point to my graphics card being on it's way out.

Fingers crossed for bad hardware. I've run the "SuperPosition" benchmark program for linux and I get no issues but I do know that it's only OpenGL and doesn't necessarily tax the card in the same way that ED might when it's using Vulkan to simulate the DX11 stuff.
 
Also running wine-5.0-rc4 (Staging) in Arch.

I don't get the permanent black screen. But it's kind of a gamble as to whether the game launches or not. For me, it seems to be related to this WINE version handing over input control to the client.

In order to get the client launched fully, I have to first click on a terminal or some other app window (I have a dual-monitor layout) in order to keep the game client out of input focus. Then once it's fully up and running, is where the gamble begins.

A lot of times, when I click into the game client to give it input focus, the client immediately freezes, and then crashes with a crash report window. Other times, I get away with it and from then on can play the game and click out of and back into focus at will. I have to unfocus the game client window twice, as it seems to want to grab input focus twice (so basically I just keep clicking on a terminal window until the client is up and running.)

If I don't click out of the game client upon launching it, the screen goes black for a bit, then I get the game crash dialogue.

Also the level of success I have with starting the game depends on the desktop environment. The simpler the environment the better;

KDE Plasma - mostly fails to run
MATE desktop - more likely to run than KDE but still mostly crashes
LXDE - more likely to run but still can crash
A plain Openbox session - most success

It could be that your black screen freezes are a similar type of problem I'm encountering.

When you encounterr the black screen, do you try to alt-tab to a different window? That might bring the picture back alive.

Regds.
Exactly the same issues here with Proton 4.11-12 on Void with i3wm. Sometimes the game successfully launches even fully in focus, but switching focus to somewhere else helps dramatically.
 
No problems for me in Debian unstable, using steam vr beta and current proton with amd 5700xt.

I will say though, to do 90fps, you definitely want to make sure your kernel is full preempt and @ a 1000hz timer. I was consistently only hitting around 14ms with 300hz voluntary preempt with my kernel built for compiling performance.... But simply changing to a desktop config allows sub 11ms. Gpu is only 75c so it still looks like I'm cpu bound more than gpu. But that's to be expected with a software layer converting graphics calls
 
No problems for me in Debian unstable, using steam vr beta and current proton with amd 5700xt.

I will say though, to do 90fps, you definitely want to make sure your kernel is full preempt and @ a 1000hz timer. I was consistently only hitting around 14ms with 300hz voluntary preempt with my kernel built for compiling performance.... But simply changing to a desktop config allows sub 11ms. Gpu is only 75c so it still looks like I'm cpu bound more than gpu. But that's to be expected with a software layer converting graphics calls
That's really good information. I was really hoping that VR would work in linux for ED. I'm going to be using an Oculus Rift eventually. I have abandoned steam for playing Elite and don't want to be bound to steam for using VR in any case ( though I may be misunderstanding the way Steam VR works. If so then DM me how it actually works so we're not OT on this thread ).
 
Anyone had any luck or know how in getting two clients up and running? I can launch either account using the copy the edlauncher.exe trick. However it refuses to start a second client and I'm sure I used to run two clients side by side.
 
Top Bottom