stereo3D

fov type is 4:3 base like quake 4.

i know what you mean. give match 100 % a chance: https://www.wolframalpha.com/input/?i=1.804999%3D2.031552*x*arctan%5B3%2F4*tan%5B72.93degrees%2F2%5D%5D%2Farctan%5B9%2F16*tan%5B83.93degrees%2F2%5D%5D

it's too fast because zoomsensitivity is bugged at aspect ratios other than 4:3. https://www.reddit.com/r/QuakeLive/comments/5ztk6d/169_zoom_sensitivity_algorithm/ try this: https://www.wolframalpha.com/input/?i=1.754752%3D%3D2.031552+x+arctan%5B3%2F4*tan%5B72.93degrees%2F2%5D%5D+%2F+arctan%5B9%2F16*tan%5B83.93degrees%2F2%5D%5D

https://www.mouse-sensitivity.com/forum/topic/235-unreal-tournament-4/

either use viewspeed or vfov 70.53 in siege.

vertical sensitivity seems to be twice as high for some reason. thankfully it's adjustable.

when you switch from 360 to viewspeed "match at" stays greyed out, but not when you used monitor distance before.

HALO 5: FORGE In addition to all of the above, Halo 5: Forge on Windows 10 will also include: Fixed mouse acceleration issues with Spartan/vehicle/turret movementhttps://www.reddit.com/r/halo/comments/5y1ste/halo_5_maintenance_update_is_now_available_for/

you can calculate m_yaw by selecting hipfire (advanced). match at 0 % = m_yaw "0.016500" (0.022 / 1.3333333)

i've played on different screen sizes (e.g. 27" vs 90") and never felt the need to change my sensitivity. since you're struggling on both setups i suggest experimenting with lower sensitivities.

i kinda tried to follow the instructions on the last page. 360/103 × (10.39145 - 14.85244012689047 percent) = 30.9253 cm 360/51 × (10.39145 - 3.379207309199 percent) = 70.8727 cm 360/103 × (13.70445 - 14.85244012689047 percent) = 40.7849 cm 360/51 × (13.70445 - 3.379207309199 percent) = 93.4683

you have to enter a dot not a comma. Sensitivity 1: set sensitivity "2.886364" 360° rotation: 36 cm Config FOV: 96 Actual VFOV: 79.59 degrees Actual HFOV: 111.94 degrees

i think there is a bug in the distance calc for non-default fovs. sens 1, dpi 500, fov 100 -> 47.1038 cm distance 47.1038 cm, dpi 500, fov 100 -> 360° rotation: 42.0606 cm, Discrepancy: 10.7066% (5.0432 cm)

no. http://www.regurge.at/ql/

raw input fix: http://community.pcgamingwiki.com/files/file/840-dead-space-mouse-fix/ fov fix: https://github.com/dlrudie/WidescreenFixer/releases judging by the fov values it seems to be using radians.

maybe you used a different zoomFOV? zoom_sensitivity_ratio_mouse "0.818933" is 0 % for zoomFOV 40 @ 4:3 (Zoomed 1: AWP, SSG 08, G3SG1, SCAR-20) and default FOV 90.

is this only true for the default fov? because when i set it to 90 then they don't match at 0 %.

Dead by Daylight Free Weekendhttp://pcgamingwiki.com/wiki/Dead_by_Daylight#Mouse_sensitivity

games like bo3, iw, mwr and doom make a new fov type with 16:9 base necessary. otherwise it gets too confusing for users with 21:9 displays.

click on hipfire and select the other one.

e.g. cl_sensitivityMultiplierADS=0.8 cl_sensitivityOverrideADS=-1

the horizontal fov lock option was replaced with a fov slider in the remaster. fov type is now resolution based.

the patched in fov slider in the remaster seems to be based on 16:9 aspect ratio.

is the fov slider actually accurate this time or is it off like in black ops 3?