Elite Dangerous (359320)

[KewaiiGamer]

I've just tried starting Elite Dangerous and it seems to not even display the game at all. It just starts and 1 second later it shuts down

I don't know how would I debug it so I would be glad if someone could instruct me on how to enable verbose for Proton Games

OS: Ubuntu 18.04 CPU: AMD Ryzen 5 1600X GPU: Nvidia GeForce 1050 Ti 3GB Driver Version: Nvidia Driver 396

[redmcg]

Not this patch. It really is a horrible hack that only considers this scenario and may very well break others. I think the root of the problem is the assumption from dotnet native that an IPv6 stack is available. That's probably a safe assumption on Windows - but doesn't work on Linux.

There may be a way to disable IPv6 in .NET, but I tried a couple of things without success. If only I had access to the source code.

[redmcg]

If only I had access to the source code.

Well much to my surprise - it turns out I do! And I just need to make WSASocket return AddressFamilyNotSupported. So now I do have a patch I'm happy to submit upstream.

[redmcg]

@Enverex This bug is fixed for 3.21. In the end they went with a mild redesign (as it was lumping a bunch of kernel error codes together - thus losing granularity). If you're interested it was fixed with a patchset of 5 patches ending here.

[Enverex]

Great, thanks @redmcg

[jh97uk]

By the way, for anyone having any trouble getting the launcher to work (as I have), delete the games compatdata folder, and create an empty new one with an empty pfx inside it. Then use winetricks to install dotnet45 and vcrun2012, THEN launch Elite in Steam, it should work then.

[admalledd]

Took me a little while, but I think I have a rebuild of redmcg's proton branch with the -5 release changes included as well.

MD5SUM: b8e2f6a5dc43bee7906176c7a8322262 'Proton 3.16-5 Beta ED.tar.gz'

Hosted on my own server because I can't quite figure out git+github releases with all these submodules abound, and it is already getting late. Same instructions as his release notes.

EDIT: removed my hacky copy, please prefer someone who knows things and see redmcg's post below.

[fls2018]

@admalledd

Appears to be working however the "proton" file needs the wine_path flipped to wine64 in order to avert the CRC error. Easy enough to do though.

[20kdc]

Just an anecdotal note... If you see a crash from dxvk EntryPoint (for me, it involves a completely spurious call to GetFirmwareEnvironmentVariableW), for me it seems to be linked to if Vulkan is working or not. If Vulkan isn't working, it crashes in a pretty weird-to-debug way. That said, it working again was tested after I exhausted a lot of options, so it was under wine-staging 4.0-rc1 + winetricks dotnet45 vcrun2012 vcrun2017 dxvk + cryptography regedit, but I was getting similar crashes under Proton. (As for why I'm posting that here: this seems to be the most current E:D on Wine debugging guide, and I figure I should chip in my own notes.) EDIT: xact seems also necessary to prevent audio popping.

[redmcg]

Yeah - I ran in to the same issue with nvidia-driver-410 and xorg 1.19. See here: https://devtalk.nvidia.com/default/topic/1044851/linux/fyi-nvidia-410-78-driver-fails-with-segmentation-fault-on-fedora-fc29-workstation-with-nvs-510-card/post/5301522/#5301522

Easiest way to test Vulkan is to run vulkaninfo

[redmcg]

I've created a new Git 'release' for Proton 3.16-5 Beta. The focus of this release is to allow easy install of dotnet40 and vcrun2015. It also fixes the crash when IPv6 is disabled. Download and instructions can be found here: https://github.com/redmcg/wine/releases/tag/ED_Proton_3.16-5_Beta

[Muirrum]

I've tried everything upthread, I've got everything installed. Installing winbind managed to get me to the loading shaders screen, but the text is just white blocks and then it crashes.

Edit: Oh wow I completely forgot my system information. Ubuntu 18.04 with redmcg's patched Proton, wine 3.0

[sizeofbool]

I've created a new Git 'release' for Proton 3.16-5 Beta. The focus of this release is to allow easy install of dotnet40 and vcrun2015. It also fixes the crash when IPv6 is disabled. Download and instructions can be found here: https://github.com/redmcg/wine/releases/tag/ED_Proton_3.16-5_Beta

