Destiny 2

Holy shit you're quick thanks dad

tnak you dude that was quick i just checked!

You're a god, that's so fast.

Don't really get how to use the ADS sensitivity configuration. 

I put Sensitivity 1 in there between 1-100, but it gives me an error. Furthermore, the multiplier is grayed out.

2 minutes ago, DPI Wizard said:

First convert to hipfire, then select ADS and use the value from hipfire in the Sensitivity 1 field. The output will show you the ADS sensitivity to use in-game.

I'm using 6 @ 800 DPI, but when I use "Look Sensitivity 6"

It says:

Calculated sensitivity too high
Increase either sensitivity 1 or new DPI 

Thank you very much!

I'm gonna kiss you on the mouth

when i convert it does not give me the exact sens it just gives me a range of sensitivities from 1 to 100.

If you're talking about the ADS, it needs you to put in the hip calculation into the sensitivity field.

How do I view this article?

@DPI Wizard So like do ALL guns in Destiny 2 have the same ads sensitivity "speed"? I noticed when playing that most of the guns have varying zooms. However, it seems that fov doesn't effect sensitivity.

Some insight into this question would be cool.

I was able to successfully convert my Hipfire sens from Overwatch to Destiny 2, but I'm getting "Enter Sensitivity 1" when I try to convert for ADS. How do I convert it properly? I'm using 1600 dpi, 2.75 in-game for Overwatch. 

17 minutes ago, DPI Wizard said:

Sensitivity 1 is the hipfire sensitivity from your first conversion

Unfortunately Destiny 2's ADS wont go past 1.5 sens. Sounds odd. Thank you for your contribution!

4 hours ago, DPI Wizard said:

What FOV do you have in Destiny 2? This conversion should work and be within the range of Destiny 2's ADS modifier;

First convert from Overwatch to Destiny 2 Hipfire using Viewspeed or Monitor Distance, then select ADS for Destiny 2 and enter the previous hipfire sensitivity. 

It's not an issue with the calculator. The ADS sensitivity in Destiny 2 maxes out at "1.5" for some odd reason, so I'm not able to do anything over that. I'm using 103 FOV. 

just use a controller and a xim 4 like the rest of them.

What is the "match at" option mean for ADS? I get that match at 100% means gives me the degrees of rotation and distance on the mouse pad to go from the center of the screen to the edge, but the other percentage values don't make sense to me.

If I'm posting in the wrong section, I apologize. But if someone would like to help me anyways, I appreciate it.
 

The goal is to match hipfire sens to ADS sens, such that the distance I move my mouse to move to the 4:3 ring is always the same. In other words, if my monitor resolution were 4:3, then moving from the center of the screen to the edge will be the same in both hipfire and ADS (cs:go scaling, if I'm correct). The problem is that the "Match at 75%" option isn't returning a degree value that makes sense. That is, if interpret the option correctly, I should get back the degree rotation required to turn to the imaginary 4:3 side edges of my monitor.

Here's a bunch of garbage math I did that may or may not be useful to people wanting to help me.

I'm at 105 degrees fov config, = 100.8 HFOV actual, =50.4 for 100% rotation. I have a 16:9 resolution monitor. I have sensitivity at 5, getting me a 27.7091 cm/ 360 hipfire, the feel of which is what I want my hipfire sensitivity to correspond to.

The degrees to move to the 4:3 edge is 35.30191712:
    x = 8 / sin(50.4)                                                                                        the 8 is from half of 16 in 16:9 resolution
    degrees to 4:3 edge = arcsin(6/x) = 35.30191712                             the 6 is from half of 12 in 12:9, where 12:9 = 4:3 resolution

"Match at 75%" should thus give me back the 35.30191712 number, as the degrees required to rotate 75% of the way from the center of the screen to the edge (which would be where the imaginary edge of a 4:3 monitor is). Instead, match at 75% is giving me back 42.19 degrees. A screenshot is included.

Note that 75% of 50.4 degrees is 37.8 degrees, so that doesn't make sense either.

2 minutes ago, DPI Wizard said:

Your math is a bit off, the formula is like this:

atan(tan(x/2)*y)

Where
x = FOV in radians
y = matching percentage (75% = 0.75)

So in this case it's: atan(tan(100.8degrees/2)*0.75) = 42.2 (rounded).

As an example, CSGO's 90 FOV is expanded to 106.26 in 16:9, so you can calculate back to the 45 degrees 75% equals by doing so: atan(tan(106.26degrees/2)*0.75) = 45.

Hope that clears it up a bit.

Wow ok I'm stupid.

Thanks a bunch for the quick reply.

Why Viewspeed or monitor distance?

I have 6.4 @ 900 dpi in Overwatch (equivalent to 7.2 @ 800 dpi and 14.4 @ 400 dpi). Overwatch FOV is 103.

Should I set FOV to 107 in Destiny 2 to compensate? The error % changes drastically for some of the values when I do that. Not sure if I should

FOV in Destiny 2 maxes out at 105 in game, 100.8 in actuality, if I recall correctly. Hence the usage of viewspeed and monitor distance over cm/360. Which I think is what's going on here, if someone else can confirm...