Spec Ops: The Line

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.

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"?).

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.

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.