hellothere

 If you want to match physical monitor distance so moving the crosshair e.g. 5 inches is the same on a 19" and 30" monitor, that can be done. But I'm not quite sure this is useful?

Yes that's what I need. To 

The new version is live now!

can't change the monitor size of the second game, I wanna match sensitivities for different screen sizes as well =)

I want to be able to edit the monitor size in the second 'game' so i can basically match my sensitivity for different monitor sizes. Thanks!

I'll try to get it done by the end of June, but I'm not sure how long it will take.

 

I'll update you when I get a feeling on how long it will take

Thank you very much! 

 What I'm planning is an option in the calculator to specify what on-screen distance you want matched.

Do you have an estimated date?

"Are the CS:GO professionals wrong playing with 400dpi? Is that just a big placebo with todays modern mice?"

Good Question! It's something i wondered to, because if you do research the most people will say and show to you that higher dpi is better, because it's more smoother, which is correct! And because of that i used 3200dpi and 0.3 ingame sensitivity (CS:GO). But... recently i tried to play with 400dpi and 2.4 ingame sensitivity to test it myself, cause i also wondered why pros are using this. And there is infact a difference! 400dpi feels a bit more jittery and not as smooth, but it also feels more snappier and it actually felt like my aim was better. So Pixel Skipping can actualy benefit you and from now on i'll use 400dpi. The only downside is that i have to constantly switch between dpi, cause 400 is much too slow for windows use. But don't take my word for granted and test it yourself! [/size]

 

It being more snappy makes more sense actually. But at distances it may be harder to finely adjust.

This mode matches the sensitivity like this:

If you want to target an object at the edge of your screen, you will have to move the mouse the exact same distance as moving from the center of the screen to the edge in Windows. This means that the calculator must account for FOV for all games.

Okay so what if you want to match a lower distance from the center of the crosshair to a closer point. So say if you want the linear sensitivity on windows desktop to match the sensitivity of CSGO in a 90 FOV world 5cm away from the crosshair. I did personal tests using a ruler etc. and found out that if you want to match windows sensitivity with small movements on CSGO, the sensitivity would need to be 4. If you want to match bigger movements, the sensitivity gradually decreases. Could you maybe add a command or box to change the distance on the game of which to match the linear sensitivity? Or could you give me the formula you use to work this out. Thank you! 

I'll try to make a video showing the different methods in action, but I gotta figure out a good way to actually show the result and how pixel accurate it is. And maybe get some youtube personality to voice it 

Is this out yet?

It's always on now

oh thanks! 

Enable advanced mode on the top right corner, and you can enter the resolution you use, from that the AR will be calculated.

 

The calculator reads your current desktop resolution and fills it in, so 16:9 is already set in the screenshot, but you must leave the FOV default (90) for CS:GO, as the configured FOV is used for calculations, not the actually displayed FOV

 I know this wont effect it, but since the 4.0 update was released, there is no option for advanced mode.

I did the test with Zowie AM, both do have the same sensor, though different DPI. I used 1150 in the test with 1.25 sensitivity which should be the exact same as 1.8 and 800 dpi according to sensitivity calculator. These mice are known for not having drivers at all, so that is unlikely the case. I can't think of any windows/ingame settings that could cause this.

When you turn in a 3D world you need to go in a straight line to get a 360 measurement equal to the cm/360^ because arches cover more distance. 

Basically you can test this by using fov_cs_debug and putting it on 1 and then you can lower your sens until there is no jumping. This will make it so that there is smooth movement however when you are on cs_debug 90 which is default, this skipping wont be visible. By a rule of thumb, A sensitivity below 1 would remove pixel skipping I think. But a sensitivity of like 2 or 3 would not really be that noticeable.

Where the point is depends on several factors like resolution, FOV, 360 distance and game engine. It's hard to say where the benefit of high DPI stops for each scenario, but in my opinion you should have at least pixel accurate sensitivity.

 

By that I mean 1 count from the mouse moves the crosshair 1 pixel.  Maybe 10 counts pr pixel is better, but 100 counts is probably overkill.

What would this be for csgo? (I use 1080p does res matter?) I have a g502. Also is the g502 really native at 12000 dpi and most responsive at that dpi?

Since in a game you are moving around an axis with a spherical FOV, the calculation is only accurate for one distance. In other words, while the movement in Windows is 100% linear, it is not in-game. If you just measured say 10 cm of the screen, you will end up moving too short. What I'm planning is an option in the calculator to specify what on-screen distance you want matched.

 

The calculator matches the sensitivity for half a screen-width. In other words, if you measure the mouse movement distance in Windows from exactly the middle of the screen to the edge, you should get the exact same distance as moving the cross-hair to the object on the edge of screen in-game (and obviously remember to turn off acceleration in Windows if it is on )

Thanks man. I am happy to know that the distance feature is going to come. Thanks man. Makes sense.

