gaminggamer111

I understand now, thank you!

Is that tracking speed difference the reason why when both Aim & Look sensitivites are set the same, aiming feels "faster" even though it's the same 360 distance? That means that my calculation should make them "feel" the same, when Look sensitivity is set to 9 & Aim to 5?

I am using 1000hz polling rate. Third Person Mouse Look Sensitivity 9 Third Person Mouse Aim Sensitivity 5 These 2 values should be different, while being the same 29 cm 360 sensitivity for both aim and look? Also, should I use mouse smoothing to mitigate pixel skipping? Does it add a lot of input lag? Not sure about direct input or raw input either, there seems to be some discussions, but nothing definitive.

Sure : https://www.mouse-sensitivity.com/?share=594bd8150d4609392555791ad359520b I tried converting from multiple games, Valorant, Aimlabs, CoD.. it seems to be different each time. The converted sens just doesn't feel right.

What would be the sensitivity slider "numbers" to get around 30-33 cm sensitivity in RDR2? (mostly interested in third person, it seems like aim and look sensitivity are vastly different)? I understand that the game has messed up input so it can't be 100% accurate, but I am still having trouble converting, it seems all over the place. Also, should I use direct input or raw input at this point? It seems like direct input with mouse smoothing has less pixel skipping, but I am not sure. I am playing RedM (FiveM for RDR2), so Windows Mouse input seems to be messed up and it's not really an option - not sure, unless I am doing something wrong, whenever I set it to Windows Mouse the sensitivity in-game is crazy high, if I move my mouse a single millimeter it starts spinning. Yes, I tried lowering Windows sensitivity, doesn't help. I am on 400 DPI. FOV is at 8/10