Jump to content

DPI Wizard

Wizard
  • Posts

    18,162
  • Joined

  • Last visited

  • Days Won

    1,764

Everything posted by DPI Wizard

  1. DPI Wizard

    8.6

    Calculator updates Focal length This is a function available in the Aspect Ratio box of the output game. What this does is calculate the correct resolution you need to set (with black bars) to keep the same focal length based on your FOV. This is useful for games that does not support FOV change. Monitor size conversion When you enter a different monitor size and/or aspect ratio the calculator will now account for this based on your setup. 360 distance will be the same, as it doesn't change based on monitor size or aspect ratio. Monitor Distance Horizontal and Viewspeed Horizontal will take into account the horizontal size of the monitor. Monitor Distance Vertical and Viewspeed Vertical will take into account the vertical size of the monitor. This means that if you go from a 24" to a 27" 16:9 monitor, both horizontal and vertical will give you the same result. However if you go from a 27" 16:9 to a 35" 21:9 the vertical sensitivity will stay about the same, while horizontal will account for the extra width. Games added Genesis Alpha One ULTRAKILL Game updated Destiny 2 - Updated ADS scale.
  2. Focal length support added!
  3. Support for this is now added, let me know if it works as expected!
  4. A new version was just published that contains two new features: 1. Focal length This is a function available in the Aspect Ratio box of the output game. What this does is calculate the correct resolution you need to set (with black bars) to keep the same focal length based on your FOV. This is useful for games that does not support FOV change. 2. Monitor size conversion When you enter a different monitor size and/or aspect ratio the calculator will now account for this based on your setup. 360 distance will be the same, as it doesn't change based on monitor size or aspect ratio. Monitor Distance Horizontal and Viewspeed Horizontal will take into account the horizontal size of the monitor. Monitor Distance Vertical and Viewspeed Vertical will take into account the vertical size of the monitor. This means that if you go from a 24" to a 27" 16:9 monitor, both horizontal and vertical will give you the same result. However if you go from a 27" 16:9 to a 35" 21:9 the vertical sensitivity will stay about the same, while horizontal will account for the extra width. Please report back if any of these features are acting weird!
  5. Ideally you should use all the values if you want the sensitivity set according to the setup in the calculator. Some games have ADS sensitivity derived from the hipfire (like BFV), so if just change the 360 distance for hipfire, all scopes will scale according to this. Other games have separate ADS sensitivity which is not linked to hipfire at all. So you need to pay attention to the values. If you don't get 100% for all the aims, something in the calculator doesn't line up with your settings.
  6. That depends on how consistent you want to be in relation to your aim as well. If you do hipfire 0% and aims 100% your kinda mixing the FOV based methods and lack consistency. It might work for you though, nothing is really set in stone
  7. No, 0% should work for basically anything.
  8. 100% because you have 4:3 stretched to fit 16:9. If you didn't stretch (i.e. black bars) or played in full resolution then 75% would be correct.
  9. That depends on what you want really. 360 distance is more consistent for navigation in hipfire, but less so for aiming.
  10. 100% because that is what your zoom sens is (zoom sens 1 in 4:3). So to keep it consistent I also did this for hipfire.
  11. Config FOV is as the name implies what you configure in the game. Also make sure you select the same FOV Measurement as is selected in the calculator
  12. If you want to match both your hipfire and aim to the monitor distance, do like this: https://www.mouse-sensitivity.com/?share=4c5385b43f57abe436ec2a0db8920743 If you want hipfire matched using 360 distance and aims using monitor distance do like this: https://www.mouse-sensitivity.com/?share=936bde139aa10c000c515d6223947d99
  13. Drivers do not support steps in 10 even though you can do this for many of them. If you set it to 220 it would in fact be 200, and when you set it to 225 it would step up to 250, hence why it feels much faster. 200 seems like your best option here.
  14. Do like this to properly enter your MW settings, and set the Kovaak's FOV to match the AR FOV: https://www.mouse-sensitivity.com/?share=4ce1c5d659b16a5ab19e234f6c2fa8e8
  15. What zoom sens do you have in CSGO? 1?
  16. Just tested now, and it's the same for AR as far as I can tell, note that AR has it's own entry in the calculator. If it's still not correct, let me know exactly what weapon it is that I can test in creative.
  17. I'm on it!
  18. DPI Wizard

    ULTRAKILL

    Config File sensitivity added.
  19. Config File sensitivity added. View full update
  20. It seems like you might have entered the wrong coefficient for BFV. I assume you meant to enter 178? If so also set the ADS and scope conversions to MDV 178%. This should make the aims in hunt match better https://www.mouse-sensitivity.com/?share=975c6b9fff0a81f0d3857a25d97da3b8
  21. There is no best method unfortunately, it depends on what you want to achieve. If you want the same 360 distance, use 360 distance. If you want the same tracking speed, use MDV 0%. If you want the same flick distance to a certain point on your monitor, use MDH or MDV and a percentage. 100% is the edges of the monitor, and other percentage is between the cross hair and edge.
  22. Should be no problem implementing this so the resolution in the output game changes. Are you actually setting this as a custom res in Windows or the game to match?
  23. I see they added a lot of games from the calculator now. Everything should work as before
×
×
  • Create New...