[Official] WINE info thread
Bump
This issue is still wide open for me. Trying reinstalling the game and changing the Proton version to the latest major update that just released. Still the exact same error. |
|
Didn't encounter the same error today, but still got some random crash, even when mapping & fighting.
err: DxvkMemoryAllocator: Memory allocation failed Size: 2579456 Alignment: 256 Mem flags: 0x7 Mem types: 0x681 wine: Unhandled exception 0x20474343 in thread 32 at address 0x7b4503f7 (thread 0032), starting debugger... Unhandled exception: 0x20474343 in 64-bit code (0x000000007b4503f7). Quite irritating, when you consider a crash in a synthetised map far away from the nexus. |
|
Well, same error in the end, even after last patch.
In Temple map, this error happened just after the entrance after a few steps in the map. Could have reproduced the bug 6 times, with different version of Wine, 4.4 staging, 4.3 stable, tkg 4.4, as well as dxvk 1.0.1 and 1.0. Tried with -gc2 startup option, but it didn't change anything. For as long as there isn't a reliable solution, I guess I won't play the game anymore, every map feels like a gamble, and when a crash far from the Nexus occurs, it's very legit reason to ragequit on the spot. Last edited by vm4na#2703 on Mar 28, 2019, 7:47:07 PM
|
|
" I encountered pretty the exact same error msg.I tried like 100 kinds of configuration(including underclocking gpu,all kinds of different dxvk/wine config,patched dxvk,updating graphics driver...)and the same issue persists. I even managed to launch the standalone version with proton and still the same error.Even when the error doesn't show up, i'm still getting only 20-30 fps, while on Win 7 i can get 40-60 with the exact same ingame settings. What's interesting is that i used to encounter the same error on win 7,but after i underclocked my gpu and used -gc2 it never showed up again.Not sure if its the former or the latter that fixed it though. My PC specs: CPU:Intel core quad Q8300 GPU:GTX 650 OS:ubuntu 18.04 Graphics driver:418.43 |
|
For reference, here's the little script that I source in my really well working setup:
--- export WINEPREFIX=/dump/poe export WINE=/home/$USER/.local/share/lutris/runners/wine/tkg-4.3-x86_64/bin/wine export wine=$WINE export DXVK_HUD=fps export DXVK_ASYNC=1 export DXVK_STATE_CACHE=0 export WINEESYNC=1 cd "$WINEPREFIX/drive_c/Program Files (x86)/Grinding Gear Games/Path of Exile" --- Then I run: $WINE PathOfExile_x64.exe The reason for letting the last step be manual is that sometimes I have to try running PathOfExile_x64.exe multiple times before it boots at all (else just crashes on startup). I have not found a cure for this. Besides that everything seems to be working perfectly! So standalone but with a wine version installed via lutris. Looking at winetricks it seems that I've installed the following: * dbghelp * dxvk (but I'm actually using https://github.com/jomihaka/dxvk-poe-hack/commits/master) * msxml6 * riched30 * usp10 * vcrun2015 * xact I also set HKCU/Software/Wine/Direct3D/VideoMemorysize to 4096 to avoid it guessing a too low value which may cause early memory allocation failures. I'll be happy to answer questions in game, if I'm online and not dying to evil bad mobs: @btw |
|
" 1440p bug looks to be fixed according to latest release notes - https://github.com/doitsujin/dxvk/releases/tag/v1.0.2 Last edited by efirps#7063 on Apr 1, 2019, 4:19:33 PM
|
|
For all the people struggling with the error messages and the Memory Allocation errors from dxvk, I can recommend trying a desktop with compositor disabled.
I used to run this on Gnome 3 all the time without problems, but since a while I was getting the exact same errors. So just a while ago I tried xfce and then with compositing disabled. This mainly since I can't find a way to disable compositing in Gnome 3. After disabling the compositing I was able to play for over an hour and switch multiple zones. When enabling it again or switching back to Gnome 3 sometimes I was even unable to log in my character before seeing err: DxvkMemoryAllocator: Memory allocation failed in the terminal. I'll give it another try to make sure but I think it might help to disable that compositor if you can (damn you Gnome 3!) --- Just tried a bit more. I tried to increase shadow settings to include GI. But then I was again experiencing Memory Allocation errors. After setting the shadows back to just shadows and quality to low I can play and switch zones again without problems. When I for example have shadows set higher, I will have a huge fps drop in Ossuary. There might be more, similar ones. For now I'll just keep my gfx settings low and my compositor disabled :) -- Edit Well, I also increased my RAM size (16GB now) and since then I have been able to play quite some content. This is also disregarding the compositor since I am getting the same mileage with and without to be honest. However I hardly ever exit the game myself, usually it's a Memory Allocation error still at some point. Last edited by activate2010#5690 on Apr 14, 2019, 5:23:11 AM
|
|
Hey Nymphzetamine, you seem pretty knowledgeable about this stuff. Do you have any idea what's causing this "swapchain" error I keep getting? My original post is on page 225. Unlike others here who can at least get the game running, I have not been able to get the game to run in DX11 mode since summer of last year (before that I was using Windows), trying on and off every few weeks. Though crash-prone, DX9EX worked perfectly fine for me.
I'm to the point where I'd be willing to pay someone for one on one help if they end up resolving the issue in the end. |
|
" Turning off DXVK helped me (Lutris->PoE->right click->configure->Runner options tab->Enable DXVK checkbox) |
|
Ok quick summary from my last tests. I've tried to play for the last 2 days, after the release of patch 3.6.3b.
Wine version 4.5 staging as well as dxvk 1.0.2 were released, so i'd have good hopes that some issues were resolved. So far, there is still a fair amount of crash, mostly after a map has been loaded, haven't seen them during combat. The errors aren't quite always the same as before : My lutris config, on Arch linux : " And a custom prelaunch script, to remove the cache, as recommended for this kind of problems on windows : " Other settings include a registry key HKEY_CURRENT_USER\Software\Wine\Direct3D\VideoMemorySize = 2048, since my graphic card only have this amount of virtual memory I don't see major improvements, my guess is that the new optimizations and changes of their directx11 driver from version 3.6 is the root cause of all those problems. Another guess might be the low amount of memory on my graphic card, which may increase the frequency of the crashs. I had none of those crashs on Betrayal. So far, my only hope is another patch from GGG, hopefully people on windows will still have some of those problems. |
|