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

[htns]

I can confirm this with a RX 580. Base game runs flawlessly, horizons hangs at planet generation.
The shaders slowly get compiled (DXVK_LOG_LEVEL=debug), but at 19% the gpu freezes.
There's some activity in this issue: https://github.com/doitsujin/dxvk/issues/36.
Nvidia works but slowly. AMD starts slowly but freezes.

I have a RX 480, and I discovered that if you just rename TerrainComputeShadersNvidia.csa to TerrainComputeShaders.csa in the game files it works (I only bought the game just recently after I had hopes it would work with linux steam/proton so it's not obvious to me how to test all the horizons features, but at least the game starts and I can land on a planet)

 

[Gordanos]

My x52pro works like a charm - i can post my .binds if you would like it?

What have you done to get the X52 working? I do not see the X52 in ED, it does not appear in the options. I followed all hints and instructions in this thread and got ED playable on Linux Debian, but only with keyboard an mouse (which is a pain...).

In general the x52 works perfect on my linux machine without a problem in another native linux game (X-Plane Flight simulator).

Any hints? Thanks!

 

[Cmdr Eagleboy]

It looks like it's already fixed.

Ok, this is confusing, but I hope you are right Fingers crossed

 

[Cmdr Eagleboy]

I have a RX 480, and I discovered that if you just rename TerrainComputeShadersNvidia.csa to TerrainComputeShaders.csa in the game files it works (I only bought the game just recently after I had hopes it would work with linux steam/proton so it's not obvious to me how to test all the horizons features, but at least the game starts and I can land on a planet)

Very interesting, be sure to mention it in that github issue So game ships with Nvidia shaders already? Interesting. I guess it works because dxvk does conversion to Vulkan shader format anyway.

 

[Grisham]

What have you done to get the X52 working? I do not see the X52 in ED, it does not appear in the options. I followed all hints and instructions in this thread and got ED playable on Linux Debian, but only with keyboard an mouse (which is a pain...).

In general the x52 works perfect on my linux machine without a problem in another native linux game (X-Plane Flight simulator).

Any hints? Thanks!

In ubuntu I didn't need to do anything to get X52pro working in wine. So should work in Debian too if it allready works in native games. Defer to earlier post for why it doesn't show as preset.

 

[fuzzylunkinz]

Hi all, just wanted to chime in and say I got standard ED working on Linux with my RX 580. Followed the instructions without issue. Horizons still freezes at planetary generation, and the Proton/Steam version crashes about a minute in. But standalone seems to be working great .

The only issue is no keybinds were set for some reason.

See my post here: https://github.com/doitsujin/dxvk/issues/36#issuecomment-435692964

EDIT:
Thanks to htns for the tip to get horizons working on AMD! I posted the commands I used to do that in the GitHub issue .

 

[Cmdr Ricey]

What have you done to get the X52 working? I do not see the X52 in ED, it does not appear in the options. I followed all hints and instructions in this thread and got ED playable on Linux Debian, but only with keyboard an mouse (which is a pain...).

In general the x52 works perfect on my linux machine without a problem in another native linux game (X-Plane Flight simulator).

Any hints? Thanks!

For me, the x52 was working great in Linux but the option for the x52 didn't show up because I was victim of the keyboard and mouse not getting mapped correctly - and still am.

I had to get my .binds file from my Win install of the game and replace the "keyboard" and "mouse" entries for the IDs that were saved in the game's file when saving the bindings out.

Here's my .binds file for the x52 but with my keyboard and mouse IDs in there. You may have to 'find replace' with yours.

https://ricey.uk/Ricey.3.0.binds

once edited with your IDs pop it into:

$WINEPREFIX/drive_c/users/<username>/Local Settings/Application Data/Frontier Developments/Elite Dangerous/Options/Bindings

hope that helps some...

Cheers

 

[Genar-Hofoen]

Well gosh darn it I managed to get Captain's Log 2 working natively in Linux - even autodetects when an ED game starts under WINE

Little bit of tidying up to do and some rewrites to make some stuff cross-platform, but great success tonight

 

[VictorT]

i'm crying you guys are so awesome!!

is anybody updating https://appdb.winehq.org/objectManager.php?sClass=application&iId=16405 ??

 

[wstephenson]

Welcome to the black, Commander!

Did you go with vanilla Frontier ED or get the Steam Play route working, I'm curious to hear?

 

[CMDR Sheehy]

Welcome to the black, Commander!

Did you go with vanilla Frontier ED or get the Steam Play route working, I'm curious to hear?

It's a couple of posts up https://forums.frontier.co.uk/showthread.php/366894-How-to-install-ED-on-Linux-using-Wine-EXPERIMENTAL-NOT-OFFICIALLY-SUPPORTED?p=7140548&viewfull=1#post7140548

Steam Version Freezes. Standard ED works.

 

[wstephenson]

It's a couple of posts up https://forums.frontier.co.uk/showt...LY-SUPPORTED?p=7140548&viewfull=1#post7140548

Steam Version Freezes. Standard ED works.

Was just checking whether VictorT had made progress with Steam, as a couple of posts further up we were talking about his preference to use that version, while we knew already that it worked with the Frontier launcher.

 

[RedMcG]

Was just checking whether VictorT had made progress with Steam, as a couple of posts further up we were talking about his preference to use that version, while we knew already that it worked with the Frontier launcher.

The Steam version needs a single patch from wine-staging to stop it freezing. I've made a fork of Valve's Wine here: https://github.com/redmcg/wine/tree/ED_Proton_3.16.

It's Proton 3.16-4 Beta with 8 additional patches that includes all the good work from this forum and fixes:
- Crash during opening video
- CRC Error when logging on to Frontier servers
- Freezing after a few minutes of game-play
- Keybind pre-sets not showing up
- Keyboard not working correctly

One interesting difference of the Steam version over wine-staging is that it installs vcrun2012 automatically and its own variation of corefonts (using open source fonts) - so using this patched version I only had one manual step: use winetricks to install dotnet40.

 

[Cmdr Eagleboy]

The Steam version needs a single patch from wine-staging to stop it freezing. I've made a fork of Valve's Wine here: https://github.com/redmcg/wine/tree/ED_Proton_3.16.

It's Proton 3.16-4 Beta with 8 additional patches that includes all the good work from this forum and fixes:
- Crash during opening video
- CRC Error when logging on to Frontier servers
- Freezing after a few minutes of game-play
- Keybind pre-sets not showing up
- Keyboard not working correctly

One interesting difference of the Steam version over wine-staging is that it installs vcrun2012 automatically and its own variation of corefonts (using open source fonts) - so using this patched version I only had one manual step: use winetricks to install dotnet40.

Nice work there RedMcG!

Yeah, they added corefonts to latest beta version. I know that adding dotnet452 would be too much for them, maybe someone could ask? Or they could allow potential usage of winetricks via some automation.

Or we could get launcher to work under mono, but as I understand that's not possible due of Win32.Forms usage.

 

[RedMcG]

I know that adding dotnet452 would be too much for them, maybe someone could ask?

Adding dotnet452 is technically easy (just include the DLL binaries in the tarball) - the issue is licensing (and Microsoft's lawyers). That's why Valve used open source fonts instead of the official Microsoft core fonts.

Or we could get launcher to work under mono, but as I understand that's not possible due of Win32.Forms usage.

That's the way forward on Linux. At the moment if you try to run it under 'mono' you'll get an error about the 'PresentationFramework' assembly missing (which is a reference to Windows Presentation Foundation [WPF]). And I think this link provides the best summary of the state of WPF on Linux:
https://www.mono-project.com/docs/gui/wpf/

At some point I'll have to investigate how much convergence there is between Moonlight and WPF and see if there is any overlap with the APIs used by EDLaunch.exe.

 

[Cmdr Eagleboy]

At some point I'll have to investigate how much convergence there is between Moonlight and WPF and see if there is any overlap with the APIs used by EDLaunch.exe.

I know it is a long shot but it would be exciting to get know what FD did to make launcher run under mono. I suspect they didn't port whole WPF just to do that.

 

[Flyinspaghetti]

The Steam version needs a single patch from wine-staging to stop it freezing. I've made a fork of Valve's Wine here: https://github.com/redmcg/wine/tree/ED_Proton_3.16.

It's Proton 3.16-4 Beta with 8 additional patches that includes all the good work from this forum and fixes:
- Crash during opening video
- CRC Error when logging on to Frontier servers
- Freezing after a few minutes of game-play
- Keybind pre-sets not showing up
- Keyboard not working correctly

One interesting difference of the Steam version over wine-staging is that it installs vcrun2012 automatically and its own variation of corefonts (using open source fonts) - so using this patched version I only had one manual step: use winetricks to install dotnet40.

Awesome work, yes that's one of the things about steam proton is that it installs most of the common core components and overrides.

I'm hoping Valve do use your patches on the main proton branch as while the standard wine/lutris methods work well having the game an easy install through steamplay would be a pretty big deal.

Also AMD users some more info on the whole shaders thing: https://github.com/doitsujin/dxvk/issues/36#issuecomment-435915946

 

[Genar-Hofoen]

For anyone interested, I have managed to produce a Linux distribution of Captain's Log 2.

Requirements for this version : any x86_64 (amd64.. whatever ) Linux distro with at least libc version 2.7

1) Download tarball from : https://www.dropbox.com/s/e3vnqmtyqhv5vtd/CaptainsLog2_2_1_8_beta_5_DIST_libc27_linux.tar.bz2?dl=1

2) untar somewhere

3) either cd to the created directory and type ./CaptainsLog2 , or browse to that directory and double-click that file

