Share this post

Link to post

Share on other sites

Recently I've changed monitor to Ultrawide, and honestly I don't know how properly convert sensitivity to new ratio

After converting from CGSO some time ago, I based my main sensitivity "feeling" around Ironsight/Holo in RS - this is the same distance as in Hipfire CSGO.
Based on this I have Hipfire about 33 cm/360, IronSight 54 cm and ACOG 94 cm

I got used to it and would like to have the same on my new monitor

As you can see below, I was trying to convert my Ironsight/Holo, but as a result I get different cm/360 distance, and I think it should be the same regardless of monitor ratio. I am making some logical error ,but I am not sure where.

Share this post

Link to post

Share on other sites

Recently I've changed monitor to Ultrawide, and honestly I don't know how properly convert sensitivity to new ratio

After converting from CGSO some time ago, I based my main sensitivity "feeling" around Ironsight/Holo in RS - this is the same distance as in Hipfire CSGO.
Based on this I have Hipfire about 33 cm/360, IronSight 54 cm and ACOG 94 cm

I got used to it and would like to have the same on my new monitor

As you can see below, I was trying to convert my Ironsight/Holo, but as a result I get different cm/360 distance, and I think it should be the same regardless of monitor ratio. I am making some logical error ,but I am not sure where.

Any help appreciated.

The outcome shouldn't have the same 360 distance since Ultrawides provide you with additional FOV. The calculator is taking that extra FOV into account and providing you with a faster sensitivity to compensate for the higher FOV. This is perfectly normal.

If you look at the "actual HFOV" between the two it changes from "106.32" to "121.72". This is the ultrawides additional FOV.

That's from my understanding at least.

Edited January 6 by Fluvio

Share this post

Link to post

Share on other sites

In my logic, regardless of monitor width when I move mouse from let's say one object (in game) to another object, distance on mousepad should be the same.
When overall 360 cm distance dropped from 54 to 40 I think it is impossible to keep this, as I will move faster

Maybe I should change FOV in my calculation from 82 to another value - but I am not sure if this value is aware of that 21:9 and 16:9 stuff, so I just left it the same

I hope you understand what I mean - maybe I am just stuck in some false logic there:)

In my logic, regardless of monitor width when I move mouse from let's say one object (in game) to another object, distance on mousepad should be the same.
When overall 360 cm distance dropped from 54 to 40 I think it is impossible to keep this, as I will move faster

Maybe I should change FOV in my calculation from 82 to another value - but I am not sure if this value is aware of that 21:9 and 16:9 stuff, so I just left it the same

I hope you understand what I mean - maybe I am just stuck in some false logic there:)

The way I try to think of it is:

When it comes to mouse sensitivity, there are two factors at work:

Muscle memory, and hand-eye coordination. If you change the in-game numbers, they alter the muscle memory, if you change FOV, it alters the hand-eye coordination. If you increase the FOV, you need to alter the muscle memory a little in order to compensate if that makes sense. Like if you have 3 * 4 = 12. And you change the 3 to a 2. It needs to become 2 * 6 = 12 for the equation to work. You need to alter things proportionately to eachother.

The calculator does this for you which is why you end up with a smaller 360 distance (changed muscle memory) due to the FOV being different (Changed hand-eye coordination).

If you go in-game and put your FOV down to 60 and do a few T-hunts, then change it to 90 and do a few, You'll notice that it feels slower on the 90 setting. That's the hand-eye coordination fucking up because the FOV got changed.

That's the way I explain it. Essentially just do what the calculator says and you'll benefit. Trust me. I play Siege, BF4, CSGO, Fortnite and recently Overwatch. And using Monitor Match at 0% I maintain my aim through all the games, despite them being different 360 distances doe to the difference in FOV.

If you want the same 360 distance, you definitely wanna match FOVs. Specifically, you wanna match Horizontal FOV. You see that "Actual HFOV =" number. Reduce the 21:9 FOV until that HFOV matches, or is as close to the same as the standard 16:9 one. That can also give you the same sensitivity. It'll probably need be between 65 and 75 I would guess.

Share this post

Link to post

Share on other sites

I feel kinda dumb to ask this, but I can't figure out what certain options for R6 conversions are. I'm talking about All /w ADS and All /w ACOG. What the "/w" means and that is the purpose of these options?

Replace the input fields with 3440x1440 and 98.89189 fov, and 1600 CPI.

Set the output field to 99 fov and optionally CPI to 2150.

