CaptaPraelium

The answer is: The distance your mouse travels when you rotate your arm through a 90 degree arc. More than this is bad for your body (over-rotates the shoulder), less than this is bad for your accuracy (lower sensitivity makes for higher accuracy) and your body (over-stresses the wrist).

It is just the focal length / zoom ratio / 0% / visuomotor / pixel ratio formula.
sens multiplier = tan(ZoomFOV/2)/tan(HipFOV/2) 
FOV’s in radians, either vertical or horizontal. doesn’t matter in this instance as long as they are both the same measurement.

A lot of these going around lately. Could you please convert that to metric for me?

Joking, but not joking. Get measurements, because feels lie. A lot. Like, most of the time.
Please don't take that personally as an attack on your or your favourite streamers, it's just the human condition.

The following command will fix it for you:
$path = '\Documents\Battlefield 2042\settings\'; $infile = 'PROFSAVE_Profile'; $outfile = 'PROFSAVE_Profile_Patch3'; Rename-Item $env:USERPROFILE$path$infile $outfile; Get-Content $env:USERPROFILE$path$outfile | Select-String -pattern "ConceptYaw" -notmatch | Out-File -Encoding utf8NoBOM $env:USERPROFILE$path$infile Just paste that into powershell and hit enter.
 
It will rename the existing file and otherwise leave it untouched. It will then create a copy of it with the correct name and the broken lines removed. If you use nonstandard bindings you'll need to recreate them but chances are that's all. HTH

no its a horrible idea dont exclusively use one type of aim,
especially not the one that is the most prone to give you carpal tunnel and other health issues down the line ( pls dont mess up your wrist )
------------------
there is no reason to not use the respective body parts that are best designed to accomplish a type of movement
so small adjustements= fingers slightly larger fine control wrist
any larger motion would be arm or shoudl based
---------
this video isnt flawless and pls dont get too stuck up on distances and that sutff but the aspect of using the types of aim for the respective movement fits well in training experimenting with exclusve styles is alright but if or rather when you overdo that has the potential to do more harm than good
 
TLDR: dont exclusively use any kind of aim ( especially not your wrist ) , there is no "god sense" that will accomplish all tasks perfectly so dont get too hung up on trying to achieve that distance
keep playing around and expand your limit sens / aim wise the more / lomger you play the more comfortable you should get with swapping sens and stuff and the less change should impact you
 
 
 
 

Cool, I'll let you know when I have a beta version of it up and running so you can verify it
I'll name them Jedi's Trick - Horizontal and Vertical maybe.
I'm working on a lot on new features like swapping input and output with a click (to reverse the calculation) and adding games favorites so they appear in the top of the list, I'll include this in the next update.

I could add this as a conversion option if you don't mind

The following command will fix it for you:
$path = '\Documents\Battlefield 2042\settings\'; $infile = 'PROFSAVE_Profile'; $outfile = 'PROFSAVE_Profile_Patch3'; Rename-Item $env:USERPROFILE$path$infile $outfile; Get-Content $env:USERPROFILE$path$outfile | Select-String -pattern "ConceptYaw" -notmatch | Out-File -Encoding utf8NoBOM $env:USERPROFILE$path$infile Just paste that into powershell and hit enter.
 
It will rename the existing file and otherwise leave it untouched. It will then create a copy of it with the correct name and the broken lines removed. If you use nonstandard bindings you'll need to recreate them but chances are that's all. HTH

@DPI Wizard I figured out why people think the controller settings affect the mouse input at least.

The soldier zoom sens multiplier and ADS FOV etc are obviously global functions that are clearly not "gamepad" settings of course, but because for convenience these are exposed in the controller menu too, players are not realising that they are global functions and not controller stick settings.

This actually make total sense from a code perspective, no point writing two functions that do the same thing of just scaling camera speed by a linear multiplier, but the way it is presented in the UI has confused people into thinking they are gamepad settings.

So it seems DICE just need to update the UI, rather than the mouse input lol

Sorry this is a little offtopic but I have a couple tips that might be useful:

1) Getting your controller to work on PC
2042 wants to use your first game controller and only that one. Lots of devices have game controller abilities even if they aren't a controller (eg my mouse does) so your controller may not be seen by the game. You can use https://github.com/ViGEm/HidHide  to hide all but the one you want to use like so:


 
2) Getting OBS to capture 2042 with an RTSS overlay:
The new version of RTSS will work with BF2042 out-of-the-box, and OBS will capture BF2042 out-of-the-box, but combine all three, and OBS captures a blank screen.
You need to edit the bf2042.exe.cfg file (C:\Program Files (x86)\RivaTuner Statistics Server\Profiles\BF2042.exe.cfg) and add these two lines to the hooking section:
[Hooking] HookDXGISwapChainPresentVT = 1 HookDXGISwapChainResizeBuffersVT = 1
Enjoy.

