High res = floaty mouse, etc

[ablemor]

Hey guys, today I noticed something about the floaty mouse movement. If I lower the resolution to 726x576 or 640x480, etc., the mouse becomes less messy, and I actually aim much better. But the problem is that it's really hard to see anything because it gets super pixelated. I don’t really understand this lowering the resolution doesn’t give me much more FPS, so I don’t think the CPU is heavily loaded. I just don’t get the connection between these things.

But even then, the mouse still feels floaty, and I hope everyone understands that by "floaty," I mean it overshoots enemies, doesn’t snap properly, etc. This issue is stopping me from improving. I wanted to reach 3000 ELO on Faceit, but I only made it to 2000. CS:GO helped a lot because it allowed me to disable raw input. When I turned it off and let Windows process the input, the mouse wasn’t as smooth, but I was able to aim more accurately. I wish I could disable it here too.

I even thought about writing a driver (though I have no idea how) that could correct bad mouse positions—adjusting X and Y coordinates if it detects excessive sliding before the cursor appears on screen. But back to the main question: does anyone know why lower resolution reduces floaty mouse movement? Or could it be that the monitor is generating massive RFI/EMI, which travels through the cable to the GPU and then spreads to the motherboard?

Also, my other big idea: can't the mouse data be stored in the processor cache? I have a 9800X3D—if it could bypass the EMI/RFI-affected RAM, the input might be less jittery.

[drosku]

Hey guys, today I noticed something about the floaty mouse movement. If I lower the resolution to 726x576 or 640x480, etc., the mouse becomes less messy, and I actually aim much better. But the problem is that it's really hard to see anything because it gets super pixelated. I don’t really understand this lowering the resolution doesn’t give me much more FPS, so I don’t think the CPU is heavily loaded. I just don’t get the connection between these things.

But even then, the mouse still feels floaty, and I hope everyone understands that by "floaty," I mean it overshoots enemies, doesn’t snap properly, etc. This issue is stopping me from improving. I wanted to reach 3000 ELO on Faceit, but I only made it to 2000. CS:GO helped a lot because it allowed me to disable raw input. When I turned it off and let Windows process the input, the mouse wasn’t as smooth, but I was able to aim more accurately. I wish I could disable it here too.

I even thought about writing a driver (though I have no idea how) that could correct bad mouse positions—adjusting X and Y coordinates if it detects excessive sliding before the cursor appears on screen. But back to the main question: does anyone know why lower resolution reduces floaty mouse movement? Or could it be that the monitor is generating massive RFI/EMI, which travels through the cable to the GPU and then spreads to the motherboard?

Also, my other big idea: can't the mouse data be stored in the processor cache? I have a 9800X3D—if it could bypass the EMI/RFI-affected RAM, the input might be less jittery.

lower res just works better in some games lol just play around or downgrade until u find one that is good
-IMPORTANT!mouse and mousepad are you on rn(if its a normal clothpad or glasspad)
people seem to not mention it lol but if u are a normal clothpad and your room has high humidity it will literally make ur aim different day by day unless your room stays the same temperature and external factors the same (im on a glasspad by some time best investment ever)
-about the cache it shouldnt affect at all imo it just stores inputs that are not needed urgently since u mentioned x3d and its heavy on l3
-faulty mouse from the box (logitech razer majority)
just a bad sensor straight out of the box

try a fresh install with driver software blockage if its razer or steelseries
there is a lighter software for ghub that you can use

you mentioned raw input and how much better if felt off this might be a sign of a faulty mouse since it worked better with windows handling it than your mouse sending data exactly like i said do not think about a mouse with like issues such as i move left it moves right just think as “stopping power” you think you stop on the target but you just snap off by a little bit losing control
-avoid 1st gen superlights
-viper v3 are hit or miss a lot of people just complain
-DO not use steelseries they are just bad
-zowies will last you a long time
-straight latency input quality/ very very minimal issues just go with lamzu maya/inca or op8k more and more pros use them

[ablemor]

I tried 3-4 mice, even expensive ones, 1000Hz, 8000Hz, and nothing changed. At most, it was a little better at 8000Hz, but other than that, nothing.
But when I used a magnet and placed it on the bottom of my motherboard, it was good for one match.

[drosku]

I tried 3-4 mice, even expensive ones, 1000Hz, 8000Hz, and nothing changed. At most, it was a little better at 8000Hz, but other than that, nothing.
But when I used a magnet and placed it on the bottom of my motherboard, it was good for one match.

