Thread is locked.

Important Guide to Uniform Soldier Aiming.

DarkEtheereal
GB Enlisted: 2011-10-27
2014-09-30 19:18 , edited 2014-09-30 23:14 by DarkEtheereal
Hello! CTE tester here!

If you've looked in your input settings post patch, you'll see a lot of new sensitivity options, either right there on the main control options, or hidden in the advanced menu.
DON'T TOUCH EM YET! You need to LEARN about them first!

I was very much involved with coming up with the concept behind the option known as "Uniform Soldier Aiming" (Which I abbreviate to UsA). I'm basically the expert on this. The only person who knows it better is probably Jjju, the dev who coded it.

It's vital you read this guide before you go screwing around playing with sensitivity sliders, because you can end up ruining your muscle memory if you don't do things properly.

Please share this and comment if you find it useful, otherwise nobody will know of the glory of Uniform Soldier Aiming.

Dealing with FOV



If post patch, your turn rate felt funny and running felt slower, it's probably because the FOV system changed to become clearer. Basically before the FOV ran on the Hor+ fov system which many games use. The problem is that this hides the actual FOV number. BF4 actually runs on vertical FOV, which is the number on the left of the new FOV slider.

So if you ever want to geek out and do calculations involving FOV, the slider now tells you your actual screen independent FOV.

However if you want to set your FOV back to what it was pre-patch, you need to match the number on the right in brackets to your old FOV number. Once you do that, things should feel normal again.

Uniform Soldier Aiming


If you look at the options, especially the advanced options, you may see lots of separate aiming sliders and want to go "Oooh! look! I can set all these sliders how I want to have the sensitivities I want!".
DON'T DO THAT.

The problem is if you go setting all your options manually, you'll play around till it feels "good enough", and you probably wont set them at the proper levels.
We've come up with a proper way to set your sensitivities with each sight to the correct level without any effort, and because it follows a clever mathematical formula, it should be easier to learn, reducing any negative effect on your accuracy when you switch scopes.

This system is called Uniform Soldier Aiming.

What does Uniform Soldier Aiming do? (Simple version).



Uniform Soldier Aiming is meant to make your sensitivity feel the same when you switch between infantry ADS sights.

When UsA is OFF, if you switch from a close range sight like an RDS to an optical zoom sight like a X4 sight, you'll probably notice a jump in sensitivity. Typically the close range sights feel less sensitive, and the long range sights feel more sensitive, which isn't very helpful.

This is because the old system of compensating for the magnification of sights by reducing the turn rate was based on poorly tuned tables of sensitivity settings for each sight which didn't adapt to your base FOV.

If you turn UsA on (with stock settings), you should feel like the difference between sensitivity is no longer present. If you switch from 8x scope to canted iron sights, it should feel natural. If you use the flip up magnifier, it should feel natural. No matter what sight you use, your sensitivity should feel sensible.

This theoretically allows you to build up superior muscle memory.

How to configure Uniform Soldier Aiming for dummies.



This is the method that I recommend everyone uses. If you don't want to read below and know what Uniform Soldier Aiming is actually doing, that's fine, just follow these instructions and you'll get all the benefit of Uniform soldier aiming.
If you're a CS:GO player you definitely shouldn't differ from this because according to the theory, this should get the sensitivity system working basically same way CS:GO does on it's telescopic rifles.

WARNING: Uniform Soldier Aiming changes sensitivities on your sights to try to make them better. Don't be surprised if it feels funny at first. Sensitivity changes always do.

Step 1: Make sure all your "sight" sensitivity options are at 100%
Sight specific sensitivity sliders are in the advanced part of the control menu. They need to be at their default 100% because they also alter sight sensitivities so they will interfere with the work of Uniform soldier aiming and you won't get a proper feel for the unadulterated effect of UsA.

Step 2: Make sure your soldier zoom sensitivity is at 100%
You should start off with no change to soldier zoom sensitivity to get a feel for the unadulterated effect of UsA. You might find that you don't need to change the soldier zoom sensitivity from 100% when UsA is enabled.
If you don't like it later, this can be changed.

Step 3: Make the Uniform Soldier Aiming Coefficient is at it's default.
The UsA Coefficient is hidden in the advanced menu again. It should be 1.33
You can learn what it does later, but I wouldn't recommend touching this until you know what it does.