EDLauncher and plain Elite Dangerous are working great with this new Proton build. Even though your scripts don't support "/.steam/compatibilitytools.d/compatibilitytool.vdf" variety of installation and it looks like "compatibilitytools.d" folder doesn't support symlinks. I had ensure VC runtime and dotNet 4.0 are installed and fixed scripts manually. I also had to delete "steamapps/compatdata/359320/" folder and rebuild it with this new Proton build.

However, Elite Dangerous: Horizons is not working for me. I'm experiencing infinite loop of EliteDangerous64.exe process and a screen freeze at initial startup, after shader generation is complete and at the beginning (0% completion) of planet shader generation. Music is playing during freeze and system continues going in background. I let it run for a 40 minutes, but that did nothing and I had to kill it from Ctrl+Alt+F1 console with # kill -9 $(pgrep EliteDangerous) I had the same problem and same behaviour with latest wine-devel 4.0-rc2 + dxvk 0.94 and fresh prefix, so my guess it is the problem with nvidia driver and dxvk.

My Specs: CPU: i5-6600 MEM: 16Gb OS: GNU\Linux Debian 9 'stretch' x86_64 (kernel 4.15) VGA: Nvidia GTX1060 6Gb (proprietary driver 390.87) DE: Xfce 4.12 (lightdm+xfwm4 with compositor enabled)

[redmcg]

VGA: Nvidia GTX1060 6Gb (proprietary driver 390.87)

I don't know if you've tried the 396.54 driver - but it's listed as a minimum requirement for Proton. 410 and 415 drivers are also available but:

• I've had issues with 410 and xorg-server 1.19 (Proton would freeze and vulkaninfo would segfault); and
• 415 has a problem rendering engineering bases.

your scripts don't support "/.steam/compatibilitytools.d/compatibilitytool.vdf" variety of installation

Ooops - you're right. I completely overlooked that possibility. I just enabled the issues section on my Wine repo. If there's something usable in your local modifications - would you mind opening an issue there and pasting them in?

Or you might prefer to wait until I add my Proton fork to GitHub and you can create a pull request. It currently has a bunch of local build edits I need to remove.

[WesCook]

Just to give my own experience: I switched from the old method to the new script. This ended up triggering the game to redownload, but it worked fine afterwards. Running a script is certainly easier than using winetricks.

Previously I had already installed vcrun2015 though to play the new update, so I can't confirm if that part worked correctly or not.

[redmcg]

This ended up triggering the game to redownload

Ooops - that's not an intended consequence. I've had this occur to me when I deleted a custom proton build whilst Steam was still configured to use it (in fact it deleted every game installed for Proton). Is this a possible cause for you?

[WesCook]

Yes, that sounds very likely. I updated the Proton build in Steam after I completed the install process.

[redmcg]

I've tried everything upthread, I've got everything installed. Installing winbind managed to get me to the loading shaders screen, but the text is just white blocks and then it crashes.

Edit: Oh wow I completely forgot my system information. Ubuntu 18.04 with redmcg's patched Proton, wine 3.0

Sounds like a graphics card/driver issue. Could you elaborate on what you're running? You might also want to test without Horizons (as some problems seem to be specific to Horizons).

[redmcg]

your scripts don't support "/.steam/compatibilitytools.d/compatibilitytool.vdf" variety of installation

I've added my Proton changes to GitHub and created an issue there for this.

[sizeofbool]

I don't know if you've tried the 396.54 driver - but it's listed as a minimum requirement for Proton. 410 and 415 drivers are also available but:

* I've had issues with 410 and xorg-server 1.19 (Proton would freeze and `vulkaninfo` would segfault); and

* 415 has a problem [rendering engineering bases](https://github.com/doitsujin/dxvk/issues/267#issuecomment-446808778).

There is a lot going on with Nvidia driver development right now and there is ongoing process of SPIR-V implementation, which currently in beta state and dxvk depends on it. This is why dxvk requires most recent Nvidia driver available and so does Proton, since dxvk is a part of it. I guess, I'll wait until Nvidia gets stable driver release and it hits Debian testing.

[Muirrum]

@redmcg I'm trying to launch the base game Computer Information Video Card: Driver: Intel Open Source Technology Center Mesa DRI Intel(R) Ivybridge Mobile x86/MMX/SSE2 Driver Version: 3.0 Mesa 18.0.5 OpenGL Version: 3.0 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 59 Hz VendorID: 0x8086 DeviceID: 0x166 Number of Logical Video Cards: 1 Memory: RAM: 7675

[dmarcuse]

@Dev-Osmium How much VRAM do you have? Based on your system info I'm guessing you have 512 MB of system memory allocated for the iGPU, which doesn't seem like a lot considering the game lists a GPU with 1 GB of VRAM as the minimum requirements.

[redmcg]

Proton 3.16-6 Beta ED has been released. It fixes the issue identified by @sizeofbool (by installing to a new location) and a bug that would have occurred when trying to run other games. Other than that it just picks up what is in Proton 3.16-6 Beta.

[WesCook]

I appreciate the new warning for dummies like me. :)

