Jump to content

DPI Wizard

Wizard
  • Posts

    18,155
  • Joined

  • Last visited

  • Days Won

    1,764

Everything posted by DPI Wizard

  1. The issues is still there, but only shows up in certain cases. I'll make a video
  2. Actually let me test it a bit more, I initially tested it in the prologue where you spawned in. But testing it now (in the Jagni Fort) it seems to work better. I'll do some testing and let you know if it's still an issue. It might be just a temporary problem in the prologue, if so there's nothing to worry about imo.
  3. It's a really cool game, for some reason I went to the dark side immediately, don't ask me why The only issue I've noticed is some inconsistency in the vertical sensitivity. It might be affected by the camera distance changing when the camera is tilted or something similar. In short, if you move say 100 counts up, then 100 counts down you don't end up in the same spot (horizontally this works perfectly). It's a minor problem, but if you could perhaps relay this issue it to the right guys that would be excellent! I could make a video to show the issue if needed.
  4. Awesome! Are you still a part of the team working on it, or is it previous work you've done?
  5. It might just be, unfortunately
  6. Are you applying to custom resolution to Windows, or starting the game with Windows in 1920x1080? Or is Valorant maybe ignoring it and starting in 1920x1080 anyway?
  7. Updated!
  8. Ok, to get this to work correctly you have to add a custom resolution to your graphics driver and make sure your monitor is not resizing it. The game should then be able to run the custom resolution in what it thinks is fullscreen.
  9. Is this with black bars (top and bottom) on an 1920x1080 (or higher) monitor, or blown up to fit a 16:9 display?
  10. What exactly are your settings for VALORANT?
  11. It should be the same yes, it just haven't been updated. In fact I think the separation between BR and Save the World can be removed as it seems to be the same now. It used to be different.
  12. No, this is the fourth request I think It's unfortunately unsupported due to serious issues with polling rates and smoothing. If they release a fix for this let me know!
  13. Just added it
  14. This bug seems to be fixed now, when I enter 6 decimals and click apply it registers correctly in the config file. The UI rounds to 4 decimals. Does it work for you now?
  15. Some features and games/aims are premium, it's literally what keeps the site alive and ensures games are being added and everything kept up to date.
  16. Hipfire sensitivity is unaffected by FOV (meaning the 360 distance stays the same), so to match it the sensitivity is lowered to 0.999995. ADS is however affected by FOV, and as mentioned earlier it is rounded before calculation. So 1.28571 which is 89.999700 4:3 FOV is rounded up to 90 before calculation. And with MDV 0% as this game is based on this results in 1.000005 to compensate for the games buggy rounding. It is already precise within 0.0001 inches, this is not even measurable with scripts so I think you're good with 6 decimals The difference between 1.000005 and for instance 1.0000059 is less than 0.04 counts/360.
  17. DPI Wizard

    BIOMUTANT

    Config file and in-game sensitivity added!
  18. Config file and in-game sensitivity added! View full update
  19. Ok, gotcha! It still zooms in, but is changed to max 65 (if your configured FOV is lower than 65 the ADS is the same as configured). Updated now.
  20. Do you have raw mouse input on for Planetside 2? Just checked it now and calculations are correct from what I can tell.
  21. Very nice, works as intended now!
  22. Apex annoyingly rounds the input FOV to the nearest whole number before doing the calculation. This is just for the sensitivity calculation though, the actual FOV stays the same.
×
×
  • Create New...