MacSquirrel_Jedi

Version 3.13 is out - Download link in video description:

- Added feature "Sens Multiplier" and "Y/X Ratio" from "RawAccel" driver. Allows you to set the sensitivity for each axis separately.
- Counter-Strike: Global Offensive renamed to: Counter-Strike 2

360°  

1 minute ago, epitome89 said:

Sweet! I must be blind: I don't see where you can edit the m-yaw value.

You can't. I manually adjust sens to receive m_yaw value

8 hours ago, epitome89 said:

How can I convert my 360 sensitivity in Overwatch (2.08 @96 FOV, 1920x1080) to Counter Strike (X.X @96.025575 FOV,  m_yaw 0.018333, 1600x1080)

CS:GO sens 0.7488

Both aspect of sensitivity 360° distance and Monitor distance is "same" for horizontal.

But vertical sensitivity is quicker about 16,8% for 360° and by rough average 1,4% (5,3% max. at edge of screen) for monitor distance in CS:GO

On 8/19/2023 at 10:04 PM, MacSquirrel_Jedi said:

Just like the "Real DPI", the rotation is individual for each mouse

This statement is wrong... I play with it again, and found that i made a mistake. The rotation deviation -2.92° is not caused by the mouse internally as i thought. But by the element i used for sliding the mouse in vertical direction. So I measured the rotation of the sensor relative to the shape of the mouse...  kill me! 

On 7/9/2023 at 9:30 PM, Vaccaria said:

The mouse forms the grip, if you change the sensor rotation through the software, the grip can also change

This is still valid and perfectly true  

On 7/9/2023 at 9:30 PM, Vaccaria said:

The mouse forms the grip, if you change the sensor rotation through the software, the grip can also change

I think you really found something !  

The rotation feature looks interesting :) I played with it today and it really has a big impact on the cursor movement. Just like the "Real DPI", the rotation is individual for each mouse. Which explains why someone still feels the difference with the new mouse, even if they set the same 360 distance as with the original mouse.

If I remove the rotation of my Zowie EC2-A mouse (-2.92°). When moving the mouse vertically, the cursor moves perfectly in the vertical axis. With almost no deviation. But if I only move the mouse with my wrist from left to right. The cursor moves at an angle. If I return the rotation to the original value (0°). And again move the mouse with my wrist from left to right. The cursor moves horizontally not at an angle. Which I think is the manufacturer's intention.

When I look at Zowie EC2-A sensor test. Rotation seems to be the reason for the deviation. However, it only seems to be active for the second (+x+y) and third quadrant (-x-y). Not for first (-x+y) and fourth (+x-y). Because the mouse is for right-handed people?

The expected deviation of the monitor distance in the video is not important. As long as we are using only one mouse. More important if we move the mouse repeatedly by the same distance and the cursor travels the same monitor distance each time with minimal deviation.

My mouse evolution has been quite a ride as well. I remember thinking I was old for Counter-Strike. And was thinking about quit playing. But then I bought Microsoft IE3.0 and was absolutely amazed. The mouse brought me back to the best  At the time I was playing with my arm placed on the table and making big movements (AWPer). After some time the mouse disappeared from market and there were no replacement. So i tried Zowie EC2-A but I immediately felt a little discomfort. But because I couldn't find anything better at the time of buy. I stick to it. When Microsoft re-released the mouse under Microsoft Pro IntelliMouse, I decided to give it a shot. But I had to give it back immediately as soon as I touched it. After some time, I got used to the Zowie EC2-A, which is smaller. It allows me to control the mouse with my fingers with much more space than Microsoft Pro/IE 3.0. Than one day I got a new computer with some office mouse at work. After some time of use. At home I realized how uncomfortable the Zowie EC2-A is compared to this office mouse... I've never felt anything like this before  Zowie EC2-A is a great mouse with perfect controls and I can 100% rely on it! But ergonomically, my hand tends to keep looking for a better position to hold the mouse, but never finds it. The mystery office mouse is a Dell MS111 and it seems to be perfect for my hand. The only problem is that I can't find any gaming mouse of this shape. Maybe some DIY project in future.

On 6/10/2023 at 2:10 AM, kizz76thebullet_alt said:

How do you know the formula for the lastconvertedsensitivity ?

When i was implementing PUBG to my utility. I was looking for some sources. And found this calculator https://jscalc.io/calc/reAvE153skIHHW5L . It's allowed to "Make a copy". So you can see a code.

On 6/10/2023 at 2:10 AM, kizz76thebullet_alt said:

Is it math you're doing or you have some source?

Both, but in this case it's pure copy. My math skills ends with a triangle.

=LOG((LastConvertedSensitivity/0,002)^50)

Works nicely ! 

Finally the vertical axis  I will definitely try it tomorrow

Hi, what I understood in the first part is that you basically take three FOV ranges (Hipfire, ADS, Scope) and for each you find a specific sensitivity that works best for you. If there are multiple weapons in this range with different FOVs. You use one sensitivity for all of them.

On 10/28/2022 at 6:02 PM, theferaltaint said:

I choose one of the three sniper scopes. Here I chose the 6x. I take that sensitivity and apply it to both the 8x and the 10x

