hello ,

i do know that there is 5 topics with the same exact idea like mine in this page and i did watch the videos and guides on the conversion but i think I'm too stupid to understand this and it would be super awesome of you if you can just tell me exactly which part is wrong : https://imgur.com/a/ICVRxjJ 

 

trying to convert the sensitivity of the desktop mouse movement to a game , monitor is 1440p res and 27inch and the game is in 16:9 aspect ratio with normal res

 

the problem i am having is that no matter what dpi i put in the first box the sensitivity is always constant

i have tried by moving the same amount by hand and it ended up at 1.9 and i see people getting 3 so i am a little confused

 

Edited January 31, 20197 yr by ZSfGuBcu

8 hours ago, Guest ZSfGuBcu said:

the problem i am having is that no matter what dpi i put in the first box the sensitivity is always constant

The calculated sensitivity will never change if you have the same DPI in both Windows and the game. If you just change DPI in the first box, it will be copied to the second box unless you have entered a value in it too.

So when you change from say 400 to 800, you are doubling your "sensitivity" in Windows, making the distance half. So to match this the same thing has to happen in the game, you should have half the distance. But since you doubled your DPI, the distance is already half and the sensitivity stays the same.

13 hours ago, DPI Wizard said:

The calculated sensitivity will never change if you have the same DPI in both Windows and the game. If you just change DPI in the first box, it will be copied to the second box unless you have entered a value in it too.

So when you change from say 400 to 800, you are doubling your "sensitivity" in Windows, making the distance half. So to match this the same thing has to happen in the game, you should have half the distance. But since you doubled your DPI, the distance is already half and the sensitivity stays the same.

hello

ok i got that part as you explained it to me but the question is still the same : what is the 400 Dpi on 0% MM should translate to on csgo for a 16:9 default fov ? is 2.7 that im getting correct ? ( 400 dpi on windows and 400 in game )

also is it possible to get an image for this conversion so i know what to do for the future ones ?

 

Edited February 1, 20197 yr by ZSfGuBcu

2.712868 is correct.

Don't change the fov type of the game unless the game allows you to. You only use that option to quickly see what the value is for other measurements so you can set other games to the same fov.

I recommend switching to Monitor Distance - Vertical 0%. Horizontal can give the wrong results if you play with black bars. For example, it will give a different result if you put CSGO at 4:3, since the horizontal fov goes from 106.26 to 90. The focal length doesn't change though, so you shouldn't be changing the sensitivity at all. The vertical fov remains at 73.74, so Monitor Distance - Vertical 0% will still give the same result, which is correct.

 

If you want to keep the same 360 distance in a game, change the input game from Windows/Desktop to CSGO and change the 'Normal' conversion method to 360 distance.

• 360 distance preserves the mouse movements for navigation, but you get a different mouse sensitivity.
• 0% preserves the mouse sensitivity, but you will end up with smaller/larger mouse movements for navigation.
• Other methods will preserve other characteristics that don't really have any benefit imo.

Edited February 1, 20197 yr by Drimzi

12 hours ago, Drimzi said:

2.712868 is correct.

Don't change the fov type of the game unless the game allows you to. You only use that option to quickly see what the value is for other measurements so you can set other games to the same fov.

I recommend switching to Monitor Distance - Vertical 0%. Horizontal can give the wrong results if you play with black bars. For example, it will give a different result if you put CSGO at 4:3, since the horizontal fov goes from 106.26 to 90. The focal length doesn't change though, so you shouldn't be changing the sensitivity at all. The vertical fov remains at 73.74, so Monitor Distance - Vertical 0% will still give the same result, which is correct.

 

If you want to keep the same 360 distance in a game, change the input game from Windows/Desktop to CSGO and change the 'Normal' conversion method to 360 distance.

• 360 distance preserves the mouse movements for navigation, but you get a different mouse sensitivity.
• 0% preserves the mouse sensitivity, but you will end up with smaller/larger mouse movements for navigation.
• Other methods will preserve other characteristics that don't really have any benefit imo.

hello

thank you so much for the detailed explanation and the picture ❤️

Could somebody tell me which conversion is the right one here?

Conversion: OW 8 at 400 dpi to battlefront 2 at 400 dpi 61 fov (mouse sensitivity & Zoomed sensitivy).

Edited February 5, 20197 yr by Nameless

55 minutes ago, Nameless said:

Could somebody tell me which conversion is the right one here?

Conversion: OW 8 at 400 dpi to battlefront 2 at 400 dpi 61 fov (mouse sensitivity & Zoomed sensitivy).

It depends on what you want.

In the first one SWBF2 hipfire is matched to OW hipfire using 360 distance, and ADS and scopes for both games are matched to OW hipfire using MDH 0%

In the seconds one SWBF2 sniper is matched to SWBF2 hipfire using MDH0%. The All conversion actually uses the sniper, but that's not the main issue.

OW hipfire and SWBF2 hipfire have different FOV's and you used 360 distance in the first conversion, that's why you get a different result here.

For the last one you are using MDV 0% for hipfire instead of 360 distance, so converting just scopes like you did in the second one does work with this setup:

what i want is my battlefront 2 at 400 dpi 61 fov mouse sens & zoomed sens to both match my overwatch hipfire sens (8 at 400 dpi 103 fov). So, if i understand your reply correctly, the correct result according to what i want is GstInput.MouseSensitivity 0.033013 &
GstInput.SoldierZoomSensitivityAll 1.204198

So this method bellow is the method i should use?

1st for ow hipfire to swbf2 hipfire

2st for ow hipfire to swbf2 zoomed

3st double check

Is that correct?

 

 

 

Edited February 5, 20197 yr by Nameless

2 hours ago, DPI Wizard said:

It depends on what you want.

In the first one SWBF2 hipfire is matched to OW hipfire using 360 distance, and ADS and scopes for both games are matched to OW hipfire using MDH 0%

In the seconds one SWBF2 sniper is matched to SWBF2 hipfire using MDH0%. The All conversion actually uses the sniper, but that's not the main issue.

OW hipfire and SWBF2 hipfire have different FOV's and you used 360 distance in the first conversion, that's why you get a different result here.

For the last one you are using MDV 0% for hipfire instead of 360 distance, so converting just scopes like you did in the second one does work with this setup:

Could u take a look at my reply when u ave time?

?

 

Edited February 5, 20197 yr by Nameless