What distro are you on? If you’re using Arch or Manjaro I can provide a working PKGBUILD.
Also no worries if you can’t easily get the compiled Wine running. Turns out this has been a known bug for a long time (an issue was opened in 2011; they attempted a fix in 2019 but it didn’t work).
I’m on ubuntu 20.04.
I solved my conformance test problems because I was being an idiot 
Will try to submit this upstream in time for wine 6.20, although the maintainers mentioned that this is a particularly difficult part of the codebase to work with correctly and get things accepted
I applied your patch to wine-staging-6.19, sisi works for me now under linux! Hell yeah!
Probably I will use this wine in the future
UPD im using gentoo
Glad to hear it! Note that the original patch could -possibly- break other things, although it’s already a super weird edge case which is why it went mostly unnoticed for so long. A more granular and “correct” patch has been submitted upstream and is waiting for review, I’ll update the thread if it ends up getting merged
Of course i am understand that wine-staging with custom homemade patches is something that can break things. That is the reason why I am keeping a dozen versions of wine, thanks to easy way to do this in gentoo.
What if it will not be merged? any chances to see whats wrong then?
FCK … same for TQ after todays patch … lol …
It seems like today’s patch broke my lutris/linux setup. It will start the launcher, but the game won’t load. Anyone else with that problem after todays patch?
Same for me was using proton 6.16 GE. Launcher loads,Steam says game is running, that’s it…
For the issue today (2021-10-13) see Client start exception after today update - steam which has a workaround.
Is there a linux w/around for this or only windows?
That’s great man! Sorry I couldn’t compile it correctly in time. Kind of a head scratcher for me there. Anyway, I suspect this patch will help play the game moving forward starting today. (see below).
Yep. Same here. I’m running Lutris as well.
So, this happened before on SiSi. And thanks to @Renard_DuGaulle 's work in diagnosing, if you copy launchdarkly_client.pyd to the SharedCache/tq location, the game will continue to work. You will have to copy this file every time you run the Eve client, as it does get deleted when Launcher boots (and maybe on other occasions).
The one liner on my computer from my user’s home directory is is: cp Games/eve-online/drive_c/EVE/SharedCache/tq/bin64/launchdarkly_client.pyd Games/eve-online/drive_c/EVE/SharedCache/tq/
I’m using the default Lutris folder locations.
I’m extrapolating a bit, given that the fix was the same as it was when the issue hit SiSi. But, it looks like his patch will hit wine 6.20, if it gets accepted. So, if it does get accepted, then that version of wine will most likely fix the issue.
I guess someone who was successful in applying the patch (and compiling the wine version) could let us know if the patch also fixes tq.
That works. Not convenient, but perhaps there will be a permanent fix later.
Yep. I agree that it’s uncomfortable/inconvenient. But, it works.
Renard submitted a patch which may make it to wine 6.20. From what I understand, it may be a permanent fix.
Excuse my linux illiteracy but where do you find launchdarkly_client.pyd?
standard is: ~/.local/share/Steam/steamapps/compatdata/8500/pfx/drive_c/EVE/SharedCache/tq/bin64/launchdarkly_client.pyd . or simmilar in ~/.steam/ … for me is ~/.steam/steam/steamapps/common/Eve Online/SharedCache/tq/bin64
Wow, so glad I started looking into this weeks ago then. Thanks everyone for reporting the issues with Sisi or we’d be way behind on this fix
I copied the file,and everything works even after a reboot. So the file being deleted seems to be different on different systems. On my system, it doesn’t get deleted.
This workaround works
Working ty