Wizard DPI Wizard Posted May 2, 2018 Author Wizard Posted May 2, 2018 Just now, uiki said: That was fast. Thank you! Looking for a 6x now, most likely a 6x modifier but I need to be sure!
Wizard DPI Wizard Posted May 2, 2018 Author Wizard Posted May 2, 2018 6x confirmed and added as well. poppe and uiki 1 1
iBerggman Posted May 2, 2018 Posted May 2, 2018 Just curious, what's the correct "MouseVerticalSensitivityMultiplierAdjusted" value now that we can adjust it in game/config? 1.0 in game (1.002118 config) is probably good enough that you wouldn't notice a difference however I still prefer to use every decimal if I have the option to do so.
Wizard DPI Wizard Posted May 2, 2018 Author Wizard Posted May 2, 2018 34 minutes ago, iBerggman said: Just curious, what's the correct "MouseVerticalSensitivityMultiplierAdjusted" value now that we can adjust it in game/config? 1.0 in game (1.002118 config) is probably good enough that you wouldn't notice a difference however I still prefer to use every decimal if I have the option to do so. 1 is now exactly 1:1. The slider in-game is a bit inaccurate, so when you set it to 1 you get some decimals in the config file. iBerggman and MuntyYy 2
RandalV Posted May 3, 2018 Posted May 3, 2018 Wait so just to clarify we set the slider to 1.00 instead of 1.42 now right?
Drimzi Posted May 3, 2018 Posted May 3, 2018 7 hours ago, RandalV said: Wait so just to clarify we set the slider to 1.00 instead of 1.42 now right? Yes
Snook_ Posted May 3, 2018 Posted May 3, 2018 (edited) Has anyone else noticed that 1.000000 feels a bit faster than the old 1.42 method in input.ini? It feels off, can @dpiwizard confirm its spot on with the ingame option when using "MouseVerticalSensitivityMultiplierAdjusted=1.000000" Is it still broken? Scrap that, for some reason PUBG put back the old 1.42... deleted again now Edited May 3, 2018 by Snook_
d1rtage Posted May 4, 2018 Posted May 4, 2018 Good day all! I was a little confused about the last comment to "Scrap that, for some reason PUBG put back the old 1.42... deleted again now.." Just to be certain, are these the new steps? -Remove the references/changes in the config.ini -Change the slider to 1.0 in-game -This will now equate to the 1.42 which was used before Patch 12? Thanks much!
Wizard DPI Wizard Posted May 4, 2018 Author Wizard Posted May 4, 2018 Just now, d1rtage said: Good day all! I was a little confused about the last comment to "Scrap that, for some reason PUBG put back the old 1.42... deleted again now.." Just to be certain, are these the new steps? -Remove the references/changes in the config.ini -Change the slider to 1.0 in-game -This will now equate to the 1.42 which was used before Patch 12? Thanks much! Correct!
Kally_tv Posted May 13, 2018 Posted May 13, 2018 Anyone know the % sensitivities needed to mimic m_yaw 0.0165 in CS?
Drimzi Posted May 13, 2018 Posted May 13, 2018 1 hour ago, Kally_tv said: Anyone know the % sensitivities needed to mimic m_yaw 0.0165 in CS? 0.022 pitch and 0.0165 yaw? 1 : 0.75
Kally_tv Posted May 13, 2018 Posted May 13, 2018 19 hours ago, Drimzi said: 0.022 pitch and 0.0165 yaw? 1 : 0.75 Thanks for the help, still a little confused due to how there isn't a sensitivity setting for horizontal in the .ini. My sens with default 0.022 pitch and 0.022 yaw in CS would be 1.9, but because I play stretched and use m_yaw 0.0165 I multiply it by 1.33 and get 2.527. I want to try playing stretched in PUBG, but in the .ini I have my sens converted from 1.9. How would I go about making it the same? Sorry, hard to wrap my head around this stuff.
fechees Posted May 17, 2018 Posted May 17, 2018 On 5/4/2018 at 5:07 PM, d1rtage said: ¡Buen día a todos! Estaba un poco confundido sobre el último comentario de " Chatarra que, por alguna razón, PUBG volvió a colocar el antiguo 1.42 ... borrado de nuevo ahora ... " Solo para estar seguro, ¿son estos los nuevos pasos? -Quitar las referencias / cambios en config.ini -Cambiar el control deslizante a 1.0 en el juego -Eso ahora equivaldrá al 1.42 que se utilizó antes del Patch 12? ¡Muchas gracias! Excuse ignorance .. then what to do ??? now with the new actalization how is all this ..? Could you explain what you mean when you put -Remove references / changes in config.ini
garuda03 Posted May 25, 2018 Posted May 25, 2018 Hey a while ago pubg stopped reading the config file for my sensitivities and just kept reverting to default. Am I the only one that experienced that issue? Has it been fixed? potato psoas 1
Drimzi Posted May 25, 2018 Posted May 25, 2018 (edited) 3 hours ago, garuda03 said: Hey a while ago pubg stopped reading the config file for my sensitivities and just kept reverting to default. Am I the only one that experienced that issue? Has it been fixed? Did you happen to put a linebreak just before the mouse sensitivity entries to make editing it easier? If so, that will be the problem. Edited May 25, 2018 by Drimzi
garuda03 Posted May 25, 2018 Posted May 25, 2018 12 minutes ago, Drimzi said: Did you happen to put a linebreak just before the mouse sensitivity entries to make editing it easier? If so, that will be the problem. I just edited it without touching anything besides the numbers. Can you give me an example for what you mean?
Drimzi Posted May 25, 2018 Posted May 25, 2018 If you pressed enter just before MouseSensitiveList=(...) in order to make it all on a new line for ease of editing, so that you don't have to scroll all the way to the right every time you accidentally click above or below the line. If you did that and then forgot to remove the linebreak before saving and launching the game, the game would recognise the incorrect syntax and restore the default values, leaving your new line of custom values as incorrect code.
garuda03 Posted May 26, 2018 Posted May 26, 2018 17 hours ago, Drimzi said: If you pressed enter just before MouseSensitiveList=(...) in order to make it all on a new line for ease of editing, so that you don't have to scroll all the way to the right every time you accidentally click above or below the line. If you did that and then forgot to remove the linebreak before saving and launching the game, the game would recognise the incorrect syntax and restore the default values, leaving your new line of custom values as incorrect code. I'll give this a shot when I reinstall the game, appreciate the help my dude.
Luckorr Posted May 26, 2018 Posted May 26, 2018 Hello, please take a look into this post. https://old.reddit.com/r/PUBATTLEGROUNDS/comments/8m2wr9/psa_pubgs_ads_sensitivity_is_broken_the_same_ads/?st=jhn7tntd&sh=a1b9dd12 He says, that the ADS sensitivity is different of every different weapon. Is this true? Or am i good with your sites calculator? Thank you for your quick feedback!
Wizard DPI Wizard Posted May 26, 2018 Author Wizard Posted May 26, 2018 1 hour ago, Luckorr said: Hello, please take a look into this post. https://old.reddit.com/r/PUBATTLEGROUNDS/comments/8m2wr9/psa_pubgs_ads_sensitivity_is_broken_the_same_ads/?st=jhn7tntd&sh=a1b9dd12 He says, that the ADS sensitivity is different of every different weapon. Is this true? Or am i good with your sites calculator? Thank you for your quick feedback! This has always been the case. All AR's are the same, and all calculations in the calculator are based on AR attachments. Note that all aims will be matched to monitor distance 100% based on their FOV by the game engine, so even though the 360 distance changes the monitor distance changes very little or not at all depending on your preference.
Luckorr Posted May 26, 2018 Posted May 26, 2018 Thank you for your quick reply. I am using 0%match for all ADS and scopes sensitivities. So the difference in ADS for different weapons will hardly be noticable? Thank you!
Wizard DPI Wizard Posted May 26, 2018 Author Wizard Posted May 26, 2018 1 minute ago, Luckorr said: Thank you for your quick reply. I am using 0%match for all ADS and scopes sensitivities. So the difference in ADS for different weapons will hardly be noticable? Thank you! They will probably be a bit noticeable since your match is in the other side of the spectrum, but the FOV's of the different ADS are quite close so it won't be much.
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