Welcome to symthic forums! We would love if you'd register!
You don't have to be expert in bit baking, everyone is more than welcome to join our community.

You are not logged in.

Hey! If this is your first visit on symthic.com, also check out our weapon damage charts.
Currently we have charts for Battlefield 3, Call of Duty: Black Ops 2, Medal of Honor: Warfighter and Call of Duty: Modern Warfare 3

  • "Dark_Ethereal" started this thread

Posts: 49

Date of registration
: Nov 26th 2013

Platform: PC

Battlelog:

Reputation modifier: 7

  • Send private message

1

Tuesday, November 26th 2013, 3:15am

What about a sensitivity guide?

It has come to my attention that BF4 likes to screw around with your sensitivity, a lot.
I am aware that most games with ADS alter your sensitivity depending on your sight's zoom factor, so that the "relative" sensitivity is constant. However it that BF4 seems to not be 100% consistent on this. While it seems most scopes with a declared zoom factor (and therefore Fixed FOV) seem to have the same relative sensitivity as hipfire mode, Ironsights and RDS sights (which seem to have a FOV dependent on the FOV setting) seem to have a lower relative sensitivity.
To see this effect in action, equip a x4 or x3.4 scope, and canted iron sights. Swing your mouse around (or practice aiming between targets) when aiming from the hip, then do it again while aiming down the ironsights. You should feel less sensitive, maybe you think it is just because it is more zoomed? switch to the scope and swing your mouse around again, it should feel more speedy (despite the fact your turn rate has probably decreased), while also being even more zoomed.

Along with this, there is the fact that there is a hardcoded sensitivity difference between Tank MG turret sensitivity and the main cannon turret sensitivity (not just the turn rate limit).

