In Windows, i get 30 to 50 fps with Horizons, landing on planets and everything.
In Linux, i'm getting a steady 30 fps without Horizons.
In Linux with Horizons, i'm getting 0 to 30 fps with lots of stuttering and freezing especially if I go near a planet.
The game is only playable in Linux for me without Horizons. If I try to land on a planet, I get stuck in the 2 fps range and have to exit the game.
I updated dxvk as RedMcG suggested in his last comment to me. The only change I noticed was that the planet generation at startup made it to about 20% then just suddenly completed and went to the menu, which means it took less time to complete.
I would like to think there is something wrong that can be fixed to improve the performance rather than it being an unavoidable consequence of using proton, dxvk, wine, etc. to run ED in Linux. It seems that there is something specifically related to Horizons and planets that is not working correctly in Linux considering the drastic difference in performance from Windows.
Here it is running without Horizons:
Is this by chance because the servers aren't up yet? BTW, live stream in a few minutes.
Just a reminder that Linux is not an officially supported platform, and we are currently investigating these issues. We wanted to let you know so you don't too much time on something that we can not support, and that could potentially change.
Now you've dumped Mac OSX support (which was a stretch goal), why not transfer that effort to Linux instead? At least compute shaders will be supported![]()
I think they might have broken Wine playing - it looks like there is something broken with the new update. I am getting errors with connections every time. I'm trying to build a new prefix with the new installer, to see what happens.
OK, a brand new prefix, following the exact same guidelines as previously, and working fine until today's client update, has confirmed breaking Linux.
Edit: it looks like the new installer has created an additional machine guid that wasn't previously present and matches neither of the existing machine guid values in the registry. I think they may be using a new cryptography API to get this machine Guid and it's not matching either of the existing ones.
I'm not getting a cdc error but I'm still getting the msg I need to use the launcher when I am using the launcher.
Of course it also says: Server Status: Issues Detected
Yeah, I noticed that as well, so it's possible that's the problem. I noticed that I now had 3 different guids for MachineGuid after setting up a new prefix. Harmonizing them all to the same value did not have any effect.