stereo3D

You can type your sens with 3 decimal places in-game. Also the default FOV is 90, not 120.

the config is overwritten by steam cloud (options - steam cloud - disable). there are options for raw input and FOV (options - multiplayer - FOV). fov_desired "104.821821" cl_viewmodelfovsurvivor "90" m_rawinput "1"

weird that the FOV option is a multiplier, but Digital Foundry also mentioned they had to increase the FOV to 77 to match the console version. does the photo mode show the actual FOV? on PCGW it says vertical FOV. that can't be right? https://www.pcgamingwiki.com/wiki/Days_Gone#Video

i don't have the game, but if there is no option, then you might also have to add: bEnableMouseSmoothing=False

are you able to measure the vertical sens in this game? to me it feels much slower and makes it really awkward to play, but i couldn't find anyone in google who even mentions this problem.

FOV type is a multiplier like in WD3. FOV 110 is fovscale 1.35. also, it would be really helpful to have the aim sens in the calculator. in general, i noticed with third person games, that matching the look sens often results in an aim sens that's pretty much unplayable.

when i select the game nothing changes.

can you please add support for the aim sensitivity? it's better to change the sensitivity in the console and leave the slider at default, otherwise the menu cursor gets a large deadzone. https://www.pcgamingwiki.com/wiki/The_Evil_Within#Console_commands

apparently flawless widescreen only increases the horizontal FOV, so the game becomes anamorphic. i found this fix: wsgfmedia.com/uploads/thales100/GRAW2_WSFix.zip hor aspect: 1 vert aspect: 1.33333 hor FOV: 1.33333 these values increased the FOV without distorting the game.

it's possible to adjust the sensitivity in the config. %LOCALAPPDATA%\CAPCOM\RESIDENT EVIL REVELATIONS2\config.ini [GAME] MouseBaseSpeed=1.000000

GRAVEN Demo %LOCALAPPDATA%\Praest\Saved\Config\WindowsNoEditor\input.ini [/Script/Engine.InputSettings] bEnableMouseSmoothing=False AxisConfig=(AxisKeyName="MouseX",AxisProperties=(DeadZone=0.000000,Sensitivity=0.010000,Exponent=1.000000,bInvert=False)) AxisConfig=(AxisKeyName="MouseY",AxisProperties=(DeadZone=0.000000,Sensitivity=0.010000,Exponent=1.000000,bInvert=False))

then they must have assigned a multiplier for each zoom step, because if you press 3 to switch to the sniper (assuming you used auto assign), there are 9 zoom steps.

Ghost Recon https://store.steampowered.com/app/15300/Tom_Clancys_Ghost_Recon/ FOV 90 Hdeg Res (4:3 base with widescreen fixer https://www.pcgamingwiki.com/wiki/Tom_Clancy's_Ghost_Recon#Video) game folder -> options.xml -> MouseRadiansPerPixel you can zoom in with the mouse wheel. zoom sens feels too slow, could be focal length scaling.

hmm, that doesn't inspire confidence. i would really like to know if MW and BOCW would fail this test: https://streamable.com/98rfc my guess is, they would fail or they would have advertised it like overwatch.

it's weird, that ADS FOV affected results in a higher ADS FOV in MW, than in BOCW and BO4. at first i thought, maybe it's because of the higher default FOV of 90 in BO4, but in BOCW it's also 80.

No One Lives Forever 2 http://nolfrevival.tk/ raw input mod: https://haekb.itch.io/nolf2-modernizer config file: controls.cfg scale "##mouse" "##x-axis" 0.000470 scale "##mouse" "##y-axis" 0.000470

1.37x sights have the same FOV as ADS (AR, TR), but 1.25x sights zoom in slightly more than ADS (SMG).

in bo4 you can enter 5 decimal places and even though the menu will round it down to 2, it will actually write all 5 to the config. it wouldn't surprise me if BOCW works the same way.

use a coefficient that feels right to you from the get-go. that's why modern games have ADS sens options, after all.

the transition timing option is only for the low/high zoom multipliers. the MDC option is always gradual.

looks like they removed prescaling and replaced mouse_sensitivity with m_sensitivity_x and m_sensitivity_y.

i think it would be better if the result got displayed more like this: Mouse Sensitivity 2.00 1x Optic / Iron Sights 1.15 (1x Optics, Ironsights (SMG, SG, Pistol)) 1x Optic / Iron Sights 1.22 (Ironsights (AR, LMG, Sniper)) 2x Optic 1.42 3x Optic 1.54 4x Optic 1.59 6x Optic 1.62 8x Optic 1.63 10x Optic 1.64

i noticed that to get an actual FOV of 120 at 2560x1080, i'd have to set the FOV slider to something between 99.5 or 100. you'd think it would be either 120, as the calculator says, or ~105.

@DPI Wizard does that FOV changer work for you with the current version?