If the game allows you to set the sensitivity for each optic separately, I see no reason to try to set one sensitivity for multiple optics. However if more optics share the same sensitivity in the game. Playing around with sensitivities to see what works best for the group can definitely be beneficial. But as with everything, it's always relative to the FOV you're most used to.

On 10/28/2022 at 6:02 PM, theferaltaint said:

But...Something Else Is Missing:

I was playing with the idea a few times, but each time I decided not to bother with it. And as you already said:

On 10/28/2022 at 6:02 PM, theferaltaint said:

When both you and the target are moving inconsistently, this adds even more randomness to the equation causing your mouse movement requirements to vary wildly.

Lets say you will compensate this, and know you have to shoot without moving, then you overshoot your opponent about this motion compensation. You can never know if the target will move to the left/right/up/down before you place a crosshair on it. 

Also this compensation is distance dependent. You will need to find some average distance of your fights. In the first image you can see that I placed the crosshair between the two corners at different distances. Then I quickly pressed and released the button to move left. And as you can see, the compensation is different for each corner.

I remembered one bug in Counter Strike 1.6 engine that we oldschool AWPers know about. This bug is present with any combination of settings you can think of  regardless of whether RawInput is on/off. This nicely illustrates that this topic has its meaning from both perspective of view (benefit/criticism). Because as you can see in the video. A slow movement of the mouse to the right is registered by the game when scoped. But not to the left.

This is also why I prefer manual verification over software. Because I want to be 100% sure how the system/game reflects the real world (long chain from sensor to photons). Not just software world.

2 hours ago, Quackerjack said:

Btw can you tell me why this happen?

 https://blurbusters.com/gsync/preview2/

15 hours ago, Chief Blur Buster said:

"I'm right too, and you're right too"

Maybe we will need something like GSync in mouse tracking -> MSync  

Another think is, that "mousefeel" is mostly local feel. No matter if you have a 10000 Hz monitor or mouse. All your mouse moves (delta moves) are distributed by let say 100 packets per second over internet. And when they arrive to your computer from your opponent. Game engine will smooth the delta difference. So it will look clean, but in reality it's "choppy". In CS 1.6, the command ex_interp "0.1" take care of this. And if you set it to 0 and your NET settings are low (cl_cmdrate "30"; cl_updaterate "20") it was unplayable. If you set ex_interp "0.1" it starts to feel clean. But input lag will be higher. 

So even when it will feel and look absolutely perfect on monitor. It can be just engine interpolation. But in the background, it can be much less precise that how it looks smooth on monitor.

Monitor distance - Dynamic

All aims (ADS/Scope) use the same base setting (convert from) 

Version 3.11

 - A stand-alone utility is introduced "MSJ_MSG" (Mouse sensitivity graph)
 - Single XY chart now covers all three modes. Previously each mode had a separate chart
 - Apex Legends: Maximum value for cl_fovScale is 1,642857 (set in profile.cfg and autoexec.cfg)
 - "Linux / Desktop (GNOME)" renamed to: "Linux / Desktop (Ubuntu 21.10)"

Version 3.12 is out - Download link

 - Fixed a problem with Tinch 2 thanks to YouTube comment from Cbuéno. Affected versions 3.1/3.11 
 - "Screen size" in the correction only serves as a note now. The display area is important.

@TheNoobPolice Good job. Another great stuff here ! This year is full of surprises   Nothing can stop us

22 hours ago, Lateralus said:

only using it to visualize the different settings

Hi i created new utility "MSG" exactly for this purpose. It's more user friendly than "custom option" in MSU

Hello guys,

I finished my new utility "Mouse sensitivity graph" you can compare with it up to 24x aims between each other in single graph  Download

Below are mouse sensitivity conversion methods compared in 23x aims at CoD: MW (2019) / Warzone. All aims (ADS/Scope) use the same base setting (convert from).

Vertical:

Horizontal:

I decided to move the "Mouse sensitivity graph" to standalone topic, to not create to much mess here  You can find it here

On 11/24/2021 at 2:13 AM, Skwuruhl said:

what?

 hello babe, i feel need to apologize to you, because i realized that some of my answers to you was a crap really  don't be mad at me, i'm just a man

On 7/16/2022 at 3:12 PM, makojunki said:

Necro coz i was looking for this answer too.

Mouse sensitivity is different on each user environment. I was playing around this in Ubuntu 21.10 GNOME 40. 

Hi im working on standalone utility  "mouse sensitivity graph" and just today it starting to get a shape. It will allow you to compare all aims in one graph (the monitor distances). Everyone will be able to compare their ideas.

Can you provide me a 360° distances for each aim of your or any game here with your method?

It looks interesting. I still didn't had the mood to express the formula. Mainly because I will have to completely rework my utility again. I also found out that I have a problem expressing functions... too long from school. Actually i think i never learned it  Also i have covid now  

18 hours ago, Skidushe said:

in effect 'Deriving' Jedi's Trick.

It should not be too much hard. You are looking for this:

The formula should contains the range (2x matching points on screen). So you will be able to define where you want to find the minimum error. For example 0-100% (Jedi's Trick) or 0-70% or wierd match like 20-70%. If the two match points will be the same like 50-50% it will turns to a standard monitor distance match to one point => Error = 0 

Hi @DPI Wizard

Can you reveal me a game, which has the most aims (ADS+Scope) on this site?

Best regards