ProuDBeasT

Support for focal length on and off is added.

And now everything is updated!

A new feature is added to the calculator that enables you to reverse calculate your current sensitivity. This functionality helps you identify the most suitable method, coefficient, and scale to align with your existing sensitivity settings. It simplifies the process of finding the precise matching parameters to effectively maintain your preferred sensitivity.

The "Reverse" button is positioned above the selected game in the "Convert from" dropdown menu. Initially, it will appear grayed out and inactive until specific criteria are fulfilled:
The selected aim must be "All" and be comprised of multiple sensitivity variables. For instance, it won't function for games that employ various aim calculations but all utilize the hipfire sensitivity. The calculation for the "All" aim must be error-free for the primary sensitivity. Errors related to ADS and scope aims being out of range won't affect this condition. When these conditions are met, the "Reverse" button will turn green. The sensitivity, FOV, resolution, and other parameters you input for the "All" aim will act as the foundation for the reverse calculation, necessitating an exact match with your current settings.

When you click the "Reverse" button, a popup with all the aim sensitivity will show. Note that aims that are not ADS or scope will not show up. Some sensitivity settings are shared between more than one aim, if so a dropdown box will show next to the sensitivity and you need to select the aim you are entering the sensitivity for. Enter your current sensitivity into corresponding boxes, vertical sensitivity is also supported for reverse calculation. You do not have to enter a value into all the boxes, but it is recommended for best accuracy. Once all values are entered, clicking "Reverse!" will generate a table presenting all suggested calculations based on your inputs.
If you are converting from a game with both ADS and scope sensitivity, you will see three tables: One for the best match for both ADS and scope combined, one for just ADS and one for just scope. If the game only has ADS or scope, only one table for both ADS and scope will show up. Vertical sensitivity will show up at the bottom.

 
The Monitor Distance methods will only show up in the ADS and scope table if the coefficient and scale is identical for ADS and scope.
Click the "Use" toggle for the matching method(s) you want to use, then click "Apply" to use the settings for your calculation.
If you find anything not working as expected, post it here. Note that you will not always get the expected result because of rounding.

https://www.mouse-sensitivity.com/?share=d5477b666b9d2b08703b975e957f87af
Don't forget to adjust the "scale" option according to your ADS multiplier value in Valorant.

No, it's a tool for the users so they can enter their existing sensitivity settings and get the best matching conversion setup back. This way you can find the best setup based on your current settings, so you can replicate it to other games.
Especially useful for those who have just fiddled with their sensitivity settings to find a setup that feels good, but have no idea how to convert this to other games.

Ok, maybe not such a big refresh to the eye, but the whole front-end code is rewritten to use a proper grid instead of stacked elements. This was quite a big job with a lot of changes, so let me know if you see something that is messed up, like elements being in the wrong place or not line up.
Changes include:
The whole front-end of the calculator is updated to use a proper grid layout instead of stacked elements. It looks about the same, but elements are now more properly aligned and scaled, as well as updated to generally look more streamlined. This update also allows for a much better layout on smartphones etc. The blue highlight around the active conversions now works correctly. The "Advanced" output is now a lot easier to read and contains the FOV of each aim. Simple mode now hides more elements not in use to make it look less complicated. Text that is too long will now scale down and split into more lines to not break the layout. Fixed a bug where vertical scale was not applied correctly. Fixed a bug where converting from an "All" aim to "Windows/2D" only used the "Windows/2D" conversion setup. Fixed a bug where the MDD power affected affected some conversions as scale. Fixed an issue where the advanced mode didn't show information for multiplier 2. FOV range is now enforced for multipliers to avoid calculation errors.

