Set "Mouse Polling Rate Support" to Yes to enable raw input!

ohhhhhhhhhhhh

The value i get from CS:GO to Crossfire doesn't feel even close to the same sensitivity.

In CS:GO i use a sensitivity of  2 and the calculator give me 15 for Crossfire ingame.

 

I already enabled the raw input mode in Crossfire but its way to fast on 15. I would say its more about 7 to 8.

4 minutes ago, dream said:

The value i get from CS:GO to Crossfire doesn't feel even close to the same sensitivity.

In CS:GO i use a sensitivity of  2 and the calculator give me 15 for Crossfire ingame.

 

I already enabled the raw input mode in Crossfire but its way to fast on 15. I would say its more about 7 to 8.

Do you get a different result with raw input on and off?

This sensitivity is analyzed for the EU version BTW.

I have to test that.

I play on Crossfire West.

2 hours ago, dream said:

I have to test that.

I play on Crossfire West.

might be the fov difference, btw how do they manage to still not get that publishing done properly with 20 bazillion different versions in 2019 their naming scheme is worse than LG and their random numbers/ ciphers 

Edited December 22, 20196 yr by fortunate reee

2 hours ago, fortunate reee said:

might be the fov difference, btw how do they manage to still not get that publishing done properly with 20 bazillion different versions in 2019 their naming scheme is worse than LG and their random numbers/ ciphers 

i use the default fov in both games.

Yeah the very first splits of all the versions were a mistake but now they try to migrate all versions to cf west (na, eu, spain are basically one version now = cf west)

mouse-sensitivity.com YES!!!!!!!

I can just say, that the calculated sensitvitiy feels way to fast for me.

I think some other user need to provide their feedback.

11 minutes ago, dream said:

I can just say, that the calculated sensitvitiy feels way to fast for me.

I think some other user need to provide their feedback.

Not sure what's causing this. I know the calculated sensitivity is correct since it's based on pi, 0 is exactly pi*10000 and 100 is pi*500. There's a tiny inaccuracy in the sensitivity slider, but should account for less than 2%. Must be something else affecting your sensitivity, did you try with raw input both on and off to observe the difference?

Crossfire's FOV is very different from any other games(much small scale), maybe that's why 360deg method will feel totally different. MDH 0% much better.

In China, the CF game only supports the return rate of 125Hz, but when I play csgo, the return rate of mouse is 1000Hz. When I use the website for conversion, the CF mouse speed obtained by csgo game is obviously very fast under 125Hz. Can I convert the mouse speed under the return rate of cf125hz。

 

Thank you。

When I play csgo, the mouse speed is 3 ，DPI400， mouse rate of return is 1000 Hz. The website gives a CF conversion speed of 25, but in China, CF only supports 125 rate of return. When I use 25 in-game sensitivity, I will obviously feel faster, and only when it is reduced to about 10 can I feel normal.

12 hours ago, zhou707377543 said:

When I play csgo, the mouse speed is 3 ，DPI400， mouse rate of return is 1000 Hz. The website gives a CF conversion speed of 25, but in China, CF only supports 125 rate of return. When I use 25 in-game sensitivity, I will obviously feel faster, and only when it is reduced to about 10 can I feel normal.

Polling rate should not affect sensitivity at all, but some games have issues with high rates. In CSGO there is no difference between 125Hz and 1000Hz, the sensitivity is exactly the same. In Crossfire 125Hz should be the correct sensitivity, but do note that I have not tested the Chinese version. If it's the same as the EU version then turning on Mouse Polling Rate should be enough to fix any issues.

On 1/4/2020 at 4:35 PM, Purestone said:

Crossfire's FOV is very different from any other games(much small scale), maybe that's why 360deg method will feel totally different. MDH 0% much better.

I agree! MDH 0% feels very close to my normally played sensitivity.

Instead of 15, i get 8 with mdh 0.

Thank you for your help.I tried the  calculator for hipfire and it should be correct .But I don't understand what ADS means.Does it mean aiming with a sniper scope?But the calculator shows that the actual VFOV during ADS is 42 degrees, which is obviously too high (for example, the VFOV of the iron sight in Battlefield 3 is 40 degrees, which is even lower than this value!).And different sniper rifles have different magnifications for their scopes in this game.Although I don't know the specific value, I know that kar98k Zoom 1＜ awm Zoom 1＜CheyTac M200 Zoom 1,so their FOVs cannot be the same .If possible, I want to convert from CheyTac M200 Zoom 1 in crossfire to AWP Zoom 1 in csgo.

I'm sorry to raise this question so late, but it is important to me because I want to have the same feel when using sniper rifles in both games. Thank you😊

 

 

In addition, CSGO's calculator supports calculating Zoomed 1 AWP and Zoomed 2 AWP.

It would be even better if CROSSFIRE's calculator also supports calculating Zoomed 1 and Zoomed 2 

