Jump to content

Varatesh

Premium Members
  • Posts

    15
  • Joined

Everything posted by Varatesh

  1. This post claims that gunsmith claimed zooms are not accurate. Have you done any testing to see if this is the case @DPI Wizard?
  2. Could you also please add kar98 7x sniper scope option to sensitivities?
  3. Is there information about HDR scope zoom yet?
  4. And battlenonsense demonstrated that GPU load >95% will cause spikes in input lag. You want steady low input lag. Gsync/freesync is not necessary if you have stable 144+ fps. Tearing is minimal at high refreshrates.
  5. Yeah, I noticed the same thing and it doesn't seem to be easily google searched. You have listed AX50 default scope zoom but not HDR.
  6. Does anyone know what the zoom on default scope HDR is? Edit: 5.5x zoom for variable scope on HDR is also not listed on site.
  7. Oh okay, it was the default setting when I picked BFV so I assumed that was the option calculator preferred.
  8. Menu in BFV claims that 70 FOV = 86 horizontal FOV whereas calculator claims that 70 fov = 102.45 horizontal FOV. Which is correct?
  9. FOV for aircraft is different from others. Is there any way to have FOV:95 for aircraft while maintaining lower FOV with infantry/tanks without affecting sensitivity? At the moment calculator uses base GstInput.MouseSensitivity to calculate sensitivity so if you have different FOVs between infantry/tank/aircraft then at least one of these will be inaccurate. @DPI Wizard could you add a seperate option to adjust aircraft sensitivity/fov?
  10. There is an ADS setting ingame now. Could we get an option to tweak that sensitivity?
  11. I don't see an option to find scope modifier. Has this been removed from the calculator? Edit: Nevermind, I had console set as location.
  12. Thanks for the new method, I'll try that out. There's still the discrepancy between 400 dpi * 8.6 sens and 800 dpi 4.3 sens. Does modern warfare treat dpi in a weird manner? I retested this using firefox and chrome to see if results changed: http://imgur.com/a/npq4O Theres still a discrepancy of seta sensitivity "0.979408" for 800 dpi and seta sensitivity "1.958815" for 400 dpi. Edit: after testing ingame 0.89 gives a cm 360 of around 65-75 not 44. My rough value of 1.769 gives around 41-43 cm/360 at 80 fov. Not sure what the issue is, but the calculator seems to struggle at 800 dpi.
  13. Hello It would seem like COD4MW calculator is bugging out. Im trying to convert my overwatch sens to COD4 and its giving me different values depending on dpi (dpi*sens remain same). I can change dpi to any setting without COD4 sensitivity changing. Edit: Third picture where sens is equal to previous picture but dpi is 2.8k without cod4 sens changing: http://imgur.com/a/HQenq
×
×
  • Create New...