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

I agree. If you look up Aric Stewart's talks at recent wineconfs, usb hid support is a bit of a building site.

But would you be able to pastebin or send me a link to a good amount of wine ED logs while starting up, and while opening the Controls screen, as well as the output of "lsusb -v" For some reason my ED doesn't log in wine, only the launcher, and I have a Wine USB dev down the hall I can ask...

I'm testing with the Combat Simulator that has the same behavior, keyboard control presets only appear with a dinput native in this case 32 bits, so I have less log lines to read. I have logs with flags +relay,+dinput,+keyboard,+keys,+rawinput,+usbd before and after going into the controls option without dinput native and with dinput native, almost ~1.6GB each. Does your friend needs any additional flag or less? or these logs are ok to upload them somewhere?.
 
Think I might have a fix for you, when I installed Lutris the first time for BF1 I had to also install lib32-gnutls to get Origin to work.

I just uninstalled it to test and launcher started but received a similar login error to the one you got.

You can find lib32-gnutls in package manager, simple install.

If that doesn't work chances are there's a another missing lib causing the issue.

Edit: Does this look familiar?



lib32-gnutls
That did it! [heart]

Copied my horizons install over, synced files, now in-game!

Two issues left:

1. "Keyboard" and "Mouse" devices are "missing".
BindingLoadingErrors.log said:
There where errors when loading preset file: Wingman2.3.0.binds
Missing devices: Mouse, Keyboard
Yea, I just copied over my config file too... I'll fiddle with that some more.

2. Page tearing at ~70% down the screen (vsync not work so good). But that's pretty minor considering it's running!


While I've basically given up on FD caring about people who care about their own hardware, rights, or privacy enough not to put up with crapware OSes, I haven't given up on playing Elite: Dangerous and at least living by example to FD in hopes that enough of us in their stats might change their minds about a native Linux version.

Hell, anybody from Frontier who'd deign to even read this thread should by all rights be floored and humbled that so many good talented people did with twigs and spit for themselves something Frontier couldn't "afford to do" as a company. They couldn't even do it with dedicated resources and first person access to the IP! Nooo, their *own fanbase* had to come "port it" for themselves just so they could play it on a perfectly viable platform that people don't actually hate to use.
I've been holding off on building a new machine basically because of THIS game. My current PC is 7+ years old now, and I sure won't be putting win10 spyware edition on anything.

Now that it is working on linux, I hope it isn't too much to ask of FDev (QA) to setup their own linux test machine to try to ensure future releases don't break for linux players. (after 3.3 at least)

I wouldn't worry about stats too much. If you look at the hardware survey spyware report the launcher does, it appears wine lists Windows XP Professional as the OS. That should clue FD in that it's wine/linux when they get a bunch of players using winXP to play the game.
 
I'm testing with the Combat Simulator that has the same behavior, keyboard control presets only appear with a dinput native in this case 32 bits, so I have less log lines to read. I have logs with flags +relay,+dinput,+keyboard,+keys,+rawinput,+usbd before and after going into the controls option without dinput native and with dinput native, almost ~1.6GB each. Does your friend needs any additional flag or less? or these logs are ok to upload them somewhere?.

That sounds great. Please upload them somewhere and let me know where i can snag them from. Thanks!
 
No freezes, have some rare odd rendering on planets - considering complexity that's given - but frame rate leaves much to desired.

Interesting. I'm using NVIDIA blob 396.54 on my 2GB GTX960 and it's basically frame for frame the same performance in Winderp and Linux (both were on High settings). Many things feel smoother on Linux, because Winderp loved loved loved making all my harddrives spin for hours on end, for no particular reason (I think cortana is a retro enthusiast and loves hearing HD whine myself), which had some fun performance impacts when playing on Winderp, those are 100% absent on Linux.