23 hours ago, Nephren_Insania said:

But I don't understand what ADS means.Does it mean aiming with a sniper scope?

It's iron sight ADS only, I don't really have access to the weapons in the game, so it's kind of hard to add anything else unfortunately.

well...I did some imprecise tests myself.In Crossfire,my mouse sensitivity is 36 and zoom sensitivity is 18.

So,I converted the hipfire sensitivity in Crossfire to the hipfire sensitivity in Battlefield 3 (The scopes do not have a separate sensitivity setting in Battlefield 3)and then I found out that fortunately, the ADS sensitivity of these two games is also very similar.For example, moving the mouse approximately the same distance causes the iron sights to rotate 90 degrees and the sniper rifle Zoomed 1(which has the similar FOV of the 3.4X scope in Battlefield 3)to rotate 45 degrees.This is not very precise, but it's basically enough.Now I converted the 3.4X scope sensitivity setting of Battlefield 3 to AWP Zoomed 1 in CSGO.

My problem has been solved. Thank you for your reply

There might be something wrong.

Chinese mainland version offers 2 display mode: "屏幕适配(suit to screen)" and "正常比例(normal ratio)". The former will stretch original 4:3 graph to suit the screen. And the latter will display a normal graph in a modern way (keep VFOV stable).

I try to use calculator to convert in "normal ratio" but get a lower sensitivity(MDV1.33). And I figure out that the result of calculator is right in [16:9+"suit to screen"](check by ruler and the mark on the screen board).

Please check the result. If the version in your country does not support "normal ratio", you can check the result in 4:3. Or just compare the graph in 4:3 and 16:9.

Thank you!

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

（the real result should be 1600x3, not 1600x2）

(My test screenshot was attached. They are "normal ratio"+16:9, original 4:3, "suit to screen"+16:9, respectively)

Edited May 31, 2025May 31 by MGYBlue
To add the name of picture in the text.

2025/5/31 PM9点00分,MGYBlue说:

There might be something wrong.

Chinese mainland version offers 2 display mode: "屏幕适配(suit to screen)" and "正常比例(normal ratio)". The former will stretch original 4:3 graph to suit the screen. And the latter will display a normal graph in a modern way (keep VFOV stable).

I try to use calculator to convert in "normal ratio" but get a lower sensitivity(MDV1.33). And I figure out that the result of calculator is right in [16:9+"suit to screen"](check by ruler and the mark on the screen board).

Please check the result. If the version in your country does not support "normal ratio", you can check the result in 4:3. Or just compare the graph in 4:3 and 16:9.

Thank you!

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

（the real result should be 1600x3, not 1600x2）

(My test screenshot was attached. They are "normal ratio"+16:9, original 4:3, "suit to screen"+16:9, respectively)

My expression might be not so clear. TLDR is that the result might be calculated by streched frames not the native frames. Please check it. Thank you.

1 hour ago, MGYBlue said:

My expression might be not so clear. TLDR is that the result might be calculated by streched frames not the native frames. Please check it. Thank you.

Whether it's calculated based on stretched or native aspect ratio is controlled by the aspect ratio selection (stretched/black bars), as well as the axis in the conversion method (horizontal or vertical).

28分钟前,DPI Wizard说:

Whether it's calculated based on stretched or native aspect ratio is controlled by the aspect ratio selection (stretched/black bars), as well as the axis in the conversion method (horizontal or vertical).

Thank you for reminding me this function since I never use this function before. But it is not easy because I need to choose ["4:3"+native] convert to [16:9 + "native"] with MDH100% to get a result equal to MDV133% in other games. Like this:

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

So, the issue still exists that CF might be tested in streched mode but you didn't realize because the 16:9 of this game is default made by stretching. I kinda understand your thought that the "native" mode should be the default mode of the game, which can benefit more beginner player, but at least the actual HFOV should be 67.22 not 83.11 because of default stretching.

I am sorry that my english is not good and these word can not fully express my opinion. Thank you for your patience.

4 minutes ago, MGYBlue said:

but at least the actual HFOV should be 67.22 not 83.11 because of default stretching.

For this you need to select 4:3 stretched: https://www.mouse-sensitivity.com/?share=f660fad539b40a2d32aaa2f0277cfe4c

6 minutes ago, DPI Wizard said:

For this you need to select 4:3 stretched: https://www.mouse-sensitivity.com/?share=f660fad539b40a2d32aaa2f0277cfe4c

You still don't understand what I mean.😭 The result of MDV133% shows that the result of "native" is actually accessed by stretching mode in-game. So I recommand that either change the actual HFOV into 67.22 OR update the result of "native" by testing in REAL native mode of the game.

I need to clarify again that the default 16:9 of CF is made by stretching, not like other old games like AVA is made by simply zooming in. You might forget to change into native ratio mode before testing.😭