Jump to content

Recommended Posts

  • 2 weeks later...
  • 6 months later...
  • 1 year later...
Posted (edited)

Hello, the calculator needs to be updated. ADS and scoped sensitivities are wrong. They probably made changes.

Edited by Shd469
  • 10 months later...
Posted (edited)

Any way we could get a car sensitivity option as well for conversion? Also, I see this hasnt been updated since Z2. Im fairly certain they may have changed ADS FOV's since then. Any chance you could take a second look DPI Wizard? I've recently been turning a lot of people in the H1 comp community onto viewspeed and I want to make sure all of the information is correct.

Edited by KandiVan
  • 3 weeks later...
Posted (edited)

My problem now is when I convert from windows 400dpi 24" 1920x1080 the scope is too fast7 I don't really understand why...

Should I leave it like default everything and don't touch ADS and SCOPED? or how does it work. Thanks.

Edited by Ivanovich
  • Wizard
Posted
On 5/13/2017 at 1:22 AM, Ivanovich said:

My problem now is when I convert from windows 400dpi 24" 1920x1080 the scope is too fast7 I don't really understand why...

Should I leave it like default everything and don't touch ADS and SCOPED? or how does it work. Thanks.

What settings are you using and what are you converting from?

4 minutes ago, Harrison Swinson said:

Does the FOV in H1 relate to the sensitivity change between two games?

Yes, unless you match 360 distance FOV will make a difference.

Posted
On 5/12/2017 at 5:22 PM, Ivanovich said:

My problem now is when I convert from windows 400dpi 24" 1920x1080 the scope is too fast7 I don't really understand why...

Should I leave it like default everything and don't touch ADS and SCOPED? or how does it work. Thanks.

 

2 hours ago, DPI Wizard said:

What settings are you using and what are you converting from?

 

Im on the same page. H1 is the one game that I just cant seem to do viewspeed on the scoped and ADS sensitivities consistently. I've tried for months of training and just cant seem to nail it down. I personally think it has to do with how slow the character movement is and how finite your mouse movements have to be to track heads (small hitbox as well). Maybe dpi wizard could check the FOV's to verify they are still correct on the ADS and scoped? Regardless, I think its just the game itself.

Posted (edited)

When I try to match the my normal sens to my ADS sens my FOV changes on the ADS. For example if I using 67 FOV on normal sens do I need to set 67 to my ADS FOV also? It seems to default back to 55

Edited by Harrison Swinson
Posted

http://imgur.com/a/HIWjh

 

This says that the sensitivity is not affected by FOV but when you change the FOV in the calculator it is affected.

 

Also is there a different FOV when in ADS mode? If I am playing at 67 FOV and I am trying to match ADS do I put 67 in the FOV also? Or is there a different FOV value because you zoom in. Same question for scoped.

  • Wizard
Posted

Not affected by FOV means that the 360 distance (i.e. the sensitivity) is unaffected by it. When you do calculations with monitor distance or viewspeed, it will affect it either way.

For all games unless noted otherwise, enter your configured FOV. The scope FOV will either be calculated based on this, or it has a fixed FOV.

  • Wizard
Posted

Not quite what it means :) But try changing FOV for  H1Z1 on both sides of the calculation now, and you will see that the 360 distance and sensitivity stays the same, that's what unaffected by FOV means.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...