benedu3095

Changing the Viewmodel FoV (fDefault1stPersonFOV) seems to affect the sensitivity values. A few days ago, after I was finally done modding the game and decided to finally play the game/test my sensitivity, it was noticeable off. Long story short after testing with a non modded New Vegas (just for reference), it was pretty obvious adjusting fDefault1stPersonFOV affects the sensitivity. Really worth looking into, since the default value of fDefault1stPersonFOV is atrocious; it looks really archaic.

I really wonder what could be causing the small amount of negative acceleration , considering every other ZDoom "based" game in the calculator doesn't have this problem (GZDoom, Zandronum, etc).

Name: EvilVEvil Website: https://store.steampowered.com/app/809090/EvilVEvil/ Status: Closed beta Release date: Q2 2024 Availability: Free

Infinity Ward and its game design choices have been a disaster for the CoD franchise.

Ohhh I see . Really weird on Raven Software or HMS to max the fov at 120 hdeg..... Pretty much any ultrawide resolution isn't even "properly" supported at the annoying 90 fov cap lol. Though maybe there should be a special option in the calculator to remove it (call it single-player 3rd party tools/H1 mod?), because if I'm not mistaking, when I played the campaign like two years ago in a different ultrawide monitor than the one I have now, I didn't really experience this annoying 120 hdeg cap. And I also mention H1 again, because when it first released, I had zero problems with it in my old uw monitor (I even used my CoD:AW/S1 client sensitivity & fov settings), though for whatever reason, it seems like either my H1 copy is bugged, or something within the client is bugged because it seems to be capped at 90 fov like the base game now?!?

Meant to post this a while ago, but it seems like ultrawide resolutions (really wide ones) affect the sensitivity??! Or let me rephrase that, it seems like MWR doesn't really support ultrawide formats wider than 21:9 (not so sure that's the exact cutoff or even if 21:9 is "properly supported"), and that seems to affect the sensitivity somehow. Here is what I'm rocking with, and you can tell something isn't right (sensitivity wise), even more so with what I would actually like to use. The latter is wayyyy off, and not quite super ultrawide for whatever reason. Images for reference: So yeah, really weird behavior, guess there is a reason why people call MWR a bad port. Something similar I have experienced and is actually worth looking into (calculator wise) is in CoD2, when you apply the ultrawide or multimonitor fix, it also seems to affect the sensitivity, but in this case, ultrawide formats wider than 21:9 work just fine.

Name: Dust and Aliens Website: https://store.steampowered.com/app/2190230/Dust_and_Aliens/ Status: Release Release date: Jun 26, 2023 Availability: Free

Name: FISHGUN Website: https://store.steampowered.com/app/2431090/FISHGUN/ Status: Release Release date: Jul 5, 2023 Availability: Free

Looking forward to it! As far as I can tell, the clients pretty much behave in the exact same way as the base games do, but some clients are/aren't affected by WPS. I really wonder if the boiii client "fixes" the issue of the game not going above ~115 FOV. In case it doesn't, I really wonder if adjusting cg_fovscale does.

Best we can do is let Mark Rubin (one of the main XDefiant devs) know through Twitter I guess, he seems to be extremely active there.

Can you really? I've tried to in both this and last beta, and the config always resets itself to 30 if you add any decimals.

I don't think the calculator is working as intended on PUBG: https://www.mouse-sensitivity.com/?share=20022860b3afe1fcbfc126813c4ebf61. Some of the sensitivity values, and stuff like 360° Distance, Pixel ratio, Actual HFOV, etc appear to be missing. Also, according to this post "Not all Ultrawide ratios behave the same in this game", and I would have to agree with. Back when I played on a regular 16:9 monitor at 114 FOV (1920x1080), and decided to play on what I personally call "Wide Focal Length" at 1920x882, I did not end up seeing less of my surroundings. I really wonder if this starts happening at aspect ratios wider than 21:9 , which would be really unfortunate now that I have a 12:5 one and it's technically ever so slightly wider.

