In the calculation I am not sure what the FOV units are in both games. This might sound stupid. Siege and Warframe both have a maximum FOV of 90, but using this conversion makes it so I have a slower sensitivity in Warframe. I am not sure if there is a way to fix this but I have been searching for a while and I cannot figure out how to calculate the exact same sensitivity for this. I intend on using my R6 sensitivity on all the other games I am playing right now like Deep Rock Galactic and it is not working there either. Please let me know what I might be doing wrong. Thank you.

Do you mean it's slower by the 2.4% as the values show (6.545 in R6 vs 6.7021 in Warframe), or is it significantly slower in the game and not matching the calculation?

Thank you for the reply. In siege I can drag my mouse from one end of the play area to the other and spin over 360 degrees twice, where if I use a 4 sensitivity with 90 fov in Warframe it does not even turn the full 720 degrees. So yes, it is a bit slower in Warframe. I did some testing on my own and found that about 8 sensitivity (if I am not mistaken) in Warframe does the same 720+ degrees spin as R6. I was just confused as to why the calculation resulted in such a drastic change and was wondering what I did wrong.

15 hours ago, OrngeMemes said:

Thank you for the reply. In siege I can drag my mouse from one end of the play area to the other and spin over 360 degrees twice, where if I use a 4 sensitivity with 90 fov in Warframe it does not even turn the full 720 degrees. So yes, it is a bit slower in Warframe. I did some testing on my own and found that about 8 sensitivity (if I am not mistaken) in Warframe does the same 720+ degrees spin as R6. I was just confused as to why the calculation resulted in such a drastic change and was wondering what I did wrong.

It sounds like your FOV in Warframe is changing from 90, it might be how the game works and changes you FOV based on buffs etc. Launch a training mission and see if it is correct there.

See this post, might it be the same issue?