20 minutes ago, kingdowning said:

Should I be doing it like this and copy the coefficient value it gives me along with the ADS values?

Or do I do it like this and leave my coefficient at 0, and then copy the ADS values it gives me?

The end result for the scopes is exactly the same for these two, the point of the suggested coefficient is to make the scope sensitivity as close as possible to 1. But since you have to set the scope sensitivity for each scope anyway it doesn't really matter.

https://www.mouse-sensitivity.com/?share=e2bf2a212774acb2de070f63a5e587a7

This is what I have tried to do with the Jedi Trick. Currently I found I really like the sensitivity of 9V 9H and ADS of 50 on siege with the 2.0x Scope. Is this the correct way to convert using the Jedi Trick to convert to Apex?

Edited January 22, 20224 yr by Magico.-

On 11/22/2021 at 7:06 AM, MacSquirrel_Jedi said:

Here comes the Jedi’s mouse trick:
Set the monitor distance to 100% MDV and note the 360° distance = 13,1815.
Set the monitor distance to     0% MDV and note the 360° distance = 11,3097.
Manually adjust the sensitivity so that the 360° distance matches the average of both values (13,1815 + 11,3097)/2 = 12,2456. By this you will receive the smallest deviation for all points. I will demonstrate it on a Square graphs (ratio 1:1).

This method looks easy. But it's practically 11 years of development behind it (With pauses of course). 

You can see the difference visually. But we can compare it also with numbers. I will use sum of absolute monitor distance deviations (SoD) for comparing with 0% MM. We don’t care if the deviation is positive or negative. We just need to know absolute deviation. If the SoD value is lower, it means that method has a lower deviation for all monitor distances. It will be not to much precise. Because we are comparing just 9x points on screen. But it’s enough to demonstrate the differences.

When you came up with the conditional expression that minimizes SoD, did you use integration or differentiation? Can you tell me how you arrived at that method?

I formulated the equation in my own way, but I could not solve the integral.

19 hours ago, a_nok said:

Can you tell me how you arrived at that method?

Hi, I'm not much skilled in math, I only remember the basics... The principle is already explained here. 

When i will integrate it to my calculator i can share it. But now I'm working on something else. 

For now i can provide you only the way how you can verify that it's working (by Sum of Deviations). Maybe during weekend. 

On 1/26/2022 at 11:56 PM, a_nok said:

Can you tell me how you arrived at that method?

In the first post, I explained what 100% MDV means. And that the mouse sensitivity is the same for only one point = one mouse distance = one monitor distance. All other mouse distances will result in a different monitor distance. And I was curious. How the rest of monitor distances are affected? And from 0% MDV? So I created 9x mouse distances in spreadsheet. To see how other monitor distances will be affected. And when I was manually changing sensitivity in steps of 0,05 from 0% to 100% MDV. I cloud visually see that at some sensitivity the deviation between points is much lower. But the problem was, how can I be sure that this sensitivity settings will give me lowest possible deviation for all monitor distances? In that time I didn't know how to build formula for that. So I did the simplest thing. I created in spreadsheet 4000x monitor distances and for each of them I received deviation. After that I converted this deviation to absolute deviation to be able count them all even if they will be negative. This gave me the Sum of the Deviations (SoD). After that I was able to find “magic” sensitivity settings that will give me the overall lowest possible deviation across whole screen. And you can be sure about that, because if you change sensitivity to anything else from that “magic” sensitivity the SoD will rise. Meaning overall deviation will rise. I made a short video with only 9x monitor distances. So you can see how I arrived to it:

Edited January 29, 20224 yr by MacSquirrel_Jedi

I'm here to say that this just might be the best post I have ever read and thank you Mr Jedi sir for doing this. This is truly incredible.

Edited February 2, 20224 yr by kingdowning

This sounds very interesting but I am confused about how to convert to this

I play on Warzone with 5 mouse sensitivity, 800 DPI, 120 FOV and 0% MDH

How do I go about converting it to your method?

8 hours ago, stalkerbronet said:

This sounds very interesting but I am confused about how to convert to this

I play on Warzone with 5 mouse sensitivity, 800 DPI, 120 FOV and 0% MDH

How do I go about converting it to your method?

https://www.mouse-sensitivity.com/?share=c28d2c651e1018a97cb9faf575f83354

smth like this, although that crazy high fisheye fov bites you on this

Edited March 12, 20224 yr by fortunate reee

16 minutes ago, fortunate reee said:

https://www.mouse-sensitivity.com/?share=c28d2c651e1018a97cb9faf575f83354

smth like this, although that crazy high fisheye fov bites you on this

