Jump to content

DPI Wizard

Wizard
  • Posts

    18,158
  • Joined

  • Last visited

  • Days Won

    1,764

Everything posted by DPI Wizard

  1. Pixel ratio is only the same if you use MDV/MDH 0%
  2. Try the different settings in Apex and see which one you like the best. Start with all scopes set to 1 (this is MDV 0%). If the scopes are too slow, use the calculator to find the scopes sensitivity for e.g. MDV 100% (this is the same as MDH 56.25% in your example) and so on until you find a scope match that feels good.
  3. Depending on your matching method the zoom sensitivity will be different based on the aspect ratio, this is correct.
  4. Do you have the same issue on different browsers and devices?
  5. See the instructions
  6. It's the "Actual HFOV" from the ADS, so it will be different for the Iron Sight. Check the output when you have the aim selected and the correct FOV entered
  7. Default for Apex is MDV 0% (all scopes set to sensitivity 1) which is also a a highly recommended match. But some might find it too slow, then MDH 75% or 100% are good options to try.
  8. Very special sensitivity in this game, will take some time to reverse-engineer!
  9. You are converting directly from ADS to hipfire without the conversion setup matching your settings. Do it like this for a better result: For ADS to like this and adjust the FOV in Kovaak's to match the FOV of your ADS:
  10. Outlast and Outlast 2 added (they are identical).
  11. DPI Wizard

    8.4.a

    Games added Outlast Outlast 2 Game removed Battlefield: Bad Company 2 - Upon revisiting the game the sensitivity was found to be to inconsistent to be calculated.
  12. DPI Wizard

    Outlast 2

    Set the sensitivity in-game with the arrow keys in this game.
  13. Set the sensitivity in-game with the arrow keys in this game.
  14. DPI Wizard

    Outlast

    Set the sensitivity in-game with the arrow keys in this game.
  15. Set the sensitivity in-game with the arrow keys in this game.
  16. Just enter 25 as the FOV multiplier for Division 2 and the calculations will be correct.
  17. Most questions are answered in the instructions
  18. If you have black bars on the sides and use 1810x1080 to get an FOV of 103, you are doing it correctly as far as I can tell.
  19. That depends on the game. For instance going from 16:9 to 21:9 on CSGO will just add the extra width while keeping everything else the same. So the 16:9 portion of your 21:9 monitor is exactly like before. PUBG however changes sensitivity when going from 16:9 to 21:9, so it needs to be re-calculated. And for games that have FOV locked to the horizontal FOV (Hdeg Res) you should change the FOV if possible, which in turn might change sensitivity.
  20. All calculations here are done with scripts to get the sensitivity 100% correct. And aside from certain games with issues regarding acceleration/smoothing, FPS dependent sensitivity, report rate or similar, calculations are spot on. As for how to measure 360 distance, using scripting software included in the mouse driver (like Logitech LUA scripts) is one way, using a tool like Kovaak's Sensitivity Matcher is another.
  21. Not for native resolutions no. But this isn't about switching monitors, it's about forcing a custom aspect ratio different than what your monitor have.
  22. The only thing that matters is the resolution of your monitor, and the custom aspect ratio you use in the game. Like 16:10 on 16:9 in R6: This would be:
  23. Yeah, even though neither of them actually are. The FOV calculation will be a fraction off due to this. I might be able to use their real respective AR actually, will look into it. This is really only an issue if you play 21:9 stretched or black bars on 32:9 though.
  24. DPI Wizard

    8.4

    Calculator updates Native support for custom aspect ratio added. Scale will not be applied when converting from ADS or Scope to avoid it being applied twice.
×
×
  • Create New...