try another surface with your mice and try to see if there is any difference
consider getting a backplate for your psu that distributes electricity to your components instead of going straight into it

[kyube]

Hey guys, today I noticed something about the floaty mouse movement. If I lower the resolution to 726x576 or 640x480, etc., the mouse becomes less messy, and I actually aim much better. But the problem is that it's really hard to see anything because it gets super pixelated. I don’t really understand this lowering the resolution doesn’t give me much more FPS, so I don’t think the CPU is heavily loaded. I just don’t get the connection between these things.

That is just a symptom of high GPU usage that CS2 has now.
Lower render resolution leads to lower GPU usage, which in turn leads to overall reduced total system latency.
There's also the motion blur of lower resolution aspect which can impact your experience too.

But even then, the mouse still feels floaty, and I hope everyone understands that by "floaty," I mean it overshoots enemies, doesn’t snap properly, etc. This issue is stopping me from improving. I wanted to reach 3000 ELO on Faceit, but I only made it to 2000.

This reads like complete bogus and a excuse for underperforming.
At this point, I'm starting to think you're just imagining it.
Placebo is pushing you to get worse.
Stop overthinking this and imagining it as if you're chasing Casper.

Or could it be that the monitor is generating massive RFI/EMI, which travels through the cable to the GPU and then spreads to the motherboard?

Also, my other big idea: can't the mouse data be stored in the processor cache? I have a 9800X3D—if it could bypass the EMI/RFI-affected RAM, the input might be less jittery.

That is not how these things work...
You seem to be influenced by the recent hybrid-optical fiber DisplayPort topic on this subforum.
You're always free to purchase a true-optical fiber DisplayPort cable, 2x true-optical USB cables (mouse and keyboard), run a TOSLINK-input battery-powered DAC through the onboard audio controller of your motherboard and purchase a media converter, SFP capable NIC and a AOC cable for a full optical fiber experience.
Oh and not using a wireless mouse while you're at it as well, iirc you're on a V3 Pro which is a wireless mouse

I personally don't think even a single thing of what I said above would alleviate or fix your issues.
Your issue (as is the case with 95% of users here) seems to be a mix of improper SW optimizations, RAM optimizations, human psychology & human physiology.

[ablemor]

But honestly, I don’t know what the problem could be anymore. With my older computer, imagine, I did this: I set the RAM to the correct setting, it was a Gigabyte motherboard, and there was selectable tuning, it was a DDR3 machine, and I had to set the Wi-Fi card to the lowest speed. And it was at that point that sometimes it worked fine. I don’t know what the issue could be. I moved, changed the computer, changed the monitor, and tried a lot of motherboards.

[kyube]

I think you should consider paying someone to do system optimisation for you, since you seem to be unwilling to do the troubleshooting steps which were provided to you by yourself.

If you want help from someone & you want to fix it yourself, provide concrete & detailed information
Start with a ZenTiming screenshot of your current RAM settings.

You seemingly have these parts, as per your small chunks of information:

X670 Strix (no mention of exact model)
Corsair HX1000i

List the rest of your system, such as hardware components, peripherals & software.

[ablemor]

My PC:

9800x3d
asus rog strix x670-ea white
16gb adata 6000mhz/cl30 ram
gtx 1080 gpu
MSI 380HZ monitor
1000hz keyboard
1000hz razer deathadder elite ( AND not, mouse problem, AND not placebo!! something is wrong.. )


I replaced everything


Zentimings:

[kyube]

My PC:

9800x3d
asus rog strix x670-ea white
16gb adata 6000mhz/cl30 ram
gtx 1080 gpu
MSI 380HZ monitor
1000hz keyboard
1000hz razer deathadder elite ( AND not, mouse problem, AND not placebo!! something is wrong.. )
I replaced everything
Zentimings:

Thank you for providing the screenshot, this helps greatly.
As assumed, your sticks are not in the supported memory list of your motherboard, meaning there's a possibility of unstability at play here.

Your options are as follows:
a) Restore BIOS to Default settings, Disable EXPO and reinstall Windows with as little OS optimisations as possible (valleyofdoom's .reg file is great for this) Test this out for 1–2 weeks without changing anything drastically.

b) Purchase a memory kit supported by your motherboard, they can be found here:
https://rog.asus.com/motherboards/rog-s ... vl_memory/

On top of all of this, try using a older NVidia driver, such as 538.58, 551.23, 566.36 (avoid the new R572 drivers)

This should be a nice foundation for you to play around with.

[ablemor]

I’ve tried different RAMs with no result, reinstalled it a hundred times, and still nothing.