Step 5: Turn on Uniform Soldier Aiming
It's in the control options.

Step 6: Consider Changing the option "Field of View Scaling in ADS"
Uniform Soldier Aiming makes your turn rate dependant on your ADS FOV. FOV Scaling heavily changes your ADS FOV on close range sights.
You might find that using UsA allows you to use ADS FOV Scaling on if you couldn't before, because it removes the perceived sensitivity reduction caused by the wide FOV with no change to sensitivty.
I like to call playing with UsA and FOV Scaling on "Oh man! This is just like counter-strike!" mode.

https://www.youtube.com/watch?v=OOI0DLY0r6s [youtube.com]

I'm not saying you should or shouldn't change it. I'm just saying if you turned FOV scaling off before because it gave you nasty sensitivity, think it over again because now it doesn't effect perceived sensitivity.
Now you just have to choose whether you want high RDS fov or low RDS fov. It's purely up to you.

Step 7: TEST!
Play with Uniform Soldier Aiming on for a bit and see if you like it, then switch it off and see if you prefer that.
The best way to test is to try using loadouts that involve switching between close range and long range sights a lot. Canted irons show off the difference especially.
Be prepared to play worse for a bit because you always have to get used to changes in sensitivities.

Optional Step: Tweak zoom sensitivity (only if you must).
If you really need lower sensitivity when you go ADS, you can use the main zoom sensitivity slider to do that.
Only do it if you feel the need though.

DONE!
All that's left to do is decide whether you like it or whether you don't. I recommend you stick with it for at least a day before you write it off.

What does Uniform Soldier Aiming do? (Advanced mode).



WARNING: Everything beyond this point may either make no sense or cook your brain.

Uniform sensitivity defines a "control distance" on your screen, a fixed distance from crosshair, and says "anything at that distance should take the same distance of mouse movement to aim at, at every scope FOV", then it uses clever maths to calculate how the mouse distance should translate to angular displacement changes to make that happen.

Or, if you use a console, it defines a distance on your screen from your crosshair, and says "anything at that distance should take the same amount of time to move to your crosshair if you move your joystick in it's direction at maximum displacement, no matter what the scope FOV".

Now if you are wondering what that control distance is, it's defined by the coefficient.
The distance from the cross hairs at which things are 100% uniform between different scope FOVs is equal to the distance from your crosshair, to the top of your screen, times the UsA coefficient.

So you must be wondering why the default coefficient is 1.33
First, because 1.33 seemed to work best, second, because that's what CS:GO used and compatability is awesome, and third, because when you times your vertical screen height by 1.33, you would get your horizontal screen width if you were using a 4:3 screen, which is the smallest aspect ration screen people use for games.

By setting a distance from your crosshair where it always takes the same distance/time to move an object to the centre of your screen, we provide a framework for our brain to work with as you build up muscle memory.

If anyone needs a more detailed description than that, you can ask.

There's more of this guide to come, but it's too long for one post, so cookies to the first person to bump so I can post the rest.
Here is how it works, when we compare our K/Ds, we assume you ALREADY try to PTFO. It's just a given that if you don't PTFO you suck...
SgtDrakula
MD Enlisted: 2012-07-23
2014-09-30 19:38
oh, thank you, this explains a lot, bump)
OvejaN3gra
ES Enlisted: 2013-09-30
2014-09-30 19:40 , edited 2014-10-18 09:17 by OvejaN3gra
Great work man!. Thanks for the explanation. It is actually a very important setting. When i got my hands on the new patch I tweaked all of the new settings until it felt good. I have to say, I had some good games switching between 3.4x sights and different reddot sights. However I will try to test the new options as you said.
Thanks a lot!!.
Technique2002
US Enlisted: 2012-02-19
2014-09-30 19:40
This really should be stickied.....
Hawk 12g is love, Hawk 12g is life!
DarkEtheereal
GB Enlisted: 2011-10-27
2014-09-30 19:43
GUIDE CONTINUE!


So should you change the coefficient?



You may have thought "Hmm, if a coefficient of 1.33 corresponds to the width of a 4:3 screen, shouldn't I change it to match my widescreen's aspect ratio?"
The answer is no. It will probably feel funny.

