stereo3D

@DPI Wizard i think it scales like jedi outcast. unnamedsoldier.cfg bind w "+forward;fov 103" // // Cvars // seta developer "1" seta ui_console "1"

yes, it worked great. there is also a fov option in the same file: <prop n="CameraDefaultFOV" v="50.0"/>

can you please add Far Cry with a widescreen fix: https://www.pcgamingwiki.com/wiki/Far_Cry console command: sensitivity zoom sensitivity: X:\Far Cry\FCData\Scripts.pak\Scripts\Default\Hud\ZoomView.lua -> Input:SetMouseSensitivityScale( 0.3 * self.OldSensitivityScale ); if you use a mod like FarOut Widescreen you can simply add the modified lua file to the mod pak with 7zip. zoom factor: e.g. desert eagle: X:\Far Cry\FCData\Scripts.pak\Scripts\Default\Entities\Weapons\falcon.lua -> ZoomSteps = { 1.2 },

@DPI Wizard mafia 3 is currently f2p. it seems to either have a turn speed cap or negative acceleration, but maybe it's good enough to be added.

i just tried "wide 21:9" and maxes out earlier. so they capped it to ~120°.

16:9

weird. all 30 steps work for me.

@DPI Wizard can you please add support for the config? https://steamcommunity.com/sharedfiles/filedetails/?id=1906956364

does the calculator support 4:3 pillarboxed? https://www.mouse-sensitivity.com/?share=c591322daf02294403b85c30cd150b12 instead of 120 / 85 * 30 = 42.35 cm distance, i'd like 120 / 101.4 * 30 = 35.5 cm distance.

the game overrides MouseX/YMultiplier whenever you enter the control options. it's better to set the sens slider to 1 and MouseSensitivity= to 3 * MouseXMultiplier. too bad, there is still no FOV fix for this game.

there is also cl_mbasesensitivity like in blood fresh supply.

"Notes: You need to enter the total change in turning speed according to your armor as "Sensitivity 1"."

both remasters are running on the kex engine. also, are you sure about the vertical sensitivity? it seems to be the same as the horizontal, when i measure it on my mouse pad.

is the vertical sens lower like in metro redux?

so you measured the 360 distance in both games and got ~15.7 inches?

does "MOUSE_ACC = 0" in "%USERPROFILE%\Documents\My Games\Capcom\RE4\usr_input.ini" make a difference?

fwiw, i'm using m_pitch 0.5625 (=9/16).

the FOV for ROTTR and SOTTR needs to be changed to 55 vdeg. also Aim should be changed to "Aim (Pistol/AR)", because bow and shotgun have a different FOV.

ah ok, i actually beat rev1 because aiming felt decent. rev2 however is awful.

in that case, don't even bother with rev2. mouse support is a lot worse.

Vanquish has a launch parameter for FOV: https://steamcommunity.com/app/460810/discussions/0/2132869574260825536/

i just tried the raw input fix for ds1 and the sens was the same with both a 60 fps and 200 fps cap. measuring the aim sensitivity should definitely have priority though, since the look sensitivity will always be a bit sluggish.

i don't think anyone wants to play this at 30 fps. could you maybe do the calculations for a 60 fps and 120 fps cap with RTSS?

there is a raw input fix for dead space 1 and 2. https://www.pcgamingwiki.com/wiki/Dead_Space_2#Raw_mouse_input_fix

i don't have the game, but in case there is no mouse smoothing option: input.ini [/Script/Engine.InputSettings] bEnableMouseSmoothing=false