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

Grimloch

G
CMDR Ialdabaoth said:
There's one thing that makes Odyssey totally unplayable for me under Proton (tried all latest versions, including GE, from 5.0 - 6.5). If I open and close the Galaxy or System map while staying on the station, I get 1-2 FPS at max after this. The only way to fix this is to restart the game completely. I don't have Windows installed to check how the game works there (and don't plan to install it just for it). It drives me crazy because overall the game is playable, and only the map bug breaks the whole experience. :c

My system specs:
Single monitor (2560x1440)
GeForce GTX 1060 6 gb
Ryzen 5 1600
16 gb RAM

Does anyone have the same problem?
Click to expand...
Experiencing this as well on the latest proton.

I've found a sort of work around for this. Switch to System map, let it load and switch back to cockpit view. Might take 2 or 3 tries but it usually switches back to my normal fps afterwards and is way better than having to restart the game every time.

Still would be interesting to see if this is a proton only issue.
 

Genar-Hofoen

Genar-Hofoen
Grimloch said:
Experiencing this as well on the latest proton.

I've found a sort of work around for this. Switch to System map, let it load and switch back to cockpit view. Might take 2 or 3 tries but it usually switches back to my normal fps afterwards and is way better than having to restart the game every time.

Still would be interesting to see if this is a proton only issue.
Click to expand...

It's not just a Proton thing - it's a WINE thing. Proton being a patched version of WINE anyway.

I run EDO/EDH under WINE and experience the exact same issue with FPS - for me though it's going into the System Map which eventually fries the FPS - seems to be a combination of factors though - notably being on-foot, then viewing the system map.

Running mangohud shows me that VRAM very quickly gets filled up, and after going into the system map and exiting it the GPU is then stuck at 100%, which is when the FPS plummets to slideshow mode.

Other threads and youtubers have pointed out that in EDO no occlusion culling is being performed like it is in EDH, this is also another big factor.

In summary;
  • No occlusion culling means an order of magnitude more work for the GPU
  • The above is probably contributing to VRAM very quickly being eaten up
  • Texture loading in the system map may also be contributing to VRAM nomming
  • There might also be some bit of System Map code which is not stopping whatever work its doing, even after the System Map is closed, which could also be eating up GPU usage and VRAM

I'm going to wait for a bit for FDEV to sort EDO out before continuing to play, and also before I start doing any work on Captain's Log.

o7
 

RedMcG

R
cpw said:
Confirming that using 6.99 of winemono I was able to run odyssey under proton with no further tweaking necessary. Looks amazing and decent FPS too!
Click to expand...
A new official release of wine-mono was made this morning; version 6.2.0. This runs the launcher.

When testing with the latest commit of wine, I also noticed corefonts is no longer needed. So once they make 6.2.0 the default wine-mono version for wine, then you will be able to run Elite Dangerous without any winetricks or wine-mono installs (although DXVK would still be recommened).
 

alexzk

A
RedMcG said:
A new official release of wine-mono was made this morning; version 6.2.0. This runs the launcher.

When testing with the latest commit of wine, I also noticed corefonts is no longer needed. So once they make 6.2.0 the default wine-mono version for wine, then you will be able to run Elite Dangerous without any winetricks or wine-mono installs (although DXVK would still be recommened).
Click to expand...
or this one and no mono needed at all:
github.com

GitHub - rfvgyhn/min-ed-launcher: Minimal Elite Dangerous Launcher

Minimal Elite Dangerous Launcher. Contribute to rfvgyhn/min-ed-launcher development by creating an account on GitHub.
github.com github.com
...however, last time I tried it tried to go in separated own prefix. Any way only launcher needs mono, so no big deal which to use. It's closed once game started.
 

Darth Ender

D
With latest odyssey patch, i'm getting an unhandled page fault when trying to run the game in the latest version of proton. Anyone else?

It updated the game, but since then it wont even verify files without page faulting and crashing.

edit: nevermind, momentary glitch it seems .. clicked on horizons (but didn't launch) then back to odyssey and now it launches without error.
 
Last edited:

RedMcG

R
FYI - (although I suspect anyone following already knows) Proton version 6.3-6 now runs Elite Dangerous out of the box. No manual steps (apart from enabling Proton for all titles) or modification required.
 

alexzk

A
RedMcG said:
FYI - (although I suspect anyone following already knows) Proton version 6.3-6 now runs Elite Dangerous out of the box. No manual steps (apart from enabling Proton for all titles) or modification required.
Click to expand...
It does not handle symlinks it seems right now, this is new bug in 6.3-6, was ok in -5
github.com

Errno 22 Invalid argument with vrclient.dll and proton 6.3-6 · Issue #5102 · ValveSoftware/Proton

Compatibility Report Name of the game with compatibility issues: Rocket League... Steam AppID of the game: 252950... System Information GPU: NVIDIA GeForce GTX 1060 6GB Driver/LLVM version: nvidia ...
github.com github.com
 

Flyinspaghetti

Flyinspaghetti
RedMcG said:
FYI - (although I suspect anyone following already knows) Proton version 6.3-6 now runs Elite Dangerous out of the box. No manual steps (apart from enabling Proton for all titles) or modification required.
Click to expand...

There is a hang on shutdown and changes to the prefix such as accidently selecting wrong Proton version might bork it causing you to start over with a new one.

Game runs great (but like windows with same fps issues in concourse and base areas) on a 6600XT, shame though I'm having issues with video capture in Linux on the Radeon card for some reason.

Unsure of Nvidia performance, sold my 1070 for two thirds of what I paid for the 6600XT, crazy market.
 

RedMcG

R
Flyinspaghetti said:
There is a hang on shutdown and changes to the prefix such as accidently selecting wrong Proton version might bork it causing you to start over with a new one.
Click to expand...
There is a fix for the hang, but it didn't make it in to wine-mono 6.3.0 unfortunately (but should be in the next version).

Not 100% sure, but I think Wine's ongoing conversion to PE DLLs is the reason prefixes aren't compatible when moving from one version to the next. I think they have the 'proton' Python script try to upgrade existing prefixes, but not sure about downgrades
 

Crimson Echo

Crimson Echo
Flyinspaghetti said:
There is a hang on shutdown and changes to the prefix such as accidently selecting wrong Proton version might bork it causing you to start over with a new one.

Game runs great (but like windows with same fps issues in concourse and base areas) on a 6600XT, shame though I'm having issues with video capture in Linux on the Radeon card for some reason.

Unsure of Nvidia performance, sold my 1070 for two thirds of what I paid for the 6600XT, crazy market.
Click to expand...
Similar on Nvidia cards. Throws an .net related error on starting the launcher, and the launcher does not close correctly. (has to be killed manually). Performance is similar to windows also.
 
Last edited:

alexzk

A
Crimson Echo said:
Similar on Nvidia cards. Throws an .net related error on starting the launcher, and the launcher does not close correctly. (has to be killed manually). Performance is similar to windows also. The performance issues with quickly opening and closing the galaxy map or system map in ED:O appears to be fixed when using an empty prefix with proton experimental.
Click to expand...
That is problem of many game, I have bash script bound to ctrl+alt+shift+ -

Bash: 
#!/bin/bash
/usr/bin/kill -9 $(ps aux | grep '[.]exe' | awk '{print $2}')
/usr/bin/kill -9 $(ps aux | grep '[.]EXE' | awk '{print $2}')
/usr/bin/kill -9 $(ps aux | grep '[H]ardwareReporter.exe' | awk '{print $2}')
/usr/bin/kill -9 $(ps aux | grep '[E]DLaunch.exe' | awk '{print $2}')
/usr/bin/kill -9 $(ps aux | grep '[M]inEdLauncher' | awk '{print $2}')
/usr/bin/kill -9 $(ps aux | grep '[w]inedebug' | awk '{print $2}')
/usr/bin/kill -9 $(ps aux | grep '[w]ineserver' | awk '{print $2}')
/usr/bin/kill -9 $(ps aux | grep '[o]verlay' | awk '{print $2}')
/usr/bin/kill -9 $(ps aux | grep '[p]ressure-vessel-' | awk '{print $2}')
/usr/bin/killall -9 Talos
 

Jack Winter

Jack Winter
As a matter of interest, how does Horizon run for you guys?

I get occasional FPS drops around stations and asteroid belts, the same place can be either ok or have FPS drops even into single digits. I haven't found any pattern to it, but I think it's related to a high CPU usage. I can see a CPU racing and my entire Linux desktop becoming quite unresponsive. Often happens when landing at coriolis stations.
 

alexzk

A
Jack Winter said:
As a matter of interest, how does Horizon run for you guys?
Click to expand...
700 fps in main menu, 200+ flying around :D
Ody does 120+ until gets bugged. Something like new internal walls' paint bugs it it seems.

No hangs - I use Arch Linux, so kernel & driver are last, and steam updates couple time per week everything else.
Also I have mitigations=off as kernel param, those new "spectre" things eat cpu high.
 
Last edited:

Jack Winter

Jack Winter
I also use Archlinux and with a GTX 1660 Ti, but don't see performance like that. At what quality settings?

I've never tried mitigations=off, I might have to give it a go.

I also run in regular wine starting from the FD launcher and not from steam at all, maybe I should see how it runs under proton.
 

WR3ND

WR3ND
So far so good on the newest Steam Proton in Manjaro!
Launcher actually launches, logs in, and installs game versions. Currently installing Odyssey and will test if and how well the different game versions run.
Like a good neighbor, I sent Frontier my computer info profile.
Hmm. Looks like it lists my OS as Windows XP Pro. Oh well, so much for that.
Cheers. :)

...

The launcher closed halfway through the Odyssey install for some reason, but other than that everything seems to work well. (y)
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom