Does this only happen on NV? VK_ERROR_INCOMPATIBLE_DRIVER isn't something that we should ever see during swapchain creation.
Does this only happen on NV?
Nope, behaves the same on Intel/anv: Chesmaster_Intel.log
The only thing that returns INCOMPATIBLE_DRIVER in Proton seems to be this:
Seems to be some windowing nonsense that's outside our control.
Oh, child window memery, got it - the situation on that front might even be worse in Wine Staging. I'll close this then since a) the game works fine anyway b) it's not related to dxvk.
Nothing extracted yet.
Chessmaster 9000 uses d3d8 partial presentation, so it ends up on the GDI path and constantly spews out:
err: D3D9SwapChainEx: Failed to recreate surface: VK_ERROR_INCOMPATIBLE_DRIVERThis doesn't appear to affect gameplay, at least it's not less functional than it is with WineD3D, so it's more of an inconvenience, but still would be great if we could fix whatever's causing this.
I've captured an apitrace, but it doesn't reproduce the problem, since it doesn't end up on the partial presentation path during replay (I guess).
Software information
Chessmaster 9000, retail copy
System information
Apitrace file(s)
Chessmaster.tar.xz
Log files
Chessmaster.log