[fls2018]

@redmcg Some issues with your latest Proton outside of ED.

[redmcg]

@fls2018 Thanks for pointing that out. I've added details in the issue as to the cause - but the work-around is to use the Steam Beta Client. Apologies to everyone for that inconvenience.

The issue is with the build environment I used - but I don't know when I'll get a chance to rebuild. Of course I'm happy for someone else to do so in my absence.

[redmcg]

Turns out the build environment wasn't the problem. I've been able to run Skyrim under the standard Steam Client just by changing my proton script. If you wish to play one of the affected games - you can replace the proton file with the one found here.

The diff can be found here: https://github.com/redmcg/Proton/commit/09f5ea82bd5462fbd75d61a9f9e32eac01e842ea

[brjhaverkamp]

Hi Redmcg, seens I am joining the ED party just at the right time! Build a GamePC over the holidays with my kids and am a long time Elite fan(from the first wireframe version:-) And I occationally checked if ED was already ported to Linux. Now it seems our new PC coincides with ED on linux!

One question. How do your patches trickle down into the offical Proton release? Can I wait that out, or should I move to your version for the forseeable future?

[redmcg]

@brjhaverkamp The TLDR is that it's up to you. I don't think Proton will have quite the same support for ED that my custom version does for a little while (although a handful of patches have been merged) - but there are also alternatives to Proton (like wine-staging and Lutris).

The long version is I can't say with any real certainty what will happen with the official Proton release (as I don't have any additional insight) but I can say that in my opinion there's a good chance they will rebase on version 4.0 of Wine (as it's a stable release). 4.0 has all my patches but for:

• futex (which is required to stop the game crashing);
• normalize string (which is required for the keyboard to work correctly); and
• hacks to allow easy install of vcrun2015 and dotnet40

The first two are in wine-staging and there's a chance they will get cherry-picked. The third I don't ever see being included (as the focus is purely for Elite Dangerous) but you can use winetricks or protontricks to manually install (the hope is eventually wine and wine-mono will make the need for these redundant).

The other change is that I use wine64 to avoid the need for the CRC work-around. Personally I think Proton should use wine64 as well because this more closely simulates a 64-bit version of Windows - but it wasn't until recently that wine64 had problems with 32-bit .NET launchers.

[tsahyt]

Using the @redmcg Proton build (3.16-5 Beta ED) I am able to start the offline demo, which runs beautifully, but I cannot launch the main game. When I try it, it comes back with an error "Unable to initialise network. Please check your connection". This happens no matter whether I select ED or Horizons in the launcher. My connection seems otherwise fine, and I didn't experience any networking issues whatsoever in the other title I've tried playing with Proton (Quake Champions). I've tried a manual install in Lutris with the same result. The problem persists with the 3.16-6 Beta ED build.

I've looked around on the internet but couldn't find anyone else having this problem, so I thought I should throw it out there and see if someone might be able to help.

OS: Fedora 29 (Kernel 4.19.10-300.fc29) CPU: Ryzen 7 2700X GPU: Vega 64 (DRM 3.27.0)

[agates]

@tsahyt I get the same error with 3.16-6 Beta ED. I haven't spent any time trying to diagnose it yet.

[mosteo]

@agates @tsahyt , this is fixed by installing vcrun2017, as several people reported in the Frontier forums thread: https://forums.frontier.co.uk/showthread.php/366894-How-to-install-ED-on-Linux-using-Wine-EXPERIMENTAL-NOT-OFFICIALLY-SUPPORTED

[tsahyt]

@mosteo, I've tried installing vcrun2017 with winetricks, still yielding the same result.

EDIT: Nevermind, I messed up the WINEPREFIX. I now get a different result, but it seems worse than before. I don't even get to the launcher anymore. Instead I get an error message saying "Internal error creating window: Add value to collection of type 'System.Windows.Control.UIElementCollection' threw an exception."