Thanks, what do you mean by fov bites you?

21 minutes ago, stalkerbronet said:

Thanks, what do you mean by fov bites you?

windows matching with "high" dpi + high fov always ends up giving you unreasonable high hipfire 360s

6 minutes ago, fortunate reee said:

windows matching with "high" dpi + high fov always ends up giving you unreasonable high hipfire 360s

oh i dont need windows matching, i just wanted to try jedi's sensitivity in game

im fine with having different sens in windows and in game

1 hour ago, fortunate reee said:

windows matching with "high" dpi + high fov always ends up giving you unreasonable high hipfire 360s

It seems like no matter what numbers I input its always gives 1.21 monitor distance  coefficient 

is the calculator working properly?

1 hour ago, stalkerbronet said:

It seems like no matter what numbers I input its always gives 1.21 monitor distance  coefficient 

is the calculator working properly?

The monitor distance used for Jedi's Trick is only based on your resolution and just a close approximation. It doesn't not directly correlate with monitor distance since it's dynamic and based on input and output FOV.

In other words, the monitor distance suggested is what you should use so the multipliers are reasonably close to 1.

On 3/12/2022 at 2:26 AM, stalkerbronet said:

I play on Warzone with 5 mouse sensitivity, 800 DPI, 120 FOV and 0% MDH

Please next time share your exact settings by clicking on . I left the rest at default.

Jedi's Trick (Vertical) - Based on your Hipfire settings: 360° distance is same for each Aim - Example.

Multiplier for "Sensitivity 2"
0	0.61	AIM
1.02327	0.99977	Handgun Iron Sight / Reflex
1.03135	0.99987	Shotgun Iron Sight / Reflex
1.04236	1.00015	SMG Iron Sight / Reflex
1.05810	1.00086	AR & LMG Iron Sight / Reflex
1.06360	1.00119	Marksman Rifle Iron Sight / Reflex
1.08180	1.00261	Holo Sights
1.08728	1.00313	2.5X
1.09059	1.00347	2.75X
1.09364	1.00379	2.8X
1.09507	1.00395	3.0X
1.10907	1.00566	3.25X
1.10993	1.00578	3.5X
1.11111	1.00594	4.0X
1.11180	1.00603	4.4X
1.11213	1.00607	5.0X
1.11245	1.00613	5.5X (Dragunov)
1.11274	1.00616	5.5X (Variable Zoom Scope)
1.11302	1.00620	6.1X
1.11400	1.00634	8.0X
1.11458	1.00642	10.0X (AX-50 Default Scope)
1.11488	1.00646	12.1X
1.11515	1.00650	12.6X

 I filled ADS settings to my utility so you can check the graphs - Download link

Edited March 13, 20224 yr by MacSquirrel_Jedi

3 hours ago, MacSquirrel_Jedi said:

Please next time share your exact settings by clicking on . I left the rest at default. "Sensitivity 2" = 0.

Jedi's Trick (Vertical) - Based on your Hipfire settings:

Multiplier    Aim
1.02327     Handgun Iron Sight / Reflex 
1.03135     Shotgun Iron Sight / Reflex 
1.04236     SMG Iron Sight / Reflex 
1.05810     AR & LMG Iron Sight / Reflex 
1.06360     Marksman Rifle Iron Sight / Reflex
1.08180     Holo Sights 
1.08728     2.5X 
1.09059     2.75X 
1.09364     2.8X 
1.09507     3.0X 
1.10907     3.25X 
1.10993     3.5X 
1.11111     4.0X 
1.11180     4.4X 
1.11213     5.0X 
1.11245     5.5X (Dragunov) 
1.11274     5.5X (Variable Zoom Scope) 
1.11302     6.1X 
1.11400     8.0X 
1.11458     10.0X (AX-50 Default Scope)
1.11488     12.1X
1.11515     12.6X

I filled ADS settings to my utility so you can check the graphs - Download link

Okay now I am even more confused, I thought this trick is to match monitor distance, not each scope individually

1 hour ago, stalkerbronet said:

Okay now I am even more confused, I thought this trick is to match monitor distance, not each scope individually

Monitor distance is just that, monitor distance set to a specific value. Jedi's Trick is the average between 0% and 100% monitor distance, so it will vary depending on your settings and the scopes.

10 hours ago, DPI Wizard said:

Monitor distance is just that, monitor distance set to a specific value. Jedi's Trick is the average between 0% and 100% monitor distance, so it will vary depending on your settings and the scopes.

The average between 0% and 100% MDV in my settings is 61% MDV so it would be correct to set monitor distance coefficient to 0.61?

