Vampire

I couldn't become friends with 0% MDV so I had to choose something else, problem is, anything other then 0% results in different calculations depending on if you have choosen MDV or MDH so what is genereally better? I assume that MDH is better for games where you only have to aim on the Y-Axes like CSGO, while MDV might be better for games that have the X-Axes present too like Overwatch or fast paced games like Apex, but I kinda wanna settle myself on one thing so what would be recommendable?

The question I now have if it even makes sense to use "Jedi's Trick" when it comes to calculating anything other then Win/Game. I personally am not sure what to convert when convertig hipfire. 360° distance or 0% MDV? When looking through the forum or just in the most recent posts, most thing I see is @Vaccariaposting this thread with the note "try this" which sounds promising but Jedis trick seems to be about 2D Windows to 3D Game the most, but barely seem to say something about using this Method for a game to game calculation, or even for using it to calculate ADS/Scope sens in one game itself

Some games have a distortion at the edge of the screen. Some games have a slightly more cylinder like of appearance as it's commonly seen on the world map where the round earth surface is shows as a square, leading to precise depictions along the equator but to "false sizes" on the side. And the screen is only a window that gives us a view inside our gaming world, however we can set the view of this gaming world in the settings with the help of the FOV slider, so how does that affect your precision? Whenever I think or speak about sensitivity, I have 3 scenarios in my head, and I now want to know how relevant the FOV is for each scenario. Scenario 1: No calculations, no conversations, only 1 game We all have a favorite game that we play the most and so we would want the best settings in that game, the settings we have in there doesn't need to be converted to another game because this game is all that matters. Does the FOV even matter in this case? We don't need to maintain any consistency amongst different games, because this one is the only we play, so we can go as high as we want right? Scenario 2: maximum consistency Doesn't need to be said much, when we want the maximum mathematical consistency between games, actual FOV need to be the same when using the calculator. Tho what actually even is the best FOV for a 16:9 Monitor? Scenario 3: No consistency We want to convert between games but don't care for the maybe slight off results when using different FOV, we just use whatever feels right in each game of their own on the expense of accuracy when converting to a new game.

Okay so at this point I truly don't know if I am just straight up completely incompetent, overseeing some major detail (or both) or if soemthing just isn't as it should be, some detail missing, something not working properly. IF I understand Monitor Distance correctly it should be as following: There is a tree at a specific point on my screen and I need 10 cm of mouse-movement to get my crosshair on that tree, 0% MDV now means that if I zoom in on my scope and due to the changed FOV there is now a car on on the same specific point on my screen, I would again need 10 cm of mouse-movement to get my crosshair to that car. It is always the same mouse-movement towards whatever is on a specific point on my screen, no matter the zoom FOV, hence the apperently "good muscle memory" because it always requieres the same input to reach a certain point, no matter what your zoom FOV is. For 50% Monitor Distance it is the same movement for whatever is currently half way from your crosshair to the edge of the screen, and it is therefore restricted to that one specific point of your screen And 100% is the same but for whatever is on the edge of the screen, and it is therefore restricted to that one specific point of your screen My problem has been so far that I am unable to proper track enemies when in scope, it just feels so slow. I also can't react to what happens a bit further away from my crosshair, like 30% Screen distance. And it is completely impossible to react whatever happens beyond that, let alone next to you. And you see all the pro players flicking 360 degrees around them while in ADS with pin point accuraty while using something like 35 cm for a 360° turn

So if I am understanding it correctly, Legacy is not true 0% MDV when using anything else then 65 FOV 4:3, which is the case for me, so I should use Relative instead from now on and for future calculations

So, easiest solution is just to always enter the FOV, makes sense and I should have kinda done that earlier. But, speaking about MW 2019 I still or now am confused about the Legacy/Relative difference. Which one of them now is actual 0% MDV? (By the way, does it even matter if MDV or MDH is taken for calculations? I always took MDH because horizontal makes more sense as you, well, often aim horizontally)

Makes sense as 0% relative appears to be the same for every scope other then the calculated settings for 0% Legacy, difference there being that 0% relative doesn't need to be "calculated" (it's all just "1" while legacy has odd numbers like "0.49042") I do not really understand why that is as I remember DPI-Wizard themselfs saying that Legacy is 0% Monitor distance and people in Forum saying the same, stating that Legacy is better for muscle memory. But that appears to not be the case when looking at your statement right?

