clar1tyyy

Same applies for mine. I was just trying to connect the gpu driver issue with the mouse input problem.

I am speculating now, but I think the issues that the drivers had, affected the mouse input because I had "GPU scaling" enabled under "display" settings.

Maybe it was a gpu driver issue all along. Today for no reason my screen started flashing, and afterwards a window popped up indicating that my gpu drivers were "incompatible" with my hardware. I uninstalled using ddu in safe mode and I reinstalled the drivers having changed "device installation settings" to "no" prior to that. I changed the mouse's polling rate back to 1000hz and I played csgo with bots in a custom map for 5 minutes. I didn't have any issues... If I encounter the same thing again I will report back. Thank you for your time. I'm sorry my thread possibly turned out to be irrelevant.

The distance travelled feels inaccurate.

Maybe it happens with relation to the faceit anti-cheat.

Yeah. I always have it on.

For me it was especially noticable when I was playing cs:go. That being said I do not use g-sync/freesync.

I noticed this myself, I googled it and it seems that others have aswell. Can you confirm this?

Thank you for the reply. Last question about the fov values in the calculator. Does "0" fov in the calculator mean that you put the fov bar in the game to its lowest setting? I am asking because if I put the fov to say 60, then I get a message from the calculator that I have way too high mouse dpi and that with the current dpi the sensitivity in the game should be "-3"( Note: I use 1.5@1600 sens in csgo). I see the notes about the fov in the calculator but it's a vague oneliner... Thank you in advance.

If I change the calculator settings for ADS for 360 distance. Then choose convert from CSGO and insert 1.5 sens@1600dpi. Then choose convert to rdr2 and choose "aim first person" or "aim third person", then, no matter what value I choose for rdr2 's fov the new calculated sensitivity stays the same. I can choose values from 0 to 1000 for the fov but the sensitivity stays the same according to the calculator of course...

Could you please revisit Red Dead Redemption 2 and correct the calculations? It would be greatly appreciated! When I select "first person aim" on your calculator I see that sensitivity is relevant to the fov of the game, but no matter what value I insert for the fov the rest of the calculations don't change.

Thank you for what you 're doing!

Search a shipwreck or sink a skeleton ship (NPC ship) and loot it.

Could you please add trident of dark tides in the calculator?