[Official] WINE info thread

Crashing on the Legion is no longer happening for me since the last couple of patches.

The game runs pretty well.

I'm using DXVK 1.2.1, with a TKG WINE 3.9 runner through Lutris, has anyone found improvements with a later version of Wine?

running with latest dxvk and wine 4.9, no problems so far

Anyone else having problems with what seems to be a GPU memory leak? A few times today I had my whole screen freeze and my computer become completely unresponsive, that behaviour got more frequent throughout the day and now I can't even log into a character anymore.

I suspect it's a memory leak because when it happens the game takes up all my vRAM and the GPU utilization drops to near 0%, whereas during normal gameplay vRAM is almost filled up but not quite and GPU utilization is nearly always 100%

Already tried deleting both the game's and DXVK's shader caches to no avail, updating to WINE 4.10 + DXVK 1.2.1 didn't help either.

EDIT: nvm, did a more thorough cleanup of my prefix and the problem seems to be gone. I just hope it stays that way now.

EDIT2: nope, it keeps coming back no matter what, really frustrating

Hi! I have started playing PoE a few weeks ago. It crashed and lagged every now and then but it was bearable. But lately it just got ridiculous.

It takes on average 15 to 30 minutes to be able to actually start playing instead of crashing.

I have lost my entire first completed Temple without ever being able to set foot in it because it crashed every time I entered one of the portals. :(

Other times I just get 3-6 minute loading screens and then being thrown out to the server selection screen. This is the most common error, that does not always lead to crash. Sometimes I have to "OK" it 20-30 times during loading screens and then it either crashes or doesn't:



And here are some others I caught, that both lead to crash:




And most often it just crashes without an error message. I'm at the point where the game is un-enjoyable, when I'm losing temples due to constant crashes, or crash with Unique items laying on the floor and then keep crashing for so long that by the time I managed to get back there the map has already reset. :(


Also, I have another issue where spawning in enemies will just cause so crazy lag that the game goes unresponsive for anywhere between 3 seconds to half a minute. I have failed several temple incursions due to getting 10-15 sec lags while trying to kill the architect, and obviously dying. So any advice on this would be great too.


I'm playing via Steamplay. My system:

Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
NVIDIA Corporation GeForce GTX 750 Ti/PCIe/SSE2
16 GB RAM
Kernel Version: 5.1.15-arch1-1-ARCH


I tried to look back in this thread but it's huge and I'm a very slow reader, so sorry if I missed something.

"

StormHUN wrote:

Hi! I have started playing PoE a few weeks ago. It crashed and lagged every now and then but it was bearable. But lately it just got ridiculous.

It takes on average 15 to 30 minutes to be able to actually start playing instead of crashing.

[...]

Hey man, I've been getting those occasionally too apart from the memory leak-ish freezes. My research so far leads me to believe this is related to this particular issue regarding Nvidia GPUs and DXVK, it would be great if you could check your DXVK logs and confirm that you're getting the memory allocation errors particular to that issue and make a report in that thread if that's the case and you find the time to do it.

Other than that the issue doesn't seem to have any solution in sight(perhaps buying a Navi as soon as they hit the market?) except for maybe deleting your shader caches and closing all applications while playing(playing without PoB, poe.ninja, poe.lab, poe.trade, in 2019? Well...), which merely make the game take somewhat longer to crash.

But I feel you. I was really pumped for this league but losing maps and stuff to these constant crashes is just completely demoralizing.

My game refuses to boot in lutris now. Have a ssd for windows and games now.

"

mathw wrote:

"

StormHUN wrote:

Hi! I have started playing PoE a few weeks ago. It crashed and lagged every now and then but it was bearable. But lately it just got ridiculous.

It takes on average 15 to 30 minutes to be able to actually start playing instead of crashing.

[...]

Hey man, I've been getting those occasionally too apart from the memory leak-ish freezes. My research so far leads me to believe this is related to this particular issue regarding Nvidia GPUs and DXVK[...]

I HAVE FOUND THE FIX!!!

To fix constant crashing, use this launch option:
PROTON_USE_WINE3D=1 %command%

I also got the vast majority of my lag fixed, but not sure exactly by which option because I added an entire line of recommended Steam launch options that are supposed to optimize this:
PROTON_NO_ESYNC=1 %command% --nologo --waitforpreload --gc 2 --noasync --waitforpreload

So my combined launch option now is like this:
PROTON_NO_ESYNC=1 PROTON_USE_WINE3D=1 %command% --nologo --waitforpreload --gc 2 --noasync --waitforpreload

I don't know if --waitforpreload being listed twice is an oversight or it needs to be like that, but it works so I leave it like this.

With these two my launch time for the game, and loading screen times increased to about 3 times to what they used to be... but once things load there is very little to no lag, and I haven't crashed once since.

Both suggestions were found here: https://www.protondb.com/app/238960

https://steamcommunity.com/games/221410/announcements/detail/1602634609636894200

looks really promising, could solve stutters for amd users without having to use the dxvk patch.

"

StormHUN wrote:

To fix constant crashing, use this launch option:
PROTON_USE_WINE3D=1 %command%

I also got the vast majority of my lag fixed, but not sure exactly by which option because I added an entire line of recommended Steam launch options that are supposed to optimize this:
PROTON_NO_ESYNC=1 %command% --nologo --waitforpreload --gc 2 --noasync --waitforpreload

So my combined launch option now is like this:
PROTON_NO_ESYNC=1 PROTON_USE_WINE3D=1 %command% --nologo --waitforpreload --gc 2 --noasync --waitforpreload

Ok, just some of observations:
1- the correct variable should be PROTON_USE_WINED3D, setting PROTON_USE_WINE3D shouldn't do anything at all
2- Setting PROTON_USE_WINED3D will cause wine to use its own implementation of D3D11, which is usually really slow when compared to DXVK. But then again, if you set the wrong variable this should have no effect and you're still using DXVK.
3- The double --waitforpreload shouldn't be necessary, yeah
4- The increase in loading times is expected. All those launch options are basically telling the game to always load everything during the loading screen rather than on-the-fly and also keep some unnecessary data for a bit longer before dumping it(which I'd guess happens mostly during loading screens)

But the fact that setting all that stuff telling the game to be conservative with un/loading resources fixed your crashes is really interesting. I'll try to play around with them too when I have time and see if I can reproduce your results, could be potentially useful info to the DXVK folks.

"

mathw wrote:

Ok, just some of observations:
1- the correct variable should be PROTON_USE_WINED3D, setting PROTON_USE_WINE3D shouldn't do anything at all

Well, catch this then:

I did some experimenting, and here is the result:

No launch options:
- Long loading times
- Tons of lag
- Very frequent crashes

All the options from above:
- Very long loading times
- Very little lag
- Very rare crashes

Only PROTON_USE_WINE3D:
- Medium loading times
- Very little to no lag
- No crashes so far

"

2- Setting PROTON_USE_WINED3D will cause wine to use its own implementation of D3D11, which is usually really slow when compared to DXVK.

I thought that was the idea, because the issues are supposedly stemming from DXVK somehow.

"

But then again, if you set the wrong variable this should have no effect and you're still using DXVK.

I tried adding the missing D. The result was extremely long loading times, so much so that it took 4 tries to log in because I was constantly timing out, and then once one, only 14 FPS with the autoscaling already minimizing my graphics down to hell.

So I removed the D and everything is fine again.

So my guess is that apparently "WINE3D" is a different option than "WINED3D", because the latter only made things worse while the former makes a big improvement.