Jump to content

DPI Wizard

Wizard
  • Posts

    18,155
  • Joined

  • Last visited

  • Days Won

    1,764

Everything posted by DPI Wizard

  1. This old game is a no-go. Too many issues with the sensitivity.
  2. Smoothing/acceleration can't be turned off completely in this game (tried in the config file too), so it can't be added.
  3. You have selected relative ADS. While it is the same as Legacy since you also have the coefficient set to 0, you might as well just set it to Legacy.
  4. As long as you have selected Legacy it doesn't make any difference, but set it to 0 to be sure.
  5. You already have the ADS Mouse Sensitivity set to Legacy, which removes the coefficient and is effectively MDH 0%, which is why you get "1" as the sen for ADS. This is correct and matches your CSGO sensitivity.
  6. When does it stop?
  7. It seems off based on that indeed. They recently did a re-take of their sensitivity so if you haven't tried it, try to reset everything to default then set it again. Other than that I'll try your exact settings!
  8. Nothing weird here, the "All" selection will use the default value of 1 as a placeholder value for global sensitivity. The Hipfire selection will ask you to fill out this value yourself (as thoroughly instructed by the output; value and valid range to enter)
  9. It's not a sensitivity on it's own, it's a multiplier for the SoldierSensitivity (hipfire) and the various aims via SoldierZoomSensitivities. So you can't make the global sensitivity match anything since it's worthless without the additional values. Setting it to 0.1, 0.5 or 1 basically means nothing until you also have the SoldierSensitivity/SoldierZoomSensitivities values. The "All" aim does not lock it to 1, it uses 1 as a placeholder value (because it's default by the game) to make calculations easier. You can use any value you'd like within the range of the sensitivity, but using values other than 1 is seldom needed.
  10. The Global sensitivity don't need calculating, just use the default value.
  11. It's not bugged, you have selected config file sensitivity, switch to in-game for the in-game values.
  12. Vehicle and in-game sensitivity added!
  13. The calculator does the magic for you. If you just enter your desired monitor distance (either vertical or horizontal), the equivalent coefficient will be calculated and used a placeholder value. You will only see this when you have not entered your own value into the field.
  14. Just checked now, and it still works after the last update. Be sure to set the correct Camera sensitivity and Look sensitivity.
  15. Everything seems to be exactly like PS2 (aside from default FOV etc), I just haven't got around to verify it yet. Try using the PS2 calculations with the correct FOV and it will probably work.
  16. Since you can't control the sensitivity of every aim and scope, this is the best you can do with the limitations of the game unfortunately.
  17. You still have the separate scope sensitivity with ADS sensitivity set to Relative, just like you have separate sensitivity for each scope in BF with USA on. Now to get a consistent scaling you should set them to the same value and preferably use the coefficient only. PS, all ADS and scope sensitivity seems currently broken in the MW beta.
  18. DPI Wizard

    7.8.m

    Game added PlanetSide Arena
  19. In-game and config file sensitivity is in!
  20. In-game and config file sensitivity is in!
  21. Scope/ADS sensitivity is broken in the beta, the sliders do nothing. Wait for a fix
  22. Hipfire was a little bit off, fixed now. In-game or in the calculator? Both should work, but in-game doesn't save the FOV. Seems like a bug in the beta indeed, ADS sensitivity does now work yet. Updated it now. Fixed, was just the wrong default FOV.
  23. Getting the exact same results here, what are your settings?
  24. It's already added
×
×
  • Create New...