Jump to content

DPI Wizard

Wizard
  • Posts

    18,162
  • Joined

  • Last visited

  • Days Won

    1,764

Everything posted by DPI Wizard

  1. Only added aiming sensitivity for ironsight for now. Is there scopes, and if so how do I get them? Random loot?
  2. DPI Wizard

    Deadside

    Note that there's a small amount of acceleration in this game.
  3. Note that there's a small amount of acceleration in this game.
  4. Unless someone knows a fix for this, both those games emulate an analog joystick for the mouse input and are impossible to add.
  5. Updated sniper now with new FOV. When converting from Splitgate you should see all aims, do you not see them?
  6. I see now, like this you mean? https://www.mouse-sensitivity.com/?share=7037f635e222c171cb08e1e5d0ae9cd0
  7. My example converts hip and ADS with your exact settings based on the conversion setup. Convert back to Fortnite and you'll see that all the numbers calculated matches your settings, so any other game you select will also use the same conversions. https://www.mouse-sensitivity.com/?share=dfec32e36eac97cfe9e106ed6977f4e1
  8. Do it like this (adjust DPI, resolution, monitor size etc according to your settings): https://www.mouse-sensitivity.com/?share=a4943315008f57d487ae56ae04fff459
  9. It seems like you didn't share the correct input, but you can use the calculator to calculate to and from this value.
  10. It says pretty clearly you are trying to use a Premium feature without premium access
  11. Fixed!
  12. Notice how your crosshair jumps around with just the slightest mouse movement on the 12X? That's why you don't want the same 360 distance for all scopes. You use scopes for aiming, not turning around. Xfactor definitely affect both ADS and scopes in R6, however in R6 all scopes max out at the same 360 distance as hipfire (i.e. they can't get any faster), so at at a certain point it stops affecting the scopes. You typically want aim sensitivity to relate to what you see on your monitor, which is why FOV as a factor even though it does not affect 360 distance. Tracking a target, flicking to a target or in one way or another react to what you see on your monitor. You don't run around through buildings and doorways zoomed in on your 12X scope The concept of having the same 360 distance for all scopes is so far fetched most games won't even support this. MW being one of them:
  13. Since hipfire in your example is matched using 360 distance, MW with a narrower FOV (120 vs 133 in BFV) will feel different. The solution to this is to use a FOV based matching method for hipfire as well, for example MDH 100% as you have done with aims. Both games use MDV, the calculator will calculate this value for you as a placeholder suggestion based on your configuration. With your setup all guns should have the exact same distance when moving the crosshair to aim at what is at the edge of the monitor as you in BFV hipfire and aims. Any other measurement will be different.
  14. You had ADS set to 360 distance, this is usually not recommend as the ADS will be too sensitive. Using another method like MDV 0% will instead match the tracking speed between the aims.
  15. They have different sources, so they are both correct in their own respect. 0.705 is MDV 0% to a vertical FOV of 73.739795 and a 360 distance of 21.5311 inches. 0.747 is MDV 0% to a vertical FOV of 70.5328 and a 360 distance of 21.4286 inches. The reason you should stick to one game as a source for everything is exactly this.
  16. The "mousesensitivity" value under playerinput didn't do anything strangely enough, but I'll poke around and see if I can find another variable.
  17. DPI Wizard

    Mass Effect 3

    You need to use a third-party tool to disable acceleration in this game.
  18. You need to use a third-party tool to disable acceleration in this game.
  19. Nice, then it's the same as in 3.
  20. Working on 3 right now actually. Not sure if 2 is possible but I'll give it a try
  21. It's based on distance, not actual pixels. Although 0% would be exactly 1 pixel per count for both (assuming you convert between the same resolution), any other percentage is just the physical distance. MDV 133% is in other words 133% the vertical distance from the crosshair to the top of the screen. Or for 16:9 this equals 75% of the horizontal distance between the crosshair and the left or right edge
  22. The only thing that changes is the pixel density. How far, fast and accurate you turn stays the same.
  23. I need to check that later.
  24. You can do this in a single calculation, no need to select Ashe. Just use the "All" option for Overwatch instead. It seems like you have set ADS to 360 distance, which will make it very fast. Try like this instead, where the tracking speed is matched: https://www.mouse-sensitivity.com/?share=6920caf3669a09e132eeded734d95b8f
×
×
  • Create New...