Philip Rebohle

vkd3d-proton cannot expose Feature Level 12.1 by default since we don't have a way to implement Rasterizer Ordered Views. Try `VKD3D_FEATURE_LEVEL=12_1 VKD3D_CONFIG=dxr RADV_PERFTEST=rt`, but also keep in mind that raytracing...

Note that on Nvidia, it's impossible to oversubscribe VRAM, so even if the game uses more than 8GB you'll never **see** that happen in the HUD, since we'll explicitly fall...

We do not implement all aspects D3D line rasterization, and it's rather difficult to do and requires features that are not supported by some Vulkan drivers. I believe the MSAA...

There doesn't seem to be any public documentation or header file yet so we cannot support this right now.

There's still no documentation, and it's rather pointless to support these without also supporting the corresponding ID3D12Device15 etc. interfaces since this isn't how the native runtime works. As long as...

Can you try to bisect this if possible? Also, please try to avoid changing more than one thing at a time, would be interesting to know if Proton-tkg 6.14 in...

Can you please post logs with `VKD3D_DEBUG=trace` instead of screenshots of an error popup?

For context, this is usually caused by games reading from memory that's only supposed to be written to, and sadly not uncommon at all. Like Josh said, `d3d9.apitraceMode = True`...

RenderDoc works fine with DXVK fwiw, you just need to set the environment variable `ENABLE_VULKAN_RENDERDOC_CAPTURE=1` and **not** start the application it through the RenderDoc GUI.

Do we know if this is a regression? Does this only affect the GOTY edition or the regular game as well? The latter is not known to have this issue....