Jump to content

DPI Wizard

Wizard
  • Posts

    18,155
  • Joined

  • Last visited

  • Days Won

    1,763

Everything posted by DPI Wizard

  1. 1. With 83 you have the same 360 distance for ADS. But the FOV is different so this is in most cases not desirable. You are better off using a match based on what you can see, like MDH, MDV or viewspeed. 2. You can do like you have done, but remember that 90 in CSGO and 90 in R6 are completely different (see actual FOV). 3. The discrepancy is so small it's negligible, and there's usually nothing you can do about it. It's there to show you what differences you might experience in the sensitivity due to limitations of the game.
  2. I wasn't able to load a mission until now, all the current calculations are based on the 1st person view in the hub. The 3rd person javelin view has horrible mouse controls, so calculations are not correct for that unfortunately. Hopefully they will do something about this before release.
  3. Yes, with raw input enabled
  4. They are the same if you use the same values. When the "All w/ ADS" more values are automatically calculated, if you use the same values with "Iron sight" the end result is the same. The reason why there is a separate option for ACOG is that it scales completely differently to ADS, so you need to chose your favorite.
  5. Fixed
  6. PUBG has changed config file syntax quite a few times, so it's not a bad idea to just delete the config file and set everything up from scratch, although it might be a bit of work. If you don't do this there might quite a bit of unusable junk in the file.
  7. If the PUBG file is correct your sensitivity is: SensitiveName="Normal",Sensitivity=45.000000,LastConvertedSensitivity=0.015870 Not 32/0.008740 Which one is correct?
  8. Well that depends on your preference. Can you post your entire config file?
  9. This is virtually impossible to achieve as none of the scopes have the same FOV. But for hipfire it is doable, change the "Normal" setup in your conversion setup to 360 distance
  10. There's a bug in the code somewhere with how sensitivity 2 is handled, switched it to multiplier 2 which works as expected! Edit: GstInput.MouseSensitivity 1 is without any acceleration as far as I can tell. I'm not sure where the cutoff is, but with 1 it's about perfect.
  11. Runs great here, except from the first mission not loading lol.
  12. Updated the game now. Select config file calculation and re-calculate your sensitivity with the GstInput.MouseSensitivity value set to 1 and you will eliminate all acceleration.
  13. I found a way to completely eliminate negative acceleration, updating calculator soon!
  14. No, the polling rate. Set it as low as possible. If it feel very jerky increase it a bit. Low CPI also works since the mouse sends fewer packets.
  15. In the mouse driver. But I'm going through the config file now and let you know if I find another way to fix it.
  16. Yes, it is. Use low report rate to alleviate it.
  17. DPI Wizard

    7.5.i

    Game added Anthem
  18. Added with hipfire sensitivity, more coming soon!
  19. DPI Wizard

    Anthem

    Added with hipfire sensitivity, more coming soon!
  20. Yes, it' like it's been trough the express port! (This is RE2 and not Anthem if anyone is confused. Anthem is fine and coming soon)
  21. Instructions here
  22. Edit: Nvm, got key!
  23. DPI Wizard

    7.5.h

    Game added Sky Noon
  24. DPI Wizard

    7.5.g

    Game added FPoSu
  25. The mouse input is horrible. Lots of negative acceleration/smoothing.
×
×
  • Create New...