doitsujin
WWE 2k19: Freeze in fullscreen when resuming Windows from sleep
Hi just a small issue I've been recently having that I never had before. playing wwe 2k19 on AMD it is necessary to use dxvk because if you don't there will be gfx issues. I've been using it on amd for a couple years with dxvk with no issues resuming from a sleep or locked states but recently when I do this the games screen will freeze until I alt+tab out. This will cause the games screen to unfreeze (music is always playing) but when you enter fullscreen again it freezes again.
There is only one way I can fix it which is to use (Borderless Gaming) which makes it fullscreen without freezing but gameplay will be locked at 40 fps. If you alt tab back out to windowed and back in to fullscreen again it will finally unfreeze and play at a full 60.
If possible I'd like to avoid doing all that and for it just to work again like it used to before a while ago because I played it for years and the screen would never freeze
Also if I remove dxvk completely it will have no problem resuming from sleep or locked state so it mush be dxvk causing the issue or atleast Vulkan?
problem.
What should I do driver wise? I've tried to revert back to older versions but I still suffer the same problem
Start with providing the DXVK logs that the issue template asked for.
WWE2K19_x64_dxgi.log WWE2K19_x64_d3d11.log
please let me know what else i can do. I used ddu to completely uninstall my driver but after using a known stable driver version im still getting a screen freeze when I wake up my console
err: D3D11SwapChain: Failed to recreate swap chain: -13
Try installing the version 23.8.2 driver if you haven't already been so far back
err: D3D11SwapChain: Failed to recreate swap chain: -13
Try installing the version 23.8.2 driver if you haven't already been so far back
Sorry is that the version of my AMD Gfx driver or an older vsrsion of dxvk
AMD driver
Damn, I just reverted back all the way to that 23.8.2 driver and still the same results.
Which makes no sense as I've used 23.10 personally and every version between until this latest update and they all functioned fine.
Is there any way a windows update could have caused this cuz that's all I can think of? This problem just randomly started happening out of the blue when I had to force my 1080p screen to 720 to play a game that wouldn't go to 720 in fullscreen so the only way to to change windows resolution. After that this started happening think.
But ya I've whipped my drivers completely and tried 3-4 older versions of my amd driver that I know work for a fact so I'm pretty stumped
AMD driver
I've now tried 3 different drivers and still get the same result. dxvk2.2 was the one i always used and that would at least let me do the borderless gaming trick to make it work again however i tried dxvk 2.5.3 and now the game will just crash upon resume. every problem i have seems to be dxvk itself because fully removing it allows me to resume my game no problem (problem is i need dxvk so theres no gfx glitches) here are updated logs please help! im going crazy trying to fix this issue
WWE2K19_x64_dxgi.log WWE2K19_x64_d3d11.log
Either way, this is a driver bug.
What can I do about it? Got any ideas? I've literally changed the driver and nothing fixes it. Tried to update my Vulkan runtime and still nothing. Changing the graphics at all while in game also causes the screen to freeze.
What can I do about it? Got any ideas?
The Linux driver does not have that problem.
What can I do about it? Got any ideas?
The Linux driver does not have that problem.
Right? But how does that help me. I need suggestions lol. I know for a fact all these driver versions I used to use work. As an expert what do you think could have changed that I should look for to solve this issue?
Newer DXVK versions do something that AMDs Vulkan driver cannot handle despite the fact that it's perfectly valid. We don't know what it is though and DXVK is built for Linux.
Newer DXVK versions do something that AMDs Vulkan driver cannot handle despite the fact that it's perfectly valid. We don't know what it is though and DXVK is built for Linux.
Fair enough. Thank you for your insight and like you say dxvk2.2 is much more stable thank the newer releases.
Very happy to announce that recently this issue has stopped due to windows finally getting their shit together. Not sure what update did it but I no longer have this issue and I'm still using dxvk 2.2 which is the best one for this game in my experience