Quoting: libgradev@Shmerl: can you easily compile a later kernel to test?

According to @lod above, newer kernel doesn't help it. Did you have a chance to test it with your RX 480 to confirm the freeze?

I'll update bug report once that will be more clear.

By the way. I saw somewhere that Vega got better GPU reset support, so may be that's why it's not causing a hard freeze but only soft freezes for some?

I dont get a freeze where I had to reboot the OS (like the old wine builds e.g. near hanging man tree). Since 2.22 on sometimes (e.g. after a quick travel) the screen stands still in fullscreenmode and dont accept input from keyboard or mouse. I can alt-tab to the terminal and then if I move the mouse I look around in TW3.

With the compiled master and the patches/hotfixes Shmerl mentioned, I played in windowed mode without an issue (despite the performance) for at least three hours. I will do more testing the next days :)

Quoting: maspeberWith the compiled master and the patches/hotfixes Shmerl mentioned, I played in windowed mode without an issue (despite the performance) for at least three hours. I will do more testing the next days :)

Did you try the save with rotfiends? It's not about how long you play, but about specific effects causing some issues.

So far I posted in the bugs, that on Vega this freeze is not reproducible. Feel free to add your hardware and driver details there.

https://bugs.freedesktop.org/show_bug.cgi?id=104193
https://bugs.winehq.org/show_bug.cgi?id=43872

sorry, got a freeze with "Moderhäuten" ("Rotfiend")

I played yesterday another two hours without any issue. I fought ghouls, Alghouls, Harpies, "Verschlinger" (similar to Moderhäuten - Rotfiend). Than I wanted to be sure and try your save. I cant read it (I play on GOTY and I think the save game isnt compatible) and than I ported to "Reuseninsel" (the Island with the tower where Y do Keiras (?) Quest with the "Pestae"). I fought 6 Moderhäute and got with the last one the freeze :( I was able to alt-tab to my terminal and exit wine.

Sorry, I play on German so I dont know the English names - but "Moderhäute" should be "Rotfiends".

Quoting: maspeberThan I wanted to be sure and try your save. I cant read it (I play on GOTY and I think the save game isnt compatible)

It is a GOTY save (GOG release).

Quoting: maspeberand than I ported to "Reuseninsel" (the Island with the tower where Y do Keiras (?) Quest with the "Pestae"). I fought 6 Moderhäute and got with the last one the freeze :( I was able to alt-tab to my terminal and exit wine.

I think it allows exiting on Vega, because it supports better GPU reset than Polaris. But at least we know now, that freeze still happens. Can you please comment with your findings in both bugs?

This is a great topic, and thanks to all of you who works on this.
I decided to test it with the GOG version 1.31.
- i5-2500K @ 4.2 GHz
- GTX 780 @ 993 MHz
- Kernel 4.14.5
- Nvidia Blob 384.98
- Wine-staging 2.21

Like so many have reported, performance is very weak i have between ~12 and ~18 fps with most of the settings on MAX (HBAO+, Vsync Off).
I have ~20 and ~26 fps with settings on LOW.
My GPU utilization is around ~70% and my CPU ~50%.
It's frustrating when it runs pretty well on Windows. (The last time i tried, about 2 years ago). Except the poor performance, the game looks nice and no bugs or missing textures at the moment.

So it's the Nvidia's fault here and no workarounds ?

Anyway, my next Graphic Card will be an AMD one as i said. ^_^

Quoting: hilparaReading the bug description, I still don’t know what to do. It seams that it happens only sometimes and it‘s quite rare. I‘ll try to make a new prefix and hope that it helps.

So I finally had time to check again tw3. This bug still annoys me. If I use dumbxinputemu to get my gamepad to work and override from winecfg the xinput1_3.dll the witcher won't start complaining err:ntdll:RtlpWaitForCriticalSection....
If I don't override the dll tw3 starts normally. I have also tried different wine versions and it always "crashes" if I override it.

If i recall correctly this happens when you copy the 32bit ddls to the x64 bin directory. Make sure you copy the 64-bit dlls ("file xinput1_3.dll" should tell if its the right one.

Not sure if needed here but did you try to copy and override the other xinput dlls as well?