Jump to content

DPI Wizard

Wizard
  • Posts

    18,149
  • Joined

  • Last visited

  • Days Won

    1,763

Everything posted by DPI Wizard

  1. 3.4X scope added. Also adjusted the other sensitivities and FOV slightly. The default match between scopes is 0% monitor distance.
  2. The calculation is 100% correct. The game is based on Unreal Engine 4 and it uses the standard Unreal Engine 4 sensitivity. It does however have serious issues with negative acceleration. You need to move your mouse really slowly to replicate the correct sensitivity. I'm in not control of this unfortunately, it's up to the devs to fix the mouse input.
  3. Yes, all scopes at least. Haven't gone through vehicles yet. It's just the default value that's changed, the USA value does exactly the same (i.e. 100% = 100% vertical monitor distance).
  4. All scopes if Override is turned on.
  5. Nothing has changed
  6. If you set the sensitivity in-game (meaning MouseSensitivityMultiplierUnit and XFactorAiming in the config file must be set to the default value of 0.02) you should set Mouse Sensitivity Horizontal and Vertical to 5, FOV to 70.53 and Aim Down Sights to 42. This will not be very accurate though, since the lack of decimals causes a discrepancy of over 8%. The recommended method is setting the sensitivity in the config file with the following values: MouseYawSensitivity=5 AimDownSightsMouse=5 MouseSensitivityMultiplierUnit=0.018431 XFactorAiming=0.176822 DefaultFOV=70.53 This is assuming you want to match the scope sensitivity to ACOG. Ironsight will be different.
  7. The sensitivity in the CSGO file is set to 3.28, not 2.96. How far is a 360 in ARK with 0.372152 and 400 DPI for you?
  8. Ok, just checked now and nothing is changed in ARK, so the calculation is spot on. Can you PM me your CSGO and ARK config files? Just copy and paste them in a message here.
  9. I'll check if anything is updated in ARK ASAP!
  10. It still works, the change is only on the test client for now. It will still work after the change, but the sensitivity variable will have a different name.
  11. Yes they scale directly with the horizontal FOV, i.e. half the FOV = double the 360 distance. This is the same as 100% monitor match.
  12. You have entered 1.255298 for Aim Lab, not 1.335402 PS! FOV 90 in Aim Lab is not the same as 90 in Realm Royale. 58.72 is the correct vertical FOV for Aim Lab if you want the same FOV.
  13. This. And if your main goal is to practice ADS, set the FOV to 41 to best mimic the ADS FOV from Realm Royale. But note that this will make your hipfire FOV very narrow:
  14. Field "Multiplier 1" when you select aim ADS or Scope.
  15. DPI Wizard

    6.11.10

    Game added Battlefield V
  16. All scopes are in!
  17. Ok, that's the same thing I do. Seems like the negative acceleration is completely unavoidable even with low polling rate, so I adjusted the formula to reflect this. Try again and see if it's better now.
  18. Can you tell me exactly how you test? Which map/mode/class/weapon etc? Maybe there's some differences between them.
  19. What version of the game do you have? Calculations are based on the Steam version.
  20. Bug in the game, but the few decimals changed are negligible. Do you mean for vehicle? If so it uses General Sensitivity.
  21. Check the FOV notes in the game info The FOV in-game is a rounded value of the 4:3 hdeg FOV, the accurate vertical FOV is in the config file and should be set there for best accuracy. If you choose to set the FOV in-game select "Hdeg 4:3" as FOV type.
  22. Scopes will be added throughout the day.
  23. Sensitivity settings are mostly the same as in Battlefield 1.
  24. DPI Wizard

    Battlefield V

    Sensitivity settings are mostly the same as in Battlefield 1.
×
×
  • Create New...