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

[Junagu]

"I would go over the list here and make sure nothing is out of order: (https://github.com/redmcg/wine/relea...on_3.16-4_Beta). The information is pretty comprehensive there at this point and was a big help for me. "
How does this compare to the instructions that wstephenson wrote on 21/10/2018, 11:34 AM (Edited. 12/11/2018 at 4:48 PM) on this thread?

I'm trying to follow the instructions from that link - the custom Proton Build. However I can't get it to appear in the Steam Play Compatibility Tool in Steam Settings. I just have the Proton 3.16-5 and 3.7-8 and their Beta's. I must be missing something. I've run the ./fixED script and downloaded the vcrun2017 packages etc. However I've found a few conflicting instructions for where the compatibilitytools.d folder should go. Anyone any ideas?

I can run ED with the 3.16-5Beta and it gets as far as the login of the launcher and then crashed when I try to move from the Username field to the Password field. I get a Wine Debugger window show briefly (where can I find the error logs for that, btw?) but that's it.

Can anyone help me out?

 

[RedMcG]

I'm trying to follow the instructions from that link - the custom Proton Build. However I can't get it to appear in the Steam Play Compatibility Tool in Steam Settings. I just have the Proton 3.16-5 and 3.7-8 and their Beta's. I must be missing something. I've run the ./fixED script and downloaded the vcrun2017 packages etc. However I've found a few conflicting instructions for where the compatibilitytools.d folder should go. Anyone any ideas?

I can run ED with the 3.16-5Beta and it gets as far as the login of the launcher and then crashed when I try to move from the Username field to the Password field. I get a Wine Debugger window show briefly (where can I find the error logs for that, btw?) but that's it.

Can anyone help me out?

For me the location is ~/.steam/compatibilitytools.d. But I've seen over on Proton DB that some people have used ~/.local/share/Steam/compatibilitytools.d. If you've tried both and neither work let us know what your distro is and hopefully someone here can help.

If it's crashing when you click in the 'Password' field - this happens when corefonts is not installed. But I didn't think that was a problem with Steam. You can try installing corefonts with protontricks or winetricks - but I feel like something else is wrong if you're even running in to this issue.

 

[EdVaessen]

I had this problem and solved it by launching Steam Runtime instead of Steam Native. Also I'm using wine-staging 4.0. It might also be an IPV6 error.

Check this : https://github.com/redmcg/wine/releases/tag/ED_Proton_3.16-5_Beta

What are Steam Runtime and Steam Native? Where can I find them?
And what is the Steam Beta client?

 

[Junagu]

For me the location is ~/.steam/compatibilitytools.d. But I've seen over on Proton DB that some people have used ~/.local/share/Steam/compatibilitytools.d. If you've tried both and neither work let us know what your distro is and hopefully someone here can help.

If it's crashing when you click in the 'Password' field - this happens when corefonts is not installed. But I didn't think that was a problem with Steam. You can try installing corefonts with protontricks or winetricks - but I feel like something else is wrong if you're even running in to this issue.

I'm running Ubuntu 18.10 with an AMD r9 380 GPU.

Putting the Proton folder in ~/.local/share/Steam seemed to do the trick.

I've also tried running with PROTON_NO_D3D11=1 PROTON_NO_ESYNC=1 PROTON_NO_ESYNC=1 and I think that that is probably the wrong syntax somehow.

I get as far as the Spinning Corolis but then get a login failure.
"Make sure you start the game from the launcher so that you are up to date" message.

