Leaderboard

already posted this on another thread just now its about apex which just so happens to default to 1.0 which also is the new 50 ads on all scopes in siege ( ie 0% mdh/mdv) others might call it focal length different names same effect ---------------------------------------------------------------------------- what those pros keep doing is or 1.3 ads which is actually purely based on the distance unfortunately this is pretty inconsistent since it just ignores the fov changes, trying to replicate the 360 distance and calling it "1:1" is something that is actually very common with those who haven't actually done their research. ( work "alright" for low zoom scopes and is close to useless when using higher magnifications) -> typically ends up wit them adamantly defending this method until they figure out that they aren't actually consistent just for them to either stumble up on this site or using a monitor seemingly random monitor distance value % . pros aren't pros because of their settings, they are pros because they are either talented or have put in lots and lots of hours into a game and thus can adapt to horrible settings easily making it look "good " when in reality you'd likely be better of sticking to 1.0 when you aren't using 0%(which gives you the same result for vertical and hor) id suggest mentioning mdh or mdv depending on what you are using since the actual results can vary. i am currently sticking to a 360 distance i like for hipfire 1.269000 @800cpi (this gives you a round number in games like cod ) paired with 0% ads for most games that support 0% inputs like siege, apex, cod and i would consider myself the most consistent i have ever been which to be fair might as well be based on the fact that i have played fps games for a long time and i wouldn't actually say that a thing like muscle memory in the sense its being used in the gaming realm exists. the more you switch sens ( 360 distance/fov ) the less it actually impacts you over time -------------------------------------------------------------------------- and yes id suggest thinking of kovaaks as less of a game specific aim trainer and more of a trainer for hand eye coordination / motor control

Oh ! Now I get it thank you !

It's only the same if you also switch FOV Measurement from Vertical 1:1 to Apex/Quake/Src/4:3 in the game.

For Vertical 1:1 yes

The only difference here is how the game measures FOV and what value you have to enter as your config FOV. The end result of the two settings (Apex/Quake/Src/4:3 at 76.329602 and Vertical 1:1 at 61.034115) is exactly the same as you can see in the Actual HFOV/VFOV in the output.

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).

With DAHM I'm able to set the sensitivity to any value I want, is there any way to override the calculator to give a result for a sensitivity outside of the set boundaries? Edit: Upon further testing, I found that negative sensitivities invert the controls. DAHM, however, handles sensitivity differently, and I'd suggest you add an option for it for those who want more precise control over their sensitivity.

I don't know what setting you have potentially messed up, but the Valorant and Krunker sensitivity in that output is exactly the same: