I have now everything at minimum and downsampling to 0.75, and it's bearable. I guess that not having played ever at high settings or in a powerful computer helps (ignorance is bliss). Pre Q4, I didn't need to downsample and I had several settings not at minimum.
How to install ED on Linux using Wine [EXPERIMENTAL, NOT OFFICIALLY SUPPORTED]
I have now everything at minimum and downsampling to 0.75, and it's bearable. I guess that not having played ever at high settings or in a powerful computer helps (ignorance is bliss). Pre Q4, I didn't need to downsample and I had several settings not at minimum.
This is easily fixed and already in newest upstream driver by nvidia.
Other topic, i have trouble gettin my hotas to work in wine, dxvk and ed. i'am not preferring proton though as i have native builds with newer software for the various components.
Anyone experienced the same issues? Maybe it's SDL and / or libinput related don't know for sure.
Really dont't want to play with keyboard and mice just to get rid of win.
(hum, gettin' feral and fdev in touch could be cool. really enjoyed tomb raider with linux) We know cobra engine can run under unixoid systems, we just need a native build without that wine fiddle. in fact mesa shouldn't be a really serious problem like the mac users face actually.
Hello commanders!
Finally, I was able to make EDEngineer to work in Linux too (Ubuntu 18.04 and wine 3.21 staging)
A short guide follows just in case someone could be interested in trying it. Proceed at your own risk.
It syncs with the game when playing and updates the shopping list (enough for me).
What doesn't work yet:
I went for a new wine prefix (32bits) in /opt/edeng-wine, installed dotnet 4.61 using winetricks and then installed the program downloaded from here.
It will fail the first time the program runs because the voice synthesis is missing.
Fortunately, EDEngineer is open source (Thank you Max) so I worked out a solution:
First, kill the still running program:
Find the configuration file (note that your path would be slightly different):
And change the value of the NotificationVoice in the xml file to avoid the error.
You can now run the program again:
It could fail when selecting the ED log directory.
As I had ED in a different wine prefix I used the Z: unit in the path (a simlink could be used too).
If you can't make it, just edit the settings manually and add the path there (the path would be different in your case, use the TAB key for autocompletion):
And add the right path:
I hope you can find this mini guide useful.
If there is anything wrong or should be better explained, please tell me and I will correct the post.
o7
Finally, I was able to make EDEngineer to work in Linux too (Ubuntu 18.04 and wine 3.21 staging)
A short guide follows just in case someone could be interested in trying it. Proceed at your own risk.
It syncs with the game when playing and updates the shopping list (enough for me).
What doesn't work yet:
- The combo boxes that filter the blueprints (can be filtered using the Search box)
- The "-" sign is not showing in the shopping list (although you can click on it). I tried to solve it installing corefonts, but it didn't work.
- The voiced notifications (never used them in windows)
I went for a new wine prefix (32bits) in /opt/edeng-wine, installed dotnet 4.61 using winetricks and then installed the program downloaded from here.
Code:
WINEPREFIX=/opt/edeng-wine/ WINEARCH=win32 wine winecfg
WINEPREFIX=/opt/edeng-wine/ WINEARCH=win32 WINE=/opt/wine-staging/bin/wine winetricks dotnet461
WINEPREFIX=/opt/edeng-wine/ WINEARCH=win32 /opt/wine-staging/bin/wine setup.exeIt will fail the first time the program runs because the voice synthesis is missing.
Fortunately, EDEngineer is open source (Thank you Max) so I worked out a solution:
First, kill the still running program:
Code:
killall EDEngineer.exeFind the configuration file (note that your path would be slightly different):
Code:
vi /opt/edeng-wine/drive_c/users/[B]alierum[/B]/Local\ Settings/Application\ Data/Apps/2.0/[B]H9DKC9B9.H4B/OGARLJ89.DKV/eden...exe_b9c6c2d0b4f2eae5_0001.0001_none_20d0eaaca46ae227[/B]/EDEngineer.exe.configAnd change the value of the NotificationVoice in the xml file to avoid the error.
Code:
<setting name="NotificationVoice" serializeAs="String">
[B]<value>--</value>[/B]
</setting>You can now run the program again:
Code:
WINEPREFIX="/opt/edeng-wine" /opt/wine-staging/bin/wine start "c:\users\[B]alierum[/B]\Start Menu\Programs\Max\EDEngineer.appref-ms"It could fail when selecting the ED log directory.
As I had ED in a different wine prefix I used the Z: unit in the path (a simlink could be used too).
If you can't make it, just edit the settings manually and add the path there (the path would be different in your case, use the TAB key for autocompletion):
Code:
vi /op/edeng-wine/drive_c/users/[B]alierum[/B]/Local\ Settings/Application\ Data/Apps/2.0/Data/[B]42KJBZQW.OXL/RE3288DR.LLT/eden..tion_b9c6c2d0b4f2eae5_0001.0001_5409e5c70c42f7a3[/B]/Data/1.0.0.0/user.configAnd add the right path:
Code:
<setting name="LogDirectory" serializeAs="String">
<value>[B]Z:\opt\ed-wine\drive_c\users\alierum\Saved Games\Frontier Developments\Elite Dangerous[/B]</value>
</setting>I hope you can find this mini guide useful.
If there is anything wrong or should be better explained, please tell me and I will correct the post.
o7
Hi everyone !
Thank you so much for making and updating this thread !
I've just succeeded in installing Elite on my Kubuntu 18.04, it works like a charm, I'm super happy
Some of the problems I've encountered, in case it helps others :
- I first had some problems with the launcher : all the buttons, menus and popups were pitch black.
To solve this, I had to uninstall my (old) stable wine completely from my system, and follow guidelines ( https://wiki.winehq.org/Ubuntu ) to install Wine Staging 4.0 (currently rc4). It allowed me to select it in Lutris once it was installed system wide, and the UI bugs disappeared.
- Then, when I started the launcher through lutris, it seemed to work, but as I validated the login credentials, I got an annoying popup saying I had to enable .net framework in the Windows control panel, which I couldn't really do in Wine. A friend of mine found a solution (thank you !), which was to close Lutris and start the launcher directly in a terminal, simply writing in the command the right prefix and the path to the game.
- At last, to recover all my bindings (which include a Thrustmaster hotas), I finally found that since the last update, the game seems to use /path_to_wine/drive_c/users/someuser/Local Settings/Application Data/Frontier Developments/Elite Dangerous/Options/Bindings/ (note the "local settings" instead of "Local", as it was on my previous install). I didn't have to do anything else than copy-pasting the .binds file, everything worked out of the box, which felt pretty impressive.
Finally, after the install KDE didn't seem really happy with the "borderless" graphics settings (window decorations tended to crash), so I opted for a windowed mode and let KDE manage the borderless option, which works fine on a double screen and allows window focus change.
Fly safe !
Thank you so much for making and updating this thread !
I've just succeeded in installing Elite on my Kubuntu 18.04, it works like a charm, I'm super happy
Some of the problems I've encountered, in case it helps others :
- I first had some problems with the launcher : all the buttons, menus and popups were pitch black.
To solve this, I had to uninstall my (old) stable wine completely from my system, and follow guidelines ( https://wiki.winehq.org/Ubuntu ) to install Wine Staging 4.0 (currently rc4). It allowed me to select it in Lutris once it was installed system wide, and the UI bugs disappeared.
- Then, when I started the launcher through lutris, it seemed to work, but as I validated the login credentials, I got an annoying popup saying I had to enable .net framework in the Windows control panel, which I couldn't really do in Wine. A friend of mine found a solution (thank you !), which was to close Lutris and start the launcher directly in a terminal, simply writing in the command the right prefix and the path to the game.
- At last, to recover all my bindings (which include a Thrustmaster hotas), I finally found that since the last update, the game seems to use /path_to_wine/drive_c/users/someuser/Local Settings/Application Data/Frontier Developments/Elite Dangerous/Options/Bindings/ (note the "local settings" instead of "Local", as it was on my previous install). I didn't have to do anything else than copy-pasting the .binds file, everything worked out of the box, which felt pretty impressive.
Finally, after the install KDE didn't seem really happy with the "borderless" graphics settings (window decorations tended to crash), so I opted for a windowed mode and let KDE manage the borderless option, which works fine on a double screen and allows window focus change.
Fly safe !
Building kernel modules is but my point is the latest 415 drivers have terrain issues therefore if you want the game to generate terrain correctly you either need an older driver (410 or below) and not update the kernel to 4.20 or to hope this bug gets fixed: https://github.com/doitsujin/dxvk/issues/267#issuecomment-445734287
I have already given my own reports about this however I'm worried due to ED not being as popular as some AAA titles and this issue not really affecting other games AFAIK it may end up slipping under the net and not getting fixed for a while, that's why more people need do need to mention this and not be content with current/old drivers or it'll never get fixed.
https://devtalk.nvidia.com/default/...g-issues-in-415-branch-up-to-415-25-/#5304771
Last edited:
Does anyone know what to do when this message appears on starting elite dangerous?
"Warning: you have a custom binding profile that contains missing bindings. Saving any changes to custom bindings will clear the remaining indicators/flags for unassigned controls."
The 'options' under the Main menu are also lit up by an exclamation mark.
"Warning: you have a custom binding profile that contains missing bindings. Saving any changes to custom bindings will clear the remaining indicators/flags for unassigned controls."
The 'options' under the Main menu are also lit up by an exclamation mark.
From the 3.3 patch notes:
That's the exclamation mark to tell you to update your control bindings for the new 3.3 features. The message is telling you that should you change your bindings, that warning icon will no longer appear, irrespective of whether the 3.3 features' bindings are bound. Capisci?
You need to use vcrun2015 at least (vcrun2017 better) since 3.3 to fix this, use winetricks for that.
Last edited:
Capisci yes and no.
I managed to tweak the controls, but only if the system would react to me clicking on 'controls' in the options menu. Which it didn't do on more than one occasion. No exclamation mark to be seen at all.
My bindings are in this file:
/data1/ed-wine/drive_c/users/vaessen/Local\ Settings/Application\ Data/Frontier\ Developments/Elite\ Dangerous/Options/Bindings/Custom.3.0.binds
Last edited:
There's a new nvidia driver release, would anyone be willing to test whether the terrain issues are resolved? https://www.gamingonlinux.com/articles/nvidia-have-put-out-the-41093-driver-for-linux-today.13269
Older long lived branch, it should not have the issue (unless they backported the bug in question) however it won't have the advancements like stream output which fix a lot of issues with other games running in Wine. However if you don't care about other games then it will work with the new kernel unlike 410.73.
Terrain issue is with the 415 branch, that still needs a fix.
That's happened to me a couple of times - or what looks like it, anyway. I ended up opening the bindings file from the ControlSchemes directory (SaitekX55.binds in my case) in a text editor and then saving it overwriting the (identical) version that was there. Just using touch might have worked just as well, actually, if I'd thought of it.
Hope that helps. Best of luck with it.
This tutorial still mentions vcrun2012:
To install Winetricks dependencies use`winetricks dotnet452 corefonts quartz vcrun2012`
Should that not be vcrun2015 or vcrun2017?
You mean to say that you opened the bindings file in the ControlSchemes directory and then overwrote it in this same ControlSchemes directory?
If so, what is the role that a bindings file plays in the directory <WINEprefix>//drive_c/users/<username>/Local\ Settings/Application\ Data/Frontier\ Developments/Elite\ Dangerous/Options/Bindings/ ?
By the way: I use the old fashioned Microsoft Sidewinder Precision 2 joystick, which is not mentioned in the ControlSchemes directory.
.
Nvidia driver 415.22.05 (latest vulkan developer driver) and Laksak base is still buried in a crater...
Can if you got time more people can mention the terrain issue here: https://devtalk.nvidia.com/default/...rendering-issues-in-415-branch-up-to-415-25-/
or here: https://github.com/doitsujin/dxvk/issues/267
Can if you got time more people can mention the terrain issue here: https://devtalk.nvidia.com/default/...rendering-issues-in-415-branch-up-to-415-25-/
or here: https://github.com/doitsujin/dxvk/issues/267
Last edited:
Exactly so, yes. If it happens again I'll try just using touch to update the timestamp and see if that also works for me.
I've no idea, I'm afraid. I didn't know that directory existed. Maybe try something analogous on whichever file you use?
I was having this issue as well and it appears to be a versioning issue with the TLS package included in Ubuntu 18.10. To get around this, I wiped my Ubuntu install and downgraded to Ubuntu 18.04 which solved the issue for me. I'm sure there's a more elegant solution but I was lost in a sea of unmet dependencies when I tried to install the older version of TLS.
From a little earlier in the thread, a fix for unresponsive controls. BTW Edvassen that is the correct path for bindings, elite seems to have more than one config file location for most things.
I removed all of the bindings from the game dir as well as all except custom and my hotas in the c: \ users directory, which fixes the issue for me.
Putting the file Custom.3.0.binds both in directory <WINEprefix>//drive_c/users/<username>/Local\ Settings/Application\ Data/Frontier\ Developments/Elite\ Dangerous/Options/Bindings/ and in the ControlSchemes directory, while removing all other binding files from the latter, did the trick. Thanks!
.
Last edited: