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

Does anyone know where are located the screenshots taken with ALT+F10 ? [smile]

Looks like they go under 'My Pictures' of your prefix. For example:
Code:
~/.steam/steam/steamapps/compatdata/359320/pfx/drive_c/users/steamuser/My Pictures/Frontier Developments/Elite Dangerous
 
I noticed your github mentions updating these and I apologize I overlooked that before.

I only added the bit about winetricks after reading your comment. And the bit about wine was only added recently too - so might not have been there when you looked.

So, now the launcher starts, but the game does not start and I think this probably has something to do with Vulkan. I've been researching and it looks like my APU might not support Vulkan because the only proprietary driver available for me is Crimson Edition 15.12 Proprietary Ubuntu 14.04 and AMD says only "Vulkan™-compatible components AMD Radeon Software Crimson Edition 16.3 and later..." support Vulkan. I am using the open source radeon drivers in Debian 9.

Here is a paste of the output log while the game is trying to run after clicking "play" in the launcher. This is at least 30 minutes after clicking the "play" button.
https://pastebin.com/rnwZgyP1.

I've never owned a Radeon card before - so I can't help in terms of driver support. But I do know you can launch the game without Vulkan (and use OpenGL instead). In user_settings.py (which will be where you extracted the custom Proton), find the following lines:
Code:
    #Use gl-based wined3d for d3d11 and d3d10 instead of vulkan-based dxvk
#    "PROTON_USE_WINED3D": "1",

and uncomment the PROTON_USE_WINED3D line. It should result in the use of the built-in Wine libraries which provide OpenGL support.

Edit: I forgot to mention that I couldn't see anything in your logs. It looks like the ED client might have frozen as what was in the log seems to all be from the Launcher. If you grep your log for VK - this will show most (all?) of the DXVK entries. When I ran in to problems with Vulkan - it had a message about required Vulkan extensions not being supported. I think it was: "Required Vulkan extension VK_KHR_xcb_surface not supported"
 
Last edited:
There are some issues with planet generation when run through wine (I'm running the standalone game from Frontier's store). I've particularly had issues at engineer bases (I couldn't land at one of them because it was entirely encased in rock), while another was just floating in mid-air.

(this is at the engineer base in Eurybia)

Possibly some floating point weirdness?

Edit: The engineer base I couldn't access was in Laksak.

I haven't noticed anything wrong with any of the engineers I've visited, but I've not gotten to that one yet.
 
I only added the bit about winetricks after reading your comment. And the bit about wine was only added recently too - so might not have been there when you looked.



I've never owned a Radeon card before - so I can't help in terms of driver support. But I do know you can launch the game without Vulkan (and use OpenGL instead). In user_settings.py (which will be where you extracted the custom Proton), find the following lines:
Code:
    #Use gl-based wined3d for d3d11 and d3d10 instead of vulkan-based dxvk
#    "PROTON_USE_WINED3D": "1",

and uncomment the PROTON_USE_WINED3D line. It should result in the use of the built-in Wine libraries which provide OpenGL support.

Edit: I forgot to mention that I couldn't see anything in your logs. It looks like the ED client might have frozen as what was in the log seems to all be from the Launcher. If you grep your log for VK - this will show most (all?) of the DXVK entries. When I ran in to problems with Vulkan - it had a message about required Vulkan extensions not being supported. I think it was: "Required Vulkan extension VK_KHR_xcb_surface not supported"
I found a method for getting Vulkan support on older AMD GCN cards on Mint 19 here: https://forums.linuxmint.com/viewtopic.php?t=272283. I tried to apply this to Debian 9 but did not have any luck with that, so I installed Mint 19 with the amdgpu driver, wine-staging and the latest version of winetricks, increased the file descriptor limit, installed the custom proton beta for ED and dotnet40, and finally the game started up! Unfortunately, the planet generation process at startup takes about an hour to complete, sometimes causing ED to open the crash report window and leaving just a black screen in the client window. Once the game was running, the framerate was very low with spikes that completely stop everything and make it hard to even exit and shutdown the game. I tried disabling vulkan and using opengl instead but the startup process was just as problematic so I didn't make it through the planet generation before calling it a day.
 
I haven't noticed anything wrong with any of the engineers I've visited, but I've not gotten to that one yet.

