stereo3D

aim sensitivities seem to be all over the place. i noticed crysis and crysis 2 still have the wrong FOV type. it should be vdeg 60 and vdeg 55 respectively.

the ADS sens cvars are actually unlikely to work in any other cryengine game. they got added after the c3 mp beta because people complained about the high ADS sens. i_mouse_smooth = 0 i_mouse_accel = 0

for crysis 3: ; Mouse Sensitivity cl_sensitivity = 2.92122 ; ADS Sensitivity Multiplier cl_sensitivityMultiplierADS = 0.714286 cl_sensitivityOverrideADS = 0 ; Skip Intro Movies g_skipIntro = 1 ; Field of View cl_fov = 67.6727 r_DrawNearFoV = 67.672748 pl_movement.power_sprint_targetFov = 67.672748

maybe it works like in crysis 3 or homefront revolution? if there is a system.cfg in the game folder you could add cl_sensitivity.

you need markc mouse fix.

it's also possible to disable FOV sens scaling or to change the coefficient. [/Script/Engine.InputSettings] bEnableMouseSmoothing=False bEnableFOVScaling=True FOVScale=0.011110

@DPI Wizardcan you please add support for these settings? [/Script/Engine.InputSettings] bEnableMouseSmoothing=False AxisConfig=(AxisKeyName="MouseX",AxisProperties=(Sensitivity=1.000000)) AxisConfig=(AxisKeyName="MouseY",AxisProperties=(Sensitivity=1.000000)) bEnableFOVScaling=True FOVScale=0.011110

mouse smoothing is on by default. %LOCALAPPDATA%\Packages\Microsoft.SpartaUWP_8wekyb3d8bbwe\LocalState\GearGame\Saved\Config\UWP\input.ini [/Script/Engine.InputSettings] bEnableMouseSmoothing=False

mouse smoothing is on by default. the in-game option does nothing and the input.ini is ignored, so there is no fix.

clear the mouse dpi field in the quake live options menu and the sens will be the same. also, FOV 120 in QL is not the same as FOV 120 in QC.

yes, i also just realized it's the same problem that i have in gears 4 and 5. when i alt tab out and change polling rate to 250 hz in the logitech gaming software, the sens becomes a bit faster and if i then change it back to 1000 hz it will be incredibly slow. so basically the same polling rate results in a different sens depending on whether i start the game with that polling rate or switch to it while the game is running.

just with a measuring tape.

the sens is too slow for me for some reason. ms store, 36 cm/360°, 1040 dpi, fov 120, MouseSensitivityValue=0.018319 but i need more like ~0.021 sens to get that distance.

because widescreen was implemented with hor+ behaviour.

decrease your dpi

@DPI Wizard default FOV got changed to 120 at some point.

simply set everything to 360° distance in the conversion setup.

Siege's default ADS sens for ACOG scopes amounts to MDV 100 % and "gradual" ADS sens transition is the only setting that makes sense to me. edit: ADS sens for 1x scopes in Siege is actually way slower than MDV 0 %.

Updated Zoom Sensitivity to use an auto scaling 1:1 monitor distance zoom sens. Zoom Sensitivity 1.0 will now provide you the exact same mouse sensitivity feeling as when unzoomed Added ‘Auto-Scale Zoom Sensitivity’ option. Recommend and enabled by default, this will apply focal length scaling to your mouse sensitivity while zoomed. When disabled, there is no auto-zoom scaling and the Zoom Sensitivity Multiplier will be applied directly to your mouse sensitivity, allowing you more control over your zoom sens. Updated Control Settings layout to support new options, keep weapon and movement binds “above the fold” and position the often adjusted mouse sensitivity values closer to the Save button Added greater precision to the Mouse Sensitivity, Pitch, Yaw, Mouse Accel, Mouse Accel Offset, Mouse Accel Sensitivity Cap, and Zoom Sensitivity Multiplier sliders

targeting FOV is 80°, just like hip-fire FOV. that's why the calculator suggests a targeting multiplier of 1. in contrast, aim FOV in gears 5 is 45° (with default FOV), which is actually closer to "scope - assault rifle".

no, it's like the tech test. i actually have a mouse that allows vertical dpi to be adjusted separately. too bad that logitech doesn't have this feature as well. the mouse support has 3-4 problems: 1. polling rate affects sensitivity 2. vertical sensitivity lower than horizontal 3. long shot zoom "deadzone", especially in the vertical direction 4. high input lag with 60 fps. the mouse input needs about 120 fps to feel reasonably snappy.

@DPI Wizard could you measure the vertical sens too, please? also a small suggestion: it would be convenient if the calculator told you the discrepancy for every aim, when using the aim - all option.

"ADS Sensitivity based on ASR 416 with red dot." should be changed to "ADS Sensitivity based on ASR 516 with Panoramic Sight."

using lower values for the sensitivity sliders gives you more accuracy. MouseYawSensitivity=1 AimDownSightsMouse=2 also, if you want a certain distance then set the calculator to convert distance instead of sensitivity.