4) Best bet is to run the First Time Configuration with all defaults

5) For configuring the location of the Journal files, for my specific installation of ED-under-WINE, I have...

/home/<username>/Games/ED/drive_c/users/<username>/Saved Games/Frontier Developments/Elite Dangerous

...as the location of the ED Journal files.

6) For the Screenshot converter, I have /home/<username>/Games/ED/drive_c/users/<username>/My Pictures/Frontier Developments/Elite Dangerous as the ED Screenshot Directory

You might also be able to configure that as /home/<username>/Pictures/Frontier Developments/Elite Dangerous

The Destination Directory for converted pictures is at your discretion, but I chose /home/<username>/Pictures/Captains Log Screenshots for mine.

7) To test against the ED 3.3 Beta, place CL2 into Game Beta Mode - click Configuration, click on the Directory Locations tab, click the Use the Game Beta Player Journals checkbox. CL2 will need a restart after this operation.

CL2 will make a copy of any existing databases and create a new directory with a _gamebeta appended to the name, and will only look at JournalBeta* log files, and will only bung data into the CL2 beta db copies.

8) TIP: Launch ED first - get to the ED Menu stage - then start CL2. This will guarantee CL2 picks up the latest Journal file generated by the game. If you exit the game, exit CL2 before restarting the game. I'm still unb0rking the code which detects a new Journal file.