Every failure to adapt to the new game or comprehend the new tech, is a bug, anyone good at any similar game is immediately a CS PhD, anyone who tries to deal in facts and data is toxic, anyone who wants a decent team is griefing.... Is it any wonder they served up a game for a generation of gamers who can't handle conflict?

tbh the off feeling is 100% from the actual zoom levels which wizard mentioned above.

"The sens is broken, it's off with muh feels cause I'm a pro gamer"

- sends exactly the right amount of counts to do a turn and at ends up at exactly the same pixel at multiple input speeds...

"err.... it's the gamepad settings that are changing everything!!!"

- literally sets gamepad settings from zero to max, same script turns exact same turn distance either way

"errr....well the scripts are wrong, my human hand knows best!"

- sends input from an Arduino to mitigate any issue of script incompatibility

""you are just trolling, I'm going to ban you from my server"

- OK then 😂

I literally just had that conversation lol. Not a lot you can do with that can you?

A lot of these going around lately. Could you please convert that to metric for me?

Joking, but not joking. Get measurements, because feels lie. A lot. Like, most of the time.
Please don't take that personally as an attack on your or your favourite streamers, it's just the human condition.

I probably should pipe up on this one since the concept is originally mine... but I never could get the math right and eventually decided not to bother, so I'm glad you've made some effort, Jedi.

The concept with this is simple: if you're using some monitor distance, it's always going to be wrong everywhere but one place, so let's just minimise the error overall, right? But it's not so simple as splitting your 0% and 100% distances (averaging) because it's nonlinear. That's where the math gets fun. It's not totally hard math but it's not garden variety either
Then it gets saucy when you realise there's a difference between minimising error magnitude (how wrong is it, 1 dimension) and error volume (how much of the screen is wrong and how wrong is it? 3 dimensions....)