Get new sensitivity values

Thank you very much for detailed answer

I get general idea behind the math you provided. Like you said "You want to preserve the same curvature in the same physical space" - this is exaclty what I tried to do but lacking knowledge how to do it:)

Unfortunately I don't understand instruction what to do - sorry...

I am confused what input and output mean. I understand Input as old values for Siege in 1920x1080 (provided in my screenshot on this page) and output as "Convert To" field with new values like 3440x1440 and new FOV (and DPI?)

You say that input should be "3440x1440 and 98.89189 fov, and 1600 CPI." and output "99 fov and optionally CPI to 2150"

Is it possible that you insert screenshot with calculation based on my settings for 1920x1080?

Share this post

Link to post

Share on other sites

The outcome shouldn't have the same 360 distance since Ultrawides provide you with additional FOV. The calculator is taking that extra FOV into account and providing you with a faster sensitivity to compensate for the higher FOV. This is perfectly normal.

If you look at the "actual HFOV" between the two it changes from "106.32" to "121.72". This is the ultrawides additional FOV.

That's from my understanding at least.

Again, thanks for answer.

Returning to your initial post I made some picture to help visualize what I am trying to do:)

I know that you mentioned that cm/360 should change with changing FOV to adapt muscle memory and hand-eye coordination, but it is really hard to imagine for me why it should , as 21:9 is only wider without changing vertical FOV.

I think cm/360 should change only when you modify FOV with the same monitor - for example raise from 82 to 90 on 16:9. Then you can feel the difference and it should be compensated somehow.

Let's assume on my 16:9 monitor I made 15cm to move from the left wall to right wall.
On 21:9 monitor I think I should make EXACTLY the same distance on this center area. So cm/360 should be unaffected because I only see more because of "bigger window". This is just some added peripheral vision

That's why I was confused after trying to convert it keeping the same 82 vFOV and getting completely different cm/360. If I am not wrong (maybe I am:) with different cm/360 there is no way that this marked distance will be the same on 21:9. I tried to keep the same vFOV because by looking on image it is clear to me that only hFOV is changing from 16:9 to 21:9, and vFOV stay the same

Drimzi provided some other point of view but I am still waiting for answer because unfortunately I don't get all the math, and instruction what exactly to put into calculator

Share this post

Link to post

Share on other sites

Returning to your initial post I made some picture to help visualize what I am trying to do:)

I know that you mentioned that cm/360 should change with changing FOV to adapt muscle memory and hand-eye coordination, but it is really hard to imagine for me why it should , as 21:9 is only wider without changing vertical FOV.

I think cm/360 should change only when you modify FOV with the same monitor - for example raise from 82 to 90 on 16:9. Then you can feel the difference and it should be compensated somehow.

Let's assume on my 16:9 monitor I made 15cm to move from the left wall to right wall.
On 21:9 monitor I think I should make EXACTLY the same distance on this center area. So cm/360 should be unaffected because I only see more because of "bigger window". This is just some added peripheral vision

That's why I was confused after trying to convert it keeping the same 82 vFOV and getting completely different cm/360. If I am not wrong (maybe I am:) with different cm/360 there is no way that this marked distance will be the same on 21:9. I tried to keep the same vFOV because by looking on image it is clear to me that only hFOV is changing from 16:9 to 21:9, and vFOV stay the same

Drimzi provided some other point of view but I am s﻿till w﻿aiting for ﻿answer because unfortunately I don't get all the math, and instruction what exactly to put into calculator﻿﻿﻿

Try this out.

Change your FOV to 60 and run around terrorist hunt for a bit. Then change it to 90. You will notice the difference... This is the hand-eye coordination change that I mentioned. The higher the FOV, the slower it will feel. This is why when you increase FOV, You should reduce your 360 distance to compensate. That realigns the sensitivity if you will.

So you have two options to transfer the sensitivity.

1) Reduce your FOV to 65 like in my picture: To realign the sensitivities as closely as possible. This won't give you the EXACT same FOV since you cannot match the FOVs exactly as far as I'm aware so you do need a tad of compensation but it's literally minuscule.

Or

2) Use 82 and use your new, faster sensitivity that will be converted. Like you have done above.

Both of these will work equally well. One maintains Hand-Eye will changing 360 distance, the other changes Hand-eye while maintaining 360 distance. That's just the way I've came to understand it. Try them both out and see which works for you. You might hate the FOV change or you might hate the 360 change. You won't know until you try.