Jump to content

DPI Wizard

Wizard
  • Posts

    18,149
  • Joined

  • Last visited

  • Days Won

    1,763

Everything posted by DPI Wizard

  1. Have you set the ADS (Iron-sight) sensitivity after the patch? What sensitivity are you using, and what is the issue?
  2. I always measure sensitivity and FOV with scripts. Aims that have blacked out the edges can be measured in two ways. Either by figuring out how the game scales FOV and sensitivity through other tests. So for instance if the game scales sensitivity to 100% monitor match, I know that double the 360 distance equals half the horizontal FOV. Or by measuring the distance visible in the scope. If only 40% (between the crosshair and edge) of the screen is visible, I can measure how far moving this 40% is, compare this to the 360 distance and calculate how many degrees I moved to reach 40% monitor distance. From there some more math to find the FOV. The FOV in the calculator is for the entire screen regardless of what is blacked out.
  3. I was going to add them, but the game has serious issues with acceleration still, so it's not really doable unfortunately.
  4. Support is only available in English. The Chinese translation is only for the forum framework.
  5. 360 distance usually works well for hipfire, but is not suitable for ADS and scope conversion. Also make sure your FOV in BF4 is correct, 105 is very wide.
  6. Correct. FOV scales very weirdly with aspect ratio for PUBG though, but it should be correct even for your aspect ratio.
  7. Yes, FOV Type is correct. But PUBG in TPP has a fixed FOV while FPP is affected by the FOV you configure, so the difference in sensitivity is very noticeable when you have it set to 103.
  8. Change your Perspective selection for PUBG to FPP
  9. There is a config file with the sensitivity, but changing it in the file does not actually change it in the game.
  10. I know, but I can't analyze them without getting to level 65 or so. Not sure how long that will take, but it's probably very time consuming?
  11. Tried the new VALOFE version now, it's still horrible unfortunately.
  12. I've updated the variable names now
  13. Nice observation, I need to look closer at what exactly is happening here. It's probably a rounding error in the discrepancy somewhere since there's very small numbers at play in the background, but the sensitivity calculation is still correct.
  14. Yeah, I actually did "fix" it and replied to you, then started the game to verify it and realize they removed it
  15. The "new" sensitivity setting is basically setting all the scopes to the same value so it doesn't need an update. Vehicle sensitivity is removed.
  16. Sorry, meant to fix this a while back! But now it is actually removed from the game It is affected by general sensitivity now.
  17. The file might not be created until you change some sensitivity setting in-game and exit. Maybe.
  18. Yes. Haven't tested with it off.
  19. Setting the new scoping to 39 is the same as setting all the "X Scope" values to 39, so you are probably better off setting it to 38. Iron-sight is the new ADS, keep it at 39.
  20. The Origin version worked very well for me without any tuning. The Steam and old DVD versions are horrible.
  21. DPI Wizard

    6.11.7

    Game added Cuisine Royale Game updated Sea of Thieves - Added scopes.
  22. No joke, this is added!
  23. DPI Wizard

    Cuisine Royale

    No joke, this is added!
  24. Yes, the scope/ADS sensitivity is not aligned to hipfire at all in this game, so you will usually get "too high sensitivity". Adjusting DPI on ADS is the only fix, but then you of course need a quick DPI swap on you mouse as well.
×
×
  • Create New...