PressingForward

The game is now out in Early Access and I assume they've changed the numbers since the demo, since the ones it calculates here are wildly off in-game. Save 10% on VOID/BREAKER on SteamAdrenaline-Fueled Roguelite FPS 🔴 Fight relentless machines driven by a hostile AI. Escape an endless cycle. Craft infinite weapon variants with deep gun modding. Forge deadly synergies. Carve your w

Name: Apex Legends (Switch 2) Website: Status: Release Release date: August 5th 2025 Availability: Free Especially curious how the switch 2 mouse sensitivity settings in the settings menu translate to DPI

Not mentioned in the patch notes, but there are new FOV settings in Fortnite since a few hours ago. Not sure if they actually do something, though:

I think this here is a new setting, in case this is relevant for the calculations:

When I want to match the ADS sens across games with different max FOV values, I run into a problem I didn't figure out how to easily solve for years. Apologies if this has been asked before but I couldn't find an answer through the forum search. Let's say I want to match from Overwatch 2 (max 103 HFOV) to Quake Champions (my preference, 120 HFOV). If I go from OW to QC, I get a correct ADS sens in OW2 but a QC Zoom Sens of 1.382. The former is perfect but the altter will feel obviously wrong in game, since the calculator now assumes I want to match the monitor distance I know from OW2 with 103 FOV, I use MD Dynamic in this example, though that happens with any other mode as well. However, if I reverse this, the values are different. Now, the calculator gives me the desired values for QC, but not for OW2. In those examples with MDD, the difference can exceed 33%. The way I've solved this issue in the past years was just to do that reverse calculation once I have calculated the desired hipfire sens. But now that I've started experimenting with MDD for Hipfire, it recalculates the values over and over again anytime I do the reverse calculation since the base sens for hipfire changes in every step. Have I been missing something? Is there a way to avoid this issue? Thanks in advance!

Ah, I see the issue. I can equip every attachment for any gun, even in categories I've not touched yet, but that's possible only in the menu before you start the Private Match. As soon as you are in the loadout menu in-game that limitation you encountered comes into play. Hasn't been that way in any COD I know of, so probably just (another) bug. Equipping them in the menu before the game works, at least for me

You have access to every attachment (meaning all scopes) in a private match!

Game is now out in Early Access, and the in-game options now go lower than 5. Don't know how or if that affects the existing calculation.

A real game changer for me in every way. Huge thanks to NoobPolice and DPI Wizard for this elegant solution

Can't believe it took me this long to stumble across this thread. Liking the approach and the values it spits out seem sensible, can't wait to take it for a spin. Thanks, bud!

Name: Fallen Aces Website: https://store.steampowered.com/app/1411910/Fallen_Aces/ Status: in development Release date: TBD Availability: Free Demo

Very excited to play this game, but this is extraordinarily bad in pretty much every way, wow.

I can't quite quantify how the calculation feels wrong, but matching for 0% MDH makes both ADS and scoped sensitivities feel much faster than they should – by almost double if I were to go strictly by feel. The calculator tells me I should use 1.2 for Hipfire, and 1.9 for ADS and Scope both, and while Hipfire feels perfect, 1.0 for the rest seems to be much more in line with what I'm looking for. This is made even more confusing since increasing the percentage of the Monitor Distance decreases the value of the zoomed sensitivities in the calculator. Edit: I should add, this is for the Demo. Accel is disabled as instructed, of course.

Much of that was my bad, I had scrolled too far down and have instead changed the controller sensitivity settings – there you can go below 0.1 (for whatever reason) and that's also why the settings didn't show up in the config files. At least I could help with the naming change – sorry for the confusion in all other regards!

Nevermind, I was accidentally looking at the Controller options...