-
Posts
18,142 -
Joined
-
Last visited
-
Days Won
1,762
Content Type
Profiles
Forums
Updates
Release Notes
Store
Everything posted by DPI Wizard
-
Hi! When BF4 USA was added to the calculator, it only supported two variables. So it was set as a requirement that Aiming Coefficient and FOV ADS Scaling was set to 0. Now that it supports up to four variables they can theoretically be added, but it might over-complicate things for some users. I'll look into making a Battlefield 4 Advanced entry maybe
-
0 is the same as the default of 30.
-
You are not doing anything wrong As long as you have the same DPI, resolution and WPS on both sides of the calculation, the sensitivity will always be the same, but the 360 distance changes. To break it down: With 400 DPI, 1920x1080 and 6 WPS in Windows, it will take you 1920/400=4.8 inches of mouse movement to move the cursor across the screen. Now you want to match this to the game, so you divide 360 (degrees) with the actual horizontal FOV and multiply it by the screen distance from Windows: 360/106.26*4.8=16.262. Lastly to get a 360 distance of 16.262 with 400 DPI in CS:GO, the correct sensitivity is 2.51563. So let's do the same with 500 DPI: It will take you 1920/500=3.84 inches of mouse movement to move the cursor across the screen. Again divide 360 (degrees) with the actual horizontal FOV and multiply it by the screen distance from Windows: 360/106.26*3.84=13.0096. And lastly to get a 360 distance of 13.0096 with 500 DPI in CS:GO, the correct sensitivity is (again) 2.51563. But as soon as you have different DPI, resolution or WPS, or if you change FOV, everything changes. Hope that clears things up
-
It's as accurate as it can get it without any decimals. Still it should not be off by more than max 1% though.
-
With default FOV (103) it will always be 50! But if you change FOV, it gets very tedious for now... To get the most accurate result with different FOV, here's what you do (and this is not very intuitive...). First you need to find a constant for your ratio, and as of now the only game to support ratio conversion is osu!. So enter values like this, converting from Overwatch with in this case 90 FOV and your other settings to osu!, note the Keep field in the Convert to section, osu! allows you to select either distance or ratio, which is key here. Select ratio: Now take note of the osu! sensitivity, 1.41 in this case. Use this, and convert from osu! to Overwatch and Widowmaker like this: This conversion will keep the ratios as close as possible, so with 90 FOV in overwatch the correct Relative Aim for Widowmaker is 57, assuming resolution and monitor size is the same between all conversions (important!).
-
Unfortunately there is no way to directly convert screen distance between games for now, but I plan to add this. The way you have to do it now is like this: Select Windows as "Convert from" and enter your desired distance. This is the 2D distance, meaning how far you want to move your mouse to cross the screen in Windows. Then select Overwatch and Hipfire as Convert to: Now note the Sensitivity 1 for Overwatch (5) and the ratio (6.0316). Then select Widowmaker ADS in the Convert to Aim, and enter 5 as Sensitivity 1: It now calculates that with Sensitivity 5 you need to set the Relative aim to 50 to get a ratio of 6.0908, which is the closest match possible to 6.0316 I have double checked this in-game, and it is correct.
-
Overwatch is now updated with full support for the Relative Aim Sensitivity for Widowmaker And it's not Relative Aim 38 to match the screen distance at 103 FOV, it's 50. And the math is quite simple; The Relative Aim is a multiplier, and the FOV is about half. So by setting it to 50 your 360 distance doubles, but since the the FOV is ~half, the screen distance is the same.
-
Great info, thanks!
-
Yes, it's different, I'll update the Widowmaker ADS with the correct FOV later today.
-
Battleborn updated with correct formulas for the release version!
-
-
Could you provide a screenshot of everything you are entering? This might happen due to some rounding mechanisms that never reach a final number. Anyway, the Battleborn calculations may be wrong for the release version, I'm checking now.
-
For what weapon in CS:GO? I guess different weapons have different zoom sensitivities.
-
The FOV type is automatically changed to the games default, so don't change it
-
Maybe they changed something on launch, I'll check tomorrow.
-
Select Windows as "Convert from" in the regular calculator
-
Remember to use the calculator on the main page
-
-
-
The old calculator will not be updated with new games, it's only there in case the something in the new one was broken, so I'll remove it soon. Use the new one and select Windows in the Convert from section, and The Division in Convert to
-
Very good point, thank you! I missed that part when I checked the game earlier. Updated it now
-
As long as the advanced settings box is not checked, what is set there does not affect the sensitivity. But you should see a flat, red line at the sensitivity value you have set. You red line is a 4.X, which means it is about half of the configured 10.92.
-
Checked it now, and it's all the same as before, as long as you do not touch the advanced settings That's exactly the point, and this is why the sensitivity changes when you change FOV. When you set a higher FOV, the sensitivity needs to be increased as well, since it now is farther (as in more degrees) to the edge. If you are swiping to what was at the edge of your screen in-game, you must also move the mouse in Windows from the middle of the screen (where the crosshair would be) to the edge, and not edge-to-edge.