Reason I decided not to bother in the end was because, put simply, the more I brushed up on my calculus (it's been a long while) the more I realised that 0% was 'the way'.

Buuuuut, back then I was completely focussed on in-game matching, and cared not for the desktop. And I had the same experience as you, jedi: I'd leave game from flicking to heads like it was easy and I couldn't flick to an OK button or a text box if my life depended on it. And I don't know about the rest of you, but I use the windows desktop a LOT. More than I do 3D gaming, such is life. As far as I can see it, if there's any value to maintaining sensitivity between games and zoom levels, there is that same value in maintaining it to the desktop.
Trouble is there's absolutely no way you're matching the desktop to any more than one FOV. So you've definitely got to pick one. I tend to play the same kind of games so my hipfire FOV is always the same and it's not an issue for me: match desktop to my standard hipfire, then 0% from there in the 3D world. But for people who don't have a standard hipfire, I'm not sure there's any way to extract any benefit in matching to desktop at all.

And then there's the million dollar question of what defines desktop speed in the first place. 0%? 100%? Horizontal? Vertical? Fight!

And the very real consideration of how far we are from the monitor/monitor dimensions, which matter less in the 3D space, but actually help to answer the above question, in a 2D space.

Welcome to my years-old rotting can of worms.

I probably should pipe up on this one since the concept is originally mine... but I never could get the math right and eventually decided not to bother, so I'm glad you've made some effort, Jedi.

The concept with this is simple: if you're using some monitor distance, it's always going to be wrong everywhere but one place, so let's just minimise the error overall, right? But it's not so simple as splitting your 0% and 100% distances (averaging) because it's nonlinear. That's where the math gets fun. It's not totally hard math but it's not garden variety either
Then it gets saucy when you realise there's a difference between minimising error magnitude (how wrong is it, 1 dimension) and error volume (how much of the screen is wrong and how wrong is it? 3 dimensions....)

Reason I decided not to bother in the end was because, put simply, the more I brushed up on my calculus (it's been a long while) the more I realised that 0% was 'the way'.

Buuuuut, back then I was completely focussed on in-game matching, and cared not for the desktop. And I had the same experience as you, jedi: I'd leave game from flicking to heads like it was easy and I couldn't flick to an OK button or a text box if my life depended on it. And I don't know about the rest of you, but I use the windows desktop a LOT. More than I do 3D gaming, such is life. As far as I can see it, if there's any value to maintaining sensitivity between games and zoom levels, there is that same value in maintaining it to the desktop.
Trouble is there's absolutely no way you're matching the desktop to any more than one FOV. So you've definitely got to pick one. I tend to play the same kind of games so my hipfire FOV is always the same and it's not an issue for me: match desktop to my standard hipfire, then 0% from there in the 3D world. But for people who don't have a standard hipfire, I'm not sure there's any way to extract any benefit in matching to desktop at all.

And then there's the million dollar question of what defines desktop speed in the first place. 0%? 100%? Horizontal? Vertical? Fight!

And the very real consideration of how far we are from the monitor/monitor dimensions, which matter less in the 3D space, but actually help to answer the above question, in a 2D space.

Welcome to my years-old rotting can of worms.

There's a bit of an issue with the alignment though, since the game info needs to align with the game if side-by-side, and be pushed down and ignore the alignment if the resolution is not wide enough. But I'll find a solution eventually 😄

I'm actually working on exactly this, it should be ready for the next version.

Ideally, I feel it would be an improvement that when the website is expanded on the desktop to sufficient page width, that the "Game Info" data could be shown along side the "Calculations", rather than underneath. Apologies if there is a way to do this already I have missed.

This would make it much easier when entering many values into a new game that uses config files where you don't know where to paste the values yet, and / or to quickly gather information without lots of scrolling up and down all the time.

Rough mockup in paint:


 

Here's a full comparison between BFV and BF 2042 scopes (10x missing on BF2042, working on it!). These are the base values showing the true optical zoom, those under 3.00x will be affected by ADS FOV on/off.
BFV are using the actual optical zoom for the scopes.
BF 2042 uses seemingly arbitrarily assigned values, but they almost line up on a linear axis.
Scope Zoom BFV Zoom BF 2042 1.25 1.250 1.710 1.50 1.500 1.997 2.00 2.000 2.586 2.50 2.500 3.188 3.00 3.000 3.793 3.50 3.500 4.405 4.00 4.000 5.016 5.00 5.000   6.00 6.000 7.482 7.00   8.711 8.00 8.000 9.950 10.00 10.000 12.420 12.00   14.907 Edit: 10X scope added!

USA does exactly what it is supposed to here at least. Again some might experience bugs, but here's a demo of it working as intended before the patch tomorrow:
 

That’s all totally unnecessary and just placebo.
Just so you know how mouse input works because it seems like you may not, but that’s fine. A mouse sends a packet of (x,y) data to the OS as defined by the DPI value and distance moved since the last poll timeframe (usually 1ms).
The game then takes this data and converts it to angular rotation, using a fixed pitch/yaw value and a variable (usually linear) sensitivity multiplier. So if it was pitch/yaw of 0.022 degrees at sens 1 for a given game, and you moved (10,5) at sens 2 then you would turn 0.44 degrees horizontally and 0.22 degrees vertically in a single update. These updates are then continually grouped together by the game engine since last simulation loop and divided by a fixed time constant (to ensure frame rate doesn’t affect the calculated distance).
When DPI wizard here analyses a game using scripts, he would send the exact same counts distance value at multiple speeds and cadences to detect what would happen if a mouse was moved slow or fast for the same distance, which would show if there was any baked-in acceleration, smoothing or packet loss(negative accel). Since the input now produces the same result every time, there is no issue.
Mouse sensitivity isn’t a black art. It’s just an objectively measurable ratio between an input and an output distance and simple math - it either arrives at the correct position in the game world for the same counts distance input, or it doesn’t.
I’m not really sure what you are trying to achieve with that video but it is not going to help either yourself or anyone else to be doing all that. Unless you are happy for people to waste their time trying to copy that just to get views then it’s probably best if you just deleted it

Also also... there's a bug (in the game, not the calculator) with the 2.5x scope, it uses the wrong FOV for the "ADS Off" sensitivity calculation than the scope actually is.
The calculator accounts for this if it affects you

Added a bunch more scopes now!
Some minor FOV adjustments might follow, but nothing that should be of significance.

It definitely doesn't affect the sensitivity, but might help with how the motion is perceived. I can't tell the difference with it on or off, maybe I'm not doing the right "certain camera movements" to trigger it.
3rd person vehicle was never added to the BFV calculations, I'll see if I can get it analyzed.