3 hours ago, stalkerbronet said:

so it would be correct to set monitor distance coefficient to 0.61?

There are many paths that lead to Rome. I updated my previous post for your 0.61. Including download link.

Edited March 13, 20224 yr by MacSquirrel_Jedi

51 minutes ago, MacSquirrel_Jedi said:

There are many paths that lead to Rome. I updated my previous post for your 0.61. Including download link.

Thank you! Seems like 0.61 is better because less variety between scopes, they all land very close to 1 so I'll do that

The original idea behind the current Jedi's Trick implementation was that it does horizontal and vertical at the same time. This obviously only works if the game supports vertical sensitivity, and it will only be 100% correct for hipfire.

So I'll add a vertical option in the next update.

I'm adding the procedure how we can manually apply the Jedi's Trick more comfortably for 3D game.

Jedi's Trick (Vertical) - Hipfire to Scope example:
1) Convert from: Choose your game and fill your settings for Hipfire
2) Convert to: Choose your Aim (Zoomed 1: AWP, SSG 08, G3SG1, SCAR-20)
3) Set MDV to 0% and note the 360° distance (33.6445 inches)
4) Set MDV to 100% and note the 360° distance (29.5703 inches)
5) Calculate average of both values (33.6445 + 29.5703)/2 = 31,6074
6) In settings switch ADS / Scope method to 360° distance
7) In settings switch Convert from sensitivity to distance and fill the 360° distance to 31,6074
8 ) Result is: zoom_sensitivity_ratio_mouse "0.871712"
9) Repeat above steps for each Aim (ADS/Scope)

From last time. By these steps the procedure is free from manually changing MDV/H% until it match 360° distance (31,6074) => MDV 65,4265%

5 hours ago, HosungKun said:

I think I need not only vertical to vertical, but also custom monitor distance range feature of JEDI's trick(average between 0 to 70 e.g)

The procedure is same. In the 4) step you are specifying the range. Just use 70% instead of 100%.

Edited March 20, 20224 yr by MacSquirrel_Jedi

Hey guys maybe jedi you can tell me this since i have been thinking a lot. i really like the sens im getting with this. BUT, i was wondering if it wouldnt be better to use jedis trick on ads, scopes and 360 distance for hip fire? what do you think would be best? becasue hip fire should be the same if i convert lets say from valorant to rainbow. 40 cm 360 should be the same in both games but when it comes to scopes you would use your trick then to match it to the 40cm. I dont know if im clear with my question. Just wanna know why you would choose to use your trick and not 360 match on hip fire since with your trick it gives me a lot of variance on the 360 distance 40 cm to 33cm with your trick. Thanks

19 hours ago, davixx500 said:

Hey guys maybe jedi you can tell me this since i have been thinking a lot. i really like the sens im getting with this. BUT, i was wondering if it wouldnt be better to use jedis trick on ads, scopes and 360 distance for hip fire? what do you think would be best? becasue hip fire should be the same if i convert lets say from valorant to rainbow. 40 cm 360 should be the same in both games but when it comes to scopes you would use your trick then to match it to the 40cm. I dont know if im clear with my question. Just wanna know why you would choose to use your trick and not 360 match on hip fire since with your trick it gives me a lot of variance on the 360 distance 40 cm to 33cm with your trick. Thanks

matching the 360 distance is my go to for hipfire only since it doesnt work for scoeps with zoom, but the fov of r6 tends to be higher than the fov of valorant so id always suggest matching either the fov or using

and creating a custom res with black bars making your 360distance actually feel identical.

as far as scopes go you dotn match the distance since it gets overly  wiggly and uncrontrollable, you could consider matchign 0% mdh/ mdv ( r6)or mdh 100%mdh/ mdv 178%( val) which would be the respective games defautl ads scaling

2 hours ago, fortunate reee said:

matching the 360 distance is my go to for hipfire only since it doesnt work for scoeps with zoom, but the fov of r6 tends to be higher than the fov of valorant so id always suggest matching either the fov or using

and creating a custom res with black bars making your 360distance actually feel identical.

as far as scopes go you dotn match the distance since it gets overly  wiggly and uncrontrollable, you could consider matchign 0% mdh/ mdv ( r6)or mdh 100%mdh/ mdv 178%( val) which would be the respective games defautl ads scaling

what is the default monitor match used in csgo ? if i wanted to match the feeling of how cs does it. And you basically use 360 for hipfire and 0% mdh for everything else and then a custom res with focal lenght

2 hours ago, davixx500 said:

what is the default monitor match used in csgo ?

MDV 133.3333%.