There is a bug in Aim Lab where if the input source is set to Raw Input, plugged in controllers can interfere with the mouse input. If you don't do this, Aim Lab will be stretched (like any other game), and it won't match Valorant which will be normal due to their quirky system.Ģ. Aim Lab can replicate this by setting the Display Stretching Ratio to your native aspect ratio. They squish it so that when you stretch it back to fullscreen, it results in a normal image (no stretched enemies for competitive purposes). Valorant forces a 103 field of view for your native resolution, squishing the image for custom resolutions with lower aspect ratios. If the assumptions are correct, then the test should make the crosshair turn one full revolution, ending up exactly where we started, and if both the fov and sensitivity is correct, then turning 51.5 degrees will turn to the edge of the screen.ġ. If any assumptions are wrong, then sending this amount of mouse movements to the game will result in a completely random rotation. To test this, we can turn 51.5 degrees (half of 103), to move the crosshair from the location at the centre of the screen, to the location at the edge of the screen. Valorants FOV is also assumed to be 103 degrees. Since it is near impossible to move 32.6571 centimetres without human-error, I will use the scripting feature inside Logitech G HUB to send the mouse movements to the game, using MoveMouseRelative(x, y).Ħ. If your mouse is 400 DPI, then there is a mouse movement every time the mouse is moved 1/400th of an inch.Ĥ. If Valorants sensitivity is set to 1, then there is 0.07 degrees turned per mouse movement.ģ. Valorants sensitivity is assumed to be Mouse Sensitivity * 0.07 = Degrees turned per mouse movement.Ģ.

I tested both the sensitivity and the field of view.ġ.

Valorant sens converter to aim lab