kingdowning

There is a config file with a more precise sensitivity value, but the game does not read from it, it only writes to it. So for now the in-game settings are the only option.

They refresh each day at 0:00 UTC. I just snagged one and will send it over for the greater good of the gamers. Thank you for your hard work on this site!

If anyone has a spare key for Marvel Rivals let me know.
I'll try to grab one when the keys are restocked tonight.

If you match FOV and convert the hipfire sensitivity from BF1 to BF2042 you can use the same sensitivity settings for the scopes (USA OFF, ADS FOV ON).
The only exception is the 2.5X which has a bug in BF2042, so you need to calculate it.

Ok. Can I match with the calculator the 8x BF2042 to BF1 and 6x BF2042 to 6x BF5? Should I change individual sens. slider or just the general sens.?

They can't be combined into one because vehicles have a separate FOV setting and a separate base sensitivity. I could potentially rename "All" to "All Soldier" and make it known in the game notes that there is a separate calculation for vehicles.
A lot of different aims use the same sensitivity, this is a limitation of the game. This goes for the soldier sensitivity too, where 6X and 7X both use the 6.00x Zoom Aim Sensitivity settings, and 10X and 12X both use the 10.00x Zoom Aim Sensitivity setting. So when the same sensitivity is listed multiple times with a clarification in parenthesis, you have to choose which one to use. It's the same for in-game and config file, no difference there.
VehicleSensitivityDefaultTurret, VehicleSensitivityTank and VehicleSensitivityTransport are already in the calculator.
The others are either not used in BF2042 (like VehicleSensitivityCavalry) or not possible to add due to how the controls work (like VehicleSensitivityPlanePilot).

Before I start this, I might give off a rude tone so if I do I am sorry.

I was looking through my settings as their were reset from BF2042 and as I rechecked them, I noticed that they were two different All's, All for Solider (All) and All for Vehicles (All Vehicles).  Now this could just be me but I feel that could lead to more people like my brick self to skip over and think that's all the options the calculator has to offer.  So, for me I feel like it would be better to make it be known that their is a different All for just vehicles or possible combine it into one All, but I feel like that you already considered that and ended up not going with it for whatever reason you had.  

Then deeper into it, the All Vehicles aim gives multiple of the same variable given (VehicleSensitivityTank and VehicleSensitivityDefaultTurret) given for the config file preset although I see it does have in the parentheses off what it's for, so I guess this is more of a support help thing than complaint.  So does this mean when it gives the same variable for multiple different things displayed in the parentheses of what it's actually for does it mean I have to switch it from config file to in-game?  And side note since I do not know where to put this, but there are multiple other variables to use for the calculations such as VehicleSensitivityCavalry, VehicleSensitivityDefaultTurret, VehicleSensitivityFieldGun, VehicleSensitivityHMGTurret, VehicleSensitivityHeavyTurret, VehicleSensitivityPlanePilot, VehicleSensitivityTank, VehicleSensitivityTransport, and so why not include these to configure as well, but I also skimmed through it and found these so maybe there useless idk. 

I think that's all I got to say for know but I'll edit it if I have something else to say.

Thank you once again, I appreciate the fast support!

@DPI Wizard
 

I've been using this setup to do all conversions.  And, it works for stuff like Warzone but whenever I do it for VALORANT and Risk of Rain 2 it ends up with a different 360/cm.  And I thought to maintain muscle memory or whatever the 360/cm should be close to each other. 
I can withstand 360/cm difference from VALORANT but with Risk of Rain 2 changing from a 33cm to a 52cm makes it feel like something is wrong and usually screws me up whenever I play Warzone again and I overaim. So, I was just wondering if the fix for it would be changing the [Hipfire / Look] to a different option instead of Jedi's Trick - Vertical.  

Guys I know you want Gundam Evolution and I have requested access, but you don't need to request it four times in a row 🤣

1.21 is just a close approximation of what Jedi's Trick Horizontal would equate to in a vertical coefficient for 16:9.
Using Jedi's Trick Vertical is more consistent, the next update of the calculator will make both options available.

Jedi, is this guy right about the 1.21 coefficient calculation?

Name: Gundam Evolution
Website:  https://store.steampowered.com/app/1816670/GUNDAM_EVOLUTION/
Status: closed beta. request beta access on steam store page.
Release date: closed beta is out now
Availability: (Free, invite only, pre-purchase, purchase etc) FREE
 

You can do it manually. I updated my previous post. This is really uniqe needs. And it is not necessary to implement it. Because it is practicaly individual adjusting. And for that there is standard monitor distance method.
In that video yes. But coefficient is changing depanding on your input and output (Win/Hipfire/ADS/Scope). You can imagine coeficient as a reference point on your monitor. And you can always find a position from which other Aims will have less deviation in sensitivity than from another position.
And you can do it by changing coefficient in game if implemented, or by changing sensitivity of each Aim separately
Great job! Mission completed I made a quick check in CS:GO and works good. Now it's perfect  
If you are playing more games, first option is better (360° for Hipfire)
I will share with you guys little philosophy behind the vertical methods. As you play, you will focus most on the area of the screen around the crosshair. And of course you want the minimum difference in sensitivity here. Rather than having zero deviation in sensitivity at the edge of the screen, for example (MD 100%). I prepared some examples below for you.
Jedi’s Trick - Vertical (Recommended) 

                       Settings 1                                                 Settings 2                                               Settings 3
