Is there any particular reason why Console doesn't get a higher Max Sensitivity?
Low frame-rate and the locked low Max Sensitivity on console (/controllers) is what creates the disparity between the performance of killers like Nurse.
https://www.youtube.com/watch?v=UMfNF8xf8zo
Youtuber acknowledging the disparity between PC and console and the effect on the game.
Frame-Rate sounds like the more difficult issue to solve and I wouldn't know what causes this seemingly simple game to be so demanding.
So, to put the first one aside, what about the second? Max sensitivity. With a mouse you can turn around way faster than you'd ever be able to do with a controller. This one should be easy to solve?!
So that is my question; why hasn't the locked max sensitivity option not been solved yet? This could possibly be as simple as changing 1 number variable in the script, being the max scope for sensitivity. Is there more to it?;
-Is it a matter of the Dev team not being aware?
-Is it related to FOV and how certain things are unloaded when not in view, which would make a higher max sensitivity problematic on console's? Thus being performance related?
-Else?
Comments
Edit. Nothing to say here...
Because developers think console players are neanderthals that can't handle fast aim speeds.
I play high sensitivity on almost all shooters. I turn off aim assist too when it's an option. If you play console a lot you can aim just fine.
Maybe devs didnt want a higher sensibility because of the frame rate, moving your camera at a higher speed and having to deal with low fps could make you go blind each time you turn around.
To my knowledge it matches the controller sensitivity of the PC version. At least it's better than it used to be before the option to change it even existed. We're talking literally 2.5 seconds to pull a full turn.
It's terrible and I don't understand why they don't change it. There is no good reason not to.
The faster you rotate, the higher the performance issues