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

[Flyinspaghetti]

After battling the normal .NET rubbish I finally got the launcher to run.
If I try and run Horizons I get to the generating planet bit ( after the shaders ) then it maxes out my laptop for 5-10mins until I reboot ( because machine is completely unresponsive, including ctrl-alt-f1 for console or ctrl-alt-esc to kill the program or ctrl-alt-del ).
If I try and run non-Horizons I get the video and music but then it crashes, sometimes it doesn't crash and I get a little further, even to the menu, but it's unresponsive.

I did the VC2017 update.
and I'm set to Windows 7.
kubuntu 18.04
wine 4.0rc1
nvidia 390.87 ( GTX 1050TI - it's a gaming laptop )

I'll keep fighting with it tomorrow for a bit - it's 2am now
Not helped by the fact it looks like the servers are still having issues, not that I've got close to actually connecting to one yet.

You need two things, first a driver version that is 396 or above but avoid the latest 415 driver as it has a nasty terrain bug.

Second is if you haven't already you need to install dxvk, which can be easily done by winetricks.

 

[RedMcG]

If they did - I wonder if they forgot to update their Steam depots. I only see 'VC 2012 Redist' there.

It looks like this could be the case. I went over to Windows and uninstalled VC 2015 (I didn't have VC 2017 installed) and ED wouldn't launch (pressing the Launch button caused the client to start briefly in the background before silently exiting). After reinstalling VC 2015 it worked.

I just helped out a couple of Windows users who ran in to this problem. When they asked how I worked it out - I told them it was with Linux.

 

[RedMcG]

FYI - there was already a bug for this - so I added my 2 cents:

Can confirm VC 2015 or higher is required (MSVCP140.DLL was only added in 2015). The Steam Depot for ED only has 2012 (thus validating game files won't work). If this can be fixed, it could also be worth adding the .NET 4.0 Client Profile (which is required by the launcher).

I'm pushing the Proton agenda. If we can get both dotnet40 and vcrun2015 in the ED depot - then I think it should just be click and play.

 

[JaskoMaughann]

Repped and subscribed...you're doing good work

 

[Cmdr Eagleboy]

If they did - I wonder if they forgot to update their Steam depots. I only see 'VC 2012 Redist' there.

Hopefully you tipped Frontier Support here

 

[Michael Arthur Long]

Anyone else having a problem with their joystick? It keeps thinking my Extreme 3D Pro is an xinput controller.

Tried a new prefix, wine 3.21, staging-4.0rc1 and even the patched staging 3.18 version posted here a few pages back. Same result.

 

[alejandor]

Count a +1 on fixing the login with wcrun2017. Thanks a lot!

 

[Cmdr Ricey]

I've just moved my OS to Mint 19.1 Beta!! I know

and I've popped wine 4.0rc1 on here and the game freezes during the intro video - as a side I didn't need vcrun2017, but I've installed it as well now and the launcher is still fine! (wine64 command)

similar to where danteuk's laptop freezes completely, mine just stops and eventually comes up with the FDev crash report tool.

What do you need from me to help solve this??

Cheers

 

[RedMcG]

Anyone else having a problem with their joystick? It keeps thinking my Extreme 3D Pro is an xinput controller.

Tried a new prefix, wine 3.21, staging-4.0rc1 and even the patched staging 3.18 version posted here a few pages back. Same result.

I use a controller but had to dig around that code to fix a bug. I would try disabling SDL under wine bus. It can be done via registry setting:
https://wiki.winehq.org/Useful_Registry_Keys

Right down the bottom is the key you're interested in (it's called 'Enable SDL'). The following command should do the trick:

wine64 reg add 'HKLM\System\CurrentControlSet\Services\WineBus' /v 'Enable SDL' /t REG_DWORD /d 0 /f

There's also another undocumented registry entry which may also do the trick (it's a bit more specific than the one above - so it would be useful in isolating the issue to know if it helps):

wine64 reg add 'HKLM\System\CurrentControlSet\Services\WineBus' /v 'Map Controllers' /t REG_DWORD /d 0 /f

 

[RedMcG]

I've just moved my OS to Mint 19.1 Beta!! I know

and I've popped wine 4.0rc1 on here and the game freezes during the intro video - as a side I didn't need vcrun2017, but I've installed it as well now and the launcher is still fine! (wine64 command)

similar to where danteuk's laptop freezes completely, mine just stops and eventually comes up with the FDev crash report tool.

What do you need from me to help solve this??

Cheers

Are you using staging? This sounds like the behaviour when the futex patch is missing (which is only in staging... for now).

 

[Cmdr Ricey]

I'm using this from the winehq repo:

$ dpkg -l | grep wine
ii  wine-devel                                 4.0~rc1~bionic                              amd64        WINE Is Not An Emulator - runs MS Windows programs
ii  wine-devel-amd64                           4.0~rc1~bionic                              amd64        WINE Is Not An Emulator - runs MS Windows programs
ii  wine-devel-i386:i386                       4.0~rc1~bionic                              i386         WINE Is Not An Emulator - runs MS Windows programs
ii  winehq-devel                               4.0~rc1~bionic                              amd64        WINE Is Not An Emulator - runs MS Windows programs

$ wine64 --version
wine-4.0-rc1

???

from the term output there are lots and lots and lots of these:

0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0
0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0

and these

0039:fixme:win:EnumDisplayDevicesW ((null),0,0x1efef560,0x00000000), stub!
0039:fixme:win:EnumDisplayDevicesW ((null),0,0x1efef7e0,0x00000000), stub!
0039:fixme:win:EnumDisplayDevicesW ((null),1,0x1efef7e0,0x00000000), stub!
0039:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x1e02ef78, (nil)) stub!
0039:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x1e02efa0, (nil)) stub!
0039:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x1e02efc8, (nil)) stub!
0039:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x1e02eff0, (nil)) stub!
0039:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x1e02f018, (nil)) stub!
0039:fixme:win:EnumDisplayDevicesW ((null),0,0x1efef560,0x00000000), stub!
0039:fixme:win:EnumDisplayDevicesW ((null),0,0x1efef7e0,0x00000000), stub!
0039:fixme:win:EnumDisplayDevicesW ((null),1,0x1efef7e0,0x00000000), stub!
0039:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x1e02f040, (nil)) stub!
0039:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x1e02f068, (nil)) stub!
0039:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x1e02f090, (nil)) stub!
0039:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x1e02f0b8, (nil)) stub!
0039:fixme:seh:RtlCaptureStackBackTrace (1, 3, 0x1e02f0e0, (nil)) stub!
0039:fixme:win:EnumDisplayDevicesW ((null),0,0x1efef560,0x00000000), stub!
0039:fixme:win:EnumDisplayDevicesW ((null),0,0x1efef7e0,0x00000000), stub!
0039:fixme:win:EnumDisplayDevicesW ((null),1,0x1efef7e0,0x00000000), stub!

