solonimbus

No need to use the slider, "mouse_sensitivity" can be modified precisely in Barony\config\config.json

Would you consider adding a calculation for chimera_mouse_sensitivity, for those using chimera? Yaw is (or is effectively) 45/2618, and behaves as expected (4 is twice as fast as 2, etc., unlike retail halo). If you're planning on testing it yourself, note that halo doesn't like scripted 360 spins, but it will work with smaller increments, like 2x180. Edit: for sensitivities 6 and below, that is. Seems like it deviates sometime after that. https://github.com/Kavawuvi/Chimera#mouse-sensitivity

Right, that's what I did, for the high sensitivity at least. I mean that the discrepancy is different depending on the count size (or whatever that's called, "in game sensitivity"?).

Replying to your post here so I stop cluttering up the request thread. This is really interesting, thanks. When I first tested this I figured slowly turning 10 counts at a time was good enough, but now I see scripting a slower smooth movement can make you turn significantly less. That's plain old positive acceleration, which explains why you have the calculator putting out higher values. Except... my results aren't consistent across sensitivities. Using even the slowest movement, at high sensitivity (1000 counts / 360) the calculator's value is still too high. But at lower sensitivity (10,000 counts / 360), turning slowly enough can make the calculator's value look way too low. This is pretty mysterious to me, but my best guess is that it works as if there is a yaw of .00452, and then also some weird stuff happens at low speeds and low sensitivities. That could explain how the scoped weapons can sometimes have noticeable acceleration and jittery movement.

I don't mean to nitpick, but it seems to be slightly off at the moment. As an example, source/quake sensitivity 3 should translate to 14.601770 but the calculator gives 15.018667. Maybe I'm doing the math wrong?

Could you add Spec Ops: The Line? I think m_yaw is .00452, but with mouse acceleration off there is a slight negative acceleration such that testing with 360 spins results in a value closer to .0045200925. To precisely change input settings, you need to decrypt, edit, then re-encrypt SRInput.ini as outlined here and here. Set mouse sensitivity by changing MouseSensitivity to the desired value. Mouse acceleration can be disabled by changing m_viewAccelEnabled to false. You may also want to change m_targetingModeMouseViewScalePct to 1.000000 to make aiming sensitivity scale with fov and set bEnableMouseSmoothing to false to turn off mouse smoothing. At lower sensitivities (below 5; it gets progressively worse as you go lower) there's some kind of strange horizontal angle snapping (or y axis acceleration?) when trying to aim to the side and then diagonally up. This seems to get better at higher sensitivities and I can't notice it at 9 or above.