Now I am a scientific sort and I like to know all the variables (that's why I love symthic!), I also don't like it when someone changes the variables of my "experiments". I know my mousepad's usable area is 45 cm wide, my mouse is 7 cm wide, which means I want to do two 360 turns in 38, or 19cm per full turn. That's the way I set it for every game. when someone alters that sensitivity (albeit the FOV relative form) I get upset.

For all these reasons, I think it would be handy to know how the sensitivity is calculated for all these instances, so that those of us with DPI switching mice could set up profiles to compensate.
And it would also be handy just to know how the numbers in the settings files get calculated into degrees per count so that it would be really easy to work out what setting you need for your chosen distance per turn.

This post has been edited 2 times, last edit by "Dark_Ethereal" (Nov 26th 2013, 3:26am)


Sheepnub

I pity the wool

(2,326)

Posts: 3,234

Date of registration
: Sep 20th 2013

Platform: PC

Location: Atlantis

Battlelog:

Reputation modifier: 15

  • Send private message

2

Tuesday, November 26th 2013, 3:25am

Check this

As you correctly noticed, sights and scopes indeed change your sensitivity. This is quite easily calculated.

Take for example the difference between hipfire, and using an RDS. When using an RDS, your sensitivity will be reduced (0.6 speed factor). If you would, for example, want to have the same sensitivity as you would when using hipfire normally, you would have to multiply your ingame accuracy by factor (1/0.6)= 1,666666666666667

You can calculate it like this for every sight, scope, and piece of armor. You just need to go into the datafiles and look up the speed of the vehicle of your choice, and then apply that in the same fashion.

Keep in mind though that the base sensitivity of bf4 is different from bf3. There is a website around that can help you match your new bf4 sens to your old bf3 sens: Clicky. You can use the same website to then match your bf4 sens to your bf4 vehicle sens, as those sensitivity values are different. After which you can start applying the speedfactors I just talked about.
"I put aside a few sceptics, the types of decency in the history of philosophy: the rest haven't the slightest conception of intellectual integrity."
Friedrich Nietzsche


Best of epic quotes :D

Spoiler Spoiler

Just realized it's 4/20 tomorrow


Thanks for the heads up!
*Logs out of Symthic in preparation*

Hardline is a fun and sometimes silly Cops and Robbers sorta thing and I think that's great. Or it would be if it didn't suck.

>littlebird passanger, semi-auto frag rounds
>gunship OP

Meanwhile at DICE-headquarters during BF4's release:

I'm pretty sure there's a massive post-it on every desk "DON'T FUCKING TOUCH ANYTHING THAT IS ACTUALLY DOING WHAT IT'S SUPPOSED TO BE DOING"

UCAV:
"Hey guys remember how stupid prenerf mav was?"

"Lets add c4 to it."

The World Champion went to China once.

They called me a Gweilo.

So I kicked a big fucking hole in their wall and let all the Mongolians in.

just thought I'd share.


The thought of Assaults running out of ACE 23 rounds mid firefight, Engineers facing the rear of an unaware MBT with no rockets left, Recons unable to...Whatever the fuck they do. These are the things that keep me up at night ;(


About hunturk:
I don't know what's funnier, the video itself of the fact that an unlisted video has more views than most of your normal videos :P

...


You just live to hit people upside the noggin with a Math Bomb, don't you?

[context] Maybe it's the UK's overly aggressive porn filter at work. After all, it does have the word "monkey" in it and monkeys have been known to have sex so...


Previously, at DICE HQ:
"Ok guys, the password is "epic dream worlds"; everyone take a letter and do your best to turn it into into something random that we can put into a picture!"


I assume a functional game (BF4) also.

Aww!
*pinches cheeks*
So cute!


But but but

He's a Youtuber ;(

There's no way he doesn't know what he's talking about


  • "Dark_Ethereal" started this thread

Posts: 49

Date of registration
: Nov 26th 2013

Platform: PC

Battlelog:

Reputation modifier: 7

  • Send private message

3

Tuesday, November 26th 2013, 3:47am

So let me get this straight, the speed factor is multiplied by your base turn rate (degrees or radians per mouse count) to produce the new turn rate right?

In that case, "relative" turn rate is something like DPI*BaseTurn*SpeedFactor/FOV which should have been constant

Therefor DPI=RelativeTurn*FOV/(BaseTurn*SpeedFactor)

Therefor the conversion rate is something like DPI_2/DPI_1 = FOV_2*SpeedFactor_1/(FOV_1*SpeedFactor_2)


=Ratio_2/Ratio_1


Well look at that, I made something quite simple look really complicated!

Just one problem, I'm pretty sure Ironsights and RDS scope FOV is user selected FOV dependant, but your sight guide doesn't seem to say that.

Sheepnub

I pity the wool

(2,326)

Posts: 3,234

Date of registration
: Sep 20th 2013

Platform: PC

Location: Atlantis

Battlelog:

Reputation modifier: 15

  • Send private message

4

Tuesday, November 26th 2013, 3:49am

So let me get this straight, the speed factor is multiplied by your base turn rate (degrees or radians per mouse count) to produce the new turn rate right?

It's easier :> is your sensitivity 0.20? multiply that by 1,6666
Just one problem, I'm pretty sure Ironsights and RDS scope FOV is user selected FOV dependant, but your sight guide doesn't seem to say that.

ye true, but that's a minor thing really. Ill add that in as soon. The speedfactor is what you want
"I put aside a few sceptics, the types of decency in the history of philosophy: the rest haven't the slightest conception of intellectual integrity."
Friedrich Nietzsche


Best of epic quotes :D

Spoiler Spoiler

Just realized it's 4/20 tomorrow


Thanks for the heads up!
*Logs out of Symthic in preparation*

Hardline is a fun and sometimes silly Cops and Robbers sorta thing and I think that's great. Or it would be if it didn't suck.

>littlebird passanger, semi-auto frag rounds
>gunship OP

Meanwhile at DICE-headquarters during BF4's release:

I'm pretty sure there's a massive post-it on every desk "DON'T FUCKING TOUCH ANYTHING THAT IS ACTUALLY DOING WHAT IT'S SUPPOSED TO BE DOING"

UCAV:
"Hey guys remember how stupid prenerf mav was?"

"Lets add c4 to it."

The World Champion went to China once.

They called me a Gweilo.

So I kicked a big fucking hole in their wall and let all the Mongolians in.

just thought I'd share.


The thought of Assaults running out of ACE 23 rounds mid firefight, Engineers facing the rear of an unaware MBT with no rockets left, Recons unable to...Whatever the fuck they do. These are the things that keep me up at night ;(


About hunturk:
I don't know what's funnier, the video itself of the fact that an unlisted video has more views than most of your normal videos :P

...


You just live to hit people upside the noggin with a Math Bomb, don't you?

[context] Maybe it's the UK's overly aggressive porn filter at work. After all, it does have the word "monkey" in it and monkeys have been known to have sex so...


Previously, at DICE HQ:
"Ok guys, the password is "epic dream worlds"; everyone take a letter and do your best to turn it into into something random that we can put into a picture!"


I assume a functional game (BF4) also.

Aww!
*pinches cheeks*
So cute!


But but but

He's a Youtuber ;(

There's no way he doesn't know what he's talking about


  • "Dark_Ethereal" started this thread

Posts: 49

Date of registration
: Nov 26th 2013

Platform: PC

Battlelog:

Reputation modifier: 7

  • Send private message

5

Tuesday, November 26th 2013, 4:05am

Something seems wrong...
So I am trying to achieve a state where "angle per distance" divided by FOV is constant across all scopes (which probably isn't possible since it seems all scopes are different).
I don't want just my "angle per distance" to be constant, because then zooming in would be too sensitive, that I what I would expect to happen if I simply used multiplied my current DPI by the speed factor, am I wrong?


Now if my DPI conversion factor was Ratio_2/Ratio_1 (where Ratio is that used in your thread), then Ratio 1, being the ratio of my normal FOV (90) to my normal speed factor (1) would be 90, however if that were the case, then my conversion factor would be less than 1, which is too small, maybe I screwed up my maths and it is actually Ratio_1/Ratio_2, In which case it would be greater than 1, however the higher zoom scopes would want a greater conversion factor, so that is wrong too because I don't have a problem with the relative sensitivity there.


I must have screwed up, let me think...
Stand by for maths!
base angle per distance = APD
Counts per centimetre CPC
Sensitivity = S
Speed Factor = SF

APD = CPC_1*S
APD_ADS = CPC_2*S*SF

APD/FOV_1 = APD_ADS/FOV_2
CPC_1*S/FOV_1 = CPC_2*S*SF/FOV_2

CPC_2=CPC_1*FOV_2/(SF*FOV_1)
CPC_2=CPC_1*(FOV_2/FOV_1)/SF

So the new DPI is equal to the old DPI multiplied by the fov ratio, divided by the scale factor.
That equation formula seems to be right, however using the data stated on that sight thread, The DPI comes out even lower than the original, whereas I expected I would need a DPI increase.

Either my understanding of what the speed factor is is wrong, the data in the thread is wrong, or my feelings about the scope sensitivity are WAY off.


This post has been edited 8 times, last edit by "Dark_Ethereal" (Nov 26th 2013, 4:34am)


  • "Dark_Ethereal" started this thread

Posts: 49

Date of registration
: Nov 26th 2013

Platform: PC

Battlelog:

Reputation modifier: 7

  • Send private message

6

Tuesday, November 26th 2013, 6:31pm

Does anyone else have any input on this? My maths doesn't seem to come up with the right answers at all, and I think it's because the speed factor isn't what I think it is, but I have no idea what else it could be.

Octopuss

Rocktopus

(274)

Posts: 2,657

Date of registration
: Feb 16th 2013

Platform: PC

Reputation modifier: 9

  • Send private message

7

Tuesday, November 26th 2013, 7:25pm

Btw, is it just me or does zoom optics upgrade in vehicles do something nasty with sensitivity? Whenever I zoom in, moving around is partially sluggish and partially stuttery. Really unpleasant.

  • "Dark_Ethereal" started this thread

Posts: 49

Date of registration
: Nov 26th 2013

Platform: PC

Battlelog:

Reputation modifier: 7

  • Send private message

8

Wednesday, November 27th 2013, 7:25pm

I noticed the problem I think. If the sensitivity factor mentioned in sheep's thread is a scaling factor for the sensitivity number used in the settings files (as implied by sheep), this number is not equal to the actual sensitivity in terms of degrees per count, thus these scaling factors would have to be converted to an angle per count scaling factor.

I'd work it out my self but I have no idea what the calculation is that turns the sensitivity number into an angle per count.

Contortrix

Professional Ninja

(507)

Posts: 3,837

Date of registration
: May 27th 2012

Platform: PC

Location: Germany

Battlelog:

Reputation modifier: 11

  • Send private message

9

Saturday, November 30th 2013, 5:32pm

Windows Mouse Things: The MarkC Windows 8.1 + 8 + 7 Mouse Acceleration Fix

Using this'll make it so that the same distance of mouse movement will be the same distance on the screen vertically and horizontally. You can try using this (give it some time to get accustomed to) and see if you like it. I used it since BF3.

  • "Dark_Ethereal" started this thread

Posts: 49

Date of registration
: Nov 26th 2013

Platform: PC

Battlelog:

Reputation modifier: 7

  • Send private message

10

Sunday, December 1st 2013, 1:32am

Windows Mouse Things: The MarkC Windows 8.1 + 8 + 7 Mouse Acceleration Fix

Using this'll make it so that the same distance of mouse movement will be the same distance on the screen vertically and horizontally. You can try using this (give it some time to get accustomed to) and see if you like it. I used it since BF3.
I am pretty sure BF3 and BF4 have raw mouse input modes that bypass the OS settings.