So since this latest mirror on SiSi, my client crashes after docking and undocking a few times in M-OEE8.
The client starts to “load” resources (the circle thing on the buttom left where the clock is) and then after a while it freezes or if I dock I get a black screen and the client doesn’t respond anymore.
My machine runs on Linux Mint 19 and kernel 4.15.0-36-generic (Ubuntu 18.4 LTS).
Radeon RX 480 8GB with amdgpu
16GB DD4 RAM
Toshiba RD400 M2 drive @PCI-E 4x
Gigabyte Z270X Aorus Gaming 7
Core i5 7500
Wine: wine-3.18 (Staging) from wineHQ
and EVE with the windoze launcher
I have the latest vulkan, mesa and mono pakets installed, as explained in the installation guide.
Any ideas?
I just saw you’re using WINE Staging. Have you tried using WINE Stable or Development? WINE Staging is full of experimental patches, which is why I don’t use it. It’s prone to give troubles due to its nature.
And is this also happening with Tranquility or is this only happening with the test server?
So i was having a problem while running eve with the graphics turned up that my computer crashed. After setting eve to performance mode instead of making it look pretty I have not had a single problem since. I don’t know what your running it at but if you have stuff cranked up its worth a shot.
Same problem here. EVE works ok for some time, then “resource loading” and then, if i try to dock/undock or use a gate, game freeze. Switching from staging version didn’t help. Resource Cache is disabled.
I switched to wineHQ stable and only got 2 freezes since then and only in M-OEE8. The 5 trillion keepstars may have something to do with it.
Purge (as in apt purge) wineHQ staging and install wineHQ stable, it would work much better (and with a certain modification sponsored by Vulkan™ even in dx11).
There is a bug in the launcher: bugs.winehq.org/show_bug.cgi?id=45939
Basically if you leave the launcher open, there will be a file descriptor leak that will eventually lock up the wineserver after about an hour or so. Simply close the launcher after you start the client, and the bug goes away.
Comment Reply