As you can see vertical method have lower deviation between points in focused area which is represented by orange square (VFOV = HFOV = "1:1"). 

Jedi’s Trick - Horizontal 

                       Settings 4                                             Settings 5                                               Settings 6
Horizontal method will find lowest deviation in sensitivity for whole horizontal field of view. But differences in focused area are bigger.

Monitor distance 0% is also for 2d to 3d. The distance to move the cursor 1 pixel is the same distance to turn 1 pixel. If you measure the fov in the 4 adjacent middle pixels, you will turn half that.

It's not that complicated. It's all about the physical scale of the image you see. If the scale changes, then sensitivity changes as well and you need to adjust the cm/360 to fix it. Treat the monitor as a window that you look through.
 
Think of the resolution, fov, and monitor as an image resizer. If any of these change the physical size of the image, then you need to change your cm/360 by the same amount (monitor distance 0%).
You will need to change the cm/360 in these cases because they will change physical size of the game:
Different fov on the same monitor Same fov on different sized monitors Reducing resolution without upscaling Changing aspect ratio in a horizontal fov game  
 
Start with 103 fov at 1080p

 
If you reduce the resolution to 720p without upscaling it, then you have shrank the physical size of the image by 66.67% of the original size.
You will want to reduce your cm/360 to 66.66% of the original value as well.

 
This is identical to zooming out 1.5x to ~124 fov. (2 * atan(3/2 * tan(103/2 * pi/180)) * 180/pi = ~124).
This shows that the resolution can be used as an FOV slider if you want, you just don't get to see the extra fov since its black.

 
 
Here we change the fov to 162 fov. It is a 5x zoom difference. It practically shrank the image to 20% of the original, so your cm/360 needs to shrink to 20% of the original value as well.

 
 
Here is 103 fov resized to 20%, overlayed on the 162 fov. If this monitor was 5x larger than the above, then there would be no need to change the cm/360. The physical size of the 103 fov area in yellow would be identical to the monitor above. Since the monitor is basically a window that you are looking through, the 5x bigger window provides the extra fov.

 
 
Here is the 162 fov image resized 500%. You can see that it's identical to 103 fov.

 

If you reduce the resolution width to go from 16:9 to 4:3, and it only crops off the sides, then there is no change to the physical size of the image and no change to the sensitivity.

 
If the game uses horizontal fov though, and it tries to keep the 103 on 1440px instead of 1920px, then there is a 75% scale difference (1440/1920). So your cm/360 needs to be 75% of the original value as well.

 
This 75% reduction results in an equivalent fov of ~118 (2 * atan(1920/1440 * tan(103/2 * pi/180)) * 180/pi).

Till today I thought that Jedis Trick was meant for 2D (Windows) to 3D calculations and not actually for Scope Sens, which is why I never used it. So it was already very hepful

Thanks to this website and a few other sources, I was able to throw together a video explaining most of the main settings that affect sensitivity when it comes to FPS gaming. Thanks to DPI Wizard and MacSquirrel_Jedi especially for all their input and help on these topics. Would be honored if you'd check it out, and feel free to leave any input or criticism on what I could have done better!
Much love!!!
Spencer

Good video thank you. 
What i would also like would be a brief explanation of the resolution and aspect ratio used in the game and that these dont change the sensitivity. Maybe also a short info how sensitivity change when switching monitors - I think these are more specific problems but still interesting.

Thanks to this website and a few other sources, I was able to throw together a video explaining most of the main settings that affect sensitivity when it comes to FPS gaming. Thanks to DPI Wizard and MacSquirrel_Jedi especially for all their input and help on these topics. Would be honored if you'd check it out, and feel free to leave any input or criticism on what I could have done better!
Much love!!!
Spencer

Thank you so much DPI Wizard, and thanks again for this amazing website!! Keep up your great work!!

Great video man! It summarizes the sensitivity nicely  It's always nice to see someone understand. Thanks
I still do not saw a video on internet that explain just the elementary basics of sensitivity in visual way. Because i still feel that lots of people do not understand what is behind red/green dots in graph. I tried to explain it in my quick start guide, but video is still better way to do it

Thanks to this website and a few other sources, I was able to throw together a video explaining most of the main settings that affect sensitivity when it comes to FPS gaming. Thanks to DPI Wizard and MacSquirrel_Jedi especially for all their input and help on these topics. Would be honored if you'd check it out, and feel free to leave any input or criticism on what I could have done better!
Much love!!!
Spencer

its great having  a video that summarises some of the basics that tend to get asked here alot , so far a few points of concern for me would be
1000hz vs 500hz doesnt matter and some hardware as well as some games perform better / more consitent on 500 than on 1000
another nag i've got for you besides that is that pseudo science about 1600 dpi being "superior", now dont get me wrong from a certain standpoint( accel) it has its benefits but this summs it up quite well ( in regards to those latency meassurements between 400 and 1600 dpi some pupular yters have been spreading)

----

a change in hipfire fov wills still affect our perception of "sensetivity" (unless you strictly seperate distance and sens) this isnt the whole truth, the whole fov/ aspect ratio (+stretched res bs ) thing is another rabit hole of itself so i get why youd only briefly mention it or leave it out.
 
criticism aside
the whole video and effort you put in is commendable and id consider using the link in some cases in which i am too lazy to explain stuff i like it alot, and appreciate the video quality the whole sens thing is something  many hardly understand because there is a lot of heresay going on so getting it in such a compressed formfactor is nice