Jump to content

Combat Champions

All aims use the same sensitivity setting, choose the sensitivity for the aim you prefer to be matched.
Read more...

Ghost of Tsushima DIRECTOR'S CUT

The sensitivity and FOV changes depending on certain actions and where you are (indoor etc). The calculations are for the view when you move around outdoor.
Read more...

Russian Fishing 4

See the game notes for instructions on how to disable smoothing.
Read more...

Arena Breakout: Infinite

Hipfire is added, aims coming soon!
Read more...

Project L33T

See the game notes for instructions on how to disable smoothing.
Read more...

Apex Legends


DPI Wizard

Updated with holo sight, 6x and 10x scope.

Edited by DPI Wizard


User Feedback

Recommended Comments



12 hours ago, ruk1_br said:

Thanks. 133.333% vertical^  at 0.7 seems more correct to me. 0% vertical gives me all scopes 0.7 on apex and that's weird to play. I've been playing like that forever.

 

For COD, should I use ADS "Relative" with 0 oe 1.33 monitor distance coefficient?

relative is the go to ,since legacy is only for old timers not usefull for 99% of players

in the end of the day scope scaling is preference after all :) happy to help

Link to comment

 hello , Apex is my first first person shooter, I play on  24.5" BenQ 1920x1080 monitor. 2.8 sensitivity in game with 500dpi and 110 fov. does it work if i convert apex to apex to match hipfire and ads sensitivity for all  ? @DPI Wizard

Edited by ziRaidenx
Link to comment
  • Wizard
43 minutes ago, ziRaidenx said:

 hello , Apex is my first first person shooter, I play on  24.5" BenQ 1920x1080 monitor. 2.8 sensitivity in game with 500dpi and 110 fov. does it work if i convert apex to apex to match hipfire and ads sensitivity for all  ? @DPI Wizard

Yes, that works. You don't even have to convert to Apex, just selecting the All aim and entering your sensitivity will convert all scopes based on this. Do note that the default setup in the calculator is exactly the same as how Apex scales the scopes, so you will get 1 as all the values unless you have changed it.

https://www.mouse-sensitivity.com/?share=0563f2c90b0f5107ce6c8148b287cd94

Link to comment
47 minutes ago, DPI Wizard said:

Yes, that works. You don't even have to convert to Apex, just selecting the All aim and entering your sensitivity will convert all scopes based on this. Do note that the default setup in the calculator is exactly the same as how Apex scales the scopes, so you will get 1 as all the values unless you have changed it.

https://www.mouse-sensitivity.com/?share=0563f2c90b0f5107ce6c8148b287cd94

https://www.mouse-sensitivity.com/?share=3578b2394f1358c785958fd38790d806

I tried these settings in game by changing it in settings.cfg , ads feels slower than hipfire @DPI Wizard

Edited by ziRaidenx
Link to comment
7 hours ago, fortunate reee said:

relative is the go to ,since legacy is only for old timers not usefull for 99% of players

in the end of the day scope scaling is preference after all :) happy to help

