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

I've never had very good results Alt-Tabbing basically anything running full-screen in Wine. I always figured that was just something that came with the territory.
 
What drivers you using? From my testing there's only one graphics corruption glitch I've seen, and this happens when DXVK is used on Windows too so it's either a DXVK issue or a problem with Nvidia's Vulkan implementation:

I just ran into this also. It happens whenever a collector limpet flies in front of you during mining. It's caused for my by Bloom at Ultra settings. It seems to go away at High, but the engine rear is still flashing colors. Even though it's not a giant sqaure/rectangle at that point.
 
This ‘Failed to find GUID for device:’ error is back with a vengeance.
This time no cunning trick (like emptying the folder with the ControlSchemes and the Bindings folder) seems to work.
Fortunately, it only is an item on Kubuntu 19.04. When playing Elite using OpenSuSE Leap 15.0 (the hardware is the same as it is on the same PC), I encounter no such problem. Not yet.

The game sees my Sidewinder Precision Pro because, when defining one of joystick controls in the Controls section, this being the yaw axis, I can choose what axis to use for it. But when I click ‘apply’ for the first time and the file Custom.3.0.binds is generated, only an empty string seems to be written to it for parameter ‘Binding Device’.
The corresponding line in the file reads:

<Binding Device="" DeviceIndex="0" Key="Joy_RZAxis" />

where it should have been:

<Binding Device="045E0038" DeviceIndex="0" Key="Joy_RZAxis" />

Next time I go to the Controls section, the specified binding has gone as if I never clicked ‘apply’. Also the error file BindingLoadingErrors.log is generated:

‘Failed to find GUID for device:’

I do not see many posts about this topic in other parts of the forum. Might it be a linux problem?
 
This ‘Failed to find GUID for device:’ error is back with a vengeance.
This time no cunning trick (like emptying the folder with the ControlSchemes and the Bindings folder) seems to work.
Fortunately, it only is an item on Kubuntu 19.04. When playing Elite using OpenSuSE Leap 15.0 (the hardware is the same as it is on the same PC), I encounter no such problem. Not yet.

The game sees my Sidewinder Precision Pro because, when defining one of joystick controls in the Controls section, this being the yaw axis, I can choose what axis to use for it. But when I click ‘apply’ for the first time and the file Custom.3.0.binds is generated, only an empty string seems to be written to it for parameter ‘Binding Device’.
The corresponding line in the file reads:

<Binding Device="" DeviceIndex="0" Key="Joy_RZAxis" />

where it should have been:

<Binding Device="045E0038" DeviceIndex="0" Key="Joy_RZAxis" />

Next time I go to the Controls section, the specified binding has gone as if I never clicked ‘apply’. Also the error file BindingLoadingErrors.log is generated:

‘Failed to find GUID for device:’

I do not see many posts about this topic in other parts of the forum. Might it be a linux problem?
What wine version are you using?
 
FWIW, I just upgraded nvidia to 430.14 and I seem to get slightly better FPS where there is fog, something I had the impression slowed down the fps before. The other nice thing is that it appears I can now alt-tab without ED crashing. My desktop still runs like a dog and xorg is still at 100%. Hopefully I'm not premature with my report :)
 
FWIW, I just upgraded nvidia to 430.14 and I seem to get slightly better FPS where there is fog, something I had the impression slowed down the fps before. The other nice thing is that it appears I can now alt-tab without ED crashing. My desktop still runs like a dog and xorg is still at 100%. Hopefully I'm not premature with my report :)
Same, performance is indeed slightly better, though not having xorg at full here, seems normal with 30-60%. Everything still runs like a dog regardless :c
But instead of alt-tab issues now I get fails during game startup and heavy freezing once an hour or so, doesn't seem like it's triggered by anything particular, may happen in a station or during combat or in plain supercruise. VRAM and GPU usage is still stuck at 100% so idk. Oh well
 
Last edited:
What wine version are you using?
Settings:
wine64 --version: wine-4.8 (Staging)
winetricks --version: 20190310-next - sha256sum: 807a351b05cecd07c8488ad0f22d0e88c7f5569d86212ee06a1e236e35f81d21
uname -a: Linux vaessen-MS-7B48 5.0.0-15-generic #16-Ubuntu SMP Mon May 6 17:41:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Installation of Elite Horizons via Steam Overlay Enabled, Proton 4.2-4 enabled and use of Steam Beta Update.
I did not use protontricks.
Steam sees my Joystick under Controller Configuration.

I followed these instructions: https://github.com/redmcg/wine/wiki/Wine


New edit: things changed for the better. I copied the file Custom.3.0.binds from the Bindings folder on OpenSuSE Leap 15.0, where I have a properly working version of ED. Then I opened it in the text editor, changed the line with 'Custom' to 'MS_Sidewinder_Precision_2' and saved the file as MS_Sidewinder_Precision_2.binds. When starting ED, the joystick worked, even though I did not choose MS_Sidewinder_Precision_2 but stuck to Custom.
Beats me.
 
Last edited:
I've found it is far to easy for a game (and/or wine) to mess up the resolution and (multi-)screen layout.
Because of this I always set the "UseXVidMode" and "UseXRandR" registry keys to "N" in the wineprefix (see: winehq wiki).
With this, for me, Elite runs fine in a borderless (primary screen sized) window, no need to use the wine virtual-desktop.
I'm also not experiencing any problems with alt-tabbing or switching virtual desktops.

And I also want to say a quick thank you to the people here.
I don't use or have windows so I was rejoiced when I read the success stories. That was around last Christmas.
At that time Elite was on sale so decided to give it a try. I have been playing it almost daily since then.
Thank you! o7 cmdrs!
 
Pro tip: Don't un-check the "Enable Steam Play for other titles" option thinking that will be a way to hide all of the other Windows software that isn't installed as a way to de-clutter your library view. It will instantly delete Elite (and anything else not a "supported" title), and you'll have to download the whole 20 GB again...
 
Nice tip :)
Pro tip: Don't un-check the "Enable Steam Play for other titles" option thinking that will be a way to hide all of the other Windows software that isn't installed as a way to de-clutter your library view. It will instantly delete Elite (and anything else not a "supported" title), and you'll have to download the whole 20 GB again...
Great tip!
 
Just want to say how fantastic it is to have Elite: Dangerous - Horizons running in Linux.

I'm using Mint19 with the XFCE desktop and I'm playing more or less issue free - as in the app crashes occasionally ( only ever on launch ) but never any more than for windows players.

It was really not hard to get working in the end too.

Thank you Wine. Thank you Valve. Thank you DXVK
 
Hello all, coming back for help. Everything runs fine but today I decided to change the Elite game to my secondary monitor and, oh surprise, the Adapter and Monitor options in Graphics have grey background and cannot be changed.
I have a single Nvidia card (primary connected to HDMI and secondary to VGA) and multi-monitor works normally in Ubuntu.
Any ideas? Thanks!
 
I'd never checked before but it's greyed out for me too. The only thing I can think of it set your secondary monitor to be primary in Linux Display Settings.
I don't see an obvious setting about this in Ubuntu but I guess it's hidden somewhere in X settings. I'll report back if I succeed. Thanks!
 
I'm still in Unity. It turns out that the primary monitor is the one that you set to have the vertical launcher.
A bit of a nuisance to change it every time, but at least it's simple and it works without issues.
 
Top Bottom