EDIT 2: Setting wine back to Win7 fixed the error above, but now I'm back to square one, with the "Unable to initialise network" error

[redmcg]

I haven't seen this error myself - but it appears to be related to network connectivity. Here is a report from a Windows user: https://forums.frontier.co.uk/showthread.php/436739-Unable-to-connect-to-network-in-Russia?highlight=Unable+to+initialise+network

Whilst I haven't seen this issue I have had network issues myself (although mine was from within the launcher). I'm using a dual IPv4/v6 stack and one of the IPv6 addresses being returned via DNS appeared to be down. I ended up adding a manual entry to /etc/hosts to workaround it. However, I don't know if the same work-around could be used here. You might need to take a network trace to see if you can find the problem. You could also check the ED netLog and/or the Wine log.

Edit: Just wondering if the game runs fine in Windows?

[tsahyt]

The ED logs report the following (IP removed)

{19:17:47GMT 0.058s} ClientBuild 3.3.0.402 EDH r189994 (win64)
{19:17:52GMT 5.232s} GetPortMapping(59702) failed with code 714 (NoSuchEntryInArray)
{19:17:52GMT 5.610s} GetPortMapping(59702) External xx.xx.xx.xx:59702 -> internal 192.168.0.115:59702 (0)
{19:17:53GMT 6.139s} IPv4 is enabled, but address not found
{19:18:00GMT 13.207s} Machine 1 x 2 Local Machine disconnected: shutdown

After some messing around, basically just trying things out, I found a way to at least get the game to start at all, by setting IPv4="0" and IPv6="1" in AppConfigLocal.xml. From there on things get strange. The options menu reports that IPv4 is on and IPv6 is disabled. The logs instead then state that 20:18:19GMT 0.799s} IPv6 is enabled, but address not found. Like before, everything that's offline works just fine, i.e. I can play the tutorial missions without any real issues (except for one issue with the mouse not working after tabbing out and back in). But I cannot connect to the Frontier servers. It discovers machines, tries connecting, and fails, again and again. In the logs this will look like this

