DPI Wizard

Let me repeat what a little paragraph from the instructions: TLDR: There is no such thing as 1:1 when it comes to different FOV's.

Apex scopes scale using MDV 0%, so if the calculator is set up to also use MDV 0% (or MDH 0% if you have the same aspect ratio) they will and should all show the same value

The way the "All" conversion work is by matching everything to the hipfire sensitivity of the input game. So when you change the USA coefficient you only change the calculation for the BF4 scopes. Hipfire is the same, so PUBG will also be the same. All the scopes for both games in your screenshots are actually still the same, since the calculator compensates for your change in USA by changing the BF4 scopes. What you need to do is to make sure the conversion setup matches your BF4 settings. Then calculations will change for PUBG as well. For your first screenshot the setup should be like this so all your scopes in BF4 are calculated to sensitivity 1: And if you change either coefficient or zoom all, you also need to change the conversion setup accordingly. I hope this clears it up!

If you're using MDH/MDV 0% there is not discrepancy shown. It's in the pipeline to add this!

0% will not show discrepancy. It's in the todo list to add this. The issue is that technically 0% is no distance, so the discrepancy must be calculated based on something else, like 360 distance.

Just tested, don't have time to make a video right now though. First of all the game does not register a "PressAndReleaseMouseButton" command at all when in a game. It does register in the menus however. By setting a 5ms delay between "press" and "release" it does register most of the time (still not every time). And the bullet mostly fires before any movement, while occasionally it correctly fires between the two movements. It never fires after the two when I tested.

See the game notes, it is in the %USERPROFILE%\Saved Games\Respawn\Apex\profile\profile.cfg file.

Your FOV is wrong. Config file calculations expect config file FOV whenever possible, and it is not unusual that the value is different from the in-game value. If you have it set to 110 in-game that would be 1.55 in the config file

All aims in R6 scale differently, so the values for the scopes are what you need to set the ADS to for that scope to match the sensitivity. It's a very bad game design, and ideally you should change sensitivity based on the aim/scope you are using.

Can you try again now? Try to save a profile and see if it loads correctly.

I'm looking into this now.

Thanks for the report, that's one of the unintentional changes the Auto FOV feature caused. Fixed it now, so reload the page and it should work like before.

An update was just published, do you still have the issue?

I've been working on this for the entire week, but it's finally done! Auto FOV is now live, read more about it in the instructions! While it might seem simple on the surface it's a quite complicated feature, so let me know if anything acts weird!

This is exactly what the scale option is for Set the conversion method to match what the game uses (MDV 133.3333 so it works for all aspect ratios), and set the scale to match your zoom sens (120 %):

Your conversion setup for ADS is set to MDH 0%, this means that the 360 distance will vary a lot depending on FOV. This conversion method keeps a constant tracking speed. So if what you want is the same 360 distance, select this in the conversion setup.

The issue with games like RE2 is that the variation is huge. You might get twice or half the calculated 360 distance based on your DPI and how you move your mouse. Some games like all the Serious Sam games have issues too, but it's more consistent. If it's always off by say +/- 10% I can make a calculation. What I possibly can do is to see if RE2 etc is consistent at any kind of (human) movement and use that as a reference with the game notes informing that e.g. small movement will be off. Regarding the automatic FOV conversion, I'm going to implement that very soon. Updating all games will take months (there's over 500 games and almost 2000 entries to go through), but I'll make an update that informs you that FOV has been calculated and you need to verify that it's valid for the games that haven't been updated.

The FOV must be set in profile.cfg, not settings.cfg

Select R6 and enter all your settings. Use the "All" aim, and adjust the conversion setup so the ADS you prefer matches your ADS setting. Select Apex and enter your FOV (preferably the same actual FOV as in R6), voila.

Can you post a screenshot of your conversion so I can see what's going on?

I've considered this, but there's a few issues with doing it, mainly that the FOV range of games varies a lot. So if the calculator automatically uses an invalid FOV, that will affect sensitivity. I'm currently going through every game in the calculator to verify them and update the notes to more standardized text. Perhaps if I also update with max/min FOV this functions can be implemented.

https://www.mouse-sensitivity.com/cancel-subscription/

Zombie Army 4 is added!