Hi!
There's a user ( @TheNoobPolice) that I think that explains it very well. The main takeaway that I've got from him (I might be wrong interpreting his view) is that we all have a level of aim skill and we improve it overtime, regardless of the sensitivity we choose. The thing is that when we get used to a certain sensitivity, our aim with that sensitivity is basically the reflection of our own level of aim skill (in contrast, when you change your sensitivity, there's an adaptation period until you reach your aim skill level again -note that in this process you might still improve that base level-). This goes to say that you should probably avoid being in that adaptation phase and your "perfect" sensitivity is the one that you are used to the most.
Now, if you want to change your sensitivity (and then stick to it), I've seen that it's usually recommended to go with a 360º distance ranging from 20 to 40cm/360º, give or take. It doesn't really matter which one you choose within that range as long as you feel comfortable and stay consistent, as you'll get to your actual aim skill level after adapting to it.
Another aspect to take into account is desktop and ADS scaling. I'd suggest to go through all the games that you usually play, then see which one has the worst sensitivity settings and adapt to that one; e.g. I love playing Destiny 2 but it has a very limited FOV and hipfire sensitivity sliders, and the ADS scaling doesn't allow to set MDV 0%, so I decided to match everything to 100.8 HFOV (the maximum FOV available in the game) and MDH 100% (which is the only option that actually makes sense for me in that game). When you've done that, look for an in-game value that gives you a sensitivity that's between 20 and 40cm/360º (more or less) and convert from that to everything else. Alternatively, you can select a desktop sensitivity (DPI) that gives you your desired 360º distance when converted from desktop to game, so that you always stay consistent.
I'd also like to point out that you can also adapt to any MDV/MDH % if you use different zoom levels in aim trainers, so, although MDV 0% is objectively the most reliable conversion method, if your base game doesn't support it, it's probably not that big of a deal, as long as it supports at least one logical ADS scaling method.
This might be what you need, but there's a lot of possibilities, so maybe someone else can give you an advice that fits you better.

I've updated the calculations now using the mouse fix, as without the fix there's a ton of variables affecting the sensitivity.
Also added FOV instructions

Happy new year everyone!
A new update was just published that adds a few new features:
Favorites - Click the star next to the game in the calculation output to add it to your favorites.

Favorites will appear in the top of the game list for easier access.

  Reverse calculation - You can now easily reverse any calculation by clicking the reverse icon between the games.

This will swap the "convert from" to "convert to" and preserve all converted data. This makes it easier to see if everything matches up, but note that: Aim calculations will be different if hipfire is matched using 360 distance and the hipfire FOV is not the same, since you change source. Any discrepancy due to rounding limitations will be carried over, which might make the reverse different.
  A new conversion method called "Jedi's Trick" is added.

More info in this thread, but it basically uses the average distance between monitor distance 0% and 100% for both axis.

feel free to ask for help if you are struggling to udnerstand the calculator
played my fair share of destiny over the past couple of years and ill  gladly help you  : )
------------------
if you mean the weird zoom system destiny uses, that kind of hinders making all of the what feels like 800 zoom levels available here that is indeed about as frustrating as destiny*s horrendous fov options.
but you know destiny players tend to downvote anything they dont understand and comment a hurr durr the game is flawless its a you problem whenever anyone tries to give some input on how to improve the user experience.
--------------
the d2 related things this site offers work pretty much flawless once you know what it does and how it works but the beginning can indeed be quite rough but that part is pretty independent as far as games go

i usually ignore stretched messages because they always end up being annoying about their half assed reasoning for using stretched 
but you havent made it very clear to begin with  is your monitor actually 16:10 or are you using stretched res ?
if you are on native 16:10 that is as easy as it wouldbe with 16:9 also

Thanks, updated it now. Can they make up their mind lol...

That's right, but I think that using the mean could be the play or not depending on the amount of discrepancy and the discrepancy tolerance of each individual. In this case, assuming the same HFOV, the mean scalar_0 value would give a 13% increase in MDH for the 1x group (MDH 88%) and an 8% decrease for the second group (MDH 67%). A >13% difference in MDH might be tolerable.
For me, personally, a 25% change in MDH is too big of a difference. MDH 100% for the 1x group gives a scalar_0 value equal to MDH 75% for the second group. That's so noticeable for me that I just try to avoid using those iron sights (very annoying in the early game). Now, if I used the mean scalar_0 value, it'd be the same as using MDH ~125% for the first group and MDH ~86% for the second one. That's up to a 25% difference again.

The conversion method that you're using in CoD is MDH 75%. It'd be set up like this:
https://www.mouse-sensitivity.com/?share=4f80cd5879d4a98cae9dd6d6408064fd
I'd suggest you to use the same FOV values for both games and also using the first "scalar_0" value in Apex (not the second one).

Hi!
I've posted a bug report on the EA forums so that the devs can see that there are some issues with the 1X ADS sensitivity slider: https://answers.ea.com/t5/Bug-Reports/The-1x-ADS-sensitivity-slider-is-shared-between-3-different-zoom/td-p/10452790
If this gets enough attention, Respawn might fix it, as they've done in the latest patch, where they included the option to disable the FOV changes when using abilities such as Octane's stim or Bloodhound's ult. That FOV issue was also posted on the EA forums, it had lots of support and it was even upvoted by two EA CMs. This bug report about the 1X slider has also been upvoted by one of them already, so it could get somewhere. 
Upvoting and commenting to bring this issue to the front pages on the EA forums would help a lot, so thank you to anyone who does it.