{20:19:35GMT 76.602s} ConnectToServerActivity: state=Init
{20:19:35GMT 76.602s} ConnectToServerActivity: state=WaitingForLogin
{20:19:35GMT 76.607s} GET server/list?protocol=33145
{20:19:35GMT 76.607s} ConnectToServerActivity: state=GettingServerAddress
{20:19:35GMT 76.704s} [MultiCrewMatchmakingLog] AdvanceInfoRequests: Matchmaking info received: 4 (Bounty hunting, 0 ships), 8 (Piracy, 0 ships), 3 (Mentor a player, 0 ships), 16 (Xeno Hunting, 0 ships), 17 (Xeno Research, 0 ships), 1 (Further activities, 0 ships), 5 (Mining, 0 ships), 6 (Exploration, 0 ships), 9 (Smuggling, 0 ships)
{20:19:35GMT 76.704s} [MultiCrewMatchmakingLog] NotifyMatchmakingInfoUpdated
{20:19:36GMT 77.271s} Parsing servers. NumServers: 1(258355904842020,) Choice: 0
{20:19:36GMT 77.271s} -> Added New Machine! RunID : 258355904842020
{20:19:36GMT 77.271s} New machine: 258355904842020 - Cipher is NULL
{20:19:36GMT 77.271s} machineId=1 numMachines=2 numFree=0 hwm=2
{20:19:36GMT 77.271s} RxRoute[1]:258355904842020 Comp:2[IP4:52.48.177.158:19364][IP6:2a05:d018:5:a102:5295:2152:5c93:558b|19364,1500]
{20:19:36GMT 77.271s} SetRouteMtu = 1500 (using 1500) for  258355904842020 x 1 [2/2]((2a05:d018:5:a102:5295:2152:5c93:558b|19364))Name Unknown
{20:19:36GMT 77.271s} New Primary Server: 258355904842020 x 8 [2/2]((2a05:d018:5:a102:5295:2152:5c93:558b|19364))Name Unknown
{20:19:36GMT 77.271s} -> Added New Machine! RunID : 240211470924386
{20:19:36GMT 77.271s} New machine: 240211470924386 - Cipher is NULL
{20:19:36GMT 77.271s} machineId=2 numMachines=3 numFree=0 hwm=3
{20:19:36GMT 77.271s} RxRoute[1]:240211470924386 Comp:2[IP4:34.255.6.19:19364][IP6:2a05:d018:5:a102:25d3:129a:a707:e42d|19364,1500]
{20:19:36GMT 77.271s} SetRouteMtu = 1500 (using 1500) for  240211470924386 x 1 [2/2]((2a05:d018:5:a102:25d3:129a:a707:e42d|19364))Name Unknown
{20:19:36GMT 77.271s} New Mission Server: 240211470924386 x 4 [2/2]((2a05:d018:5:a102:25d3:129a:a707:e42d|19364))Name Unknown
{20:19:36GMT 77.271s} ConnectToServerActivity: state=WaitingForConnection
{20:19:46GMT 87.276s} ConnectToServerActivity: state=Init
{20:19:46GMT 87.293s} ConnectToServerActivity: state=WaitingForLogin
{20:19:46GMT 87.309s} GET server/list?protocol=33145&failCount=1&lastPrimaryServerRunID=258355904842020&lastSecondServerRunID=240211470924386
{20:19:46GMT 87.309s} ConnectToServerActivity: state=GettingServerAddress
{20:19:46GMT 87.876s} Parsing servers. NumServers: 1(256583460643104,) Choice: 0
{20:19:46GMT 87.876s} -> Added New Machine! RunID : 256583460643104
{20:19:46GMT 87.876s} New machine: 256583460643104 - Cipher is NULL
{20:19:46GMT 87.876s} machineId=3 numMachines=4 numFree=0 hwm=4
{20:19:46GMT 87.876s} RxRoute[1]:256583460643104 Comp:2[IP4:34.251.219.79:19364][IP6:2a05:d018:5:a100:4537:4c45:3418:ca64|19364,1500]
{20:19:46GMT 87.876s} SetRouteMtu = 1500 (using 1500) for  256583460643104 x 1 [2/2]((2a05:d018:5:a100:4537:4c45:3418:ca64|19364))Name Unknown
{20:19:46GMT 87.876s} New Primary Server: 256583460643104 x 8 [2/2]((2a05:d018:5:a100:4537:4c45:3418:ca64|19364))Name Unknown
{20:19:46GMT 87.876s} RxRoute[1]:240211470924386 Comp:2[IP4:34.255.6.19:19364][IP6:2a05:d018:5:a102:25d3:129a:a707:e42d|19364,1500]
{20:19:46GMT 87.876s} New Mission Server: 240211470924386 x 5 [2/2]((2a05:d018:5:a102:25d3:129a:a707:e42d|19364))Name Unknown
{20:19:46GMT 87.876s} Machine::ConnectDirectly:unexpected state: state=0, m_attempt=11.605941, fdis=0: Y Disconnected ** Comp:UDP LastRx=10.61s LastTx=10.61s SyncSent=0.00s  [0] Timeout Disc=0.00s Hold=19.39 srtt=1000ms rttvar=0 drc=Unknown
{20:19:46GMT 87.876s} ConnectToServerActivity: state=WaitingForConnection
{20:19:57GMT 98.881s} ConnectToServerActivity: state=Init
{20:19:57GMT 98.898s} ConnectToServerActivity: state=WaitingForLogin
{20:19:57GMT 98.915s} GET server/list?protocol=33145&failCount=2&lastPrimaryServerRunID=256583460643104&lastSecondServerRunID=240211470924386
{20:19:57GMT 98.915s} ConnectToServerActivity: state=GettingServerAddress
{20:19:58GMT 99.499s} Parsing servers. NumServers: 1(254496286725356,) Choice: 0
{20:19:58GMT 99.499s} -> Added New Machine! RunID : 254496286725356
{20:19:58GMT 99.499s} New machine: 254496286725356 - Cipher is NULL
{20:19:58GMT 99.499s} machineId=4 numMachines=5 numFree=0 hwm=5
{20:19:58GMT 99.499s} RxRoute[1]:254496286725356 Comp:2[IP4:54.229.231.159:19364][IP6:2a05:d018:5:a100:5cc3:4933:fae7:e633|19364,1500]
{20:19:58GMT 99.499s} SetRouteMtu = 1500 (using 1500) for  254496286725356 x 1 [2/2]((2a05:d018:5:a100:5cc3:4933:fae7:e633|19364))Name Unknown
{20:19:58GMT 99.499s} New Primary Server: 254496286725356 x 8 [2/2]((2a05:d018:5:a100:5cc3:4933:fae7:e633|19364))Name Unknown
{20:19:58GMT 99.499s} RxRoute[1]:240211470924386 Comp:2[IP4:34.255.6.19:19364][IP6:2a05:d018:5:a102:25d3:129a:a707:e42d|19364,1500]
{20:19:58GMT 99.499s} New Mission Server: 240211470924386 x 5 [2/2]((2a05:d018:5:a102:25d3:129a:a707:e42d|19364))Name Unknown
{20:19:58GMT 99.499s} Machine::ConnectDirectly:unexpected state: state=0, m_attempt=23.227995, fdis=0: Y Disconnected ** Comp:UDP LastRx=22.23s LastTx=22.23s SyncSent=0.00s  [0] Timeout Disc=0.00s Hold=7.77 srtt=1000ms rttvar=0 drc=Unknown
{20:19:58GMT 99.499s} ConnectToServerActivity: state=WaitingForConnection

