dontjustdontok

I suppose there can be many ways to calculate counts/360 but I really should have specified about how Mouse-sensitivity.com calculates counts/360 and later pixel ratio. But I do like the this formula: outputAngle = yaw * sensitivityFunction() * counts Say for CS GO, I use 0.944628 sens, 800 DPI, and I assume the yaw for CSGO would be 0.022, thus: 360 = 0.022 * 0.944628 * counts 360 = 0.022 * 0.944628 * counts 360 = 0.020781816 * counts 17322.83646 Which aligns with Mouse-sensitivity.com's calculation of 17322.8365 counts. But as for pixel ratio (px/count)? Can it be used to calculate px/360? I feel like I'm missing something fundamental.I calculated the px/360 without using pixel ratio with FOV 106.3 and H px 1920. But this is maybe too simple and doesn't really capture what it means to have px/360? px = (H px / FOV) * 360 px = 18.06208843 * 360 px = 6502.351834 We can adjust it so that we can move 80 degrees, or to get a px/80: px = (H px / FOV) * 80 px = 18.06208843 * 80 px = 1444.967074 But if we use the pixel ratio of 0.1741 px/count from Mouse-sensitivity.com, for the example calculation for CSGO, 17322.8365 counts/360, to get the px/80: px = counts/360 * 80 * pixel ratio px = 17322.8365/360 * 80 * 0.1741 px = 670.2012966 I end up with two different values 1444.967074 and 670.2012966 for the total amount of pixels after turning 80 degrees. I'm missing something... I'm sure I miscalculated or they are correct and refer to different things?

I tried to speculate calculations mostly for counts/360, but I could never find out this missing value, I narrowed it to: counts/360 = unknown variable * eDPI I think unknown variable might have to do with 360 or yaw? But I'm really not sure. I tried to look around for the calculation for counts/360 but I'm not getting favorable results. Any technical clue? I just want to know exactly what counts/360 means so I know what I'm actually getting