?????

 

[LaVolte]

Sorry to bother, but how did you install vcrun2017, I've tried protontricks 359320 vcrun2017 but it didn't install anything.

It did return a strange line : ~/steam/steamapps/common/Proton 3.16 Beta/dist/bin/wine cmd.exe /c echo '%ProgramFiles%' returned empty string, error message ""

I feel like something missing in the Proton install folder.

I can only run the demo (Elite tutorials) witch runs perfectly either with Proton 3.16-4 ED or 3.16-5 Beta.

Still getting those errors :

Elite Dangerous Launcher

Elite Horizons Launcher

Steam is updated, wine-staging 4.0rc1-1 is installed, with latest nvidia-vulkan, vkd3d, dxvk-win64, and protontricks.

Any ideas ?

 

[Flyinspaghetti]

Sorry to bother, but how did you install vcrun2017, I've tried protontricks 359320 vcrun2017 but it didn't install anything.

It did return a strange line : ~/steam/steamapps/common/Proton 3.16 Beta/dist/bin/wine cmd.exe /c echo '%ProgramFiles%' returned empty string, error message ""

I feel like something missing in the Proton install folder.

I can only run the demo (Elite tutorials) witch runs perfectly either with Proton 3.16-4 ED or 3.16-5 Beta.

Still getting those errors :

