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

I agree that it makes copies into prefix, but it doesnt need exact matched version, mostly "not lower than". You can see it in descriptions https://github.com/doitsujin/dxvk/releases, for example since 1.7 - 5.8 wine minimal. It will not break prefix as it is possible to complete uninstall DXVK from prefix via "sh setup_dxvk.sh uninstall".

I don't have exact 5.13 version, but I have 5.8, 6.1, 6.2 installed and with/without DXVK it crashes even before running ED launcher.

Taking into consideration that it runs normally (except FPS) I suspect the game could use some graphic features that is being translated by DXVK into some vulkan features that are not supported by my GPU (haswell has only partial support of vulkan, however, other games I played works fine).
I played ED for years using Linux on gts 450, then 1050 and 4770 CPU (Haswell).
It was pretty OK. As I recall I was using 5.13 and DXVK 1.6 or 1.7 prior going to proton.
5.18+ like had issues with many games, so I think I froze with 5.13 that time for most games.

You can try this launcher:

to avoid problems with .NET/Mono. It is not ideal too, but at least removes dependency on .NET so you can figure to run game 1st.
Game itself and launcher have different reasons to fail on wine. So you should treat it as 2 different "games".

P.S. Also launcher loves to stuck in memory keeping wine server loaded with all current consequences of the last crash/bug. Make sure you kill all EXEs prior doing 2nd run of game.
 
Last edited:
P.S. Also launcher loves to stuck in memory keeping wine server loaded with all current consequences of the last crash/bug. Make sure you kill all EXEs prior doing 2nd run of game.
I have a script for this that does WINEPREFIX='path/to/prefix' wineserver -k because the epic version of horizons has never exited cleanly for me I think, even on windows (still using legendary though).
 
I have a script for this that does WINEPREFIX='path/to/prefix' wineserver -k because the epic version of horizons has never exited cleanly for me I think, even on windows (still using legendary though).
Yeh...however as it is "still working", script may never execute.
I have kill -9 "all-exes-command-list" bound to long keystroke, get used to press it after any game.
 