Regarding this, I have tested measuring a certain distance by drawing on a lined piece of paper a straight line and followed that line and saw how far it would move (using very low dpi) and then checked how far it would move in CSGO. With the 2.515630 calculated by the calculators I have found that the distance moved on screen is lower in csgo than on windows. 2.515630 seems to be 70% of what the windows sensitivity is. I have therefore done 2.515630/7*10 and got around 3.59 and then lowered it to 3.5. This is much closer to the actual distance moved by the mouse cursor on windows to CSGO being 1:1. Please respond to this. Thanks.

After reading:

https://www.reddit.com/r/GlobalOffensive/comments/43urd4/why_0818933027098955175_is_the_best_zoom/

https://www.reddit.com/r/GlobalOffensive/comments/3q3cpm/you_are_using_the_wrong_zoom_sensitivity/

etc. 

I am confused as to what is the correct zoom sensitivity/ratio in order to match the normal sensitivity.

In the first reddit post it says this "EDIT3: When I'm saying sensitivity, I am not refering to cm/360° but the distance your crosshair travels on your screen relative to the amout you moved your mouse. The only thing that matters when aiming." at the bottom of the thread. So I am doubting the 360/cm method that you use.

Aside from that. Can you calculate what the correct zoom sensitivity should be? Both the x1 zoom sens and x2 as well as the AUG zoom and SSG53, scout etc. Thanks.

Thanks for this! Have you tested MARC mouse fix though? Should I use that?

You can check that the default value is 90 if you start a private game and enable cheats. Setting "fov_cs_debug 0" (which is default) and "fov_cs_debug 90" should yield the same FOV. The actual FOV you are seeing on your screen does indeed change with resolution change (e.g. at 16:9 it is 106.26), but the configured FOV is still 90, and this is the value that is important for the calculations [/quotes

 

 

If it has an fov of 106.26 why is it the 90 that matters?

Indeed, maybe I can add it as a feature, I'll look into it, but it is as easy as DPI/OldHorizontalRes*NewHorizontalRes=NewDPI

I think what the situation is that if I keep the sensitivity which the calculator gives and then change the windows resolution it keeps the distance to degree rotation the same. What I think is going on here and i'm trying to figure this out is that the mouse distance moved when having the same DPI on a lower resolution on windows desktop. It moves further on the screen than it would on a higher. What I am confused about is whether when you change to fullscreen mode in CSGO in 1280x720 whilst having a desktop resolution of 1920x1080 resolution is whether the mouse pointer in the buy menu on csgo. Does the distance moved on screen in the 1280x720 resolution of the game in full screen match the distance that is moved on desktop.

I actually just tested this and it came to be that the distance that I moved on the CSGO in 1280x720 with 1920x1080 windows resolution. The distance to move from one side of the screen to the other was more on the desktop itself than the game. This means that my menu game sensitivity is not the same as my menu sensitivity and at the same time being the same as my windows sensitivity. The only way to achieve this would be to make the windows and game resolution the same with the correct in game sensitivity given by your calculator

Converting sensitivity of windows resolution to another windows resolution. Is this possible? 

Why can't we change windows sensitivity in CSGO converter? Thanks

When you use the desktop calculator, the sensitivity is calculated based on the Windows settings.

 

So in Windows:

1280x720 and 500 DPI = 2.56 inches to move the mouse from edge to edge (1280/500)

1920x1080 and 500 DPI = 3.84 inches to move the mouse from edge to edge (1920/500)

 

When you convert these two inputs to 1280x720 @500 DPI in CS:GO, you will get different results since the input distance is different.

 

Makes sense?

 

Also, it's the game resolution that is important, regardless of windowed or fullscreen.

Thank you very much. So would there be a way to match the sensitivity when changing your windows resolution? Will this matched sensitivity be the distance in relation to 360 degrees rotation or will it be sensitivity in relation to windows resolution. Thanks.

Okay so basically:

http://prntscr.com/7f21vf the sensitivity for 1920 x 1080 is 2.5156

http://prntscr.com/7f22mn but the sensitivity for 1280 x 720 is  3.7734

I'm talking about full screen mode. Notice the game resolution is 1280 x 720 on both so I do not see why the 360 rotation should change if the DPI is kept the same and the in game resolution is kept the same when running full screen.

Another question: what would happen if a 1280 x 720 window was running on a 1920 x 1080 resolution screen. Would the sensitivity/360 rotation match for if it was full screen?

Thanks.

That's not necessary

So sensitivity on different resolutions are the same even in windowed mode such as if there is a 1280x720 window on 1080p would the sensitivity change from 1920x1080 full screen to the 1280x720 windowed? Thanks

You need to enter the value in the config file rather than doing it in-game. The in-game slider is not very precise

One question also. I know it's aside from this topic however on csgo will the sensitivity change if you are in windowed mode such as 1280x720 windowed on fullscreen etc. Will there be a option for fullscreen? I don't know if it needs one.

You need to enter the value in the config file rather than doing it in-game. The in-game slider is not very precise

Oh thank you very much!