Jump to content

DPI Wizard

Wizard
  • Posts

    18,141
  • Joined

  • Last visited

  • Days Won

    1,761

Everything posted by DPI Wizard

  1. I actually did it on purpose as a quick fix since the last part of the path got cut off by the page. Will fix it better soon
  2. This is correct, as Titanfall is Source based. However there's a bug in the beta; if you set the sensitivity to a value below 1, e.g. 0.8, it will automatically reset it to 1 when you launch the game. So the calculator has a minimum value of 1 for now, I will change this when/if they fix it
  3. This will be possible with a feature I'm adding soon! So I will add the game as well then
  4. I'm signed up, really looking forward to this game! Looks awesome!
  5. There is a way of doing this precisely, but you need resolution and probably FOV as well to calculate it. And there's no universal equation that will work, it will need to be integrated into the existing game algortihms. I'm working on it
  6. This is an upcoming feature, but it's not quite ready yet.
  7. It's next on my todo list, should be up in a few days
  8. You were absolutely right, the correct sensitivity is half of what the calculator said. The mouse response is very good now, as opposed to when I tested it initially. Thanks for notifying me, the calculator is updated now
  9. I will, reporting back soon!
  10. Can you check if you have the same issue with other games, also if the distance is the same with slow and fast movement? There might be some driver related acceleration going on here.
  11. Viewmodel is just the rendering of the gun if I'm not mistaken? Correct me if I'm wrong. Other than that, the calculator uses the 4:3 FOV in the calculations, I know this can be confusing, and not exactly easy to work with. An upcoming update will let you enter both resolution and FOV in either horizontal or vertical FOV or Radians. And also calculate these numbers for you
  12. I don't know if they've fixed this in Warface yet, but as stated in the notes, Warface does not register single counts. This means that if you move your mouse really slowly, the crosshair will not move at all. The experienced effect is that a lot of counts from the mouse are dropped, and you need to lower the sensitivity to get the correct distance. This is a workaround, and hard to calculate... If you try one 360 with very slow movement, and one with rapid movement, are they the same distance?
  13. Hi! The calculations for BF4 are 100% accurate, I've checked them many times In your case two things might cause the difference in distance. First of all, is raw mouse input turned on? If yes, then the cause is most likely inaccuracy in the mouse sensor. It's not uncommon that they are 10% off, meaning when you have set it to 800 DPI, it is in reality 720 DPI. To doublecheck, try to calculate another game in the calculator if you have one, preferably one with no acceleration (like Mincraft, Crysis 3, BF3, TF2), and see if the distance is still 10% off.
  14. Hi! I think acceleration makes the calculation seem off. They are correct for 100% unaccelerated movement, however this is only possible to achieve with scripting (which is what I do). I plan to add customizable acceleration to the calculations in the future
  15. I'll check it! Btw, what numberes where yiu using, and what was the measured result?
  16. Yes, more unreal games are coming
  17. Strange. Are you sure acceleration is turned off, and raw mouse input is on? Also, are you using default FOV?
  18. Correct, the slider in the game menus is the only way, unless they've changed something in recent patches,
  19. I will look into this!
  20. Thanks, removed now
  21. Just added, enjoy!
  22. Loadout is just added!
  23. Working on it right now, will be added shortly.
×
×
  • Create New...