Finding root cause/fix

[MaleGigolo]

I've already explained this in my previous comment but none of the tweaks that you do that temporarily help you actually address the underlying problem. What you are essentially doing when you are applying random tweaks is altering the behavior of your PC by messing with Windows kernel and system configuration, timer sources, thread scheduling, interrupt/DPC behavior, power-management states, driver behavior, etc. This will mess everything up including how long it takes for your opponents to react to you and is a form of cheating, which is one of the reasons why you are not allowed to mess with any of this in LAN/tournaments.

Sorry but your theory is ridiculous. Most gamers like 95% of them do not have this problem. Your reaction time, skill and time spent practicing playing games are your limiting factor not when Microsoft decides to give you consistent gameplay.

But aren't the symptoms of this "problem" similar to those results by windows tweaks? Meaning that maybe one part of this "problem" is your OS.

They are not , at least not to me. Mouse is still inaccurate and i can tell that the PC is not running not even 10% to what it should because i remember what good PC feels like. It might run way better but it is still trash.

[Templar_Warden]

I've already explained this in my previous comment but none of the tweaks that you do that temporarily help you actually address the underlying problem. What you are essentially doing when you are applying random tweaks is altering the behavior of your PC by messing with Windows kernel and system configuration, timer sources, thread scheduling, interrupt/DPC behavior, power-management states, driver behavior, etc. This will mess everything up including how long it takes for your opponents to react to you and is a form of cheating, which is one of the reasons why you are not allowed to mess with any of this in LAN/tournaments.

Sorry but your theory is ridiculous. Most gamers like 95% of them do not have this problem. Your reaction time, skill and time spent practicing playing games are your limiting factor not when Microsoft decides to give you consistent gameplay.

But aren't the symptoms of this "problem" similar to those results by windows tweaks? Meaning that maybe one part of this "problem" is your OS.

another thing is that others run windows just fine.

[playa]

I've already explained this in my previous comment but none of the tweaks that you do that temporarily help you actually address the underlying problem. What you are essentially doing when you are applying random tweaks is altering the behavior of your PC by messing with Windows kernel and system configuration, timer sources, thread scheduling, interrupt/DPC behavior, power-management states, driver behavior, etc. This will mess everything up including how long it takes for your opponents to react to you and is a form of cheating, which is one of the reasons why you are not allowed to mess with any of this in LAN/tournaments.

Sorry but your theory is ridiculous. Most gamers like 95% of them do not have this problem. Your reaction time, skill and time spent practicing playing games are your limiting factor not when Microsoft decides to give you consistent gameplay.

But aren't the symptoms of this "problem" similar to those results by windows tweaks? Meaning that maybe one part of this "problem" is your OS.

another thing is that others run windows just fine.

Pretty basic take for someone who's constanly shutting down ideas and acting like he's seen it all. The endless amount of topics and posts that are linked to this problem and OS should be one clue. So maybe scroll through it all and look for patterns, what are the things that keep coming up? F.ex electricity, OS and your display - what unites them all? How exactly does it all work etc... just a thought

[SweatHatesMe?]

I've already explained this in my previous comment but none of the tweaks that you do that temporarily help you actually address the underlying problem. What you are essentially doing when you are applying random tweaks is altering the behavior of your PC by messing with Windows kernel and system configuration, timer sources, thread scheduling, interrupt/DPC behavior, power-management states, driver behavior, etc. This will mess everything up including how long it takes for your opponents to react to you and is a form of cheating, which is one of the reasons why you are not allowed to mess with any of this in LAN/tournaments.

Sorry but your theory is ridiculous. Most gamers like 95% of them do not have this problem. Your reaction time, skill and time spent practicing playing games are your limiting factor not when Microsoft decides to give you consistent gameplay.

But aren't the symptoms of this "problem" similar to those results by windows tweaks? Meaning that maybe one part of this "problem" is your OS.

another thing is that others run windows just fine.

Pretty basic take for someone who's constanly shutting down ideas and acting like he's seen it all. The endless amount of topics and posts that are linked to this problem and OS should be one clue. So maybe scroll through it all and look for patterns, what are the things that keep coming up? F.ex electricity, OS and your display - what unites them all? How exactly does it all work etc... just a thought

It’s not windows, happens on my Xbox, iOS and different OS

[playa]

Didn't mean windows per se. Meant any Operating System that handles your entire setup and has to calculate things

[Templar_Warden]

Didn't mean windows per se. Meant any Operating System that handles your entire setup and has to calculate things

just a feeling, but i dont think going to linux will fix my issue.

[playa]

Didn't mean windows per se. Meant any Operating System that handles your entire setup and has to calculate things

just a feeling, but i dont think going to linux will fix my issue.

Yes... i didn't say it would, i was just trying to steer the converastion into thinking about how the operating systems work. I think the basics are all similar, be it Windows, Linux or IOS. The communication between your motherboard and operating system is what i was getting at.

[SweatHatesMe?]

Didn't mean windows per se. Meant any Operating System that handles your entire setup and has to calculate things

I understand why you say that, but if I’m being honest, this is something that happens before even the signal gets interpreted by the software. If it was a software issue, applying certain configuration would solve it. That’s why it’s so hard to diagnose because software doesn’t detect as a critical/visible error so therefore it doesn’t show on a log or can be troubleshooted by software. It’s more of an issue between you and the input device, for example: You move at x=1 speed with your mouse/joystick in paper everyone should be able to trigger it. the problem comes when you realize that this isn’t always true, people having this problem instead of moving at x=1, moves around x=.97 and the margin error is to small to cause a “big” error and in online games is reflected by screen desync, heavy mouse/controller feeling, you see weird game physics on client side, client desync (this desync can be clearly obvious or on certain cases be so small or is intermittent and I’ve a lot situation when all scenarios happened). Still it isn’t bad enough to cause an immediate crash/disconnection more like the program/game is fighting for his life to be stable, that’s why if you start monitoring packet loss, ping, out pkt, in pkt, ibuf target you will not see any error (in case of online games). This “noise” (lets called like that) happens before even reaches the system (pc/laptop/console/etc), I do believe is something related with us, not in a way that we produce a weird signal, we hold more electricity, yeah I know I’ve said that, and I was wrong. I see it more like we produce event A (which is weird input devices behavior) and by doing Z action, we modify event A which makes event B appear (when the input devices work without any anomaly) for a period of time till event B converts into event A again, reason why probably there’s a lot of temp solutions and sometimes can be just really dumb or work sometimes till it’s defined again. The hard thing is to actually diagnose this issue and know the cause or know a way when can Event A transform to Event B by a big period of time and can be used any amount of times, basically not just temporary. There’s a lot of things going on in that exact time and knowing the issue is tricky.