Maybe you have thought "Hmm, a coefficient of 1.33 means the circle of uniformity is wider than the screen! Shouldn't I set the coefficient to 1 or less?".
The answer is maybe?

It might be appropriate to play around with the coefficient depending on what you want out of the system, but you need to be careful.

The system as it stands was based around this idea of having it so at a certain distance, you always have to do the exact same thing to get it to the center of your crosshairs, no matter what scope you use. This was with the goal of improving muscle memory and making percieved sensitivity uniform.

The issue is we didn't know what coefficient made perceived sensitivity uniform.

When the setting is far bellow 1, the perceived sensitivity of scopes goes down as their FOV goes down..
When the setting is far above 1, maybe around 2 or 3, sensitivity of scopes goes up as their FOV goes down. That's not good.

The originally planned coefficient was 1, but we found that this too didn't feel quite uniform. Sensitivity still seemed to go down at higher FOV scopes.
At 1.33, the effect doesn't seem to be noticeable. And since we knew CS games already use it, we decided to go with it. It's not necessarily "perfect" but it does the job well.

However, let's say you are a sniper. All you do is snipe all day.
If you are a sniper, first, the sniper scopes limit your screen space so that you can't see anything in the "circle of uniformity" at a coefficient of 1.33. If you want to do drag shooting, you can only see the things in that circle, and maybe you want your sensitivity to be lower on higher zoom scopes for more precision.

In that case, you may want to play with lower coefficients, so that the zone where your muscle memory is most accurate is brought into the circle of your scope.

If you really really really want to have lower sensitivity on higher scopes, you can set the coefficient to 0.

What happens when the coefficient is 0?



According to what I said, the coefficient is used to define a distance by multiplying it with your monitor height.
However if the coefficient is 0, something multiplied by 0 is 0.

So how does that make sense? If the control distance is 0, then that means it takes the same mouse movement to move something no distance to the center of your crosshairs? What?

It turns out when the coefficient is 0, the clever math we use breaks down, because you end up dividing by zero, which isn't fun.
So when the coefficient is 0, a slight change is made to the formula. It doesn't change what happens much. When the coefficient is 0, it acts a lot like when the coefficient is 0.001

Basically when the coefficient is zero, instead of thinking in terms of what happens at a point at a certain distance away from your crosshair, we are thinking about what happens under your crosshair.

Imagine that what's shown on your screen isn't a 3D world, imagine it's an image of a world printed onto a sheet of rubber. When you turn, the sheet of rubber moves, but it also contracts and expands in certain places, so the velocity of the sheet of rubber isn't constant through the entire sheet.
When the coefficient is zero, it's like making sure that the bit of the sheet directly under the crosshairs always has the same velocity when your mouse has the a constant velocity, no matter what sight FOV you are at.

If you don't understand, that's fine. You don't need to. That's the best analogy I could come up with.

Basically when you turn, the projected image on your screen shifts at different rates at different areas because of the deformation of projection. When the coeffficient is zero, the velocity of the point directly under your crosshairs is matched to your mouse velocity in a proportional relationship.

The problem is this isn't helpful really, since your brain still sees the image as 3D, not 2D, so perspective comes in and it ends up not looking uniform.

Should I ever play with the individual sight sensitivity sliders?


In my oppinion you should never touch those things.

They're the quickest way to ruin your muscle memory.
UsA allows you to do most of the stuff you would want to do with them anyway.

If you do choose to change them because you've got some special need to do so, bear in mind that all the settings are multiplicative.

If you apply UsA at the same time as any of the other ADS sensitivity sliders, the sliders will multiply with the UsA to determine your new sensitivity.
Here is how it works, when we compare our K/Ds, we assume you ALREADY try to PTFO. It's just a given that if you don't PTFO you suck...
Crazy_Canadian24
CA Enlisted: 2011-10-26
2014-09-30 20:05
Gonna second that this should be stickied.
Your resident Hardcore specialistâ„¢.
LeShannon_Sharpe
US Enlisted: 2013-12-23
2014-09-30 20:07
Yeah, this needs to be stickied.
JackalWasUsed
US Enlisted: 2012-01-25
2014-09-30 20:08
what about a 16:9 ratio?
DarkEtheereal
GB Enlisted: 2011-10-27
2014-09-30 20:10
bmxbobbo said:
what about a 16:9 ratio?