I can confirm Laksak is bugged:

dpmRrRv.png
 
I think that can be fixed with a few well placed seismic charges

Weird but I'm sure I visited Traders Rest in Linux before... and this is happening in both steam proton and lutris.

Tried older DXVK same issue, a driver downgrade as I recently upgraded to 415.18.04, see if going back to 396.54.09 has any difference.
 
Update: That solved it!!

415 branch of nvidia drivers appears to have the issue, going back to 396 solved it (don't know about 410 although I personally need transform feedback for TW3 & other games).

Screenies below in spoiler:

hWbIr5m.png
ZKicEUe.png

The best place to report this would be the nvidia thread on the DXVK github as a nvidia dev frequents there:

https://github.com/doitsujin/dxvk/issues/267
 
Unfortunately, the planet generation process at startup takes about an hour to complete, sometimes causing ED to open the crash report window and leaving just a black screen in the client window. Once the game was running, the framerate was very low with spikes that completely stop everything and make it hard to even exit and shutdown the game. I tried disabling vulkan and using opengl instead but the startup process was just as problematic so I didn't make it through the planet generation before calling it a day.

OK - I haven't seen that personally so it might be related to AMD cards. I did see a person post over on ProtonDB that they "Needed dxvk >= 0.92 to work around AMD shader problems for Horizons.". To install the latest version of dxvk - you can use winetricks again:
Code:
WINEPREFIX="~/.steam/steam/steamapps/compatdata/359320/pfx" winetricks dxvk
 
Update: That solved it!!

415 branch of nvidia drivers appears to have the issue, going back to 396 solved it (don't know about 410 although I personally need transform feedback for TW3 & other games).

Screenies below in spoiler:


The best place to report this would be the nvidia thread on the DXVK github as a nvidia dev frequents there:

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

Excellent work! Would it be worth noting in any bug report if OpenGL has the same issue?
 
Update: That solved it!!

415 branch of nvidia drivers appears to have the issue, going back to 396 solved it (don't know about 410 although I personally need transform feedback for TW3 & other games).

Screenies below in spoiler:


The best place to report this would be the nvidia thread on the DXVK github as a nvidia dev frequents there:

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

That puts paid to the plan I had of upgrading to 415.22 then. Things have been working great here in 396-land. Ain't broke, so no need to fix it. Not even going to try wine 4 rc1 for the time being, either. ;)
 
Update: That solved it!!

415 branch of nvidia drivers appears to have the issue, going back to 396 solved it (don't know about 410 although I personally need transform feedback for TW3 & other games).

Screenies below in spoiler:



The best place to report this would be the nvidia thread on the DXVK github as a nvidia dev frequents there:

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

Thanks for confirming that - I was indeed running the 415.22 driver. I have no use for that specific VK feature, and the only reason I upgraded from an earlier 415 was because the driver had a regression introduced where Windows Unity games run through Proton would fail to launch. I suppose I'll downgrade to 396, then.
 
I found a method for getting Vulkan support on older AMD GCN cards on Mint 19 here: https://forums.linuxmint.com/viewtopic.php?t=272283. I tried to apply this to Debian 9 but did not have any luck with that, so I installed Mint 19 with the amdgpu driver, wine-staging and the latest version of winetricks, increased the file descriptor limit, installed the custom proton beta for ED and dotnet40, and finally the game started up! Unfortunately, the planet generation process at startup takes about an hour to complete, sometimes causing ED to open the crash report window and leaving just a black screen in the client window. Once the game was running, the framerate was very low with spikes that completely stop everything and make it hard to even exit and shutdown the game. I tried disabling vulkan and using opengl instead but the startup process was just as problematic so I didn't make it through the planet generation before calling it a day.

The memory requirements for ED and DXVK are quite punishing. If you're using an older AMD card, you may well just be out of luck. I have a GTX960 with 2GB of RAM, and it chugs at times with ED and DXVK - I think I'm probably near the trailing edge of setups where this is going to be playable. Something from a couple of generations prior is likely to struggle greatly. Sadly, Linux isn't going to make it better than your Windows experience.
 
I use 410.78 nvidia drivers and I don't get any odd visual things that I have noticed. And It uses about the entire 3gb of my 10603gb to play elite dangerous with dxvk. I get around 60-120 fps with medium settings. And around 40-60 at high. I think maybe 24-40 in ultra or a bit better(up to 60fps) if I make sure to set shadow quality down. The only reason I play on medium instead of ultra is because I run background things like firefox for looking up things and if I play vidoes on youtube while playing elite it hickups. But it's very smooth at medium settings. And playable at ultra if you turn down shadows and don't do anything besides play elite. The only thing I need to adjust at ultra is the shadow quality. And I can even turn up the bar on how hard the gpu is working to max.

I'm hoping that is still the case after the patch. Big updates tend to break games for me. Hopefully not permanently.
 
Last edited:
I use 410.78 nvidia drivers and I don't get any odd visual things that I have noticed.

Have you tried at the Traders Rest engineer base in Laksak with 410? Be good to know if that specific location isn't buried under terrain so we can pinpoint which driver has the regression.

Edit: Tested a few drivers myself.

All 415 drivers I tried had the issue where as 410.78 doesn't.

So if you don't care about transform feedback 410.78 should be fine, if however you need that for other games then 396.54.09 developer beta driver is still required.
 
Last edited:
Hi !

So I played Elite this weekend (on route to Colonia) and everything was working nicely.

I've tried to run it (Elite Horizons)this evening and I got this error message :

80daa1194612ef7ec4fd58a88520c5b578bf9989.jpg


And the launcher doesn't start.

If I launch Elite Dangerous, the launcher appear, I login and the same error message appear. The system clock is working fine and I've verified the game files integrity in steam

Any idea ?
 
In answer to my post #516, Wine 4.0rc1-1 may be the culprit. There's other games that are broken too.

My drivers : nvidia-vulkan 415.18.04-1
 
The memory requirements for ED and DXVK are quite punishing. If you're using an older AMD card, you may well just be out of luck. I have a GTX960 with 2GB of RAM, and it chugs at times with ED and DXVK - I think I'm probably near the trailing edge of setups where this is going to be playable. Something from a couple of generations prior is likely to struggle greatly. Sadly, Linux isn't going to make it better than your Windows experience.

In Windows, i get 30 to 50 fps with Horizons, landing on planets and everything.
In Linux, i'm getting a steady 30 fps without Horizons.
In Linux with Horizons, i'm getting 0 to 30 fps with lots of stuttering and freezing especially if I go near a planet.
The game is only playable in Linux for me without Horizons. If I try to land on a planet, I get stuck in the 2 fps range and have to exit the game.

I updated dxvk as RedMcG suggested in his last comment to me. The only change I noticed was that the planet generation at startup made it to about 20% then just suddenly completed and went to the menu, which means it took less time to complete.

I would like to think there is something wrong that can be fixed to improve the performance rather than it being an unavoidable consequence of using proton, dxvk, wine, etc. to run ED in Linux. It seems that there is something specifically related to Horizons and planets that is not working correctly in Linux considering the drastic difference in performance from Windows.

Here it is running without Horizons:
330QMZJ
 
There is something floating around about a new updater. We will need to install it to play. You are prompted when starting the launcher to download it. Just came out.

I got it installed and ran it once and so far I got a thing saying to start with the launcher. It was started with the launcher. So, I will try again and see if it works the second time. This happened some time into the planet generation thing.(which is a bit slow for me now and prior to the new launcher.) Did anyone else get this?

uCR0JbZ.png


My spidey sense is saying there is an incredibly stupid and simple solution to this problem.
 
Last edited:
There is something floating around about a new updater. We will need to install it to play. You are prompted when starting the launcher to download it. Just came out.

I got it installed and ran it once and so far I got a thing saying to start with the launcher. It was started with the launcher. So, I will try again and see if it works the second time. This happened some time into the planet generation thing.(which is a bit slow for me now and prior to the new launcher.) Did anyone else get this?

A new ED client/launcher needs to be installed for the incoming update. This is achieved by downloading the ClientInstaller.exe and running it like you did when you were first setting up your wine prefix. When you run the current launcher it says you need to download a new one and do you want to download it now - click on Yes and your default web browser should launch with the download link, which you then save as ClientInstaller.exe

After that it's just running EDLaunch.exe as per usual. I just performed this operation and the launcher works as before.
 
Last edited:
Back
Top Bottom