The only things I've noticed:
1. The main menu "scene" backdrop occasionally will just go black for no reason.
2. There's a slowdown in borderless windowed when I'm using other applications while ED is displaying. (which by the way is MUCH better behaviour than borderless windowed on Winderp - there it minimizes always if you switch away, on Linux, I can answer an IM or slack message on another monitor and just get back to space truckin, without losing visibility into what's going on in game).
3. FPS droops a bit when the scene gets really busy. Though I think it was basically the same on Windows.
 
** EDIT Looking at your old posts, you are on Debian. Which one? Any Debianites on here fancy walking Victor through the setup process? My skills are focused on the rpm side of Linux - last Debian I used was woody m68k on an Amiga 4000. If I don't get a volunteer though, I'm sure I can remember how to use dpkg ;).

Hi, Debianite here. I'm running mostly Sid, with a touch of experimental. I have the NVIDIA binary blob installed (396.54). I am currently not running ED through SteamPlay/proton, because it seems to be a bit broken there. I'm using the wine that was shared by @wstephenson and @Cmdr Eagleboy for Centos. I looked into building my own, but yeah, that's a big pig, especially since the wine-staging repo at winehq does not include sources (very sad about that) (I would have otherwise just patched and generated a new deb from it).

To get started, I would use the mainline wine-staging to get going: (add a file /etc/apt/sources.list.d/wine-staging.list with this line in it:
Code:
deb [URL]https://dl.winehq.org/wine-builds/debian/[/URL] buster main
)

Next up, use /opt/wine-staging/bin/wine as your wine to do the setup as detailed in the top post. If you have steam installed from debian's repo, you should have all the debian deps you need.

Finally, unpack the rpms linked above and extract the wine juiciness inside. To get that wine instance to run, you need to install an ancient lib from debian's POV. Go here: http://snapshot.debian.org/package/libjpeg8/8d1-2/ and grab both the libjpeg8_8d1-2_amd64.deb and libjpeg8_8d1-2_i386.deb libs and use dpkg -i to install them (they're really old, so they don't conflict with anything in a recent debian).

You should then be able to run with the unpacked wine and get all your keybinds.
 
So for Arch users, there is an AUR package called wine-staging-git, which when used makes it super duper straightforward to compile the latest bleeding-edge wine-staging from a github repository which just happened to have incorporated the keyboard fixes and whatnot.

It's awesome.

Installed that this afternoon and after it built and packaged wine-staging, told Lutris to use that system wine-staging instead of the Lutris-downloaded one, and I'm now running ED nicely on Arch.

Couple of foibles like having to set joystick deadzones and it'd be nice to somehow do some joystick calibration to reduce the need for in-game deadzones. Also have some crackling in the audio but I'm just about to try and fix that by adjusting pulseaudio.

Anywhoo - how good is it to get ED running on Linux? :D
 
Interesting. I'm using NVIDIA blob 396.54 on my 2GB GTX960 and it's basically frame for frame the same performance in Winderp and Linux (both were on High settings). Many things feel smoother on Linux, because Winderp loved loved loved making all my harddrives spin for hours on end, for no particular reason (I think cortana is a retro enthusiast and loves hearing HD whine myself), which had some fun performance impacts when playing on Winderp, those are 100% absent on Linux.