I played ED for years using Linux on gts 450, then 1050 and 4770 CPU (Haswell).
When I mentioned incomplete support of vulkan on haswell, I was talking about iGPU (integrated intel graphics, 4600 HD in this case), while in your case you used nvidias.
And years ago, but now after many-many updates.. I mean maybe that old version would run normally on my hardware but the current version - not really (it's either crashes with DXVK or low fps/missing some textures without DXVK).
You can try this launcher:
Thanks, now it launches (even with new clean prefix! with no any vcruns or dotnets) the game normally with older wine, but crashes like in my first message (with more recent DXVK version –between menu and the hangar – "A file has failed to load after multiple attempts as Direct3D cannot lock a buffer." or within first seconds of hangar with older versions it crashes in other way. I've installed 5.13 wine-staging and tried different versions of DXVK up to 1.3.4 with same result as on 5.8 version).
I consider to try that fork of proton https://github.com/GloriousEggroll/proton-ge-custom and later, normal proton.
 
intel HD 4600

While it'll work with open source radv, vulkan is not officially supported by Intel with that. There may be some vulkan extensions that dxvk call on that are totally incompatible and refuse to run.

To find out what the issue is, create an issue on the mesa gitlab or dxvk github however vulkan is best run on a gpu that officially supports it.
 
Since yesterday Elite Horizons will not start anymore on OpenSuSE Leap15.3. However, on the same PC (a dual-boot) it will start when run under KUbuntu 20.04, which resides on another partition.
What goes well so far is the appearance of the start window, where I can push the big blue 'Play' button in the lower left corner.
The button disppears, but the game is not started and the big blue 'Play' button reappears after some time.
In between, the messages below came up.

uname -a gives:
Linux localhost.localdomain 5.3.18-59.34-default #1 SMP Thu Nov 11 12:18:45 UTC 2021 (a2a53aa) x86_64 x86_64 x86_64 GNU/Linux

These are the NVIDIA packages installed:
nvidia-gfxG05-kmp-default-470.86_k5.3.18_57-lp153.46.1.x86_64
x11-video-nvidiaG05-470.86-lp153.46.1.x86_64
nvidia-computeG05-470.86-lp153.46.1.x86_64
kernel-firmware-nvidia-20210208-2.4.noarch
nvidia-glG05-470.86-lp153.46.1.x86_64

Wine:
wine-6.0-bp153.1.173.x86_64
winetricks-20201206-bp153.1.11.x86_64
wine-devel-6.0-bp153.1.173.x86_64
wine-32bit-6.0-bp153.1.173.x86_64
wine-gecko-2.47.2-bp153.1.10.noarch
wine-mono-6.1.1-lp153.1.1.noarch

The messages:

00f4:fixme:seh:NtQueryInformationThread ThreadIsIoPending info class not supported yet
0024:fixme:msctf:InputProcessorProfileMgr_GetActiveProfile (000000001BFFFA00)->({34745c63-b2f0-4784-8b67-5e12c8701a31} 000000000021E430)
0024:fixme:msctf:InputProcessorProfileMgr_GetActiveProfile (000000001BFFFA00)->({34745c63-b2f0-4784-8b67-5e12c8701a31} 000000000021E350)
0024:fixme:msctf:InputProcessorProfileMgr_GetActiveProfile (000000001BFFFA00)->({34745c63-b2f0-4784-8b67-5e12c8701a31} 000000000021D980)
0024:fixme:msctf:InputProcessorProfileMgr_GetActiveProfile (000000001BFFFA00)->({34745c63-b2f0-4784-8b67-5e12c8701a31} 000000000021D8A0)
0024:fixme:msctf:InputProcessorProfileMgr_GetActiveProfile (000000001BFFFA00)->({34745c63-b2f0-4784-8b67-5e12c8701a31} 000000000021E430)
0024:fixme:msctf:InputProcessorProfileMgr_GetActiveProfile (000000001BFFFA00)->({34745c63-b2f0-4784-8b67-5e12c8701a31} 000000000021E350)
0024:fixme:msctf:InputProcessorProfileMgr_GetActiveProfile (000000001BFFFA00)->({34745c63-b2f0-4784-8b67-5e12c8701a31} 000000000021D980)
0024:fixme:msctf:InputProcessorProfileMgr_GetActiveProfile (000000001BFFFA00)->({34745c63-b2f0-4784-8b67-5e12c8701a31} 000000000021D8A0)
0024:fixme:msctf:InputProcessorProfileMgr_GetActiveProfile (000000001BFFFA00)->({34745c63-b2f0-4784-8b67-5e12c8701a31} 000000000021D9A0)
0024:fixme:msctf:InputProcessorProfileMgr_GetActiveProfile (000000001BFFFA00)->({34745c63-b2f0-4784-8b67-5e12c8701a31} 000000000021D8C0)
00e4:fixme:seh:NtQueryInformationThread ThreadIsIoPending info class not supported yet
0024:fixme:path:parse_url failed to parse L"System.Xml"
00dc:fixme:eek:le:thread_context_callback_ContextCallback 000000001B465F18, 000006447F28CE80, 0000000019A5F8A0, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 0000000000000000
00dc:fixme:eek:le:thread_context_callback_ContextCallback 000000001B465F18, 000006447F28CE80, 0000000019A5F7D0, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 0000000000000000
00dc:fixme:eek:le:thread_context_callback_ContextCallback 000000001B465F18, 000006447F28CE80, 0000000019A5F7D0, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 0000000000000000
0024:fixme:mshtml:HTMLDocumentObj_QueryInterface Unimplemented interface {00000144-0000-0000-c000-000000000046}
0024:fixme:mshtml:HTMLWindow2_QueryInterface (000000001BDBF980)->(IID_IMarshal 000000000021A9E0)
0024:fixme:ieframe:get_location_url semi-stub
0024:fixme:ieframe:get_location_url semi-stub
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0268:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0274:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
Invalid MIT-MAGIC-COOKIE-1 key0274:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0274:fixme:heap:RtlSetHeapInformation 0000000000010000 0 000000000021E890 4 stub
0274:fixme:ntdll:EtwEventRegister ({5eec90ab-c022-44b2-a5dd-fd716a222a15}, 0000000001031124, 00000000010B94D0, 00000000010B94F0) stub.
0274:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 00000000010AFA70, 43) stub
0274:fixme:eek:le:CoInitializeSecurity 0000000000000000, -1, 0000000000000000, 0000000000000000, 0, 3, 0000000000000000, 0, 0000000000000000 stub
0274:fixme:wbemprox:client_security_SetBlanket 00007FAFB604D720, 00000000000ACB20, 10, 0, (null), 3, 3, 0000000000000000, 0x00000000
0274:fixme:wbemprox:client_security_Release 00007FAFB604D720
Invalid MIT-MAGIC-COOKIE-1 key0278:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
0278:fixme:toolhelp:Heap32ListFirst : stub
02c4:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpWithDataSegs
00f4:fixme:seh:NtQueryInformationThread ThreadIsIoPending info class not supported yet
02c4:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpWithDataSegs
02c4:fixme:file:ReplaceFileW Ignoring flags 2
0268:fixme:ver:GetCurrentPackageId (000000000021FD50 0000000000000000): stub
0024:fixme:ieframe:get_location_url semi-stub
0024:fixme:ieframe:get_location_url semi-stub
 
Last edited:
Since yesterday Elite Horizons will not start anymore on OpenSuSE
Check other games, looks like generic problem with wine. Also check Elite's network logs. Elite, SWTOR and some other games had the same issue happening over 2 years randomly - thing is, they use outdated certificates so system needs outdated ROOT certs installed too.
Also it was problem with TSL 3 + wine. It was sending "broken" data to cipher as MS windows do too. I think i solved this by downgrading tsl layer in my system to older.
 
Since yesterday Elite Horizons will not start anymore on OpenSuSE Leap15.3
Did you update your system that day? I am/was running ED on Arch and I did a daily system update which sometimes caused a package to install that depended on another package that hasn't been pushed at that time. After waiting for a day or so, the dependency eventually got updated too and I was fine.
 
Did you update your system that day? I am/was running ED on Arch and I did a daily system update which sometimes caused a package to install that depended on another package that hasn't been pushed at that time. After waiting for a day or so, the dependency eventually got updated too and I was fine.
I upgraded wine to 6.22, having now this configuration.

wine-devel-6.22-lp153.1396.1.x86_64
wine-6.22-lp153.1396.1.x86_64
wine-32bit-6.22-lp153.1396.1.x86_64
wine-gecko-2.47.2-bp153.1.10.noarch
winetricks-20210825-lp153.33.1.x86_64
wine-mono-7.0.0-lp153.42.1.noarch

The game started but, it is not what it was. For one, the custom bindings became a mess. Also, at game start (when it starts at all, to be honest), the shading takes long time, which it normally only does when a wine upgrade is performed or a new driver for nvidia is installed.
I played the game and left a space station, stopping and requesting docking, which was granted. The ship went back into the space station then halted above the docking platform without descending on it.
I am going to restore my saved OpenSuSE partition (which contains wine) and the home partition (which coniantns the game) to what they were half a year ago and see what the sytem does.
 
I upgraded wine to 6.22, having now this configuration.

wine-devel-6.22-lp153.1396.1.x86_64
wine-6.22-lp153.1396.1.x86_64
wine-32bit-6.22-lp153.1396.1.x86_64
wine-gecko-2.47.2-bp153.1.10.noarch
winetricks-20210825-lp153.33.1.x86_64
wine-mono-7.0.0-lp153.42.1.noarch

The game started but, it is not what it was. For one, the custom bindings became a mess. Also, at game start (when it starts at all, to be honest), the shading takes long time, which it normally only does when a wine upgrade is performed or a new driver for nvidia is installed.
I played the game and left a space station, stopping and requesting docking, which was granted. The ship went back into the space station then halted above the docking platform without descending on it.
I am going to restore my saved OpenSuSE partition (which contains wine) and the home partition (which coniantns the game) to what they were half a year ago and see what the sytem does.
At least the game runs. The docking might be related to the game itself as the docking procedures are not considering too many edge cases. You can even see NPCs with the same behavior at times. Especially in crowded instances with lots of players or traffic in general.
Also, let me know how your attempt works out, I'm interested.

Best regards
 
At least the game runs. The docking might be related to the game itself as the docking procedures are not considering too many edge cases. You can even see NPCs with the same behavior at times. Especially in crowded instances with lots of players or traffic in general.
Also, let me know how your attempt works out, I'm interested.

Best regards
Things work now as they did of old after restoring the situation I stored half a year ago with fsarchiver (and upgrading to present day of course).
I wonder what caused the problem in the first place.
 
Last edited:
Things work no as they did of old after restoring the situation I stored half a year ago with fasarchiver (and upgrading to present day of course).
I wonder what caused the problem in the first place.
Interesting. Have you attempted a full reinstall? Including wine. Sometimes some config files get changed. I am unsure if these will get wiped during a reinstall but it might be worth a try. But other than that, this issue sounds weird. Certainly doesn't help that I am using Arch instead of Suse. I must admit I have no real idea beyond the basic "did you try to turn it off and on again" suggestions at this point.

If you don't mind, what exactly does not work as before?
 
I upgraded wine to 6.22
You need STAGING. Don't even try plain wine.
Settings / bindings --- that is windows mess, win xp / 7 / 8 / 10 were moving shortcuts like "Local User" between different physical folders on drive (renamed), so wine follows this pattern. Older had name for XP, now you have name for 7 or 10. And with new name game can't find it.
You just need symlink all this window's mess to single folder of your choice and put things there.

...your wine's prefix had "xp folder names", now it has "win7 folder names" - they're different. So game fails. Need to do symlinks.
 
Last edited:
Interesting. Have you attempted a full reinstall? Including wine. Sometimes some config files get changed. I am unsure if these will get wiped during a reinstall but it might be worth a try. But other than that, this issue sounds weird. Certainly doesn't help that I am using Arch instead of Suse. I must admit I have no real idea beyond the basic "did you try to turn it off and on again" suggestions at this point.

If you don't mind, what exactly does not work as before?
I did not do a full reinstall. Frankly, I wouldn't now how to do that since the last time I installed ED was nearly 3 years ago. Complicated stuff with having purchased it from Frontier and then making it work with Steam. I just upgraded wine to version 6.22 and then found that I had new problems. Sometimes, the games would not start at all. When starting, again and again it was slow with preparing the shaders and the planet generation system, which it will normally only do after an upgrade of ED, the kernel and/or the graphics drivers. I also encountered problems with the Bindings file for the controls. Then I had this problem that an auto docking stopped just right above the landing pad.
I concluded something had screwed up the software and that was why I reinstalled my OpenSuSE system from half a year ago.
 
You need STAGING. Don't even try plain wine.
Settings / bindings --- that is windows mess, win xp / 7 / 8 / 10 were moving shortcuts like "Local User" between different physical folders on drive (renamed), so wine follows this pattern. Older had name for XP, now you have name for 7 or 10. And with new name game can't find it.
You just need symlink all this window's mess to single folder of your choice and put things there.

...your wine's prefix had "xp folder names", now it has "win7 folder names" - they're different. So game fails. Need to do symlinks.
I used to use wine-staging, but somehow that changed. I must confess I cannot recall when an why that happened.
Meanwhile, ED works fine with wine now and has done so for a long time.
 
I did not do a full reinstall. Frankly, I wouldn't now how to do that since the last time I installed ED was nearly 3 years ago. Complicated stuff with having purchased it from Frontier and then making it work with Steam. I just upgraded wine to version 6.22 and then found that I had new problems. Sometimes, the games would not start at all. When starting, again and again it was slow with preparing the shaders and the planet generation system, which it will normally only do after an upgrade of ED, the kernel and/or the graphics drivers. I also encountered problems with the Bindings file for the controls. Then I had this problem that an auto docking stopped just right above the landing pad.
I concluded something had screwed up the software and that was why I reinstalled my OpenSuSE system from half a year ago.
I'd actually suggest a reinstall since today it's much easier than 3 years ago. There is a custom proton version that works well with most games and explicitly supports Elite: Dangerous. The workflow for me was downloading Elite via steam, enforcing a custom proton version upon startup and it worked just as well as you'd expect it to run on a windows machine.
 
I'd actually suggest a reinstall since today it's much easier than 3 years ago. There is a custom proton version that works well with most games and explicitly supports Elite: Dangerous. The workflow for me was downloading Elite via steam, enforcing a custom proton version upon startup and it worked just as well as you'd expect it to run on a windows machine.
I deleted the game, deleted wine en started to follow the instructions on https://cialu.net/how-to-install-and-play-elite-dangerous-on-linux/
First step was to install Steam. Alas, a few repositories that needed installing were not installed and that gave me some bad feelings.
Still it seemed Steam itself was installed.
I could go through the instructions and got quite far. ED was installed on my system. There was this Play button.
Bu the game still does not play.

Are there alternative instructions to make ED work from scratch with Steam?

Maybe the information on https://cialu.net/how-to-install-and-play-elite-dangerous-on-linux/ is outdated.
 
Back
Top Bottom