Leaderboard

I've updated it now. The slider has notches so you can count them manually to set the FOV you want.

Updated

I want to add something about the sensitivity conversion way of MDH(MDV).The monitor distance and the corresponding mouse movement distance are involved in MDH (MDV),but there is one more parameter that is ignored,that's the speed at which a point on the display moves. Analogous to speed, time, and displacement, the moving distance of the mouse is time,the distance of the monitor is displacement,The speed at which a point is moving is the velocity.First, the calculation formula for the distance of the display can be obtained,then the expression for the instantaneous velocity of movement at this point is the derivative of the displacement.In addition to the monitor distance, there is another kind of displacement expression,which is the sum of the arc length corresponding to a certain point moving a certain distance(denoted as l(arc)).Here is an explanation of why it is a certain point on the display, not the center point,because the center point is always at the center, of course this is nonsense, but because it is always at the center,when the sensitivity is determined, the speed of the center point remains unchanged.What we are going to discuss is the speed of each point on the display. Therefore,we cannot only take the center point (or front sight) as the analysis object.Another important point is that in the process of aiming, we should pay more attention to the target,rather than the front sight at the center point, so the target point is more valuable for discussion.Another point is that my analysis here is based on HFOV. Of course, there is no problem with VFOV, but when it is applied to a specific game, it is necessary to distinguish between HFOV and VFOV. I have made this mistake before.If it is not calculated in a specific game, there is no need to divide HFOV and VFOV, there is no difference between the two,and it can be considered as just two FOVs of different sizes. X means that the front sight rotates a certain angle, and the mouse moves the distance. C means the distance that the mouse moves when the front sight rotates for one circle. In this way, the MDH used by the website is obtained under the condition that the display distance is equal and the corresponding mouse movement distance is equal.There are two other cases. The first case is the ratio of sensitivity obtained when the display distance is equal and the corresponding target point moving speed is equal.The second case is obtained when the moving speed of the target point is equal and the corresponding mouse moving distance is equal. Sensitivity Ratio.According to my own calculations, the calculated results in the second case will make the sensitivity ratio too large,and the monitor distance cannot be taken from 0% to 100%, so use the method currently used by the website and the first method.In addition, the idea of MDD is very good, so I will borrow the method of TheNoobPolice,add the idea of dynamic monitor distance.In fact, a in the formula will change with the value of zoomfov.The final formula is in the following website, and I only learned about it because of TheNoobPolice, I am really grateful to him. https://www.desmos.com/calculator/tkzyfeh3cd? Because I am Chinese, my English is not good, so I can only use a translator, so please forgive me if I have trouble reading, thank you.

Yeah, the challenge is that it's not possible to do mathematically, it has to be done programmatically. So it basically has to iterate through tens of thousands of percent/power/scale combinations to find the best ones across all aims. I will make it so it tests both ADS alone, scope alone, and both combined. This is the work in progress, when it's done it will be in a nicer layout for the result, and have the ability to click the conversion you want to use

The Optimum Tech video on DPI latency / input lag used a flawed methodology to test movement latency as there was no normalised output distance for each tested input distance (DPI’s). He measured movement resolution, NOT latency. There is no input lag or latency effect at all for different DPI values. Imagine Usain Bolt was sprinting against a 5 year old and they both set off at exactly the same time. If we apply the same testing philosophy that we see in that video, we would only measure the time until the first foot landed on the ground, and because of their tiny little legs and narrow stride pattern, we would therefore conclude the 5 year old was the faster runner. Suffice to say, it’s not the time until first point of data, but the time to a significant target location to define “input latency” i.e input to “something”. Of course, a higher DPI would make “some first movement” faster than a low DPI at the same hand speed, as that is the definition of DPI, but presuming you have the same effective sensitivity in a game between DPI settings (i.e the same 360 distance) then the distance turned in-game is smaller for that first movement, so additional inputs (which take additional time!) would be required to turn the same distance as only one input would do from the lower DPI mouse. Once the minuscule amount of time has passed for the lower DPI mouse to send data, it updates to exactly the same position as the higher DPI mouse at exactly the same time. Saying there is a different “sensor lag” or "latency" for the natural effect of DPI is misleading - the path the data takes to your pc is exactly the same. In other words, there is no difference in input lag for different DPI values. What was tested is easily calculable with simple math and isn't required to test in this manner. If you could set the DPI to "1", and moved your hand at 1 inch per second, you would see 1000ms pass before the count was sent and their measuring devices registered some movement. This does not mean there is 1 second latency in the mouse input.