Identical cm/360's at various FOV's (as it relates to viewspeed)

[MattKelly]

.

Edited October 10, 2018 by MattKelly

[Drimzi]

Edited January 28, 2018 by Drimzi

[DPI Wizard]

7 hours ago, Drimzi said:

You may find key rotations such as 45°, 90°, 135°, and 180° being too difficult depending on how low the game forces the FOV,

A bit off-topic here, but do you think it would be useful to add 45°, 90°, 135°, and 180° conversions in addition to the 360° one? I feel like a lot of people want especially hipfire to be matched to a certain degree, so they have the muscle memory of a 90 or 180 degree flick for instance, and them for aims use Viewspeed.

[Drimzi]

Edited January 28, 2018 by Drimzi

[DNAMTE]

19 hours ago, DPI Wizard said:

A bit off-topic here, but do you think it would be useful to add 45°, 90°, 135°, and 180° conversions in addition to the 360° one? I feel like a lot of people want especially hipfire to be matched to a certain degree, so they have the muscle memory of a 90 or 180 degree flick for instance, and them for aims use Viewspeed.

In my opinion, showing partial rotation has no benefit to showing just complete rotation. If you want to match 90deg, simply match 360deg, perfect!? Besides, if people want to keep 180 flicks the same then matching FOV between games is always going to be critical.

Aiming is a combination of things and keeping a datum field of view between games for hipfire is very important IMO. For arguments sake, overwatch to CSGO or 103' to 106' in practical use would not affect someone's 180 flicks if all else remains equal IMO.

 

 

[DPI Wizard]

True, it would probably just clutter up the results. Besides if you want to know what the distance for different degrees are, the math is not too hard

[DNAMTE]

I would hope users of this website could divide something by 2 or 4.

[MattKelly]

.

Edited October 10, 2018 by MattKelly

[Drimzi]

Edited January 28, 2018 by Drimzi

[MattKelly]

.
 

Edited October 10, 2018 by MattKelly

[Drimzi]

Edited January 28, 2018 by Drimzi