Some news on Wine; bug 46208 has been fixed:
https://bugs.winehq.org/show_bug.cgi?id=46208
This means from 4.2, the futex patch from wine staging will no longer be required. However, wine staging will still be required for the NormalizeString functionality (required for Keyboard functionality).
I also found a bug introduced in 4.1. If you are using an Intel CPU, the registry value of PROCESSOR_ARCHITECTURE is set incorrectly. This results in the launcher only offering the demo (as it thinks your machine is 32-bit). I have submitted a fix to the mailing list.
For now, the work-around is to fix the PROCESSOR_ARCHITECTURE value manually (it should be "AMD64"). Or to avoid 4.1.
Also - an observation I thought I'd share: if you launch ED with the '/steam' option (for example: 'wine64 EDLaunch /novr /steam') - then the launcher will display correctly (as in the launcher glitches don't occur). So that's odd.
I read a little about that a month ago, is the performance decent with the method they settled with? I don't understand much but from what I read the futex patch performed better than the alternative but they didn't want to use the futex method due to other things?
Also considering the whole idea behind getting this sorted in wine devel was for it all to be eventually pulled into proton someday, if NormalizeString & other stuff can't yet be pulled upstream is there any chance of them being looked at again with Proton?
Wanted to just quickly dip in and add that Nvidia *finally* fixed compute shaders regression that caused big disformations on ice planets on Windows (418.81 driver). It is worth to look after when Linux driver update lands if that fixes those issues we had with Engineer bases being sunk into the ground.
Latest Linux driver is actually 418 branch a few days before the Windows one however that still has the issue. Maybe the next one will have it, I got my second account in the bubble at Bakers Prospect ready to test differences if another drops soon.
I've never used Lutris myself, so I'm not entirely sure, but x86_64 might refer to the type of prefix (as in it'll support 64-bit). The ED Launcher however is a 32-bit .NET app that needs to be ran as a 64-bit process; so it needs to be started with wine64. But I get the impression from this post:
that you can't use wine64 from within Lutris. I think you'll need to run it manually from a Terminal. Hopefully someone here with experience running under Lutris will be able to comment with a bit more authority.
Yes, you can but you just need to set it to "Custom" and manually direct it to the wine64 executable.