Jump to content

DPI Wizard

Wizard
  • Posts

    18,154
  • Joined

  • Last visited

  • Days Won

    1,763

Everything posted by DPI Wizard

  1. I've added iron sight now. Scope has the same issue as in Sandstorm in that it scales the wrong way when changing FOV... It's really strange that they kept this design, it makes no sense!
  2. That's correct if you want to convert directly from Widowmaker.
  3. Ashe is in!
  4. I'm on it!
  5. Just verified it now, and it is indeed 30%. Added it to the calculator
  6. You want to use MouseSensitivityMultiplierUnit 0.002230 instead of 0.02? Not possible, as it would be 0.02*12/0.00223=107.62 which is above the max value of 100. Why do you want to do this btw?
  7. Alternatively MDV 133.333333 works on any AR
  8. Yes, use MDH 75% if you're on a 16:9 monitor.
  9. It had too much acceleration/bad mouse input registration last time I tested it. If there's been any updates I'll check it again.
  10. 37.94 is the correct value with decimals, 38 is from good old days without decimal support.
  11. That's basically what All does, calculates scope based on hipfire. The calculation is based on the Scope setting in conversion settings, try setting it to MDH 0%.
  12. Gotcha, like the USA Coefficient calculation for BF1 (works on the old version, but currently broken on 7.x, will fix it next). Which is actually impossible to calculate with a formula AFAIK, but I've got a script that does it. I should be able to do some minor modifications to the script and make it work with BO4.
  13. I missed something here, in what scenario do you mean?
  14. DPI Wizard

    7.3.b

    Game added Fallout 76
  15. Fallout 76 is here!
  16. DPI Wizard

    Fallout 76

    Fallout 76 is here!
  17. I'm ready for it, pre-loaded and re-downloaded
  18. CSGO with 2.212659 should be the exact same 360 distance as the R6 settings if that's what he wants to achieve. Also assuming the config file sensitivity in R6 are both the default value of 0.02 btw.
  19. Does he have raw mouse input on in CSGO? Or Windows Pointer Speed set to 6/11?
  20. 360 distance doesn't have a percentage attached to it, it always matched the distance to turn 360 degrees.
  21. 360 distance is different from Monitor Distance, and is generally only used for hipfire to hipfire conversion. But since the aim in R6 has such wide FOV you can use it there as well if you prefer.
  22. No, then movement to the edge of the monitor will be the same between the aims, but tracking will be different.
  23. It's the slowest matching method, meaning tracking a target is the same between scopes.
×
×
  • Create New...