Not sure if there's anything we can or want to do here, using third-party overlays with DXVK on Windows is not recommended. I don't know which version of the Steam overlay we're even running but if it's the Vulkan one then it's not going to be aware of any sort of D3D9 mouse cursor weirdness, and DXVK will not be aware of the Steam overlay even being present.
Is there a way I could figure out the Steam overlay version?
It creates a log in your steam folder called GameOverlayRenderer.log
Here is one generated with the native game with me going into a offline match opening the overlay, left clicking and exiting the overlay and then the game.
GameOverlayRenderer_native.log
Here is same with dxvk.
GameOverlayRenderer_dxvk.log
Edit: Note that setting the DISABLE_VK_LAYER_VALVE_steam_overlay_1 enviorment variable to 1 makes the overlay not show while using dxvk. Only when using native
This is a Windows Steam overlay bug. Have seen it before. Nothing we can do about it on our side.
Nothing extracted yet.
Opening the Steam overlay causes the mouse cursor to be stuck on the game screen forever until the game is restarted. Happens every single time.
#2174 may be related.
The game has its own cursor and the mouse cursor that gets bugged into the screen can not actually interact with the game's UI.
Software information
System information
Apitrace file(s)
I was unable to provide a trace file as it does not apparently get created for some reason
Log files