I've considered this, but there's a few issues with doing it, mainly that the FOV range of games varies a lot. So if the calculator automatically uses an invalid FOV, that will affect sensitivity. I'm currently going through every game in the calculator to verify them and update the notes to more standardized text. Perhaps if I also update with max/min FOV this functions can be implemented.