[Bug 47731] World of Warcraft BFA Crash with error 132 Memory could not be read.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47731

--- Comment #32 from Sveinar Søpler <cybermax at dexter.no> ---
(In reply to Lunia from comment #31)
> I'm using 450.57 right now. DX12 with VKD3D works perfectly fine with no
> error 132 except sometimes when closing the game, however DX12 VKD3D
> performance is quite a lot worse than DX11 DXVK for me, so I'd love to get
> DXVK working. :(
> 
> This seems to be some weird issue with DXVK + NVIDIA. Doitsujin said it was
> fixed by NVIDIA in like 440.59 but clearly that hasn't really been the case.
> My friend using an AMD GPU has no issue whatsoever and whenever I google
> this problem every single person seems to have an NVIDIA GPU.

I don't feel vkd3d is "quite a lot worse" when i use the vkd3d-proton branch
atm, but it is lower than DXVK.
And yes, the #132 error does happen a lot more with DXVK than with
vkd3d-proton.

I did try the 450.57 driver, but found the performance a bit worse than 450.51
when it comes to "release" drivers. 

The reason for using the "vulkan beta" driver is that it is nVidia's testbed of
new vulkan extensions. The nVidia "versioning scheme" is really confusing, cos
one would THINK that 450.57 had all the stuff 450.56 has, but that is not the
case. The 450.56.x "vulkan beta" driver has vulkan extensions the 450.57 does
not have.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.