Vertical mouse sensitivity fix

[Ed]

sauce

A bunch of people found out that vertical sensitivity is actually 70% of horizontal, people already figured that x and y sensitivity was off but they didn't know the exact values (test: try looking in the shape of a perfect square in game...you'll have to move the mouse up and down more than you do left and right.)

So.. as previously discussed pubg has a different vertical and horizontal sensitivity. Exactly, vertical sensitivity is 70% of the horizontal one (https://www.mouse-sensitivity.com/forum/topic/607-playerunknowns-battlegrounds/?page=20&tab=comments#comment-13853) (it's discussed here too https://www.reddit.com/r/PUBATTLEGROUNDS/comments/85tfkp/vertical_sensitivity_correction/). We got use to it over a year but it's far from ideal and if you play different games your muscle memory can be screwed up. I opened a topic on the official forum to ask the devs for a solution with no response.. so here it is.

Go to your ini folder, it's located in C:\Users\YOURUSERNAME\AppData\Local\TslGame\Saved\Config\WindowsNoEditor

Open input.ini and copy this

[/script/engine.inputsettings]
AxisMappings=(AxisName="Turn",Key=MouseX,Scale=1.000000)
AxisMappings=(AxisName="LookUp",Key=MouseY,Scale=-1.428571)
AxisMappings=(AxisName="WorldMapZoom",Key=MouseWheelAxis,Scale=1.000000)

save it and put it read only.

That's it. Horizontal and Vertical mouse movement will be the same (https://www.mouse-sensitivity.com/forum/topic/607-playerunknowns-battlegrounds/?page=21&tab=comments#comment-14031).

Some keybinds may break (like wasd), you can just rebind them in the ingame menu (or put gameusersettings.ini as read only before launching the game).

Big thanks to Dpi Wizard.

EDIT: if you can't drag the map around , add this to input.ini

AxisMappings=(AxisName="UI_MapMoveX",Key=MouseX,Scale=1.000000)
AxisMappings=(AxisName="UI_MapMoveY",Key=MouseY,Scale=-1.000000)

I tried this earlier today and ♥♥♥♥♥♥♥, I still suck at the game but in fights I definitely notice my aim improve when spraying.

What this also means is that the AKM is no longer as bad as everyone thought...

Hopefully this gets pinned because it's a pretty glaring issue to be honest.

[Last Shinobi]

Publicado originalmente por etwas:

this reddit post is from april 1st?

Doesn't make it an April fools joke, because it's VERY obvious PUBG's Vertical sensitivity is only @ 70%, whereas other FPS games have 100%, both horizontal and vertical.

[BLAME! 40K]

Banable offense , read the tos :).

We had that discussion yesterday and someone posted it in the dev forum , where the community manager responded : thank you for letting us know , we will discuss if we change the sensivity.

As long as it is not in the game from there site , its a violating of the ToS.

So use at your own risk , better safe then sry

[Last Shinobi]

The point is, they SHOULD change the sensitivity to 100%, because there is no logical reason for only 70% Vertical Sensitivity.

But who knows, if WE, as a community, complain hard enough, it will get changed to be 100% on Vertical Sensitivity, just like Horizontal is now.

[BLAME! 40K]

Publicado originalmente por SCP-049 ︻芫═──:

The point is, they SHOULD change the sensitivity to 100%, because there is no logical reason for only 70% Vertical Sensitivity.

But who knows, if WE, as a community, complain hard enough, it will get changed to be 100% on Vertical Sensitivity, just like Horizontal is now.

Indeed , already themed in there forum.

[Ed]

You know, you don't have to post a comment on my profile and have yours on private so I can't reply back...of course posting how to violate the ToS is a bad idea, who said otherwise? Since this fix doesn't violate the terms of service, that's why I'm posting it... :|

I see you failed to read my earlier comment where I even quoted the reddit comment by Tamat, the lead community manager, who is aware of the issue and thanked OP for posting the fix.

The amount of backseat moderating because of misinterpretation is ridiculous.

[BLAME! 40K]

Publicado originalmente por Ed:

You know, you don't have to post a comment on my profile and have yours on private so I can't reply back...of course posting how to violate the ToS is a bad idea, who said otherwise? Since this fix doesn't violate the terms of service, that's why I'm posting it... :|

I see you failed to read my earlier comment where I even quoted the reddit comment by Tamat, the lead community manager, who is aware of the issue and thanked OP for posting the fix.

The amount of backseat moderating because of misinterpretation is ridiculous.

Yes i red it , i was part of that discuss . And he says he will pass it to the team for discuss, nothing more :)

I hope they implement it

[MonkehMaster]

Publicado originalmente por Ed:

You know, you don't have to post a comment on my profile and have yours on private so I can't reply back...of course posting how to violate the ToS is a bad idea, who said otherwise? Since this fix doesn't violate the terms of service, that's why I'm posting it... :|

I see you failed to read my earlier comment where I even quoted the reddit comment by Tamat, the lead community manager, who is aware of the issue and thanked OP for posting the fix.

The amount of backseat moderating because of misinterpretation is ridiculous.

editing any game files in any way is bannable, end of story.

[BLAME! 40K]

Publicado originalmente por MonkehMaster:

Publicado originalmente por Ed:

You know, you don't have to post a comment on my profile and have yours on private so I can't reply back...of course posting how to violate the ToS is a bad idea, who said otherwise? Since this fix doesn't violate the terms of service, that's why I'm posting it... :|

I see you failed to read my earlier comment where I even quoted the reddit comment by Tamat, the lead community manager, who is aware of the issue and thanked OP for posting the fix.

The amount of backseat moderating because of misinterpretation is ridiculous.

editing any game files in any way is bannable, end of story.

