I was curious in finding the best 3D -> 2D Conversion for Desktop and osu! etc.. I assumed this was 0% as this is the tangent and would reflect the 2d plane of the monitor, but then when trying other % matches around it the value is wildly different. It seems to converge to a value going down the range, but then at exactly 0% something different happens? Anyone know what's going on here?

This seems like a bug, I'll look into it right away!

Thought so, Thanks!

The unit (inches vs cm) got applied twice, so the results were altogether wrong with cm. Try again now, it should work as intended.

Yes, all working well. Also, is the standard 3D -> 2D 0% MM as this is the speed at the crosshair on the tangent 2d plane?

11 minutes ago, Skidushe said:

Yes, all working well. Also, is the standard 3D -> 2D 0% MM as this is the speed at the crosshair on the tangent 2d plane?

I personally think 0% on 3D -> 2D is too fast, it's opposite of 3D -> 3D where 0% is the slowest.

The perceived sensitivity for 2D will always be impossible to properly convert because you are comparing a crosshair to a cursor. The crosshair remains at the center of the screen but the cursor can be anywhere on the screen. Since sitting distance affects perceived sensitivity, we can conclude that the perceived sensitivity for 2D will feel faster at the center and slower at the edges, depending on the conversion method you use. Here is a diagram showing the difference in sitting distance for the center point on the monitor and at the edge:

Since 0% is matched at the center, it should and will feel the same at the crosshair and much slower as the cursor approaches the edge. 2D will also require a greater mouse movement distance to move to the edge of the monitor than higher FOV at lower match percentages.

Is it equivalent to FOV -> 0?

15 minutes ago, Skidushe said:

Is it equivalent to FOV -> 0?

Yeah it is essentially 0 FOV.