I'd still recommend leaving the coefficient on 1.33
You can try it set at 16/9 to see if you like it though. Might be good, probably won't be.
Here is how it works, when we compare our K/Ds, we assume you ALREADY try to PTFO. It's just a given that if you don't PTFO you suck...
Ferdiee
SK Enlisted: 2011-10-28
2014-09-30 20:11
So are you saying that we should set FOV scaling to ON when using uniform aiming? How would this work with FOV scaling disabled? (my current setting)
NightwingIvI
Enlisted: 2013-04-01
2014-09-30 20:18
The last bit did hurt my brain, since I've just got a grasp of basic stats, but I will for sure turn on UsA.
Screw Marvel
DarkEtheereal
GB Enlisted: 2011-10-27
2014-09-30 20:20
Ferdiee said:
So are you saying that we should set FOV scaling to ON when using uniform aiming? How would this work with FOV scaling disabled? (my current setting)


I'm saying FOV scaling is your choice, but you should choose again.

Before Uniform soldier aiming, you had to chose between either a wide fov low sensitivity when using close range sights with scaling on, or low fov, sensible sensitivity with scraling off.

Now the sensitivity when scaling is on is much more sensible, and because UsA makes sensitivity depend on FOV, and when scaling is enabled, your FOV when ADS with RDS is almost the same as your base FOV, it essentially feels just like aiming with hipfire.

Personally I value the extra zoom that Scaling OFF delivers, but others might love hipfire style close range ADS with scaling ON.
Here is how it works, when we compare our K/Ds, we assume you ALREADY try to PTFO. It's just a given that if you don't PTFO you suck...
Zombi3Hotd0g
CA Enlisted: 2011-10-24
2014-09-30 20:29
ExpiredCodes said:
Yeah, this needs to be stickied.


Thirded on the stickied request.....
--- t1mb0b
NightwingIvI
Enlisted: 2013-04-01
2014-09-30 20:32
Can we report for sticky or is that an abuse of the function?
Screw Marvel
kellar01
LY Enlisted: 2012-11-08
2014-09-30 20:50 , edited 2014-09-30 20:51 by kellar01
ExpiredCodes said:
Yeah, this needs to be stickied.

EDIT: Well it is now :p
Stronius445
Enlisted: 2013-10-04
2014-09-30 21:02
So that's what it means.....
graham_cracka15
US Enlisted: 2012-07-29
2014-09-30 22:48
As a console player I think I will leave it alone for now. I may come back to it in the future.
DarkEtheereal
GB Enlisted: 2011-10-27
2014-09-30 23:15 , edited 2014-09-30 23:16 by DarkEtheereal
graham_cracka15 said:
As a console player I think I will leave it alone for now. I may come back to it in the future.


It's meant to be equally beneficial to consoles as it is to PC players. It will help you thumbstick users just as much as mouse users, because the sensitivity problem is on both.
I think you should at least try it for a day.
Here is how it works, when we compare our K/Ds, we assume you ALREADY try to PTFO. It's just a given that if you don't PTFO you suck...
BleedingUranium
CA Enlisted: 2011-10-25
2014-10-01 00:19
Setting Zoom Sensitivity to 100% with UsA on results in 1x sights having effectively the same sensitivity as hipfire. That's how it's supposed to work, right?
DarkEtheereal
GB Enlisted: 2011-10-27
2014-10-01 00:26
BleedingUranium said:
Setting Zoom Sensitivity to 100% with UsA on results in 1x sights having effectively the same sensitivity as hipfire. That's how it's supposed to work, right?


Yeah.

But when I say sensitivity, I don't mean turn rate.
It doesn't take the same mouse movement to do a 360.

If the turn rate was the same, it'd feel super sensitive on the zooming sights.

What's the same is the sensation of sensitivity. Everything should FEEL the same.
Here is how it works, when we compare our K/Ds, we assume you ALREADY try to PTFO. It's just a given that if you don't PTFO you suck...
 
Thread is locked.
Thread is locked.