That was my point. Better safe then sry

Also im very optimistic they will do a change , as it is very reasonable to not have 2 sensytivs

[Ed]

Publicado originalmente por MonkehMaster:

Publicado originalmente por Ed:

You know, you don't have to post a comment on my profile and have yours on private so I can't reply back...of course posting how to violate the ToS is a bad idea, who said otherwise? Since this fix doesn't violate the terms of service, that's why I'm posting it... :|

I see you failed to read my earlier comment where I even quoted the reddit comment by Tamat, the lead community manager, who is aware of the issue and thanked OP for posting the fix.

The amount of backseat moderating because of misinterpretation is ridiculous.

editing any game files in any way is bannable, end of story.

Then all of us should've been banned a long time ago because changing anything in the settings menu just saves those changes to the various ini files already lol.

So many people have already tweaked their inis in regards to sensitivity and whatnot and they're still going strong. Tweaking sensitivity won't get you banned lmao.

But if you guys want to continue to backseat moderate go right ahead. Hopefully Bluehole is compensating you well for your efforts.

[Ed]

We've had this conversation before and it looks like we will just go around in circles yet again.

You're right - there is a difference, the reason there isn't separate X and Y sliders in the game menu is because the devs wanted both to be equal. One slider for vertical and horizontal. But because in the ini, both are already at 1.0000, the devs most likely assumed that nothing needed to be done:

[/script/engine.inputsettings]
AxisMappings=(AxisName="Turn",Key=MouseX,Scale=1.000000)
AxisMappings=(AxisName="LookUp",Key=MouseY,Scale=-1.000000)

However in practice, due to the way changing FOV works in the game, this means vertical sensitivity will not be the same as horizontal, even though the scale for both X and Y sens is already at 1, because the height of your screen is going to be shorter than its width. All this does is change the -1 to -1.428571 so you can actually have the same camera behaviour as in other FPS.

[BLAME! 40K]

Thanks for the info

[Last Shinobi]

Publicado originalmente por Ed:

We've had this conversation before and it looks like we will just go around in circles yet again.

You're right - there is a difference, the reason there isn't separate X and Y sliders in the game menu is because the devs wanted both to be equal. One slider for vertical and horizontal. But because in the ini, both are already at 1.0000, the devs most likely assumed that nothing needed to be done:

[/script/engine.inputsettings]
AxisMappings=(AxisName="Turn",Key=MouseX,Scale=1.000000)
AxisMappings=(AxisName="LookUp",Key=MouseY,Scale=-1.000000)

However in practice, due to the way changing FOV works in the game, this means vertical sensitivity will not be the same as horizontal, even though the scale for both X and Y sens is already at 1, because the height of your screen is going to be shorter than its width. All this does is change the -1 to -1.428571 so you can actually have the same camera behaviour as in other FPS.

So why haven't they compensated the value from 1.0 release onwards to erase that practical difference?

It's not that big a problem to actually get used to this lowered vertical sensitivity. But it is, however, a problem, because handling the AK (and partially the SKS) recoil control feels (or actually is) off from what it should actually be.


EDIT: Wait, why is there no text at all in my PUBG input.ini file? Is this normal or not? I can play the game normally, but this file having no actual text in it just doesn't make sense to me, because it is where the game gets its input data from... Or so we are told anyway...

[Ed]

Who knows, the cynical of us will say 'it's bluehole wat did u expect lel,' those of us on the fence will say 'ehh, not impossible for things like this to not get noticed' and fanboys will be like 'git gud'.

It really does change how the unstable guns handle, the AKM is actually pretty viable now. Coupled with war mode, my aim has improved a fair bit. Definitely no shroud but I can at least put up a decent fight.

If I recall, input.ini is where you can put your own commands in for the game to load. Think of it like the autoexec.cfg in source games. Not a 100% match, but it's fairly identical in that you can put your own settings there.

Early on, the devs didn't blacklist certain commands that did things like...removing grass...trees...etc. top kek and even though those commands have long since been blacklisted, people still get the idea that you can get banned for entering convars that simply change performance or in this case...fix a pretty big bug, when it's already been mentioned a few times by community handlers on the main pubg subreddit that as long as edits made to ini files aren't cheats, they really don't give a ♥♥♥♥...assuming they actually could in the first place without invoking a serious breach of privacy in the process. That's also assuming they could tell the difference between players editing ini files directly vs. editing settings in the game menus which then get applied to the ini files anyway. I'm no programmer but I'm pretty damn sure that you'd need to install software onto the user's computer to do that sort of thing, wonder how would go down /s

[Last Shinobi]

Hmmm, well, there is another way of solving this.

Bluehole should just make an announcement with the instructions on how to correct this big bug for the current playerbase and patch things up for new players who may not read thru every single announcement made.

That way, they do not have to breach any privacy and we can all play the game with the correct sensitivity setup/calibration.

I'm no programmer/game dev either, we're both just using good old healthy common sense :)

And now i think about that, why haven't they fixed this obvious bug within a week after replying the Reddit post itself? It's obviously not that hard.

[Ed]

Publicado originalmente por SCP-049 ︻芫═──:

Hmmm, well, there is another way of solving this.

Bluehole should just make an announcement with the instructions on how to correct this big bug for the current playerbase and patch things up for new players who may not read thru every single announcement made.

That way, they do not have to breach any privacy and we can all play the game with the correct sensitivity setup/calibration.

I'm no programmer/game dev either, we're both just using good old healthy common sense :)

And now i think about that, why haven't they fixed this obvious bug within a week after replying the Reddit post itself? It's obviously not that hard.

lel remember who we're talking about, it's the same reason it took several months of people asking for clothing to be removed as loot before it actually got removed in one of the more recent updates