all you're actually saying here is that you recommend scaling sensitivity proportionally to fov - which is nothing new, people have been doing this in their custom zoom scripts for donkey's years.

when changing dpi there is only one correct way in which to adjust your setup so that it remains the same overall - see here.

however when changing fov, there is more than one method by which you can take it into account (if you want to at all). see here.

since there's more than one way to factor in fov, it's more useful to keep the fov dependence as a separate issue, and let players decide which method they like the best (if any).

your 'absolute sens' measure isn't fully valid, since it only takes into account sens and dpi - there are many other variables which affect the 'real sens' and 'real accel' as i call them (click).


p.s.
some of your descriptions are wrong ("proportional to distance on the screen" being the worst offender). also the crosshair doesnt "move across the screen" like a 2D pointer does. it's more correct to think of the world *rotating* around the player, from the player's frame of reference.

Firstly, I hate accel.

I was just logging my thuoghts really.. it is a journal after all ;-)

I realised your "p.s." statement shortly after posting.. :/

"equal values will result in the same mouse movement moving the crosshair the same distance across the screen"
this is still true, but the "distance" on screen is not a simple multiple of the distance on your mat. I've been told that your FOV is more like a 2d projection of a parabola.

The reason i wanted to get involved with "distance on the screen" is because this is the most obvious way in which mouse movement could be translated to something more tangible.

the values for that are, however, still relevent as it is proportional, but not in a simple way.

thanks for the feedback btw :)