Jump to content

OrangeGuac

Premium Members
  • Posts

    22
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by OrangeGuac

  1. I've always run with USA off on all games but saw a recommendation to run with USA on and the coefficient set to 0 due to focal length scaling. Can anyone provide some pros/cons to doing this versus running with USA off. Thanks.
  2. DPI Wizard and fortunate reee, thanks for the information and answer and quick response.
  3. Been reading about legacy vs relative and affected vs independent and am a little confused (read that Relative with coefficient set to 0 is same as legacy but calculator doesn't agree and that relative set to 1 is same as USA off in BF V). Goal is to set up MW similar to BF V. Both games use same FOV and hipfire matches in both games but when sighted/scoped in they feel different. BF V: usa off, fov on (zoom sensitivity = 100% for all magnifications) So to get the same feeling in MW when sighted/scoped in, which settings should I use in MW? MW: affected, legacy or MW: affected, relative with coefficient 1 or MW: affected, relative with coefficient 0 Guessing don't even want to use independent since it isn't consistent across FOV changes. Any help would be greatly appreciated.
  4. Understand now. Thanks and thanks for quick reply.
  5. Thanks. I don't see a sensitivity 2 for setting ADS sensitivity (i.e., I only see 1 sensitivity for mouse sens).
  6. A heads up: You can change FOV in game. Separate ADS sensitivity now: 40% by default (would be nice to have in the calculator).
  7. Thanks. Prefer empirical evidence versus feel.
  8. Always amazed how fast you update the calculator when games change. Thanks.
  9. I think there may be an issue with the calculator and BF V. In BF 1 when you aimed down iron sights your FOV did not change (so my iron sights 360 distance was was exactly the same as my hip fire 360 distance). In BF V, when you aim down iron sights the FOV does change so my iron sights 360 distance is now higher/larger than my hip fire 360 distance; however, in the calculator it stills shows them as the same.
  10. Appreciate the comments and work but wouldn't you need to test sensitivity pre vs post patch?
  11. Yeah, a couple of the pros said sens has changed with the latest update (the one in production not TTS). Would be nice if you could run a check on it. TIA.
  12. I play R6 more than any other game and try to match sensitivities in other games to R6. R6 basically has hipfire, 1x and 2.5x. Is there a mathematical formula I could use to determine what other sensitivities would be. For example, if they add a 4x or 5x scope to R6, is there a formula I could use to determine what the cm/360 would be? Thanks for any help.
  13. Thanks for doing this so quickly.
  14. I'm guessing this may be a simple answer but I'm not getting it. I understand hip fire and 2x-15x but what do targeting and scoping represent in the calculator (is one of these for iron sights)? Thanks for any help.
  15. Awesome job on the new calculator. So glad I found this site and spent the money (saves a huge amount of time). I've set BF1 up to match my sensitivities from Rainbow Six Siege and this was easy with the calculator. My cm/360 from R6S are: Hip: 18.6965 Iron/1x: 31.16083 Acog/2.5x: 53.4186 This was easy to set up but how do I extrapolate for those not available in R6S? Is it simply multiplicative: If 2.5x = 53.4186, does 5x = 53.4186 x 2 = 106.8372 or is it not simply a matter of multiplying by 2? If so, what formula should I use to figure out 5x, 10x, and all the other zoom levels? Any help would be appreciated.
  16. Thanks for the help, appreciated.
  17. In-game, if I set FOV (vertical) to 86 it shows a horizontal FOV of 102. In the calculator, if I enter 86 as the vertical FOV is shows an actual horizontal FOV of 112. Which is correct? I want a hfov of ~102. Thanks.
×
×
  • Create New...