-
Posts
17,877 -
Joined
-
Last visited
-
Days Won
1,717
Community Answers
-
DPI Wizard's post in Call of duty Relative affected, to apex conversion was marked as the answer
You have done it correctly, although you should technically use MDV 178% and not 177.7778% to match Relative Coefficient 1.78, but this will not make a discernible difference.
That is what you should put in the config file yes, and for scalar 0 you have to choose between the two options depending on what you prefer.
-
DPI Wizard's post in API request was marked as the answer
As said above, the calculator already does "everything" for you, you don't need to know anything about the complexities of the math, you only need to specify how you want the sensitivity to be converted.
While it could be possible to to make AI answer questions such as
"What sensitivity do I need to set in-game in RoboCop: Rogue City with FOV 116, resolution 2560x1440 and 800 DPI to match the 360 distance of in-game sensitivity 1.48 Apex Legends with FOV 110, 3440x1440 and 1000 DPI?"
it would be faster and more reliable to just select these options in the calculator.
-
DPI Wizard's post in Question about how to adapt sens between Rainbow Six Siege and Aimlabs (or other aim trainers)! was marked as the answer
Set the FOV in Aimlabs to the same FOV as you ADS in siege, then match the 360 distance. This will make it identical.
-
DPI Wizard's post in Warzone 2 legacy to Apex legends and Battlefield 2042. was marked as the answer
Since Legacy MW is based on a specific FOV, you have to use this FOV as the source for your conversion. So do like this, and just change the game you are converting to.
-
DPI Wizard's post in 4:3 to 16:9 cs 2 was marked as the answer
The vertical FOV is the same with 4:3 stretched and 16:9, so you need to switch the conversion to MDH 100% instead of MDV 133%:
https://www.mouse-sensitivity.com/?share=1083d3cd8f5b3a3010a2dd484aba6bdd
That should feel better.
-
DPI Wizard's post in Mouse Sensitivity Discord Server was marked as the answer
I do agree that this would be a good thing to have in place, I will try to get it up and also integrated as soon as I can.
-
DPI Wizard's post in Why do I have to change DPI to fit some games? was marked as the answer
The in-game sensitivity has a quite limited range, if you use the config file instead you should be able to match it without changing DPI.
-
DPI Wizard's post in How does pixel rate affect recoil? was marked as the answer
The recoil, and any other forced movement like sway and head bob, are based on set parameters that move you x degrees up, down, left and right. It is completely detached from your sensitivity setting. If that is what you were asking
-
DPI Wizard's post in What does "The sensitivity slider is not accurate, expect some discrepancy" mean? was marked as the answer
This is not related to the discrepancy shown by the calculator. This discrepancy shows you what the sensitivity/360 distance is with the calculated sensitivity is compared to the target sensitivity/360 distance, and is caused by the lack of decimal support by the game.
The inaccurate slider note means that when you set the slider to say 3.3 it might in reality be anything from for example 3.21 to 3.39. This is the case for a lot of games unfortunately, and if there's no config file option there's not much you can do about it.
This will make the actual sensitivity differ from the calculation, but usually not by a significant amount. Although this will vary depending on your sensitivity. If your target sensitivity is for instance 0.2, and the actual sensitivity is 0.29 due to the slider being inaccurate, you will get a significant difference since it's 1.45 times higher.
-
DPI Wizard's post in Satisfactory outdated was marked as the answer
My bad, I thought they had moved everything to the GameUserSettings.ini file. I've fixed and updated everything now
-
DPI Wizard's post in Fortnite to valorant was marked as the answer
Since Fortnite is 3rd person and has a quite narrow FOV, it's really hard to make it "feel" the same as a 1st person game with a wider FOV.
What you have tried is the correct way to go about it, but I would suggest also trying 133 and 178%.
-
DPI Wizard's post in Call of Duty: Black Ops III: boiii Client fovScale bugged was marked as the answer
In that case you can just use the normal Black Ops III calculations, they are the same as the boii client but with the fovscale locked to 1.
-
DPI Wizard's post in Windows/Desktop and game sensitivity was marked as the answer
Nothing is really necessary as it depends on you preference. The positive of matching everything to Windows using MDV 0% is that 1 pixel movement will always be the same. The downside is that this will drastically affect especially hipfire when your FOV is different. 360 distance is usually preferred for hipfire as it keeps a constant movement for orientation rather than aim. So you know how far to move your mouse to turn around a corner etc. With MDV 0% or a match made to Windows/Desktop, this distance will change depending on your FOV. And while it keeps the aim consistent, this is usually less important than navigation when it comes to hipfire.
But it all depends on the game and your preference, nothing is right or wrong, what is important is what feels natural to you.
-
DPI Wizard's post in When "Synced"? was marked as the answer
It's unsupported because the sensitivity is directly affected by the framerate, making it very unstable and any sensible calculation impossible.
So as to your question of "when", it will be added when the devs fix this issue
-
DPI Wizard's post in How to convert ADS from game to game? was marked as the answer
Sensitivity 2 is the Coefficient (you can see this in the output), and the 0.68 is the scale for the ADS conversion, where also enter the coefficient so it matches, like this:
https://www.mouse-sensitivity.com/?share=f42f0a7af910c8457de15d13bdc1db5a
-
DPI Wizard's post in How is the "actual zoom" calculated? was marked as the answer
Trigonometry
https://www.wolframalpha.com/input?i=tan((PI*74)%2F360)*cot((PI*66.6)%2F360)
-
DPI Wizard's post in Relation between FOV and monitor distance was marked as the answer
The relation between the actual FOV and the monitor distance is calculated, in this old video you can see it visualized:
This is Monitor Distance 100%, and depending in whether you use the horizontal or vertical FOV to do this, you get either MDH 100% or MDV 100%. The method will for many make the scopes feel too fast, since you need to match the movement to the edge of the monitor (side for MDH, top for MDV) to actually match the movement. Monitor Distance 0% however, will match the tracking speed, i.e. the rate at which you move your mouse to track a moving target.
-
DPI Wizard's post in Roblox Criminality sensitivity conversion completely off was marked as the answer
Actually, do you have zoom enabled in Windows? 150%? It might affect certain games like Roblox. If this is the case, multiply the sensitivity by 1.5 to compensate for the zoom.
-
DPI Wizard's post in convert BATTLEFIELD 4 (FOV) TO KOVAAK (FOV) was marked as the answer
Just set the FOV to Vertical (1:1) and use the same value (86).
-
DPI Wizard's post in conversion fov hor for vert was marked as the answer
You can try to use the same conversion for hipfire as your ADS and scopes: https://www.mouse-sensitivity.com/?share=6d0061b61632e557e421e98084031850
-
DPI Wizard's post in Problem when converting sensitivity in Apex Legends was marked as the answer
Set the ADS and scope scale to 99.083: https://www.mouse-sensitivity.com/?share=17de5bb30efe2973a47d30d9f48c41bf
-
DPI Wizard's post in GZDoom has total mouse sensitivity rework was marked as the answer
x and y are still different, but they have halved the x sensitivity so they are much closer. I've updated it now
-
DPI Wizard's post in Question about the calculation of ADS-Sensitivity was marked as the answer
What you said is correct, and it has to be this way to make any sense. If the scopes were matched to the hipfire of the output game you would not get any consistency unless you also match the hipfire FOV between the games.
Consider this example converting from Overwatch with FOV 103 to Overwatch with FOV 80: https://www.mouse-sensitivity.com/?share=43c8dace9347072001b6b2962b254eaf
The FOV change only affects hipfire, the zoom FOV stays the same. So the sensitivity (360 distance) for the zoom should also stay the same to keep it consistent. If they were matched based on FOV 80 instead, you would get a completely different sensitivity for identical zoom levels.
Click the reverse calculation button between the input and output game
-
DPI Wizard's post in Battlefield 2042 Conversion for 1×00 was marked as the answer
The "Zoom Level: Iron Sight" is also 1.25x, at least on the weapons I've tried so far. Just switch between 1.25x and iron sights and you'll see it's the same.
There might be a 1.00x somewhere, but it's really hard to find!