Sjoer van der Ploeg

Hah, I just read that as well in the release notes! Now we know :D

When I try this using the Vulkan Beta driver, I get the following: ``` 03ec:info:vkd3d_config_flags_init_once: VKD3D_CONFIG='dxr11'. 03ec:info:vkd3d_get_vk_version: vkd3d-proton - applicationVersion: 2.5.0. 03ec:info:vkd3d_instance_init: vkd3d-proton - build: c29d005ef4eddf3. 03ec:warn:vkd3d_remove_extension: Removing VK_NVX_binary_import extension...

I have found this to be true for other DX12 titles as well, for example if I play SotTR in DX12 mode I can play it for quite some time...

[vkd3d.txt](https://github.com/HansKristian-Work/vkd3d-proton/files/8145462/vkd3d.txt) This is the vkd3d log when the WIDTH CT violation happens. edit: ramblings of a fool.

I have found the specific issue that causes it, at first I assumed it was "random" based on graphics load. But I have since then ran WoW in a testing...

https://youtu.be/FPCDyq5ua4M It seems to only happen when a render scale below 100% is used if MSAA is enabled and a mark is set to show.

[vkd3d.log](https://github.com/HansKristian-Work/vkd3d-proton/files/9125938/vkd3d.log) ``` [ 1427.231142] NVRM: GPU at PCI:0000:08:00: GPU-aa03a635-c459-0d82-a2bc-27deb755feeb [ 1427.231147] NVRM: Xid (PCI:0000:08:00): 13, pid='', name=, Graphics Exception on GPC 0: WIDTH CT Violation. Coordinates: (0x3f0, 0xa3) [ 1427.231159]...

> Experienced crashing in Retail as well, but reporting the issue here. Steps to reproduce, change render scale to anything below 100%, queue for a dungeon. During dungeon the game...

``` Fixed a bug where Marvel's Spider-Man Remastered would sometimes crash with Xid 13 errors on Turing and later. ``` I will test if this also applies to WoW!

Nope, still happens with WoW raid marks with resolution scaling and MSAA enabled! ``` [ 2021.570566] NVRM: GPU at PCI:0000:08:00: GPU-54e8e643-074f-a010-9bd3-353eb9bd55fe [ 2021.570572] NVRM: Xid (PCI:0000:08:00): 13, pid='', name=, Graphics...