ODSYViper

I play a lot of Modern Warfare as well. Legacy I believe is 1.33 monitor distance. In any case, switching between values for relative distance does have a noticeable difference on ADS sensitivity. Changing between them will mess up your muscle memory. I think most people on the forum use 0%, which scales ADS speed by the focal length of the scope FOV and maintains the same feeling at the crosshair.

This defeats the whole purpose of gsync though. Without a frame limit if your fps goes above your monitors refresh rate then gsync is no longer active. So if you are getting 300fps with gsync on you aren't actually getting any of the benefits of gsync. Whats worse is if you have vsync on as well like they recommend you'll actually be getting higher input lag than having gsync + vsync off completely.

Ok, I'll do some more tweaking and see if I can get gsync to work better for me. Appreciate the insight.

I also have nvidia low latency on, 1000hz polling rate and 1600dpi. Are you checking your average stable fps with rtss and using the in game limiter? I am familiar with the blur busters guide although the one time I did try gsync I was using rtss to cap the framerate and the increased input lag was very noticeable (with my current settings/setup at least, its possible I was doing something wrong).

Do most people here play with their fps uncapped? Capping the fps to 120 in game seems to the only way I can get my aim to feel consistent and the game to look visually smooth on my 240hz monitor. I guess maybe because the variation in frame rate when uncapped also means the frame times are inconsistent. I've tried external fps limiters (rtss, nvidia frame cap) which cap the frame rate very accurately but they seem increase the input lag considerably.

I've tested with and without rivatuner and gsync now but still have the same issue unfortunately. I can live with it for now but I hope they fix it in the future. I prefer gsync in most games now, capping the framerate + gsync + vsync on gives consistent frame times and no tearing.

Aiming feels really good now compared to the last flight. Does anyone get a weird shuddering image when strafing? Everything else seems fine but if I keep my reticle on an object or character and strafe around the object kind of stutters and vibrates, making it blurry. I'm playing on a 240Hz monitor with gsync on and the framerate capped at 200fps with rivatuner.

Going back and playing the modern warfare games, seems like 0% scaling for ADS. Can someone confirm? Does this apply to all the COD games?

Awesome, good to know. Thanks Wizard!

Having the exact same fov in all games would be nice because then you can just use the 360 distance calculation to have the exact same hipfire sens in all your games. As you've discovered though, this is rarely practical because some games just don't support the same fov range. Just set the fov as close as the other games allow and then convert hipfire using 0% monitor match which will correctly scale your sens so that it feels exactly the same. Then you can use whatever conversion method you prefer for ads and scopes.

I thought I'd have a go at helping but hopefully someone with more experience can double check for you because I could be wrong. My thinking is that converting for hip-fire and keeping your relative and co-efficient settings the same will keep everything consistent for ads. Edit: Noticed you already converted hip-fire and are using the same value I calculated so if the ads feels off maybe it is necessary to tweak the other values.

I have noticed when changing settings in the config file that have multiple decimal points, that the in-game settings still display these values as rounded. For example, I have my sens set to '3.497' in the config, which just gets displayed as '3.5' in the settings menu. I'm assuming that its being applied correctly, but just being displayed as a rounded value in game? Also, does anyone know if the config allows for decimal points for fov? The comment in the config just says "60 to 120". I set mine at '106.26' to match csgo, but again it just displays in game as '106' so I don't know if its working. Maybe DPI Wizard could chime in on this one for me. Much appreciated.

Ok, got it. Thanks for taking the time to explain everything.

Sorry, I'm not really sure what you mean by this part. Ok thanks, so basically even a small change like 5 degrees is enough to throw off your aim. I guess I just liked the idea of keeping 360 sens the same and thought the small fov change wouldnt have any impact on accuracy.

Hi guys, just wanted to know if there's a general consensus on what method to use for converting hipfire sens to different games with similar (but not exactly the same fov's). If two games differ by say 5 or 6 degrees or less should I be maintaining my 360 distance or using some other conversion? The game with the larger fov will look slightly zoomed out but rotating the aim between two objects in game still requires the same mouse movement doesn't it? Because the angle between them is still the same. Although the sensitivity might feel slower also due to the wider fov so im not sure.