Godot mouse sensitivity calculations

Help
1

Godot Version

4.2.2

Question

Hi, I’m creating a project that could be considered an aim-trainer.

For such a tool it would make sense to have parity between the mouse sensitivity in Godot and the mouse sensitivity in other games, so that skills you practice in the aim-trainer can be transferred between the two applications, or simply to just be able to use a familiar mouse sensitivity number without having to go and translate it.

Ideally, I’d like to be able to have the same mouse sensitivity value in this, and say, a Source Engine game like Counter-Strike.

To my knowledge, the mouse sensitivity as a factor in Godot is a rather small number. I’m applying mouse movement by what seems to be the standard method - rotating the camera axes by the relative event * mouse sensitivity variable.

I’m not really sure if it’s right to ask here since it’s pretty much a generic maths question, but the factors are related to this engine, so I think it makes sense to some degree: does anyone know of a way to translate the Godot mouse sensitivity variable to the Source Engine variable?

1 Like
2

I recently ran into the same exact problem.
TLDR: multiply your CS sensitivity by 0.00038397243458548043006658879114174 to get the radians turned per screen_relative unit

For InputEventMouseMotion you have a [screen_relative](https://docs.godotengine.org/en/stable/classes/class_inputeventmousemotion.html#class-inputeventmousemotion-property-screen-relative) field (as the godot docs suggest, do not use the relative field but the screen relative field for fps games when you want to rotate the camera) which is a vector with X and Y components, I believe these components represent how many “dots” the mouse read in the corresponding direction.

So with an 800 dpi (dots per inch) mouse if you move 1 inch horizontally you should end up with 800 relative X.

Normally you are using this event to rotate the camera a certain number of radians, so you’ll need to know how many dots the mouse travels to do 1 full 360 turn in CS.

mouse-sensitivity.com is a website where you can convert your sensitivity from one game to another, using this website you can figure out that at 800dpi you need to do 20.4545 inches of horizontal motion to do a full 360, or in other words you need to move 20.4545 * 800 dots which is 16,363.6. You don’t really need to do this calculation however, if you enter 1 dpi as your dpi in mouse-sensitivity you can find out what 1.0 sens is in terms of dots, the number is usually also more accurate this way.

Inputting 1.0 sens and 1 dpi 16,363.6364 which is exactly how many dots you need input to do 1 360 turn in CS 2.

To get how many radians you should rotate your camera per dot you can just do 2pi(this is a 360 turn)/(dots per 360) so in this case that is 0.00038397243458548043006658879114174, I’ll call this number the sens multiplier.

Now you can have your player input a sensitivity like 1.6 and multiply it by that sens multiplier and you will exactly the same number of cm/360 as you would in csgo.

I’m not entirely sure that screen_relative X and Y represent dots moved (because I can’t find anything that actually says this but I must assume it must mean a dot because that is the smallest unit of measurement for mouse motion) but from my rudimentary testing I find that the sensitivity I get feels the same as the games I play (e.g. Apex) and I turn roughly the same amount of degrees over 50cm.

Also using this method you can also implement a cm/360 → CS sensitivity converter similar to what Kovaaks.