And lastly, note that CL2 2.1.8 betas are still a Work In Progress - there are and will be bugs, freezes, and other SNAFUS. I have a Discord server for bug reports (see my sig for link). I've made a linux category with a couple of channels, for linux-specific bugs/issues/chat.

 

[Flyinspaghetti]

For anyone interested, I have managed to produce a Linux distribution of Captain's Log 2.

Requirements for this version : any x86_64 (amd64.. whatever ) Linux distro with at least libc version 2.7

1) Download tarball from : https://www.dropbox.com/s/e3vnqmtyqhv5vtd/CaptainsLog2_2_1_8_beta_5_DIST_libc27_linux.tar.bz2?dl=1

2) untar somewhere

3) either cd to the created directory and type ./CaptainsLog2 , or browse to that directory and double-click that file

4) Best bet is to run the First Time Configuration with all defaults

5) For configuring the location of the Journal files, for my specific installation of ED-under-WINE, I have...

/home/<username>/Games/ED/drive_c/users/<username>/Saved Games/Frontier Developments/Elite Dangerous

...as the location of the ED Journal files.

6) For the Screenshot converter, I have /home/<username>/Games/ED/drive_c/users/<username>/My Pictures/Frontier Developments/Elite Dangerous as the ED Screenshot Directory

You might also be able to configure that as /home/<username>/Pictures/Frontier Developments/Elite Dangerous

The Destination Directory for converted pictures is at your discretion, but I chose /home/<username>/Pictures/Captains Log Screenshots for mine.

7) To test against the ED 3.3 Beta, place CL2 into Game Beta Mode - click Configuration, click on the Directory Locations tab, click the Use the Game Beta Player Journals checkbox. CL2 will need a restart after this operation.

CL2 will make a copy of any existing databases and create a new directory with a _gamebeta appended to the name, and will only look at JournalBeta* log files, and will only bung data into the CL2 beta db copies.

8) TIP: Launch ED first - get to the ED Menu stage - then start CL2. This will guarantee CL2 picks up the latest Journal file generated by the game. If you exit the game, exit CL2 before restarting the game. I'm still unb0rking the code which detects a new Journal file.



And lastly, note that CL2 2.1.8 betas are still a Work In Progress - there are and will be bugs, freezes, and other SNAFUS. I have a Discord server for bug reports (see my sig for link). I've made a linux category with a couple of channels, for linux-specific bugs/issues/chat.

I'm suffering from some dependency issues regarding lib32-qt4 & qtwebkit4, it seems the version 5 is the only ones available for my distro. AUR has the version 4 but they fail to build.

 

[wstephenson]

Fails for me (openSUSE Leap 15.0, don't laugh at the versioning, I only made up the colour codenames) because the bundled cx_freeze depends on libffi6, and we have libffi7.

Also, in case it's not intentional, the tarball contains another tarball.