Hi!
I've posted a bug report on the EA forums so that the devs can see that there are some issues with the 1X ADS sensitivity slider: https://answers.ea.com/t5/Bug-Reports/The-1x-ADS-sensitivity-slider-is-shared-between-3-different-zoom/td-p/10452790
If this gets enough attention, Respawn might fix it, as they've done in the latest patch, where they included the option to disable the FOV changes when using abilities such as Octane's stim or Bloodhound's ult. That FOV issue was also posted on the EA forums, it had lots of support and it was even upvoted by two EA CMs. This bug report about the 1X slider has also been upvoted by one of them already, so it could get somewhere. 
Upvoting and commenting to bring this issue to the front pages on the EA forums would help a lot, so thank you to anyone who does it.

Hi!
I've posted a bug report on the EA forums so that the devs can see that there are some issues with the 1X ADS sensitivity slider: https://answers.ea.com/t5/Bug-Reports/The-1x-ADS-sensitivity-slider-is-shared-between-3-different-zoom/td-p/10452790
If this gets enough attention, Respawn might fix it, as they've done in the latest patch, where they included the option to disable the FOV changes when using abilities such as Octane's stim or Bloodhound's ult. That FOV issue was also posted on the EA forums, it had lots of support and it was even upvoted by two EA CMs. This bug report about the 1X slider has also been upvoted by one of them already, so it could get somewhere. 
Upvoting and commenting to bring this issue to the front pages on the EA forums would help a lot, so thank you to anyone who does it.

Hi!
I've posted a bug report on the EA forums so that the devs can see that there are some issues with the 1X ADS sensitivity slider: https://answers.ea.com/t5/Bug-Reports/The-1x-ADS-sensitivity-slider-is-shared-between-3-different-zoom/td-p/10452790
If this gets enough attention, Respawn might fix it, as they've done in the latest patch, where they included the option to disable the FOV changes when using abilities such as Octane's stim or Bloodhound's ult. That FOV issue was also posted on the EA forums, it had lots of support and it was even upvoted by two EA CMs. This bug report about the 1X slider has also been upvoted by one of them already, so it could get somewhere. 
Upvoting and commenting to bring this issue to the front pages on the EA forums would help a lot, so thank you to anyone who does it.

I'd say that sticking to MDH 0% is a good solution. You're already used to it, so the main factor that decides right now if you hit your flicks or not is your mouse coordination. Getting used to a higher MDH % won't change your coordination by itself, so the % of flicks that you hit after adapting will probably be the same.

Wow I've used this website for many years, crazy to finally see I game I've worked on appear on the homepage
(I was actually visitng for Necromunda: Hired Gun though haha)
 

Are you kidding me? For every game I need to:
Buy it (if not free) Download it Potentially play a bit Analyze movement Reverse engineer sensitivity formula Measure FOV/reverse engineer it Analyze potential aims and reverse engineer them Potential issues with acceleration/smoothing or similar needs to be worked out or worked around and so on Then it needs to be tested and verified to work as intended with The calculator Different DPIs Different FOVs Reporting rates Resolutions Aspect ratios Windows settings and so on. Adding a game can take anywhere from a few hours to many days. It's a bit more work than adding a game name to the calculator... And premium members usually gets priority.

Since your hipfire FOV in Apex is greater than the hipfire FOV  in Valorant and you are used to MDH 0% (1.0 ADS multiplier in Apex), matching your hipfire sensitivities using MDH 0% will give you that ADS "feel" (Valorant hipfire would be like a sight with 103 HFOV in Apex):
https://www.mouse-sensitivity.com/?share=45f894cabeadf1a65388d6633f45637e

useless, you are trying to recreate a flawed system 
 the reason why ubi implemented the new system is that the old values were not good so there is little reason to match 
yes this is 0% and if you use this you can easily  match both apex as well as call of duty 
 
https://www.mouse-sensitivity.com/?share=14510c00b119a2f252c9b57619da140f replace the bottom game 

I've added a new aim to Destiny 2 called "Custom Zoom Ratio" now, so you can simply enter any zoom ratio as Sensitivity 2 to get the correct calculation for any weapon and aim.

Valorant converts hipfire sens to ADS using MDH 100% by default (Multiplier = 1.0). It also has a locked 103 HFOV (16:9). The same settings in R6S would be: 
https://www.mouse-sensitivity.com/?share=5deb8b4bf6b4b72f013c82129f862f91
These are the key calculator settings in order to achieve the same sensitivity: