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.