As to whether the game works in Windows, I don't know, I don't have a Windows install. I've tried disabling UPnP and setting up Port Forwarding on my Router (and ED), but behaviour is the same as before. The fact that it can't connect may be related to the config setting I used to get it running at all, but it seems to use IPv4 regardless. I've also tried just disabling both protocols (because why not, this stopped making sense a while ago), but with the same result.

[sizeofbool]

{19:17:47GMT 0.058s} ClientBuild 3.3.0.402 EDH r189994 (win64)
{19:17:52GMT 5.232s} GetPortMapping(59702) failed with code 714 (NoSuchEntryInArray)
{19:17:52GMT 5.610s} GetPortMapping(59702) External xx.xx.xx.xx:59702 -> internal 192.168.0.115:59702 (0)
{19:17:53GMT 6.139s} IPv4 is enabled, but address not found
{19:18:00GMT 13.207s} Machine 1 x 2 Local Machine disconnected: shutdown

Can you post more information about your distro, DE, what firewall do you use locally (ufw, iptables)?

What connection type your ISP provides for you to access Internet? (Ethernet, xDSL) Also does it requires additional connection via PPPoE, L2TP\PPTP?

Do you have "white" IP address assigned by your ISP? (white as in public ip address range, not private ip address range)

Your local network private ip address is assigned by DHCP or is it static?

I play ED without any additional setup like UPnP or Port Forwarding. Check your local firewall ruleset and ensure it has rules for unrestricted outbound connections and restricted unknown inbound connections.

...
{20:19:36GMT 77.271s} New machine: 258355904842020 - *Cipher is NULL*
...

My logs don't have this line, so I think you could also have some dependency problem. Check if you have "gnutls" libraries installed. I'm not sure if having Steam Runtime is enough. Could be the reason why you can't establish a secure connection with game servers, except the ones with HTTP 80\443 connections.

It could help (in fact I had to do it myself) if you delete and rebuild prefix for Elite Dangerous. (it is located here "steamapps/compatdata/359320"). Close Steam client before deleting prefix folder. Be sure to backup all Frontier folders in proton user's folders (C:\Users\steamuser...) or at least your keybinds for the game, before you delete prefix folder.

[tsahyt]

@sizeofbool I use Fedora 29, mostly default setup, using GNOME as a DE. Fedora uses firewalld as a frontend for management for iptables (netfilter). I use a fibre connection to the curb, coaxial cable from there into the Modem, to which I connect via Ethernet. It's always been pretty much plug and play on Linux.

From what I understand I do have a "white" IP address, though not a static one from my ISP. Locally, I get an IP address from the modem via DHCP, but it's always the same one.

Firewall settings should be fine, but to be sure I tried opening everything up to see whether it changes anything and it didn't. gnutls is installed, both the 32 and 64 bit version. Note that I get the same problem installing the game through Lutris (followin https://www.youtube.com/watch?v=jG7TUOXZhng).

In the process of trying things I've deleted and rebuilt the prefix several times already, it never changed anything.

[jp7677]

@tsahyt Just a shot in the dark, I remember that I had to add my machine name to my /etc/hosts file on my Fedora 29 box before ED wanted to start. So my /etc/hosts looks now like: cat /etc/hosts

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
127.0.1.1   lnx-desktop lnx-desktop.lan

