Jump to content

DPI Wizard

Wizard
  • Posts

    18,155
  • Joined

  • Last visited

  • Days Won

    1,764

Everything posted by DPI Wizard

  1. You need to enter a value for Sensitivity 1 for the config file conversion. Anything should work, for instance 10 as in the previous calculation.
  2. 0.4 is so slow compared to your hipfire that you need to do this in two steps. You should first do hipfire to hipfire: Then do Scope to ACOG:
  3. Fortnite uses horizontal FOV, so it's not the same as 80 in R6 which uses vertical FOV. The same FOV in R6 would be 50.53, which is really low for that game. As for your sensitivity, what are your Mouse Sensitivity, Mouse Targeting Sensitivity and Mouse Scope Sensitivity in Fortnite?
  4. DPI Wizard

    7.9

    Calculator updates Monitor distance now supports negative numbers for a match slower than 0%. MDH and MDV 0% will now show the discrepancy for the 360 distance.
  5. I just updated the calculator to support negative monitor distance. This is very useful for those who prefer a match slower than 0%. So if you for instance prefer 0.8 for 3X scope in Apex, you can now do this in the calculator: So in this case you'd want to use MDH -100% for your scopes so they match this.
  6. Leave the 2D/Win setup at 100%, but for ADS and Scope you can use 0%.
  7. Try it like this:
  8. Try with 100% instead.
  9. But what percentage? 0 or 100?
  10. What is the Win/2D setting in your conversion setup? MDH 100% is usually the recommended method for 2D.
  11. Are all the values for R6 exactly as in your config file? I.e. MouseYawSensitivity AimDownSightsMouse MouseSensitivityMultiplierUnit XFactorAiming If not the calculation will be off.
  12. It depends, but changing the FOV for hipfire does not change the 360 distance. It is the same regardless of FOV.
  13. The in-game calculation requires the multipliers in the config file to be set to the default values of 0.02. If they are not it will be wrong.
  14. 1 is MDH 100%, while MDH 0% is close to 0.8.
  15. So I've checked now, nothing has changed. FOV is still 96% of the configured value, and sensitivity is exactly the same.
  16. I will check when it's finished downloading
  17. First do hipfire like this (make sure to input your CoD FOV): Then convert ADS to ADS:
  18. DPI Wizard

    7.8.p

    Game added Die Young
  19. Just added!
  20. I thought I had this game figured out, but when I started playing I noticed that sensitivity randomly changed. Also smoothing can not be turned completely off, so it's unsupported for now.
  21. The FOV shown in-game in Apex is "wrong" in that is not exactly Hdeg 4:3, the correct FOV is the value from the config file multiplied by 70. It's just a bad implementation by the devs.
  22. The FOV is wrong. When Location is set to Config File, the calculator by default expects the FOV value from the config file (cl_fovScale). You have entered the in-game FOV which completely messes up the calculation. For CoD you also need to enter your current hipfire sensitivity since it's a part of the ADS sensitivity and needs to be provided for the calculation to work
  23. Because it's calculated since you have selected an "All" aim. If you want to convert from a specific aim, select it in the aim dropdown. Then the multiplier will be unlocked
×
×
  • Create New...