First of all, placebo can be a hell of a drug.novorei wrote: ↑31 Mar 2023, 11:32But what are the tools that can measure some effect of it? Preferably, some tracking tool which has a server-client configuration with load processing, timestamping, external capturing of mouse/screen.Chief Blur Buster wrote: ↑30 Mar 2023, 17:19You can see the answer by reading the whole thread (click through the pages 1, 2, 3, 4, 5, 6, 7, 8, 9 and read almost a hundred posts):
TL;DR Conclusion: (A) It's a legit issue; there is a mix of successes and no-successes, on a per-person per-system basis. (B) It's hard to troubleshoot; (C) Far more common than some niche causes such as EMI;
DPC latency (high and low, never really felt a difference), ping tracking (is compensated by game netcode), Capframex (only captures stuttering) does not directly translate to the issues of hitreg, heavy mouse, "playing" in past feeling.
Never found the silver bullet. Sometimes feels a bit better, sometimes not, other times nothing has changed and the feeling is different.
Are there "gaming certified" hardware and software platform?
Using a debloated Windows is a good start. Server 2022 is considered as barebones as it gets and it can allow for much granular control of the OS. LTSC Is very barebones too. I don't think W7 and W11 are good to switch to because the former is losing support day by day, while the latter has a few issues for now (I'd rather wait till W11 LTSC gets released) even though it has the +500hz Windows cap fix and supposed 'high polling rate' fix in the Insider build, which could definitely help alleviate issues.
Linux has the potential to be superior in regards to latency than all the above mentioned versions of Windows, sadly lacks developers to implement modern features and a more GUI approach to some features.
DPC latency has a noticable impact on overall system responsiveness and claiming 'never felt a difference' while you can 'feel' your cursor being 'heavy' is kinda ironic.
TCPOptimizer just adjusts registry of Windows, Leatrix fix does nothing.
Minimum rendered frames is a feature from the past and is called ULLM, which is superseeded by Reflex (much superior) and is only used to lower input lag at high GPU usages. Reflex (ease of setup) >= proper frame cap > ULLM / Anti-lag in terms of solutions for GPU-limited scenarios.
Aa few verified ways you can do for 'heavy' mouse feel:
Use xperf (analyzing DPC latency) and tools listed here: https://github.com/djdallmann/GamingPCS ... /README.md can be a a good start to hunt down your issues. (I personally use LatencyMon as well on top of xperf)
Using MouseTester (ver1.4 for +1kHz) to verify whether polling rate is stable is also another one.
Different sensors have different ways of tracking ('most responsive feeling' being the MLT04, 3366, 3360 SROM 5, 3399, 3950 due to the way their tracking works) I have on purposely excluded the Hero sensor (even though it has better circle motion handling), due to variable framerate which some people don't like. Perhaps consider switching out the mouse.
Different games have different ways of calculating mouse inputs. Diabotical is currently the only game I know of that has multithreaded mouse input, a feature that's desperately needed in modern games imo. It also features a very robust and stable in-game framecap, unlike any other game.
Perhaps your monitor just has slow response times?
RAM Tuning has a noticable impact on system responsiveness / cursor 'feel' as well.
Have you considered that humans are variable as well and not consistent? There's a ton of human factor at play (other than the above issues) from a physical and psychological aspect.
I don't want to get into the EMI aspect at all. It can be a culprit but I think there are a ton of other things at play before this has any play.
Oh, btw, what PCIE NIC have you used? I'd like to know if you're experiencing any DPC issues with it and if the drivers are good, been on a lookout for a NIC to replace my Atheros with.