benedu3095

Name: Mortyr 2093-1944 Website: https://archive.org/details/Mortyr-repack Status: Release Release date: August 30, 1999 Availability: (Free, invite only, pre-purchase, purchase etc) Side note: "Custom" install with fixes pre-installed to run on modern computers

Sure!

I can vouch for @AZURE_251, it seems the devs adjusted the sensitivity values. For instance, this is what I'm supposed to be using but it's off by way more than just -0.641%. 0.48 feels closer to what I should be using instead of 0.54.

Finally! Hope this new update actually fixed the issue.

The calculations for MWR work as intended for the mod. If you use an FoV higher than 90, then just use the calculations for CoD4.

You're 100% right, it's pinpoint accurate. My fault. When I first played it almost 2 years ago for a youtuber event I must have missed something since I set up my game in such a rush. As for the BFG Edition, I see now thanks! Kinda neat the sens in DOOM (1993) and DOOM II is pinpoint accurate too, something the newer official ports can't say lol. Only problem is, I think they struggle with higher polling rates.

I can confirm @Audile's claim that the sens is noticeable off in regular Doom 3. Also, any reason why the BFG option is grayed out? It'd also be great if you could take a look at the embedded versions of DOOM (1993) and DOOM II that come included with DOOM 3: BFG Edition .

I actually decided to email support, and it looks like they are looking into the mouse sens problems, which is nice.

You know, the new rerererelease (lol) made me remember I meant to post this a few weeks ago: Name: DOOM (1993) and DOOM II - embedded versions within DOOM 3: BFG Edition Website: https://store.steampowered.com/app/208200/DOOM_3/ Status: Release Release date: Oct 16, 2012 Availability: Purchase

Name: Chambers: The Outlaw Website: https://store.steampowered.com/app/2669490/Chambers_The_Outlaw/ Status: Release/in development (?) Release date: May 10, 2024 Availability: Free

You know, in my humble opinion, instead of this convoluted and "poorly" implemented ads sensitivity slider, I would take the no option MDH 100% (I think ?) ads sensitivity of Killing Floor 1 over it any day of the week. I'd rather have a fixed consistent value over whatever Tripwire Interactive came out with in 2. Really hope KF3 is way better in this regard...

Name: Korrupt Zombies Website: https://www.roblox.com/games/10975855395/Korrupt-Zombies-Released Status: Release Release date: June 14, 2024 Availability: Free

It worked like a charm, thanks! Values lower than 90 seem to work fine, but going over 120 just breaks FOV; instead of becoming wider it becomes way narrower (tried it with 132). So yeah, if anyone with an ultrawide monitor is reading this, just follow this guide and the poor ultrawide implementation will be fixed. Here is what I'm rocking and I can confirm in works flawlessly: https://www.mouse-sensitivity.com/?share=53659ce78fcf91cb8519ce068ee73e12

Just wondering, is it possible to adjust the FOV by hex editing the corresponding config file (think it's either display or gameSettings.sav)?

Name: My Friendly Neighborhood Website: https://store.steampowered.com/app/1574260/My_Friendly_Neighborhood/ Status: Release Release date: Jul 18, 2023 Availability: Purchase

After beating Fallout 3 a few days and doing some more "testing" in NV I can confirm that changing the Viewmodel FoV (fDefault1stPersonFOV) affects fMouseSensitivity, just like in 3. Well, at least changing the Pip-Boy FoV (fPipboy1stPersonFOV) doesn't seem to affect either game, so there is that . Also, setting bBackground Mouse to 1 in addition to fForegroundMouseAccelBase=0 fForegroundMouseAccelTop=0 fForegroundMouseBase=0 fForegroundMouseMult=0 seems to make the menus like the main menu and Pip-Boy use raw input, I think??

It's already on the calculator, and just like Fallout 3, both calculations are extremely accurate. Only problems with both games is the lack of decimal places, which sadly hasn't been fixed by any mod out there if I'm not mistaking (though this can easily be mitigated by using Raw Accel), and changing the Viewmodel FoV (fDefault1stPersonFOV) affects fMouseSensitivity, so you're stuck with the horrid Viewmodel FoV. Other thing worth mentioning is that if you feel like the menu/Pip-Boy sensitivity is too fast, don't forget to turn off acceleration (it only affects menus), and more importantly setting bBackground Mouse to 1 massively helps.

Let's just hope for the best.... The lack of decimal places was really annoying, also the viewmodel fov of most weapons was really in your face.

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