Suddenly changing mouse sensitivity after launching dota 2 with vulkan api on Arch Linux /Debian Linux

[koreanfan]

Your system information

Arch linux 5.4.43-1-lts, steam 1.0.0.62-1 Debian Bullseye, steam 1.0.0.62-2

• System information from steam (Steam -> Help -> System Information) in a gist:
• Have you checked for system updates?: [Yes/No] Yes
• Are you using the latest stable video driver available for your system? [Yes/No] Yes
• Have you verified the game files?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large pastes as a Github Gist. Launch Dota 2 with vulkan api. After dota 2 main menu shows up, a few seconds later (5-7 seconds) mouse sensitivity suddenly changing without user prompt. When you alt tab and recheck mouse sensitivity settings in terminal via xinput list-props id , they shown sames as before, but mouse sensitivity is different. So i use xinput set-prop id .. for changing mouse sensitivity to previous (was before launching dota 2 with vulkan) value , but again after alt tabbing to dota 2 main menu, a few seconds later mouse sensitivity changing again without user prompt. With opengl renderer there were no issue.

Steps for reproducing this issue:

1. Launch dota 2 with vulkan api, wait few sec (5-7) and mouse sensitivity changing
2. Alt tab to terminal, recheck value with xinput list-props id, value didnt changed
3. Set the same value with xinput set-prop id ..... , mouse sensitivity changed to previous (was before launching dota 2 with vulkan)
4. Alt tab to dota 2 again and a few seconds later mouse sensitivity changing again

[koreanfan]

When valve fix this?

[koreanfan]

Or its will be a redirection game mesa -> valve -> mesa -> valve and etc

[koreanfan]

I have tested dota 2 with amdgpu-pro drivers on CentOS 8.2 (with pro opengl and pro vulkan) and there were no issue with suddenly changing mouse sensitivity. But when i used mesa drivers on CentOS 8.2 i hade this issue. So i think this is mesa driver problem.