DPI Wizard

Aim (pistol) is added now.

This is added now. I've never looked at Roblox Studio so I don't know what options you have when you make a game, but there's a lot of different sensitivity schemes for the different games. Although there are a few common reoccurring schemes, there's no way to know what each specific game uses. So every game has to be added individually.

It's still the same as far as I can tell, what seems to be different?

The config file is exactly 4:3 HFOV (70*multiplier). The in-game FOV is likely just "beautified" to go from 70 to 110 instead of 108.5.

Thanks, updated the path now.

Is your FOV correct (120)? This impacts the conversion. Other than that you can adjust the Windows/2D conversion setup, but it's already at it's traditionally slowest. This matches the pixel-by-pixel movement between 2D and 3D.

This is a bit counter-intuitive to do at the moment, because you have to convert from the stretched aspect ratio to the native aspect ratio for the calculator to pick up the difference. It does not currently consider the difference in physical dimensions of the aspect ratio within the same game (i.e. using the "All" conversion). You also have to use the custom Y sensitivity setup, and consider what you want to match. Usually it will be either tracking speed (MDH 0%) or 100%. Since the FOV is stretched, these will result in different sensitivity values. https://www.mouse-sensitivity.com/?share=5bf217a4eb1835b702a7dc87898e4966

Hi! Put requests in this thread so we have them in one place. Cheers!

Unfortunately this game is unsupported due to issues with too much smoothing/acceleration combined with a maximum turn speed.

This is on WeGame, right? I need to borrow an account for this.

The base sensitivity is updated now. The 1x is indeed the same as hipfire, but will only result in the same sensitivity if the ADS and Hipfire conversion settings are the same, unless the FOV is matched between the games.

Still a lot of smoothing, how they haven't fixed this simple thing after all this years is pretty bad.

The Sensitivity 1 field for Tarkov is the total change in turn speed due to armor, not the sensitivity (see the game notes section). The sensitivity goes into the Multiplier 1 field. Fix that and the conversion should work as intended

Some games do have the FOV as a part of the sensitivity formula, but the FOV itself is not considered when using "distance" as input or the "360 distance" conversion, it will just use whatever sensitivity results in the target 360 distance with the configured FOV. The difference between say 90 and 110 for a 360 is proportionally exactly the same for a 180. All other conversion methods (monitor distance, viewspeed, jedis trick) use the FOV in their calculation.

This is exactly the same as matching it using 360 degrees. The only difference is if you use the "Distance" input (where you enter a specific distance you want for 360 distance), you have to enter twice the distance (say you want 10 inch 180 turn, you enter 20 inches).

I have not gone through and analyzed the zoom scaling yet, but it shouldn't affect hipfire. The FOV is indeed 90 for first person.

It depends on what you want to achieve, but if you want the same 360 distance for hipfire, this will do it.

It's a formula based on pi divided by sensitivity.

Yes, but this is not keeping the 360 distance the same, but the tracking speed.

First Person sensitivity is added now.

First Person Hipfire is added now.

It's the same as the ADS, but I've added it now to avoid any confusion

I have not noticed any smoothing issues with this game, so it probably does nothing.

You are changing the source here, which is why you get different results. In the last one the correct Apex settings would be 1x Optic 1.29, not 1.

The issue with USA Off is that it's based on the default FOV of 55 and ADS FOV Off. So what you can do is change your source to match this. For BF2042 itself it would look like this (ADS FOV on still makes the low power scopes different though). And for Delta Force it would be like this.