Crashes, 5700 XT AMD Issue?

"

Ygidua wrote:

"

Bl4ckExe wrote:

"

Nagon01 wrote:

Made it to maps and was having a blast, ran a whole lot of maps, no problems what so ever. Until I ran a Peninsula map. Kinda the same kind of open door environment that was my bane while levelling.

Yep. It crashed again. I'm getting really tired of this shit.

GGG, can we please get an update on this? An ETA for a fix? Some sign of life?

I don't think they can fix it. I bet they are waiting for AMD to fix this, and keeping silent until they do, but the reality is AMD won't fix this anytime soon. AMD drivers have so many problems right now, i doubt they will fix half of them.

The driver crash exists since they went DX11. It happens on AMD and NVidia cards and is very typical for games developed under DX9. When the game is ported to Dx11, something breaks and this is almost always the case when you run a video card outside of stock clock.
For years people try to fix that, by underclocking or upvolting their cards, sometimes it helps, sometimes it doesn´t.

Many games have sufferd under it, WOW, ESO, POE, D3 and so on. The issue lies in the games code and API, not so much the drivers of the graphics card, as you can downgrade as much as you want, and the issue remains the same.

That´s why running it with Vulkan, fixes the crashes. GGG only has one chance and that is Vulkan, they ignored these crashes for many years now, as only a minor faction of players was affected and they happened randomly, when a specific draw call was made, in my case, at Delves or big explosions.

But now that there is something in the animation of Tane, many more are crashing, as it´s content we all play. It´s not a coincidence, that the crash always occurs at the exact same moment, like A2 fields or Ledge A1.

If it would be a GPU or driver issue, the crashes would happen at different settings more randomly, but now the common denominator is Tane, who gets summoned in certain maps.

AMD or Nvidia can´t fix this, if they could, RDNA wouldn´t suffer so badly, as it´s a new brand for AMD, they would be silly to overtake the error from GCN. You can track it down at google yourself, these errors started with DX11 and only happen in games using that API.

Not all GPU´s are affected though, mostly those with an overclock, which might hint to a problem with the cards power consumption, maybe there is a spike caused by DX11, who knows.

"

julus wrote:

For guys using Vulkan workaround:

If you find anything that makes the game run faster, or you are facing some issue which you was able to solve (for example game not starting with vulkan but you did something what fix it). Drop me please PM. In case I would be forced to do some guide (GGG releases auto-pickup without fixing the crashes), I would like to have as much information as possible to provide best experience with it.

As a bonus, here is what I have so far to reduce the stuttering a bit at cost of slightly longer loading times (non-steam client only so far). Did not have much time to test it, but initial results were promising.

1) apply the workaround

2) create .bat file with following 4 lines in it in the game directory

@echo off
set DXVK_STATE_CACHE=0
set DXVK_ASYNC=1
start PathOfExile.exe --waitforpreload --gc 2

3) launch the game trough the .bat file

"

julus wrote:

"

FadingDuch wrote:

Can you explain how to (try to) fix it with Vulkan? I got the link to GitHub but can't get the idea what to do with this list.

Page 49 of this forum, first post for quick guide. (I will not post detailed one, unless I will really have to)

Before applying the workaround, set game to run on windowed or windowed fullscreen to avoid some issues.

"

julus wrote:

"

schmonkes wrote:

"

julus wrote:

For guys using Vulkan workaround:

If you find anything that makes the game run faster, or you are facing some issue which you was able to solve (for example game not starting with vulkan but you did something what fix it). Drop me please PM. In case I would be forced to do some guide (GGG releases auto-pickup without fixing the crashes), I would like to have as much information as possible to provide best experience with it.

As a bonus, here is what I have so far to reduce the stuttering a bit at cost of slightly longer loading times (non-steam client only so far). Did not have much time to test it, but initial results were promising.

1) apply the workaround

2) create .bat file with following 4 lines in it in the game directory

@echo off
set DXVK_STATE_CACHE=0
set DXVK_ASYNC=1
start PathOfExile.exe --waitforpreload --gc 2

3) launch the game trough the .bat file

Did as you said, all the comments. Actually i think i might delete it. Overall it seems really smooth. But when you start the fights with Metamorph Bosses the shader kinda collaps, framedrops to hell and beneath and the complete stutter-linux-experience. it wasn't that bad without the parameter. Might be my personal impression and it might work for others.

Thanks for the report, as mentioned I did not tested it much (did not had time to actually go to metamorph with the above settings), but it appeared more fluent at the first glance.

However, even without these I got some metamorphs which almost FPS dropped-killed me, while the previous and next one was without a hitch (usually got this problem on maps with rain/wet surface). I still have some combinations to go trough (got reports that 32bit is better on 64bit system, and also that vxdk with poe specific patches behaves better)

Also I wonder if some of these "stutters" are result of the code which is causing nvidia/amd cards to crash, but vulkan handles with only fps drop.

"

Batmanf0re wrote:

Let me know if this is an inappropriate or too rash response, but I think we should give them thumbs down reviews on steam. Right now, their recent ratings are at overwhelmingly positive and they did an announcement a couple of days ago that this was one of their smoothest launches ever without even mentioning this issue. I get this is a huge issue that will take a long time to fix, but it definitely feels like we've been cut off like an infected leg. At first, this seemed like a small bug with the league mechanic, but this is a bigger issue that they let pile up for a long time. It's only now that it's biting them in the ass to the point that it's unplayable for us. It really sucks since this is my main game, and I was looking forward to this league a lot. I'm going to leave a negative review on steam until the issue is either fixed or they give us a rough ETA. I think that's fair. If that's the wrong thing to do, let me know.