stereo3D

because that's what bo4 and bf games use. at 16:9 both MDH 100 % and MDV 178 % would be the same, but only the latter would give you the correct sens in those games.

simply adjust the MDV % in the conversion setup until you get your widowmaker sens. in you case it's 10 % = 0.1 coefficient in bo4 (bf1, bf4, etc...) not sure tbh, @DPI Wizard would have to answer that.

yes, that's right.

unfortunately the calculator assumes that you leave the coefficient at default 1.33 but then your ads sens would only be correct with a reflex sight. since you want it to be correct with every sight you should leave the ads multi at 1 and instead change the coefficient to 1.72

in the conversion setup set everything to "monitor distance vertical 178 %" = MD coefficent for bo4 convert from overwatch all to bo4 all with ads you will see that your widowmaker sens should be 49.54. if you really want it 49 then use 172 % for everything. if you want to use a higher fov in bo4 the calculator will scale your sensitivity accordingly.

fov 103, sens 13, ads multi 1, monitor distance coefficient 1.72

there are so many different sights, that it's hard to say. if you have trouble hitting long shots then use independent, but if you find that you have trouble tracking targets at closer range, like when an enemy suddenly slides or jumps into the room then switch to affected.

you can use the same settings in bo4, except FOV 101 and monitor distance coefficient 1.78

that's a monitor distance coefficient of 0.36

enable advanced mode under conversion setup set everything to MDH 0 % convert from fortnite - targeting to pubg/bo4 - all

have you fiddled with the in-game sliders? looks like they are additional multipliers for x- and y-axis. not sure if it's worth adding support for them, but the notes should probably tell the user to leave them at default. one big problem is that mouse movement at lower sensitivities gets ignored. with MouseSensitivity=4.427166 and 1000 DPI it won't let me aim upwards unless i move the mouse pretty quickly.

definitely a bug in the calculator. ads multi should be 1 with both affected and independent fov.

did you actually measure a difference with viewaccel on and off? it might only affect gamepads, because i don't notice it. in MoH 2010 viewaccel also affected mouse input and it was very obvious. also it would be really helpful to have support for m_targetingModeMouseViewScalePct= in the calculator as well.

select 360° distance in the conversion setup.

so reflex is basically FOV 50 at 4:3. looks like they are still working with 4:3 internally. i guess, ELO/ironsights could be 55 and holo 45 at 4:3?

https://www.desmos.com/calculator/l4igdvmlfb https://www.reddit.com/r/QuakeChampions/comments/9ndtw4/updated_czm_calculator_with_zoom_fov_for_october/e7lpnus/

then cap your fps at 110 with RTSS.

seems like it's only wrong for ADS FOV "independent".

sry, but nothing changed for me?

i'm getting an incorrect ADS multiplier: MDH 100 %, 47 cm, DPI 1000, FOV 100 mouse_sensitivity = "2.9452" mouse_ads_monitor_distance_coefficient = "1.7778" mouse_ads_yaw_ads_multiplier = "0.8619" <--- should be "1"

update is live. zoomFOV is now adjustable between 30 and 100.

well, in that case just set scope to 360° distance in the conversion setup and you will end up with sensitivity "1.312594".

for 1x sights ADS 90 is the same as 1/0.6/0.02=83.333 with that in mind your CSGO sens is: sensitivity "6.510858" for 360° sensitivity "6.108362" for MDH 100 % sensitivity "5.717426" for MD 0 %

it should be possible to adjust the sensitivity more precisely in the config. original: %APPDATA%\Bioshock2Steam\Bioshock2SP.ini -> MouseSensitivity=1.234560 remaster: %APPDATA%\BioshockHD\Bioshock2\shared.ini -> MouseSensitivity=0.123456

the calculator tells you where the config is in the game info section. if you still can't find it, right click on the game in your library, select properties -> local files -> browse local files -> \user\profiles\default\attributes.xml (open with notepad++)