The only things I've noticed:
1. The main menu "scene" backdrop occasionally will just go black for no reason.
2. There's a slowdown in borderless windowed when I'm using other applications while ED is displaying. (which by the way is MUCH better behaviour than borderless windowed on Winderp - there it minimizes always if you switch away, on Linux, I can answer an IM or slack message on another monitor and just get back to space truckin, without losing visibility into what's going on in game).
3. FPS droops a bit when the scene gets really busy. Though I think it was basically the same on Windows.

you are the wind beneath my wings.. being a fellow debianeer, i appreciate your input!
 
So you could bear to drop the Steam requirement and give it a go with just the Frontier account? AFAIK you can still convert to a zsream ED account after purchase, once Proton is working.
 
I'm assuming that even through ED is available via Steam, Steam Play/Proton/DXVK doesn't really kick in because Steam is just a wrapper in this case? I've had a pile of games go from being non-functional to perfect via Steam Play on Linux (Manjaro KDE), it would be great to see ED join the list. Performance is coming on in leaps and bounds.
 
Interesting. I'm using NVIDIA blob 396.54 on my 2GB GTX960 and it's basically frame for frame the same performance in Winderp and Linux (both were on High settings). Many things feel smoother on Linux, because Winderp loved loved loved making all my harddrives spin for hours on end, for no particular reason (I think cortana is a retro enthusiast and loves hearing HD whine myself), which had some fun performance impacts when playing on Winderp, those are 100% absent on Linux.

The only things I've noticed:
1. The main menu "scene" backdrop occasionally will just go black for no reason.
2. There's a slowdown in borderless windowed when I'm using other applications while ED is displaying. (which by the way is MUCH better behaviour than borderless windowed on Winderp - there it minimizes always if you switch away, on Linux, I can answer an IM or slack message on another monitor and just get back to space truckin, without losing visibility into what's going on in game).
3. FPS droops a bit when the scene gets really busy. Though I think it was basically the same on Windows.

1. Dunno about this yet. Assume it's the video decoder.

2. Have you disabled any desktop compositor (also a must if you happen to have a nvidia G-Sync setup)?

3. Could be anything, CPU or GPU bounds kicking in. Benchmark if it's bad enough to care about.
 
1. Dunno about this yet. Assume it's the video decoder.
This was my assumption as well. I give zero cares.

2. Have you disabled any desktop compositor (also a must if you happen to have a nvidia G-Sync setup)?
No, I'm using gnome shell/gnome 3 because I like it. To be honest, I don't care that it's a tad slower - its in the "background" then so it doesn't matter if it's slightly less than 60fps :D

3. Could be anything, CPU or GPU bounds kicking in. Benchmark if it's bad enough to care about.
Heh. As I said, I think it was the same on windows. I'm not exactly running bleeding edge hardware here (GTX960 + i3770k (no overclock)). I don't care enough to actually boot winderp. In fact, my finger is now perilously close to "delete partition > windows" :D
 
Okay so basically on Arch this is running really well...

unknown.png


Wine version : ==> Making package: wine-staging-git 3.18.r8.g8519a9ea+wine.3.18.r75.ge55aca8f49-1
Nvidia driver : 410.66.0
Vulkan : 1.1.82
DXVK : 0.90

Working pretty darned good.

Note the FPS seems low but for an AMD Phenom II X4 945 - which I'm pretty sure holds the GTX 1070 back a lot - and Ultra settings and supersampling set to 1.5, that FPS isn't too bad at all.
 
Last edited:
So how well does Captain's Log run on Linux? Is it necessary to run it under Wine as well, or can it run natively vs the journal files in the wineprefix?
 
So how well does Captain's Log run on Linux? Is it necessary to run it under Wine as well, or can it run natively vs the journal files in the wineprefix?

I haven't tried that one. EDDiscovery works OK and I've been filing bug reports to make it run nicely on native mono. I'll probably push a couple of PRs this weekend.

Code:
MONO_IOMAP=all mono EDDiscovery.exe -portable -notheme -tabsreset
 
So how well does Captain's Log run on Linux? Is it necessary to run it under Wine as well, or can it run natively vs the journal files in the wineprefix?

I haven't ported Captain's Log to Linux. I'm just about to see if it'll install into the same prefix - should be good to go because it's self-contained.

I remember the bother I had porting CL1.x to MacOS. Also, CL2 uses some Windows API calls for various things, which I'd need to find a way of doing in Linux (similar to how I had to do it on MacOS).

I'll consider porting it in the near future - got the Q4 beta to get through first ;)
 
I was able to run launcher in my system by following wstephenson's guide but using Wine 3.17. But now I have a new problem - mouse cursor disappears when entering launcher window and I simply can't click any button (they even don't get highlighted). I switched to another WM without any compositing (bspwm), but it does not help. Can't find similar problem in Google and running Wine with emulated desktop doesn't help too.

UPDATE:
I was wrong. That problem with mouse cursor is related to the network connectivity. Currently there is some problems with it in Russia, they blocking many addresses. And it looks like after going into big network via VPN launcher finally works. Now waiting for shaders to prepare.

UPDATE #2:
Was able to login and start online session. Now messing with hotkeys.

GKcofWS.png


UPDATE #3:
Building multiarch Wine is complicated... Got problems when trying to install wine32 build which I compiled under i386 LXC, but that's another story, probably. Will wait for binary 3.19 builds.
 
Last edited:
CL2 does run in the same prefix, and even detects when the game starts and stops.

It also detects the latest journal file.

Alas, it doesn't appear to be reading & parsing the journal file. So probably does just need to be a native Linux application, or adapted in some manner to cater for running via WINE - presumably file handling is somehow different such that CL2 can't continuously read the journal - who knows..
 
Hi All,

Been lurking a long time - hoping someone found the fix for the CRC error! and yes I got it to work - mostly.

Was using Arch (Antergos) and almost got it somewhere near - but I've switched to KUbuntu today and having real trouble getting the Launcher to load with the same WIMEPREFIZ as previously.

I'm getting the same 'Failed to synchronise...' error as above and I appear to have 32bit libgnutils:i386 installed.

any thoughts?

Code:
dpkg -l | grep gnutls
ii  gnutls-bin:i386                               3.6.4-2ubuntu1                              i386         GNU TLS library - commandline utilities
ii  libcurl3-gnutls:amd64                         7.61.0-1ubuntu2                             amd64        easy-to-use client-side URL transfer library (GnuTLS flavour)
ii  libgnutls-dane0:i386                          3.6.4-2ubuntu1                              i386         GNU TLS library - DANE security support
ii  libgnutls30:amd64                             3.6.4-2ubuntu1                              amd64        GNU TLS library - main runtime library
ii  libgnutls30:i386                              3.6.4-2ubuntu1                              i386         GNU TLS library - main runtime library
ii  libneon27-gnutls:amd64                        0.30.2-2build1                              amd64        HTTP and WebDAV client library (GnuTLS enabled)
ii  libneon27-gnutls:i386                         0.30.2-2build1                              i386         HTTP and WebDAV client library (GnuTLS enabled)
but this is what the error looks like.. (the what seems relevant bit)

Code:
$ WINEPREFIX=/HomeStore/ED wine "c:\Program Files (x86)\Frontier\EDLaunch\EDlaunch.exe"
0009:fixme:ras:RasEnumConnectionsW (0x56b3318,0x33e584,0x33e588),stub!
0009:fixme:ras:RasEnumConnectionsW RAS support is not implemented! Configure program to use LAN connection/winsock instead!
0009:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0009:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0009:fixme:ras:RasConnectionNotificationW (0xffffffff,0x358,0x00000003),stub!
0009:fixme:ntdll:EtwEventRegister ({38ed3633-5e3f-5989-bf25-f0b1b3318c9b}, 0x4d408d6, (nil), 0x16a8a1c) stub.
0009:fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
0009:fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
0009:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
0009:err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733
GnuTLS error: A packet with illegal or unsupported version was received.
0009:fixme:shell:URL_ParseUrl failed to parse L"System.Configuration"
0009:fixme:wincodecs:JpegDecoder_Frame_GetThumbnail (0x56b1b2c,0x33e538): stub
0009:fixme:wincodecs:JpegDecoder_Frame_GetColorContexts (0x56b1b2c,0,(nil),0x33e590): stub
0009:fixme:dwmapi:DwmDetachMilContent (0x4007c) stub
0066:fixme:ntdll:EtwEventUnregister (deadbeef) stub.
0066:fixme:ntdll:EtwEventUnregister (deadbeef) stub.
0066:fixme:ntdll:EtwEventUnregister (deadbeef) stub.

Thanks all

Same problem here on Ubuntu 18.10, I can't seem to find the missing library.
 
Back
Top Bottom