Tried the CRC fix (this https://www.youtube.com/watch?v=jG7TUOXZhng video came in handy) but still getting the login error.

 

[EdVaessen]

This is the installer you download from https://www.elitedangerous.com/, just click 'Downloads' -> 'Windows 64-bit'. It looks like the file is now called 'Client-Installer.exe'.

Just go to the directory to which you downloaded this and run:
wine64 Client-Installer

Make sure before you run this command you have defined your WINEPREFIX (for example with `export WINEPREFIX=~/ed-wine`)

I went to https://www.elitedangerous.com/
Yet the 'Downloads' -> 'Windows 64-bit' I could not find there.

 

[RedMcG]

I went to https://www.elitedangerous.com/
Yet the 'Downloads' -> 'Windows 64-bit' I could not find there.

Interesting - looks like you might need to buy and install through Steam now.

 

[RedMcG]

I'm running Ubuntu 18.10 with an AMD r9 380 GPU.

Putting the Proton folder in ~/.local/share/Steam seemed to do the trick.

I've also tried running with PROTON_NO_D3D11=1 PROTON_NO_ESYNC=1 PROTON_NO_ESYNC=1 and I think that that is probably the wrong syntax somehow.

I get as far as the Spinning Corolis but then get a login failure.
"Make sure you start the game from the launcher so that you are up to date" message.

Tried the CRC fix (this https://www.youtube.com/watch?v=jG7TUOXZhng video came in handy) but still getting the login error.

You shouldn't need PROTON_NO_ESYNC=1 (unless you are worried about your file descriptor limit and can not increase it). And you shouldn't need PROTON_NO_D3D11=1 (unless you know Vulkan or DXVK will not work).

If you're using one of my custom builds then the CRC workaround isn't required.

The error you're seeing occurs when vcrun2015 (or vcrun2017) is not installed. If you are using '3.16-5 Beta ED' and you ran ./fixED.sh - then it should have installed dotnet40 and vcrun2015 when you first ran Elite.

If that didn't work (or you're using '3.16-4 Beta ED') - then you'll need to install it manually (with protontricks or winetricks).

 

[Junagu]

You shouldn't need PROTON_NO_ESYNC=1 (unless you are worried about your file descriptor limit and can not increase it). And you shouldn't need PROTON_NO_D3D11=1 (unless you know Vulkan or DXVK will not work).

If you're using one of my custom builds then the CRC workaround isn't required.

The error you're seeing occurs when vcrun2015 (or vcrun2017) is not installed. If you are using '3.16-5 Beta ED' and you ran ./fixED.sh - then it should have installed dotnet40 and vcrun2015 when you first ran Elite.

If that didn't work (or you're using '3.16-4 Beta ED') - then you'll need to install it manually (with protontricks or winetricks).

That, as they say, was the ticket.



Thank you very much [yesnod][yesnod][yesnod]

EDIT: yes, everything works fine and it's looking really good too.

2ndEDIT: now how to run it in fullscreen..:S

 

[RedMcG]

2ndEDIT: now how to run it in fullscreen..:S

Under your wine prefix for Elite - do a 'find -name DisplaySettings.xml' - you should find a file here:
.../users/steamuser/Local Settings/Application Data/Frontier Developments/Elite Dangerous/Options/Graphics/DisplaySettings.xml

Change the FullScreen setting to '1'; for example:
'<FullScreen>1</FullScreen>'

But I've had trouble with that before - I'll add it to my Troubleshooting list - along with the 'Make sure you start the game from the launcher so that you are up to date'. Let me know if there was anything else missing that would have helped you.

 

[Noobilite]

If you change the fullscreen to 1 manually, do it when the launcher is not up. If the launcher is up it auto detects it and sets it back to some defaults. If any of the ED software is up it may default to default settings and get rid of your changes before you can use them to get in game to do anything to permanently change them.

Used to have this problem when testing before this started playing well and had to get it to windowed for quicker testing/exiting/restarting.

FYI, if you want windowed mode you have to put 'false' instead of '0' as it won't accept it. Oddly 1 makes it full screen. I think true might work also. I wonder if that is for borderless vs fullscreen.

 

[Flyinspaghetti]

Two things today:

First I've discovered that removing the stock presets in the Control Schemes folder stops my keyboard/joystick locking up every other boot of the game. I've noticed this before when trying to use my custom Windows preset, however stock presets weren't an issue up until 3.3.

Secondly Terrain bug is still in the latest released Nvidia driver 415.25, I've created a thread on the Nvidia Unix forum and I'd ask for anyone here even if you are happy with older branches to give your feedback on the 415 branch of drivers on either the Nvidia Unix board or the DXVK github thread if you can.

https://devtalk.nvidia.com/default/...rendering-issues-in-415-branch-up-to-415-25-/

https://github.com/doitsujin/dxvk/issues/267

 

[Junagu]

Two things today:

First I've discovered that removing the stock presets in the Control Schemes folder stops my keyboard/joystick locking up every other boot of the game. I've noticed this before when trying to use my custom Windows preset, however stock presets weren't an issue up until 3.3.

I've been having issues with keyboard too - sometimes it's completely unresponsive once the launcher has started the game and when it does work it can easily drop out again.

Got the Fullscreen working just fine as per suggestion, though.[up]

 

[Jack Winter]

First I've discovered that removing the stock presets in the Control Schemes folder stops my keyboard/joystick locking up every other boot of the game. I've noticed this before when trying to use my custom Windows preset, however stock presets weren't an issue up until 3.3.

How do you do that? For me it's been close to unplayable after 3.3 came out, as I mostly start with no working keyboard or hotas. Faffing around I can normally get it up and running again at some point, but sometimes it takes so many retries and so much time that I've lost the incentive to play...

 

[Flyinspaghetti]