The ED wine logs were complaining before that addition that my local ip could not be resolved (or similar, don't remember exactly)

Edit: Sorry, I'm seeing just now that extending /etc/hosts was already suggested.

[tsahyt]

@jp7677 I haven't tested it fully yet, i.e. I've only checked whether the menu shows up correctly now, but this seems to have worked, the buttons are no longer grayed out and the debug message at the bottom disappeared! Thank you!

[redmcg]

@tsahyt Did that resolve your issue? If so I'll update my troubleshooting guide (with thanks to @jp7677)

[tsahyt]

@redmcg I've now played the game for several hours, and started it several times. I had no more connection problems and the game always started without fail, so yes my issue seems to be resolved fully. I added 127.0.1.1 myhostname.fullyqualified myhostname to /etc/hosts just like @jp7677 posted above.

The only thing that remains is one or two problems with the mouse. The mouse cursor flickers in menus (it disappears more often than not, but reappears when hovering over some UI element again), and when tabbing out to some other application and tabbing back in, the game doesn't receive any mouse input anymore until I restart it. Those are easy enough to avoid for now though, I just thought I'd mention them regardless.

[jp7677]

@redmcg I wonder what the root cause of the work around with /etc/hosts is. Unfortunately I lack the knowledge about dns, nsswitch and friends to fill a proper bug report in wine. I remember seeing "Failed to resolve your host name IP" (https://github.com/wine-mirror/wine/blob/master/dlls/ws2_32/socket.c#L6787) in the wine logs. The comment in the source was the reason that I tried modifying my hosts file.

@tsahyt Which window mode did you use? I couldn't switch to full screen and ended up using borderless window which worked really well. I can't remember any mouse issues. Note that this was a test with wine staging that comes with Fedora, not Proton.

[tsahyt]

@jp7677 I've got it set to full screen. I remember having some issues with it initially (back when I could only access the combat demo), and I think setting the resolution first and then switching to full screen did the trick.

I've tried it with borderless window now, the mouse problems are gone.

EDIT: The flickering part still happens sometimes, but the focus issues are resolved in borderless window mode.

[redmcg]

@jp7677 The code you linked is within the getaddrinfo function.

It looks like the job of that function is just to convert a host name to an address. Wine doesn't do the translation itself - it calls on the underlying OS. If the underlying OS can't do it then it fails.

I'm curious though, before adding the '/etc/hosts' entry - could you ping your hostname? If so - I might take a look at the source code for ping and see if it's doing something that could be added to wine.

[jp7677]

@redmcg Just tested your suggestion. No, when reverting my modification I cannot ping my host name. So I guess wine isn't doing anything wrong. No idea what the philosophy of the host name in Fedora is. I hadn't experienced any issues before my modifications, so I guess Fedora itself just doesn't rely on the host name. May be Fedora expects that any name resolution should always come from an external DNS server. Though as stated, my knowledge of nsswitch and similar things is rather limited.

[jh97uk]

My keyboard doesnt seem to work in game, on the main menu it seems to be working fine though. Running the latest version of the ED proton build. The mouse doesnt seem to work either, oddly.

[mosteo]

@JamesHealdUK Check that you have bindings, on my first run it was all cleared.

A different issue is that sometimes the keyboard doesn't work at all, not even in the main menu. When this happens a restart does the trick. In my case I estimate it at <20% chance.

[brjhaverkamp]

I noticed the same thing. Keyboard sometimes is completely non-responsive. Only restart works

[kaiarne]

I'm very satisfied with the current state of Elite und Proton except with one thing: Thrustmaster Hotas X is only recognized when mapped via Steam as Gamepad or Xbox Controller. Afaik this only gives me the possibility to use 4 Axis where the Joystick has 5. It's not mapping Start and Select buttons. Starting Elite via proton_run without Steam running lets Elite correctly DETECT a Thrustmaster Hotas X, but I cannot map any joystick activity to any Elite function. "wine control" in the wineprefix shows the windows control dialogue with a perfectly working Thrustmaster with 5 Axis (with and without Steam). No idea, what else I can try. Distribution used: Arch Linux.

[redmcg]

Proton 3.16-7 Beta ED has been released. It just merges the changes made in Proton 3.16-7 Beta. It also includes a fix for the issue found in Proton 3.16-6 Beta ED that prevented running Skyrim & Fallout 4.

[WesCook]

Thanks for keeping this maintained @redmcg. Hopefully we'll eventually see the fixes merged in with WINE or Proton directly, but this'll do for now.