Gotta love this game, one of the best zombie survival games out there, I highly recommended it. With that out of the way , just like Half Life 2 and other Source Engine games, the ADS sensitivity in NMRiH can be adjusted with the zoom_sensitivity_ratio command (only scoped weapons in-game are the JAE-700 & Sako 85). I can also confirm the FOV can be adjusted by up to 6 decimals places (if I'm not mistaking).

Can confirm you can adjust the ADS sensitivity by changing <prop n="LookAimVertSpeed_Mouse" and <prop n="LookAimHorzSpeed_Mouse".

Thank you!! Based on @Skwuruhl's old research, I would say the Flamethrower, 9mm Pistol, MP5RAS, M79 Grenade Launcher, SCAR-H &/or MP7, Winchester 1894, and Husk Cannon would pretty much cover most of the weapon "types" present in the game. It would also be worth taking a look at scoped weapons such as the Crossbow, M14 EBR, and Railgun, though I think these are already covered by the "ACOG" sensitivity you just added .

Name: Bloody Faerie Website: https://store.steampowered.com/app/811950/Bloody_Faerie/ Status: Release Release date: Sep 28, 2018 Availability: Purchase

I can confirm it is affected by WPS.

If I'm not mistaking, the Halloween 2022 update added UI Horizontal and Vertical sensitivity settings, though I don't think this affected any of the calculations, I guess it is worth mentioning. Also, as some users pointed out before, could you look into the LookRightScale and LookUpScale values (KFInput config file), I personally set both to 0, and the only thing I noticed is the calculated sensibility is ever so slightly off (barely noticeable if I'm being honest). It would also be great if you could add the ADS sensitivity for the various types of weapons instead of the unknown weapon the calculator uses .

I can confirm I had the same issue as @1kFace8aby. I even tried the Riptide workaround, but it doesn't seem to work in this game. I had to settle with changing the sensitivity in-game and adjusting accordingly with Raw Accel. @GreekBoyI imagine you unzipped the .pak file, don't. You just have to open Data0.pak with 7-Zip, and edit the file accordingly, once done 7-Zip will ask you if want to update the file in the archive, click Yes.

Name: Blood And Zombies Website: https://store.steampowered.com/app/1739880/Blood_And_Zombies/ Status: Release Release date: Jul 26, 2022 Availability: Purchase

Would you mind checking the included "original" DOSBox version ? Though I wouldn't be surprised if it can't be added for some reason or other.

Name: Nosferatu: The Wrath of Malachi Website: https://store.steampowered.com/app/283290/Nosferatu_The_Wrath_of_Malachi/ Status: Release Release date: Oct 21, 2003 Availability: Purchase Side note: Hope it can be added without problems , looks to be an interesting early 2000s FPS.

If you happen to use cg_fovscale (I've used it in both iw5 and h1), you just have to divide your FOV by cg_fovscale to get the actual FOV you should use in game. For instance I use an FOV of 104.821821 in these classic CODs, and I use a cg_fovscale of 1.3 in h1, which equals to 80.63217. If you do this, the sensitivity calculation stays the same.

I can confirm these clients use the same calculations as their base game. For reference, I've played iw4x, s1x, iw5, & h1, and they all work just fine. The only thing worth noting is that some of these clients aren't affected by WPS.

Decided to try again (made sure to fully erase my previous settings folder and checked the game integrity just in case), and it still felt way to fast. For reference, here is what I came up with yesterday: https://www.mouse-sensitivity.com/?share=9ea8b4cc8e2cf2efca5f38a046d4acaa and https://www.mouse-sensitivity.com/?share=88e1ea294fe4e7e14179211f911c9147. This is what I tested today (didn't change the FOV just in case, and I also disabled gradual ads transition just to be safe): https://www.mouse-sensitivity.com/?share=5f80acc3acb22de630f33757b0911232, but it still felt way way off, though I decided to also test MouseScopedSensitivity=0.0752420 instead of 0.752420 and it honestly felt pretty good .