How do you do that? For me it's been close to unplayable after 3.3 came out, as I mostly start with no working keyboard or hotas. Faffing around I can normally get it up and running again at some point, but sometimes it takes so many retries and so much time that I've lost the incentive to play...

You need to remove the .binds files in the Control Schemes folder in the game directory, I suspect some of them may be conflicting which causes everything to lock up entirely. Removing them then starting a lone custom preset from scratch is probably best, I haven't had mine lock up since doing that.

 

[Oswald-p]

I finally managed to run ED so thank you very much for your help Mr flyingspagetti.
I am though limited to windows mode only. When I try to go to full screen 1080p it goes back to window mode. It seems to work well at 720p (full screen).
I am thinking that the game may check my config judging it cannot properly run the game at 1080p.
Does any body had the same experience?

My config (8 years old with some updates):
AMD phenomII black edition (running at 80% during the game)
Nvidia GTX 750Ti 2GB
8gb ram
ubuntu 18.04
Latest mesa + 396 nvidia driver series (idem with the 410 series)
The game is running at 60 fps on the menus and 30 fps in space (first tutorial).

I was thinking building a new config with a ryzen 7 1700 and a nvidia GTX1050 Ti next year. Would it worth it?

By all.

O-p

 

[Jack Winter]

You need to remove the .binds files in the Control Schemes folder in the game directory, I suspect some of them may be conflicting which causes everything to lock up entirely. Removing them then starting a lone custom preset from scratch is probably best, I haven't had mine lock up since doing that.

You are my hero at the moment!

I finally found the folder. Moved all the .binds files into a subdir, except for KeyboardMouseOnly.binds & SaitekX52Pro.binds, that combined with my custom binds seems to have fixed it, so far no problems starting the program.

 

[Maverick Togenada]

vcrun2017

I'm back on my laptop trying to install vcrun2017 so I can play ED. I get this error:

"Note: command wine VC_redist.x86.exe returned status 5. Aborting."

Here is the full log: https://pastebin.com/Migp1d6u

The game will not start when I click "play" in the launcher. Nothing happens. It was working before the update. I am assuming the inability to install vcrun2015 or vcrun2017 is the problem.

 

[RedMcG]

I'm back on my laptop trying to install vcrun2017 so I can play ED. I get this error:

"Note: command wine VC_redist.x86.exe returned status 5. Aborting."

Here is the full log: https://pastebin.com/Migp1d6u

The game will not start when I click "play" in the launcher. Nothing happens. It was working before the update. I am assuming the inability to install vcrun2015 or vcrun2017 is the problem.

The only error I can see is in regard to the missing libpng12.so.0 library. So you may want to address that.

But I can also see you are using a Steam prefix. If you're using '3.16-5 Beta ED' then you shouldn't need to manually install anything once you have ran the './fixED.sh' script. Are you having a problem with that approach?

 

[Maverick Togenada]

The only error I can see is in regard to the missing libpng12.so.0 library. So you may want to address that.

But I can also see you are using a Steam prefix. If you're using '3.16-5 Beta ED' then you shouldn't need to manually install anything once you have ran the './fixED.sh' script. Are you having a problem with that approach?

I fixed the libpng error by putting libpng12.so.0 from elsewhere into /lib/i386-linux-gnu.

dotnet40 and vcrun2017 are now installed.

With 3.16-5 Beta ED, I get this error: "line 576, in run if "legacycompat\evaluatorscript_" in sys.argv[3]: IndexError: list index out of range".

With 3.16-4 Beta ED, I see this in terminal when running EliteDangerous64.exe: https://pastebin.com/pSD3NeKr

I can see in terminal with top command that the exe is running, but the game never appears. This behavior is the same running from Steam or from the terminal.

 

[RedMcG]

I fixed the libpng error by putting libpng12.so.0 from elsewhere into /lib/i386-linux-gnu.

dotnet40 and vcrun2017 are now installed.

With 3.16-5 Beta ED, I get this error: "line 576, in run if "legacycompat\evaluatorscript_" in sys.argv[3]: IndexError: list index out of range".

With 3.16-4 Beta ED, I see this in terminal when running EliteDangerous64.exe: https://pastebin.com/pSD3NeKr

I can see in terminal with top command that the exe is running, but the game never appears. This behavior is the same running from Steam or from the terminal.

For 3.16-5 Beta ED - that's a bug in my script. That second if statement at line 576 should be indented to run only if the previous one is true.

For 3.16-4 Beta ED - it looks like a shader compilation issue.

You could try installing DXVK 0.94 on 3.16-4 Beta ED. You can do that with 'winetricks dxvk'. If that doesn't help, you might want to share what graphics card and driver version you are using. But make sure you are meeting the Proton Graphics Drivers Requirements.