The beta is added!

View full update

aww, thx! hope they let config the exact file value soon.

Edited December 5, 201510 yr by Ankore

aww, thx! hope they let config the exact file value soon.

Hopefully they will, but quite a lot of Unreal based games have this problem. The config file is either ignored, or like in this case, gets overwritten.

The sensitivity value / ratio for Paladins doesn't seem accurate.

 

3 sensitivity @ 1600 DPI in Paladins

 

should be equal to...

 

0.998757 sensitivity @ 1600 dpi in Quake Live / Source engine games

 

But there is a slight difference. Would you mind checking the game out again?

Edited September 24, 20169 yr by Luckylock

Also default fov is 100 now

Yeah, the sensitivity values are completely off now. Also, there is now an in-game fov slider and it seems to be set a different fov then the "/fov" command for the same values. The sens values are off regardless of whether I use the FOV in the slider or the /fov command.

Could you update ? Much apreciate!

Updated! FOV is now horizontal degrees (was vertical), that's what changed.

thx! <3

Is config sensitivity still not working? 

According to this Steam guide, it is possible to fine tune sensitivity by typing /setsensitivity into chat. Not sure how many decimal places.

 

https://steamcommunity.com/sharedfiles/filedetails/?id=855692895/

 

Could anyone else confirm? Thanks.

Edited February 12, 20179 yr by Guest

Can confirm /setsensitvity does work, tried settings decimal values in the shooting range and it does seem to change the sensitivity at least with 1 decimal anyway. Problem is you have to type it in at the start of every match...

Can we have support for decimal values in the calculator please? 

4 minutes ago, iBerggman said:

Can we have support for decimal values in the calculator please? 

Added a "Default (Console)" option in the aim selection

6 minutes ago, DPI Wizard said:

Added a "Default (Console)" option in the aim selection

See this is why I bought a lifetime membership! What was that, 5 min to respond? 

 

Hey DPI Wizard,

Are you saying "Default(Console" allows for decimals for the PC version as well? I'm confused. If so, that's insanely helpful!

16 hours ago, CyanMagenta said:

Hey DPI Wizard,

Are you saying "Default(Console" allows for decimals for the PC version as well? I'm confused. If so, that's insanely helpful!

This causes some confusion from time to time, but it is referring to entering the sensitivity in the console in-game as opposed to in the menus, not the sensitivity setting on a gaming console

I see. Thanks!

I hear mixed things about whether or not using this setting in the config file gets automatically overwritten. It seemed not to work, but typing it in the console did the job. Still, I'd love to not have to reset it every single session. Can anyone confirm or deny this?

Can you add scoped sensitivity?

Any chance you can check into scoped sensitivity? I know for a long time the slider didn't work, but I tried today and the slider stuck, which must've been silently changed sometime fairly recently, as a few days ago it didn't work. Will you be looking into that in the very near future? Kinessa is hard to play as it is right now, when I'm used to the same relative sensitivity, like Overwatch/Widowmaker. Thanks!

Have they made any progress at all with finally putting a decimal in the sensitivity level in the menu? I know this can be worked around from the console, but it's still absurd they don't do this when nearly every other team shooter I play(even Dirty Bomb, which has a far smaller player base) has done so for years.

I know I just posted here a little while ago, but it seems like they genuinely fixed the Kinessa scope sensitivity bug in the game. Will you be adding a calculator addition for scope sense for Paladins now that its fixed?

Updated! Scopes and decimals added. Also removed the console option as it does not save the values you enter.

Re-enable console option please for those who re-enter sens in console each game via /setsensitivity x command 

I like having the extra precision.

Today's patch "increased kinessa zoom". Means her FoV changed or atleast i suppose it did - im actually quite confused. Since theres now also a scope sense option id love for you to check what the n ew FOV is!

It is me again, there has been another scope FOV change this time for STrix, so both kinessa and strix have different scope FOVs then in your tool right now, would appreciate an update!