Jump to content

DPI Wizard

Wizard
  • Posts

    18,163
  • Joined

  • Last visited

  • Days Won

    1,764

Everything posted by DPI Wizard

  1. DPI Wizard

    8.6.i

    Calculator updates Fixed an issue with monitor conversion. Games added Renegade X A Story About My Uncle Games updated Roblox - Added new game modes and support for both old and new UI. Blockpost - Added ADS sensitivity.
  2. This game has an awful lot of negative acceleration, can't be added I'm afraid.
  3. Too much negative acceleration in this game to be added.
  4. It's a general problem with the game, they even posted about fixing it on twitter but it was never actually fixed.
  5. For aims and scopes you want the aim to be the same, not the 360 distance. This is achieved by matching monitor distance, from 0% which is tracking speed to any percentage value which is the movement to a certain spot on your monitor. See the instructions thread for some videos explaining this
  6. It's not supposed to be the same with that setup. It's keeping the same tracking speed between scopes, which means increased 360 distance when the zoom increases. This will keep the same 360 distance, but is not a recommended method as aiming will be incredibly fast for scopes.
  7. That was an unintentional effect of the monitor calculations, fixed it now
  8. Added with config file and in-game sensitivity.
  9. Added with config file and in-game sensitivity.
  10. It depends on the game, so just enter your sensitivity into the calculator and change the FOV to see if the 360 distance changes.
  11. Too much smoothing even when set to 0 unfortunately, can't be added.
  12. All these Roblox modes are added now, as well as support for both old and new UI.
  13. What exactly do you mean by slow btw, difference in 360 distance, or the tracking speed seems too slow? BTW, shoulder aim (first ADS step) is treated as hipfire so it will be matched using 360 distance in your setup.
  14. Tested again now, it's still horrible. Tried everything I can think of, Direct 3D11, disable Origin overlay, vsync, frame limits, raw input etc. The game doesn't even register a lot of the packets from the mouse.
  15. That looks correct, what specific aim/gun/scope is too slow that you've tested?
  16. Yes, but make sure your Apex FOV is correct, you should enter the value you have in the game if it's not 90.
  17. Like this then: https://www.mouse-sensitivity.com/?share=359abb9ab25442a6aa6875544bb8dbd6
  18. m_yaw is what's being calculated, but you can switch the values around. It will give you an error because the calculation is out of range, but you'll see the sensitivity. https://www.mouse-sensitivity.com/?share=17ecc41a205f26092da2835a896b72f4
  19. Technically it does through the discrepancy (which is 40% off here), as it is solely caused by lack of granularity in the sensitivity settings
  20. No, the conversion setup handles this for you. If you convert back to CSGO you'll see that it shows the correct scope sens: https://www.mouse-sensitivity.com/?share=20cff01c097427e65e54affa09feeca3
  21. Do like this, replace resolution and DPI etc with your own: https://www.mouse-sensitivity.com/?share=8479d8e40c93c76c0d3928c80ecf31cf
  22. You can't set the sensitivity to 14 in the game, it can only be set in steps of 10. So the calculator rounds it to 10 since it is the closest you can get to your distance.
  23. Check out this thread
×
×
  • Create New...