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?

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

I checked the game now, and it is still correct.

But this game is a bit quirky, the calculated sensitivity is correct for when you jump into a mission. Onboard your ship etc. the FOV is different which affects the sensitivity.

Are you testing in a mission?

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

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