Well, that certainly didn't take long did it? Valve have already put up an update to Proton Hotfix, that works around the crashing issue in DirectX 12 in The Witcher 3 next-gen on Steam Deck.
Now it will work out of the box without the need for any workarounds. You can simply uncheck any forced compatibility option you had set on it, as Valve set it to Proton Hotfix by default now for the Steam Deck. You can also install Proton Hotfix yourself in your Steam Library, and set it on the game manually in the compatibility menu if you have any issues.
Just imagine if CD Projekt gave Valve a bit of early notice and testing on this, it could've worked right away.
YouTube videos require cookies, you must accept their cookies to view. View cookie preferences.
Direct Link
Direct Link
There's still numerous issues with the new update though across all platforms, with masses of complaints about it. CD Projekt have announced that they're looking into it. Hopefully it won't be too long before it gets properly stable once again. Nice that it was a free update but they really need to do some more QA testing before pushing things out.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
For me with the fix on my arch with rx6600xt and r1600X it hangs and gets the whole screen corrupted.
I can only go then to the console and kill the game. And it seems that I only can reboot to get to the desktop (restarting the desktop doesn't seem to work).
It needs a little more work. I haven't test the performance, but I tried all at maximum and it seems ok (I used to play it with a gf660, so I don't require hight fps).
I can only go then to the console and kill the game. And it seems that I only can reboot to get to the desktop (restarting the desktop doesn't seem to work).
It needs a little more work. I haven't test the performance, but I tried all at maximum and it seems ok (I used to play it with a gf660, so I don't require hight fps).
0 Likes
So the AcquireWrappedResources performance hit in D3D11On12 is still a thing?
0 Likes
Avehicle7887 Dec 15, 2022
Quoting: ShmerlPerformance experience with DX12 version is really bad. DX11 one works well.
Just gave it a shot with the newly released vkd3d-proton 2.8, game loads fine however fps is very unstable compared to dx11.
I'd say right now the only reason to use the DX12 version is to enable FSR2.
1 Likes, Who?
Mohandevir Dec 15, 2022
Quoting: Avehicle7887Quoting: ShmerlPerformance experience with DX12 version is really bad. DX11 one works well.
Just gave it a shot with the newly released vkd3d-proton 2.8, game loads fine however fps is very unstable compared to dx11.
I'd say right now the only reason to use the DX12 version is to enable FSR2.
Even that... I'm unconvinced. The image looked too blurry. I still get that 40fps mark, though. I also tried comparing that setup (FSR2 in automatic mode) to Steam Deck's FSR (3) with TAAU AA at 1152*768 resolution. It looks better and feels smoother, imo. I'll try a more extensive play session later to confirm it's not just a weird occurence, but the Steam Deck's internal temps were oscillating between 60 and 68deg with this setup while with FSR2, it got regularly above 80deg with the fan noise typical with these temps.
Anyone to comfirm/deny?
Edit: I stand on my first impressions. DX12 at medium settings with TAAU AA, 1158x768 resolution and the Steam Deck's FSR (3) , it runs and looks much better than in-game FSR2 automatic with similar settings, for this game. Something wrong with this FSR2 implementation?
Last edited by Mohandevir on 16 December 2022 at 7:02 pm UTC
0 Likes
Quoting: MohandevirQuoting: Avehicle7887Quoting: ShmerlPerformance experience with DX12 version is really bad. DX11 one works well.
Just gave it a shot with the newly released vkd3d-proton 2.8, game loads fine however fps is very unstable compared to dx11.
I'd say right now the only reason to use the DX12 version is to enable FSR2.
Even that... I'm unconvinced. The image looked too blurry. I still get that 40fps mark, though. I also tried comparing that setup (FSR2 in automatic mode) to Steam Deck's FSR (3) with TAAU AA at 1152*768 resolution. It looks better and feels smoother, imo. I'll try a more extensive play session later to confirm it's not just a weird occurence, but the Steam Deck's internal temps were oscillating between 60 and 68deg with this setup while with FSR2, it got regularly above 80deg with the fan noise typical with these temps.
Anyone to comfirm/deny?
I've did a quick Windows install just to try out there for sanity, same problems when using FSR2 on an Nvidia card...
CDPR really did it again lol.
1 Likes, Who?
Played some on both DX12 and DX11 today. DX11 gives me slightly higher fps, but it's not really noticeable and it looks exactly the same. Do have to say, the Ultra+ settings are very nice for draw distance but they are brutal on fps. I'm managing about 65 fps with it around the White Orchard area. I think this is why I have pretty stable fps and similar numbers to DX11. I hammering the GPU and not really giving it a chance to become CPU bound. As far as I understand, the real problem starts when D3D11on12 starts hitting core limits.
Honestly, I don't understand why they went the D3D11on12 route. They could have (and it's what I expected) back-ported the DX12 support from CP2077 into the game for a more solid implementation. Instead using a translation layer, that microsoft itself says not to use, and making the game cpu bound seems like a bad choice when you're trying to repair some of the reputation damage for prior releases. I imagine it would have been better received if they never put the RT in and stuck with the DX11 version that still has a good list of graphical improvements.
Honestly, I don't understand why they went the D3D11on12 route. They could have (and it's what I expected) back-ported the DX12 support from CP2077 into the game for a more solid implementation. Instead using a translation layer, that microsoft itself says not to use, and making the game cpu bound seems like a bad choice when you're trying to repair some of the reputation damage for prior releases. I imagine it would have been better received if they never put the RT in and stuck with the DX11 version that still has a good list of graphical improvements.
0 Likes
Quoting: EhvisThey could have (and it's what I expected) back-ported the DX12 support from CP2077 into the game for a more solid implementation.That's what I expected as well since I read the announcement of the “upgrade”, although I wasn't sure about the solid part.
0 Likes
Proton Hotfix from Valve doesn't get it working for me (PC, not Steam Deck). It still crashes out to handler dialog at the last moment before the game spawns, for me. Not only that, Proton Hotfix renamed the wine pfx out of the way and I had to go fishing for my game data.
I'm going back to my upstream wine based proton-tkg (proton_tkg_7.22.some.git.spaghetti) where at least the game launcher works ("REDlauncher"... it looks like a thin version of the Galaxy client or something) and I can choose between DirectX 12 and DirectX 11. It does not appear with any of the valve wine based protons (including my proton-tkg with valve bleeding edge) for whatever reason (aborts and default game exe runs?)
The DirectX 11 version seems to be a separate build and it runs OK. I do see that d3d11on12.dll in the bin\x64_dx12 directory but that's not being used for the DirectX 11 build. I didn't think so, but I renamed the x64_dx12 directory right out of the way to see and it did not affect the DirectX 11 build of the game at all.
steam/steamapps/common/The Witcher 3/bin/x64 <---- DirectX 11 build
steam/steamapps/common/The Witcher 3/bin/x64_dx12 <--- DirectX 12 build
I'm sure they used some translation at the source level in the first place to port this to DirectX 12.
I'm going back to my upstream wine based proton-tkg (proton_tkg_7.22.some.git.spaghetti) where at least the game launcher works ("REDlauncher"... it looks like a thin version of the Galaxy client or something) and I can choose between DirectX 12 and DirectX 11. It does not appear with any of the valve wine based protons (including my proton-tkg with valve bleeding edge) for whatever reason (aborts and default game exe runs?)
The DirectX 11 version seems to be a separate build and it runs OK. I do see that d3d11on12.dll in the bin\x64_dx12 directory but that's not being used for the DirectX 11 build. I didn't think so, but I renamed the x64_dx12 directory right out of the way to see and it did not affect the DirectX 11 build of the game at all.
steam/steamapps/common/The Witcher 3/bin/x64 <---- DirectX 11 build
steam/steamapps/common/The Witcher 3/bin/x64_dx12 <--- DirectX 12 build
I'm sure they used some translation at the source level in the first place to port this to DirectX 12.
0 Likes
I feel like the hotfix only works for AMD maybe, I run an Nvidia 3090 TI and it takes FOREVER to load, if ever. I kinda gave up and went back to dx11 for now. Game load almost instant on dx11.
0 Likes
Proton hotfix worked for me but when I got the part where they reach the first village and go to the tavern, my pc crashed so hard, I had to reset it.
0 Likes
Patreon
PayPal
See more from me