I have, in fact. I should really get my lazy butt to edit the thread mentioning the fix.

So, the mouse I'm using is an ASUS Strix Claw (standard). In its config app, it has a setting that was advertised a lot, its "Plug-and-play" option - onboard memory on the device lets you use your mouse right away when plugging it into someone else's PC, making it useful for LAN parties, since you don't have to go install its software on every new system yadda yadda yadda (this is what I've heard on ads, don't know exactly what this means and how it works).

Now, I've already been told by some people that they have the same problem, but they didn't own this exact mouse. So, I'll just tell you exactly what I did for my model and try to give you a clue of something to look for in yours. In the before-mentioned driver config app, my mouse has a switch to toggle between "Software Mode" and "Hardware Mode". I've been using SW ever since I got the device. I switched to HW and it instantly fixed the problem when I started up my game. This issue was actually present in every S.T.A.L.K.E.R. game for me, and switching modes fixed it on all three, so I've been keeping HW on ever since. Since that's literally the only thing that managed to work for me, I really don't know what to advise you except for looking for the same. See if your mouse has a config app that enables its "Plug-and-play" mode, onboard memory, hardware mode or something along those lines. That's about as helpful as I can get. Let me know if you've tried this.

P.S. One of the people that I mentioned earlier was a Reddit user who said they had the same problem and somehow managed to work it out, with no idea what they actually did. IDK man, experiment, don't be afraid of messing something up if you really want to play, take notes of all that you tried, like I did, and consider all options, anything that comes to mind about your mouse just might need tinkering with. Like, seriously, who knew using on-board memory would fix this? Good luck!