I normally always use the highest FOV available in a game. I feel the most comfortable with it. When not using max FOV it feels cramped, restricted and somewhat claustrophobic. But when calculating to other games I never much cared for the advice that you should also convert the actual H,VFOV, thinking "I rather have a little imprecise result than not being able to use max FOV" But today I found out that FOV not only matter when calculating from game to game, but it matter in the game itself too, and that brought huge confusion so I am now here in hopes of finding answers. Whenever calculating things I usually use COD MW 2019 as a baseline because it has the "legacy" option which is 0% Monitor distance, it just feels right to use that for calculations. The problem is as followed: I never changed the FOV when calculating because it said that FOV doesn't affect the sensitivity so it was set on the default "80", tho I actually use 120 in-game, because as mentioned above: always max. And only now I noticed that when changing the FOV, it also changes the calculated results of the scope sens, and not only by a bit, but that change cuts the calculated results for higher zooms almost in half. This is the setting that I usually used with the default FOV, and this is what it calculates when using the actual 120 FOV that I have in game. Why would I need to change the Scope sens based on FOV when the legacy options should already be 0% on the scopes? and why do the Ironsights of the different weapon types all have a different calculated result in MW 2019 while they all share the same setting in the config file?

@MF_GAVIN Well only way to fix that problem is to lower your DPI when playing Warframe to 800 and then play with an ingame Sensitivity of 0, that would give you the same Ingame horizontal distance that you have in Windows

Edit: Part of the Problem was my HyperX Pulsfire Haste as this mouse has issues when it comes to the custom DPI setting and only works precisly with the preset DPI settings (400, 800, 1600) Working with 800 DPI fixed the same Issue I have with Warframe in other games that I haven't noticed when I used the custum DPI together with the calculator, as I never bothered to actually test it. Using the DPI Analyzer here has confirmed that using 1000 DPI has a 25% deviation while using 400, 800 or 1600 DPI has non. However, that still doesn't completely fixes the Issue in Warframe. With my new stats of 800DPI, 90 FOV and 4 Ingame-sens it calculates 25,5 cm for a 360°, but that is not a bit to much as it only requieres around 23-24cm for a 360°. Obviously not much of a deal but still a bit off which is weird

I tried it in mission and it still is off for me, set up the sensitivity to 7 with 300 DPS and 90 FOV to have a 25cm 360°, but it actually took around 30cm for a 360° in a mission. Faster then outside of a mission but weirdly not yet fully correct for me

@DPI WizardI excuse the ping but I just can't find a solution to this problem

Hello, According to the calculator, in order to do: a 360° turn with 27cm mouse movement 200 mouse DPI, 90 FOV I would need a ingame sense of 12. However, this doesn't appear to be true as with an sensitivy of 12 I would almost need roughly 50 cm for a 360 So here my question: Is the conversion simply wrong because warframe has updated something, or is there something I don't understart regrading 3. Person games?

yes I am aware but at this point I am just to much used to always use the highest FOV in a game that you can select. I know that this does mess with the convertion between games but that I think that I can allow myself that. Whenever I use a FOV that is below the maximum I just get a headache, so I won't change this. https://www.mouse-sensitivity.com/?share=a397cfc4619a1043f60b1741c908b15b

Well I sure now understand the mechanic behind Monitor Distance, which I am highly thankful for because it gives me a better understanding of aim overall, surely changing the way I will aim from now on, but as a result I lost track of how the calculator actually works, or kinda the "All" selection for the Aim. So, I basically want the Legacy option of CoD 2019 in Rainbow six siege, which is a 0% MDH. (And I also changed the ADSMouseMultiplierUnit from R6 itself to 0,01667 and the MouseSensitivityMultiplierUnit to 0,002230 as those were highly recommended to have a even finer adjustment) I go to the calculator and type in my stats that I have for CoD (7.7 Sens, 600DPI, 120FOV, Legacy mode, ADS Field of View: Affected, Aim: All) Then I want to convert to Rainbow Six Siege, select it and type in my stats (600 DPS, 0.01667 ADSMouseMultiplierUnit, 90FOV) And that is where I lost track of how things even work now. The calculator now calculated the MouseSensitivityMultiplierUnit with a preset Ingame-Sensitivity of 50, but I already have the MouseSensitivityMultiplierUnit, and want the Ingame Sensitivity to be calculated and/or what ADS-Sensitivy I would need for each scope inorder to achive MDH 0% So because of me now understanding Monitor Distance, I stopped understanding the calculator and I hope you can help out of the mess