It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I've never had a problem like this before in any game but I'll try my best to explain it:

The sensitivity is either actually what it says, half that value, or double that value. The game seems to want to change it every 10 seconds or so and sometimes it even seems that it may be linked to the type of room that you are standing in.

At first I thought it rather seemed like inside the sensitivity was automatically halved and outside it returned to normal -- however I have been able to witness it being both correct and wrong on inside areas and outside areas.

It's really a shame, as I'm in act 4 now and it's literally driving me mad. The workshop always seems to be at a normal value and immediately upon loading into a level it's usually doubled and sooner or later it will literally halve itself from the normal value.

I really like to get my sensitivity just so and can notice changes rather easily.

I don't believe this is a hardware issue as I've never had anything like this happen in 30 years of gaming and my dpi settings have not been changed in any way. It's not even as if the game is 'just forgetting' your settings and going into the menu and switching it up will correct it -- instead I'm just left with these bizarre issues.

I have also noticed that the crosshair seems to sometimes change it's size on the same weapon and this happens to coincide with the sensitivity change at times.

There is absolutely some erratic programming error going on behind the scenes.

I really think this is one of the best FPS's ever made -- no joke -- would love a fix for this!

Thanks!

: )
No posts in this topic were marked as the solution yet. If you can help, add your reply
Mouse sensitivity seems to be related to the framerate, which is all over the place if you don't cap it manually. Please try using a program like NVIDIA Inspector to cap the framerate.
Okay well... it gets even weirder! I've done some more testing!

Level One (the level immediately following New Game) always seems to work properly as does the Workshop. Unless of course the problem is the reverse and these levels are somehow lowering the sensitivity.

Other than those two instances the sensitivity immediately goes up upon level load -- but wait, it gets even weirder than that. The sensitivity actually appears to change depending on which direction the player is facing. If we imagine a circle or a radius of 360 degrees, some spots around that radius actually appear to be gaining mouse sensitivity depending on player facing and the spot around the radius that the player begins his turn.

There also definitely does seem to be some changes based on player location. I've noticed sensitivity going up specifically inside secret areas.

It's worth noting that this is not a velocity based error, at least on my end, I have mouse acceleration off, but I was wondering if the game perhaps has some hidden acceleration happening? Although I really don't think so because the movement doesn't seem to be affected by velocity at all, rather the other outlying issues I have described.

Thanks!

: )
avatar
SpecialSidekick: Mouse sensitivity seems to be related to the framerate, which is all over the place if you don't cap it manually. Please try using a program like NVIDIA Inspector to cap the framerate.
Ah! You know what, this actually makes a great deal of sense. Based on the direction around the radius I'm facing, my framerate is changing and thus the sensitivity.

The question remains however -- how come this doesn't happen in any other game and why in the "$%^&" is mouse sensitivity affected by the framerate if the framerate is always at or above the refresh rate of my monitor?


Never heard of anything like this before and I play many FPS's.


Perhaps the Dev's could weigh in on this eventually.


Thanks for the info SpecialSidekick!


: )
Post edited November 21, 2018 by Anyway.706
Hi,

I am working on fixing this issue. Next patch should contains a lot of improvements in that area.

Best Regards,
Jakub