ivoplaty Posted September 8, 2024 Posted September 8, 2024 (edited) 3 Years I got to upgrade my pc with motherboard, ram, cpu and added a NVME m2, ever since i lost complete control of my sensitivity in game (went from a 4.5 kd in apex to struggling to mantain 1.0, using the same mouse, sens, dpi) I thought it could only be something in my head, that I was the problem, so i gave up and went to play other types of games, and then last week decided to play apex again, and the same problem(i've tried every sensitivity range of motion, to 1/cm360 to 50/cm360 and i couldn't play better on any of these) continued, so i decided to try and find a fix, and then i came up to the idea of updating my bios to see if it fixed, and it worked, my aim was perfect again, i could feel the difference and i became consistent again, but this only lasted for 3 days, then the problem came back. Does anyone have gone through something related? could my motherboard defective? i really want this to get fixed. Edited September 8, 2024 by ivoplaty
TheNoobPolice Posted September 8, 2024 Posted September 8, 2024 (edited) Ensure you don't have any "latency tweaks" installed / applied to Windows, including USB overclocking or other nonsense. This often messes up device input. Use MouseTester to ensure your mouse is working correctly. If it is, this means you can completely rule out any hardware issue. Use that or the DPI analyser here to check your DPI is what your mouse software says it is. Ensure the game you are playing is a Raw Input game (Apex is) so there is no effect from your Windows mouse settings. Double check your sens and FOV in-game to ensure it is correct to what you want. Check you haven't changed monitor refresh rate or resolution - while this won't affect the sensitivity, it can affect the feel of the game. If all the above checks out, then I'm afraid it's you that's the factor Edited September 8, 2024 by TheNoobPolice
Magico.- Posted September 8, 2024 Posted September 8, 2024 One thing ive found that usually gets missed is making sure to turn off 'enhance pointer precision' in your windows mouse settings.
TheNoobPolice Posted September 8, 2024 Posted September 8, 2024 You’d want to view counts vs time and interval vs time. But looks like you’ve got packet loss based on the velocity graph. Time for a lot of troubleshooting by the looks of things.
ivoplaty Posted September 9, 2024 Author Posted September 9, 2024 (edited) So that means that the problem is with my mouse? this below is the test with a very cheap mouse use. Edited September 9, 2024 by ivoplaty
TheNoobPolice Posted September 14, 2024 Posted September 14, 2024 Well, there's a problem with that velocity graph you previously uploaded - whether it's caused by the mouse, the connection, driver software is not possible to say. Your "very cheap mouse" counts graph above doesn't show any discontinuities, although it clearly has some smoothing incidentally. Not necessarily a bad thing, depends on the implementation. The obvious test would be - do you get the same symptoms with the cheap mouse that you notice in game with you main mouse?
ivoplaty Posted September 15, 2024 Author Posted September 15, 2024 Yes, after a few days trying it feels the same as the other mouse, i've tried all of my usb ports and the result is always the same, and both mouse are wired, already reinstalled the drivers multiple times. could be a cpu or motherboard problem?
ivoplaty Posted September 16, 2024 Author Posted September 16, 2024 After messing around with a few testing apps, i noticed that my polling rate is fluctuating, specially when making small movements, and think that this is the cause of my mouse being inconsistent, just don't have any idea on how to fix this.
TheNoobPolice Posted September 25, 2024 Posted September 25, 2024 Around 5-10% update rate fluctuation is "normal" Windows behaviour and this is unavoidable, but much more than is usually some issue. Dodgy polling stability is most often caused by people messing with things they don't understand (such as running "latency tweaking" apps / configs, that usually just break stuff). I'd start with a clean install of Windows (on a separate partition if you wish to not commit just yet) and the bare minimum you need to see if the problem resolves without installing any complicating factors / drivers.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now