Elite Dangerous Launcher



Elite Horizons Launcher



Steam is updated, wine-staging 4.0rc1-1 is installed, with latest nvidia-vulkan, vkd3d, dxvk-win64, and protontricks.

Any ideas ?

Have you installed lib32-gnutls?

 

[LaVolte]

Yes, I have this version : lib32-gnutls v3.5.19-2

 

[Cmdr Ricey]

I'm not using steam/proton yet - i just used winetricks

env DXVK_HUD=fps WINEPREFIX="<prefix path>" WINEARCH=win64 winetricks vcrun2017

 

[Michael Arthur Long]

I use a controller but had to dig around that code to fix a bug. I would try disabling SDL under wine bus. It can be done via registry setting:
https://wiki.winehq.org/Useful_Registry_Keys

Right down the bottom is the key you're interested in (it's called 'Enable SDL'). The following command should do the trick:

wine64 reg add 'HKLM\System\CurrentControlSet\Services\WineBus' /v 'Enable SDL' /t REG_DWORD /d 0 /f

There's also another undocumented registry entry which may also do the trick (it's a bit more specific than the one above - so it would be useful in isolating the issue to know if it helps):

wine64 reg add 'HKLM\System\CurrentControlSet\Services\WineBus' /v 'Map Controllers' /t REG_DWORD /d 0 /f

Forgot to mention earlier that I tried Single Player Combat Training and the same thing happened.

First registry key stops it from being detected as an Xbox controller and now it's not detected at all. Second key seems to have done nothing. It does show up on joy.cpl though.

 

[LaVolte]

I've installed vcrun2017 with this WINEPREFIX : steamapps/compatdata/359320/pfx/, but I still get the same errors. Maybe my proton or wine installation was broken during packages updates.

 

[Flyinspaghetti]

I've installed vcrun2017 with this WINEPREFIX : steamapps/compatdata/359320/pfx/, but I still get the same errors. Maybe my proton or wine installation was broken during packages updates.

Try backing up and deleting your steam runtime (and other associated files) from ~.local/share/Steam/ubuntu12_32 .

Also make sure you are not running steam beta but the stable client.

 

[RedMcG]

I'm using this from the winehq repo:

$ dpkg -l | grep wine
ii  wine-devel                                 4.0~rc1~bionic                              amd64        WINE Is Not An Emulator - runs MS Windows programs
ii  wine-devel-amd64                           4.0~rc1~bionic                              amd64        WINE Is Not An Emulator - runs MS Windows programs
ii  wine-devel-i386:i386                       4.0~rc1~bionic                              i386         WINE Is Not An Emulator - runs MS Windows programs
ii  winehq-devel                               4.0~rc1~bionic                              amd64        WINE Is Not An Emulator - runs MS Windows programs

$ wine64 --version
wine-4.0-rc1

???

from the term output there are lots and lots and lots of these:

0093:fixme:nls:NormalizeString 1 0x554bef38 -1 (nil) 0

?????

Yeah - that's wine-devel. Both the futex patch and NormalizeString patchset are only in wine-staging. Try:

sudo apt install winehq-staging

 

[RedMcG]

Yes, I have this version : lib32-gnutls v3.5.19-2

Looks like there is a bug with Wine and gnutls v3.5.19:
https://bugs.winehq.org/show_bug.cgi?id=46161

It's fixed in 4.0-rc1 - but it won't be in my Proton build.

Looks like there's also a fix in gnutls v3.6:
https://gitlab.com/gnutls/gnutls/issues/621

So options are:
- downgrade (upgrade?) gnutls;
- use wine version 4.0-rc1 (and ditch Proton); or
- wait for me to make another custom Proton build (the wine fix easily applies)

Edit: There's also the possibility that your distro has applied the gnutls 3.6 fix to v3.5.19-2 and the error you are seeing is unrelated. You could add GNUTLS_DEBUG_LEVEL=2 and check for:

gnutls[2]: Advertizing version 3.4
gnutls[2]: Advertizing version 3.1

to be 100% sure.