Jump to content

The Long Dark

Use the Mouse Mod linked in the notes to disable acceleration and smoothing.
Read more...

Sword Art Online: Fatal Bullet

Just added!
Read more...

KovaaK's FPS Aim Trainer

Added with full support for all sensitivity scales and FOV measurements!
Read more...

Fallout 76

Fallout 76 is here!
Read more...

Star Citizen

Version 3.3 fixed mouse issues, hipfire is added. Aims coming soon!
Read more...
DPI Wizard

Spec Ops: The Line

Recommended Posts

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.

Share this post


Link to post
Share on other sites

Try scripting 1 count at the time with 10ms delay, and you should get a pretty consistent result.

There is some acceleration that will happen from time to time either way though, so it's very hard to get a good reading of the sens.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Edited by stereo3D

Share this post


Link to post
Share on other sites
On 10/23/2018 at 7:23 PM, stereo3D said:

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.

No, didn't notice anything different in the measurements, only the smoothing had an effect. I included it in the info anyway in case it does something in certain cases since it seems to be mentioned everywhere. It seems to be in a gamepad portion of the config file indeed.

I take a look at m_targetingModeMouseViewScalePct.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×