Wizard DPI Wizard Posted January 20, 2022 Wizard Posted January 20, 2022 Raw input is currently bugged, turn it off for best accuracy. View full update
LeopardTurret Posted January 21, 2022 Posted January 21, 2022 What does it do if you have Raw Input 'On'? Does it drop polling inputs from the mouse or something?
Wizard DPI Wizard Posted January 21, 2022 Author Wizard Posted January 21, 2022 3 hours ago, LeopardTurret said: What does it do if you have Raw Input 'On'? Does it drop polling inputs from the mouse or something? Correct, it's seems like the same bug R6 Siege had last year. LeopardTurret 1
Captain Funsponge Posted January 23, 2022 Posted January 23, 2022 (edited) I think I need the sock puppets version of what I'm doing wrong here because I can't seem to figure it out. My goal is always to have a consistent sensitivity acoss hipfire and ADS (in this case primarily 1.0x), but I can't seem to achieve that with the numbers the calculator is providing. As a side note I can set values above 100 in the config file and they are reflected in the game menu, not positive they are having an effect above 100 though. The in-game setting with a default MouseSensitivityMultiplierUnit=0.02 suggests 7 for pitch and yaw. The config file method suggests a pitch and yaw sensitivity of 50 with MouseSensitivityMultiplierUnit=0.002765 which feels equivalent to the in-game setting as far as I can tell. With pitch/yaw set to 7 in-game and multipliers to 100 (since I can't set 119 in-game) the ADS sensitivity is still noticably higher than hipfire sensitivity. I've tried this with both the default MouseSensitivityMultiplierUnit of 0.02 and with pitch/yaw set to 50 with MouseSensitivityMultiplierUnit=0.002765. ADSMouseMultiplierUnit is also set to the default 0.020000. Any idea what I'm doing wrong here? Edit: With some very imprecise testing, the ADS multipliers which seems closest to the pitch/yaw 50, MouseSensitivityMultiplierUnit=0.002765 is around 60 if that helps. Edited January 23, 2022 by Captain Funsponge Additional information.
Wizard DPI Wizard Posted January 23, 2022 Author Wizard Posted January 23, 2022 3 minutes ago, Captain Funsponge said: Any idea what I'm doing wrong here? Your settings for Destiny 2 indicates that you have set the FOV to 76.366893 (this is a multiplier, true vertical FOV is 45.42), while you have it set to 90 in Extraction which is almost twice as high. With these settings a 2x scope in Extraction will have the same FOV as your hipfire in Destiny 2, which is not ideal. You should whenever possible match the actual FOV for hipfire, which makes the calculation more sensible: https://www.mouse-sensitivity.com/?share=2e2438bfa7d4a1a39a04f9ea08f455b7 Captain Funsponge 1
Captain Funsponge Posted January 23, 2022 Posted January 23, 2022 Right OK. I was making the assumption the calculator would account for FOV settings as long as they were specified at either end. Thanks for the clarification.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now