I use 74(+90). I will try to get my USA to match but I dont wanna do math >.<!

Quoted from "BleedingUranium"

Quoted from "I Eat Playdoh"

Wow such vocab for having such a hard time understanding the most basic concepts of how uniform aiming works: your 360 distance/time is NOT uniform. It attempts the equalize the number of pixels traveled on screen for X amount of control input at all zoom levels. Testing based on degrees traversed is a totally flawed method, end of story and if you can't understand that read through this till you have a grasp of what USA does: Important Guide to U - Forums - Battlelog
/ Battlefield 4

You're actually not really making a point here, just saying the same thing with more text. I chatted with Dark a lot back in BF4's CTE, before and after he developed UsA, so this stuff isn't unfamiliar to me.

What you haven't explained is why pixels travelled is supposedly more desirable than distance travelled. Linking me to a post which also doesn't explain this (because it's not the topic there) isn't adding anything useful. Also, I've read it before.

At present I have a functioning, logical model backed up with significant testing, and numerous other people who agree this method massively improves their aiming experience. Don't bother telling me I'm wrong if you're not going to explain and demonstrate why.

I'm not critcizing your testing, but rather the guy I was originally responding to. You did the math to convert degrees traversed relative to zoom level, which he did not from what I could tell. And since he didn't understand my criticism of it all...

Quoted from "grizzlywzzlybear"

I use 74(+90). I will try to get my USA to match but I dont wanna do math >.<!

The FOV you use has no bearing on USA unless the findings here are proven correct. That would mean that DICE has some super funky business going on with aim mechanics in ONLY the console versions even though they have taken the time and effort to add numerous options in for controller users.

I'll try again; Are the findings independent of if you have FoV dependent zoom on or not?

As a side note, my aim drastically improved when I went from 12x% (tried to customize it) to 100%, with the same hipfire sens I use in CS and every other game (~9% at 800DPI, one 180 deg turn when using half of my mouse pad). Universial soldier aiming on. Maybe I've just gotten used to it, but with everything set at 100% it doesn't really feel weird when going back to other games, and then later on back on BF1.

Thanks Mr. Uranium. I used your settings last night on xbox and thoroughly enjoyed the way the game felt.

Thanks for doing all that work.

You should probably clarify your post that this is only for Console, so as to prevent PC players perhaps getting misinformation.

PC works fine as intended with the settings doing what they should.

As far as I would expect on Console, the screen space distance modifier (UsA coefficient) should synchronise turn-rate velocity at full pitch on the stick for any given base sensitivity to screen space across different FOVs. Since max pitch (since BF1 calculates everything from Vertcial, not horizontal FOV) is the only absolute. Gamepad input always features some element of acceleration in how they work at any other position apart from max, making synchronisation impossible when the stick is some point at halfway.

If Julian Manolov has decided to do use a different method for BF1 on Console for UsA than BF4, then I'm not sure what would make more sense, but maybe there is a reason. Have you asked him?

On PC in BF1, even UsA off uses base FOV for ADS turn-rate calculations (just with a 100% fixed coefficient, rather than 133) so UsA is not as necessary as it was in BF4, although it does still help with calculating ADS sens transitions which is still essential in my opinion, although people have different ideas.

Quoted from "TheNoobPolice"

You should probably clarify your post that this is only for Console, so as to prevent PC players perhaps getting misinformation.

PC works fine as intended with the settings doing what they should.

As far as I would expect on Console, the screen space distance modifier (UsA coefficient) should synchronise turn-rate velocity at full pitch on the stick for any given base sensitivity to screen space across different FOVs. Since max pitch (since BF1 calculates everything from Vertcial, not horizontal FOV) is the only absolute. Gamepad input always features some element of acceleration in how they work at any other position apart from max, making synchronisation impossible when the stick is some point at halfway.

If Julian Manolov has decided to do use a different method for BF1 on Console for UsA than BF4, then I'm not sure what would make more sense, but maybe there is a reason. Have you asked him?

On PC in BF1, even UsA off uses base FOV for ADS turn-rate calculations (just with a 100% fixed coefficient, rather than 133) so UsA is not as necessary as it was in BF4, although it does still help with calculating ADS sens transitions which is still essential in my opinion, although people have different ideas.

sometimes it's easy to forget that there exists people that play first person shooter games on consoles with a controller

Ok, I'm confused by the 167% part of this. So, using your example, 25% Soilder Stick Sensitivity sould be mated wit a 83% Zoom sensitivity. What if I ran with a 35% Stick sensitivity?

Or perhaps a better question, is there some kind of formula to determine an ideal Zoom sensitivity using the 167% rule?