PlayableShow Details
Unknown
horizons works great! i haven't tried odyssey but given how unstable it can be on windows i expect there would be similar linux issues.
a little bit of clipping when using other applications (youtube, spotify) but i believe that it may be a limitation with my hardware.
runs great without any flaws.
Works perfectly, in VR, will all my peripherals.
I had small issues where I had to modify my binding file from windows as the game thinks, for instance, than the ² or ~ key is "F14" and other things like this in linux. This is a minor issue, however this is a game with enormous binding files, over multiple devices, and people will want to be aware that a few modifications need to be made in your bindings if you keep the same file.
I am a very long time Elite dangerous player (Over 2000 hours pre steam version). I play it with ALL my peripherals: X52 (non pro) hotas for flight, m+kb for controls on foot, razer nostromo for many bindings because I play in VR and can't see my keyboard, Xbox 360 controller for driving SRVs. All are recognized immediately and bindable in the menus. Very few changes were needed in the binding, taking the same binding file I had on windows.
It just straight up the same, and I play in VR with wivrn. After many hours of gameplay on linux, landing on planets, fighting, docking and exploring, I have not encountered a single issue.
Installation under EndeavourOS is straight foreword. Install OS, install Steam, install Game, set Compatibility to Proton - Experimental. Start the game, Launcher starts, select play. No additional tricks or something else needed. Works right OOTB
game-performance
Everything works, runs great, no issues at all. Did not need to tinker beyond setting up proton-cachyos and running with 'game-performance'.
OXR_PARALLEL_VIEWS=1 %command%
virpil hotas required protontricks >explorer>control panel>enable sdl and disable hidraw both checked. also requires regedit fixes, easily found online
may be a "tinker" report, but the tinkering was very minor, and most probably don't need to. Using the latest kernel. my build stats are out of date.
Launcher works, game does not. Hides main window and cannot switch to it.
The game launches, you can hear the intro play, and the menu audio, but you cannot get the game to display. Switching to the main game window shows it's a black screen and it auto hides itself again. Tried on Proton Hotfix, and Experimental and both exhibit the same behaviour.
I tried a few versions of Proton, mostly new ones. The one that finally worked for me was 8.0-5. The others go to the launcher, you try to launch the game and it fails to launch. 8.0-5 worked first try.
Works OOB on experimental as recommended, joystick works as intended
Poor antialiasing set to SMAA
joystick is T.16000M
Game works after adding VK_ICD_FILENAMES and VK_LAYER_PATH and checking file names in /usr/share/vulkan/icd.d/ and /usr/share/vulkan/
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd64.json VK_LAYER_PATH=/usr/share/vulkan/explicit_layer.d force_vk_vendor=-1 %command% -opengl -SkipBuildPatchPrereq /edo /autoquit /autorun
Originally the game would crash at the "Planet Generation" screen at 0 complete. After trying a bunch of stuff, adding the VK_ICD_FILENAMES and VK_LAYER_PATH to the launch options fixed the issue. I had to change my VK_ICD_FILENAMES variable, by using the command "ls /usr/share/vulkan/icd.d/" and then using one of the files in there as my VK_ICD_FILENAMES variable. The other fixed using VK_ICD_FILENAMES didn't have the same file names as my system.
Launch options "VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd64.json VK_LAYER_PATH=/usr/share/vulkan/explicit_layer.d %command%" is probably all you'll need to get past the planet generation screen.
DXVK_CONFIG="dxgi.maxDeviceMemory = 15360;" %command%
I've been playing this game for a long time over a lot of different hardware. For the most part, it runs very well, with almost nothing that can be blamed on Linux.
- [Proton] I've used various flavors and versions of vanilla Proton (8-9), Proton GE (9+), and Proton-cachyos (202412+), and they all work fine.
- [Stuttering] The late 2024, early+ 2025 stuttering, especially at 5 minutes past the hour, is a game issue not a Linux issue.
- [Odyssey] On-foot FPS is not nearly as bad as it was 4 years ago, but it's still not as good as in space, and not as good as it is in the Legacy version. But it's fine.
- [Shadows, lighting] Flickering shadows and weird lighting sources are a game issue not a Linux issue.
- [9070 XT - current card] As of this writing, the 9070 XT requires 3 kernel patches in amdgpu not yet in a release (all titled "Protect FPU in ...") in order to not crash the kernel/display needing a hard poweroff. With them, and a recent linux-firmware and mesa 25.0.2+, the game works very very well. In space I can sustain 150-250 FPS with 1.5x supersampling and AA on at 1440p, so I plan to cap around 120 as my monitor is 120 Hz.
- [6700 XT] Runs fine, for this old card.
- [3070 ti] 8 GB VRAM is too low and causes constant stuttering. Limiting the VRAM using DXVK environment options (as noted here) helps significantly. This shouldn't be as much of an issue on AMD cards.
- [Crashes] Some, nothing unusual compared to playing on Windows.
Runs fine with no tinkering
Having run this on windows and linux through proton, I think it actually runs better through proton. Seems to run fine out of the box and most of the issues people report are just the game itself and not the proton translation.
I had a lot of severe stutterings. I was able to reduce it significantly by reducing the details to mid (on windows11 high woked). Additionally i had to turn off ambient occlusion. I still have instable framerates, bit it is now manageble.
Works flawlessly as far as I know, never played the Windows version. Meh graphx on 1080p, might just be upscaling, but 1440p looks fine.
Flying low to planet surfaces might stutter occasionally. Not certain if that's just me or if others experience any of that.
ran just as well if not better than windows. used less ram of course, temps were lower, and i actually forgot i was playing on linux.
a little janky on first launch but easily fixed
i have a thrustmaster f16 button panel, and steam was picking it up as a regular controller with joysticks and stuff. im sure it can be fixed but im too lazy
when launching without forcing older proton, i couldnt get the game client to show up. but that was an easy fix. other than that it works perfectly! actually astonished!
Game runs almost as good on Linux as it does on Windows. Not perfect, but more than good enough.
If you are experiencing pixelated text, make sure the resolution is set correctly in Settings > Graphics > Display and make sure upscaling is turned off in Settings > Graphics > Quality
I use bordless windowed. Sometimes the mouse will be able to leave the window and go to my other monitor. Pausing, clicking the game, then unpausing fixes it
Game has trouble detecting clipboard updates. If you are using EDMC and copying stuff from that to paste in game and it's not properly coping, try copying anything from another application, and then copying the text in EDMC. This works for me
gamemoderun mangohud %command%
Needed to use Nvidia beta (570) drivers. Stable (550) had black flickering issues, and supersampling resulted in 10 fps
gamemoderun gnome-terminal -- ./MinEdLauncher %command% /autorun /autoquit /edo
Alt-Tabbing on the full screen mode crashes the game
Was able to pass the "planetary generation" bug by waiting 35 minutes for the 1st time, but you cannot play on the latest proton, you also need to NOT CHANGE the bindings, it will crash at some point
Playing on latest versions of Proton (Valve ones and GE ones) crashes the game at the "Planetary Generation Screen".
- Install the game
- Choose "Proton 6.3-8" in the compatibility list
- wait (not like 30 seconds, but almost 35 minutes for the 1st launch)
- Quit the game once it started.
- Install Minimal Elite Dangerous Launcher from here : https://github.com/rfvgyhn/min-ed-launcher
- Add this in the args : gamemoderun gnome-terminal -- ./MinEdLauncher %command% /autorun /autoquit /edo
- Enjoy !!
and 8) If the game still doesn't works, install the xenmod kernels, you are probably using the 6.x kernels
Works surprisingly well...
Occasional performance drop but not gameplay impacting.
Besides the occasional performance drop compared to native, its like running under windows. It even picked up on my two part HOTAS setup of a Logi stick and Thrustmaster throttle. Unless you need helper apps, it's difficult to tell the difference between Windows and Proton.
ANV_NO_GPL=1 force_vk_vendor=-1 gamemoderun mangohud %command% -opengl -SkipBuildPatchPrereq
I have the games at Epic. So i installed Epic Launcher with Lutris and the Game with the installed Epic Launcher
had to disable Ambient Occlusion in option to get rid of shadow flicker
Live Version crashes on planet generation
Legacy Version works, but had to disable Ambient Occlusion
Registry edits to anble HOTAS to work instead of being deteced as xbox controller according to this thread: https://www.reddit.com/r/hotas/comments/uw3l03/comment/i9p82da/
See registry tinkering
Обов'язково запускати з сьомим Протоном. На новіших його версіях не адекватно працює ланчер гри.
No longer opens the game past the launcher.
PROTON_LOG=1
Changed registry settings to enable HOTAS to work (instead of picking up everything as an Xbox controller) according to this thread: https://www.reddit.com/r/hotas/comments/uw3l03/comment/i9p82da/
Pressing the Play button now opens nothing.
A little fiddling making sure my drivers were working properly, but it ran pretty much out of the box using Experimental.
Fixed this by updating the NVIDIA drivers to version 550.
Slightly slower than windows, had to drop from Ultra to High graphics.
WINEDLLOVERRIDES="d3d11=n,b;d3dcompiler_46=n" %command%
The launch options provided above are required for EDHM UI to work, but are otherwise not necessary! I run EDMC (journalling tool) and EDHM UI (HUD recolour mod) alongside the game. I launch both of these using Bottles, where I've symlinked the game's appdata folders and main directory.
I've encountered no issues with this setup, and both tools work as expected. I then run both EDMC and Elite Dangerous with a non-steam game with the target set to xdg-open bottles:run/ED/EDMarketConnector & xdg-open steam://rungameid/359320.
Stopped working
No longer works, gets to planet generation and bombs out @ 0%
Tried Recent version of GE too
