DPI Wizard

They did change how FOV works as it is now resolution based and not fixed to 16:9, just updated the calculator

Can you take a screenshot like this so I see all the weapon stats etc?

Not possible, tested in the config file now and it doesn't work with any other numbers than what you can set in the game. There is a new feature in the calculator however that lets you find the perfect DPI to account for the discrepancy. If you select "Advanced Plus" mode you will see the "DPI for 0%" in the output. Note that most if not all mouse drivers rounds UP to the nearest 50 DPI, so in this example it would be best to set the DPI to 1050 as 1067 would be rounded up to 1100.

They nailed the scope power, not the sens I think. Last time I checked everything scaled differently with seemingly no logic, but let me know which scope you want (post a pic of the whole gun maybe) and I'll see if I can add it.

Are you combining the calculated sensitivity into one line? So it becomes: SoldierSensitivity=0.251454 SoldierZoomSensitivities=((1.000000, 0.209545),(4.000000, 0.165523),(8.000000, 1.000000))

Tested some more now, and while still having some issues with smoothing and doubling mouse reports, sensitivity is only somewhat stable at 30 FPS. Any other frame rate causes a lot of negative acceleration, so it can't be added until this is fixed.

The default setting for ADS (MDV 0%) is a good place to start, so just leave it at the default.

I see FPS tied sensitivity every now and then, most likely because the game doesn't correctly process what happens between the frames or something. However the issue is fixed now in Dauntless now! Sensitivity scale has changed from previously though, but I've updated it now. Note that the game might not read the config file on launch, so just go into settings and change Frame Rate Limit back on forth to force it to read the file.

The aspect ratio switch is now automagic.

You have a lot wider FOV in Apex than in Overwatch. So while the scopes in Apex perfectly matches those in Overwatch (3X being pretty much identical to Widowmaker etc), the difference between them and the hipfire is bigger. For this reason it's sensible to also match the FOV, which means setting it to 1.237600 in Apex.

A lot of negative acceleration in this game, and no numerical sensitivity. Not sure it can be added, but will work some more on it to see what can be done.

While this is a feature most probably won't use, it was important to integrate it into the calculator so it can fully support every aspect of the sensitivity settings in games. Over 100 games have been updated to support vertical sensitivity! If you notice a game that does support it but haven't been updated in the calculator, let me know! This feature have three settings: 1:1 is keeping the scaling of the vertical sensitivity the same as the horizontal. This is how the calculator has always working up until now, so just keep it at 1:1 if you don't want to use this feature and make everything behave like before. "Scale" is probably the most useful and simple method if you want to use this feature. It simply scales all vertical sensitivity to the percentage chosen. If you for instance want to mimic the behavior of a lot of Unreal Engine 4 games (like ARK) you can simply set this to 70%. This will for those game that is doing this by default result in the same X and Y sensitivity value. Finally we have "Custom" which reveals a Y axis selection for all the different aim options. With this feature you have the ability to both set a preferred scale percentage for each option, OR you can select a different matching method all together. If you for instance want ADS horizontal to match MDH 100% and ADS vertical to match MDV 100% you can this with the "Custom" option. "Custom" with all Y axis set to scale and the same percentage is exactly the same as selecting "Scale" and setting that percentage.

MDV 0% (what Apex uses by default) is what most people generally prefer. It is technically the same as MDH 0% as long as you don't convert between different aspect ratios.

Correct, MDV is vertical and MDH is horizontal. As for the conversion it seems correct yes.

They are both multipliers of the hipfire, but they are based on different methods. In Apex multiplier 1 is MDV 0% (i.e. same tracking speed), while in Valorant 1 is MDH 100% (i.e. same movement to the edge of the screen). So 1 in Valorant is a lot faster than 1 in Apex.

The one for the zoom you want perfectly matched. Others will be slightly off compared to your Apex sensitivity, but that's a limitation in Valorant you can't get around.

You barely have to change anything in the calculator for this, just select the game and enter your details and it should work https://www.mouse-sensitivity.com/?share=92fca643df48f981c45069a03e45aaaf

Checked the game now and can't find anything different, and no issues with acceleration. Did it work differently for you before?

A lot of Unreal Engine 4 games from a specific time period had the Y sensitivity default to 70% of the X sensitivity. Some were the same and changed to 70% while other were 70% and changed to the same at some point. This is not a new change for ARK, but it's correct as of now.

A lot of Unreal Engine 4 games from a specific time period had the Y sensitivity default to 70% of the X sensitivity. Some were the same and changed to 70% while other were 70% and changed to the same at some point. This is not a new change for ARK, but it's correct as of now.

I've actually already updated this in the upcoming version that supports separate vertical sensitivity. Hope to publish it in a few days.

Just made a video if you need it. Sensitivity here is: Sensitivity=37.869423,LastConvertedSensitivity=0.011440 Meaning a 360 distance of 11000 counts. The configured FOV is 103, resolution 1920x1080. Vertical FOV is 70.5328, meaning half the vertical counts are 11000/360*70.5328/2=~1078. I made a script moving 1078 counts so what is at the top should align with the crosshair dot after execution. As you can see it perfectly matches when far away, and overshoots when close. It's also exactly the distance it should be if the vertical FOV is in fact 70.5328 far away. I did half view to the crosshair rather than the entire view because it's easier to see how much it overshoots. Doing the whole view yields the exact same result.

Just tested, it's spot on what it should be. Are you also testing your horizontal FOV? Can you attach your GameUserSettings.ini file please? You will get an error of about 13-14% if you stand next to the object you are measuring against. If you don't get a difference between an object close and an object far away you must be doing something wrong.

As for other improvements there's a big update coming soon with full support for separate vertical sensitivity for over 100 of the games