nicolovbg

Hello! I decided to try your program in Quake Live. I play with in_mouse -1 (=m_rawinput 0) instead of in_mouse 2 (m_rawinput 1) because I've discovered (of course by feeling; but I am such a sensitive person to this stuff) that RawInput in QuakeLive has relative delay as well. So, what's the problem with your program? Well, I start the game, play a little bit, open Rinput v1.37, type quakelive_steam.exe, the *.dll file successfully injectes, I go back to the game, play a little bit (everything's fine), then press ESC. After that buttons in the main menu cannot be pressed, like MOUSE1 doesn't work at all. Then I press ESC again and go back to the game. And here the real problem startes. Eventually, I can shoot, but I cannot aim with my mouse, the crosshair doesn't move. Could you please explain the problem to me, or, try to fix it? Thank you

Everything workes fine. Guys, your work is invaluable. I can finally play with 99,99% of accuracy and no delay at all, I am so sensitive to those miliseconds. :/ Thank you a lot! (:

I replaced the Rinput.dll with yours, started CS GO, typed csgo.exe and got: failed to load Dymanic Link Library. Is everything alright with your file?

Hello, I've recorded two videos with the following settings: m_rawinput 1, fps_max 0 and V-Sync 0. Just look how the mouse delay increased when full 3D scene has been rendered. And in this situation the game's cursor should represent the crosshair behavior, no? I write about this because I can definitely feel the difference between mouse responce in 1.6 and CS GO. https://youtu.be/zEwDSlyD85Y