Leaderboard

I found the issue now, if the sensitivity set in the registry is outside of the range of the in-game slider, this will happen. Tested it now and increased the max sensitivity to 10

Are you good with trigonometry, Mr BLC? Edit: wow ok I misread your post. I think you knew all this already, and it doesn't answer your question. sorry TL;DR: you want to match the distance your reticle moves when you move your mouse, and not the amount of degrees you rotate when you move your mouse. This is "MDV 0%" or "MDH 0%" Picture your monitor from above - a straight line representing the monitor's top edge. Now create an isosceles triangle with your monitor's top edge as the base. Look at the peak of your triangle - the inside angle of the peak is your FOV Try drawing the isosceles triangle with different FOV/angle values. Notice that at high FOVs, the triangle is short and fat, whereas with small FOVs, the triangle is tall and skinny. Now imagine what happens to your triangle as you look from left to right in a video game - the triangle rotates around its peak, as if you impaled the peak with a stick and then spun the triangle around. Notice that if you rotate a large FOV triangle, the distance covered by its base (your monitor) is much smaller than that covered by a small FOV triangle: Drawing is kinda shit so its hard to tell.... This makes sense intuitively - say a disc 1 foot in diameter makes a rotation once every minute. The outer edge is not moving very quickly. Now picture a disc 1 kilometer in diameter making a rotation every minute - the degrees per second (angular speed) is the same, but the distance covered by the outer edge is much, much faster for the larger disc. This is what sensitivity is in video games: not the angular speed of rotation, but the speed of the outer edge. This is why you want your cm/360 to increase as your FOV drops - to match the distance your monitor covers per cm of mouse movement. ======================================================================================================= The problem is, its not actually possible to match monitor distance precisely. Notice for your isosceles triangle, that the center of your monitor is closer to you than the edges are: This means the center of your screen actually moves much slower than the edges do at high FOVs. This is not the case for low FOVs: That is, different parts of your screen have different sensitivities, and this sensitivity discrepancy changes at every FOV. Therefore, it is impossible to match your sensitivity across all FOVs. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ So, while its impossible to perfectly match sensitivity, it is possible to match part of your sensitivity. What most people opt for, and what Fortunate Ree and I both recommend, is to match the sensitivity of your reticle across all sensitivities - the speed of your reticle will be the same at every zoom level. This is known as "MDV 0%" or "MDH 0%" (it takes the same amount of movement to move your screen 0% of the way vertically/horizontally).