Is there any video or tutorial explaining with more details the difference between percentages on 'monitor distance'? I've read the 'instructions' but it was not clear to me... I'm probably kind of slow :( @DPI Wizard

I thought monitor distance 25% or 100% would be the same....

Edited by ruk1_br
Link to comment
  • Wizard
Just now, ruk1_br said:

Is there any video or tutorial explaining with more details the difference between percentages on 'monitor distance'? I've read the 'instructions' but it was not clear to me... I'm probably kind of slow :( @DPI Wizard

There's several videos in the instructions post showing exactly what monitor distance is. In short 0% is tracking speed, 100% is matching the distance between the cross hair and the edge of the monitor, any other percentage is related to this. So 50% is half way between the cross hair and edge etc.

Link to comment
7 minutes ago, DPI Wizard said:

There's several videos in the instructions post showing exactly what monitor distance is. In short 0% is tracking speed, 100% is matching the distance between the cross hair and the edge of the monitor, any other percentage is related to this. So 50% is half way between the cross hair and edge etc.

I've seen the videos and it's still kind of confusing to me. Gonna spend more time on this.... I play 3 different games, but if I'm adsing and an enemy appears in the edge of the monitor,  I want to move my mouse on mousepad the same distance in all 3 games to reach him (regardless if its 2x, 3x, 10x) .... what method would you recommend? Is that the best way to create 'muscle memory'?

Edited by ruk1_br
Link to comment
  • Wizard
2 minutes ago, ruk1_br said:

I play 3 different games, but if I'm adsing and an enemy appears in the edge of the monitor,  I want to move my mouse on mousepad the same distance in all 3 games to reach him (regardless if its 2x, 3x, 10x) .... what method would you recommend? Is that the best way to create 'muscle memory'?

In this case MDH 100% would be best. The caveat is that for any matching method you choose, all others will be slightly off. So if you want flicking to the edge to be the same, tracking a moving target will be different, as will flicking to something halfway between your cross hair and edge. There is no best way for muscle memory, but the most important thing is that you stay consistent with what method you use.

Link to comment

I'm playing 2560x1440 and I'm using sens 1.8 and it tells me same 360 degrees for 1x scope would be 1.28 something but when Im hipfiring it just feels like I cant track for shit but when Im adsing it feels like I have an easier time following targets even if they are in my face. This doesnt feel accurate?

Link to comment
7 hours ago, philheath said:

 AMsYihN.png 

It's correct in both.

Apex [bad implemented] in-game FOV scale:  110 hipfire FOV -> 1x FOV = 93.896104

That converted to HFOV looks like this: 123.268762 hipfire FOV -> 1x FOV = 109.119302

image.png.6a0b126e693b4892d42fb3b641b7f4ba.png

 

image.png.0f8e908a81dc969b1cd730ee6417c2a7.png

Link to comment

Yep, that's so you can see that the calculator and Aimlab (which, I think, got the values from this site) are correct. 

In the first image you can see that with 110 in-game hipfire FOV you get 109.119302 (16:9) HFOV for the 1x scope. 

In the second image you can confirm that 109.119302 (16:9) HFOV would be 93.896104 Apex in-game FOV. Aimlab is using this [broken] scale for everything, including the scopes, because that's what you selected in the settings menu.

Edited by ProuDBeasT
Added "(16:9)"
Link to comment
  • Wizard
1 hour ago, philheath said:

YOU are comparing all (which is hipfire) to 1x scope, completely different

Aimlab is showing the in-game value which is close to 4:3 FOV:

image.png

Link to comment

The field of view value in Aim Lab is the game's fov value.

If you want to compare the 'Actual VFOV' and 'Actual HFOV', you need to enable to Advanced Field of View Options. It will then show the rendered vertical, horizontal, and diagonal fov. You will then see the same result.

Link to comment
  • Wizard
26 minutes ago, Quackerjack said:

If FOV is halved, the sensitivity would be halved.

Isn't it then MDH 100%?

For horizontal FOV that is resolution based yes, but Apex uses 4:3 FOV, so this equates to MDV 133.3333%.

Link to comment

  Hello @DPI Wizard,

On 7/2/2020 at 6:37 PM, DPI Wizard said:

Calculations for Apex are correct, no question about it as it is based on a standard Source sensitivity.

On 7/2/2020 at 6:40 PM, fortunate reee said:

when the calculator is "  image.png.34080fde7263326fdd5e0a7ccf2d2a64.png"

just like all the other times it wasnt

I'm just letting you know, that FOV calculations are wrong for resolution ratio below 1,6. I guess no one noticed it, because it's not affecting 360° distance.

Same mistake here: https://jscalc-blog.com/apex-legends-calculator/

I'm sending you correction in Excel format:

Vertical resolution = Resolution set in game

Vertical resolution2 = Real rendered resolution = IF(horizontal resolution/Vertical resolution<=1,6;horizontal resolution/1,6;Vertical resolution)

HFOV = 2*DEGREES(ATAN(TAN(RADIANS(VFOV/2))*horizontal resolution/Vertical resolution2))

you're welcome :D

Edited by MacSquirrel_Jedi
Link to comment
  • Wizard
17 minutes ago, MacSquirrel_Jedi said:

  Hello DPI Wizard,

I'm just letting you know, that FOV calculations are wrong for resolution ratio below 1,6. I guess no one noticed it, because it's not affecting 360° distance.

Same mistake here: https://jscalc-blog.com/apex-legends-calculator/

I'm sending you correction in Excel format:

Vertical resolution = Resolution set in game

Vertical resolution2 = Real rendered resolution = IF(horizontal resolution/Vertical resolution<=1,6;horizontal resolution/1,6;Vertical resolution)

HFOV = 2*DEGREES(ATAN(TAN(RADIANS(VFOV/2))*horizontal resolution/Vertical resolution2))

you're welcome :D

Nothing wrong in the calculator, you just need to select the correct aspect ratio when the game adds black bars ;)

https://www.mouse-sensitivity.com/?share=360bf5894a24652d9052ae65ba679ed6

Link to comment
56 minutes ago, DPI Wizard said:

Nothing wrong in the calculator, you just need to select the correct aspect ratio when the game adds black bars

:D nice try. It's working. BUT why anyone would want to fill 16:10 black bars, when game resolution is 4:3 (1280x960) = 1,33 < 1,6 . Without knowing this problem? It should be automated in calculator.

1707812922_Beznzvu.png.7321f518cc6b8ed2fe83e31a01d427a5.png

Edited by MacSquirrel_Jedi
Link to comment
16 hours ago, MacSquirrel_Jedi said:

:D nice try. It's working. BUT why anyone would want to fill 16:10 black bars, when game resolution is 4:3 (1280x960) = 1,33 < 1,6 . Without knowing this problem? It should be automated in calculator.

1707812922_Beznzvu.png.7321f518cc6b8ed2fe83e31a01d427a5.png

again -> image.png.79a877d87cb7085be6a1b9720c341202.png why not ask dpiwiz before assuming

 

why would you do that in any reasonable scenario

the option works well when you use it as intended

image.png

Edited by fortunate reee
Link to comment
17 hours ago, MacSquirrel_Jedi said:

  Hello @DPI Wizard,

I'm just letting you know, that FOV calculations are wrong for resolution ratio below 1,6. I guess no one noticed it, because it's not affecting 360° distance.

Same mistake here: https://jscalc-blog.com/apex-legends-calculator/

I'm sending you correction in Excel format:

Vertical resolution = Resolution set in game

Vertical resolution2 = Real rendered resolution = IF(horizontal resolution/Vertical resolution<=1,6;horizontal resolution/1,6;Vertical resolution)

HFOV = 2*DEGREES(ATAN(TAN(RADIANS(VFOV/2))*horizontal resolution/Vertical resolution2))

you're welcome :D

i think no one noticed cause none plays apex legends in 4:3. So for 16:10, 16:9 everything ok.

Link to comment



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...