Just tested on Bleeding Edge, seems like it's fixed. Thanks! > running it in D3D12 mode shows the same issue even on Windows. Supposedly, the game isn't meant to run in D3D12 and it's a bug that it sometimes launches in ...
Should be fixed in DXVK now (and Bleeding Edge very soon), game is straddling undefined behaviour territory here and running it in D3D12 mode shows the same issue even on Windows.