Battlefield 6

After some time testing in the firing range, I’m pretty sure the current hip-fire sensitivity conversion isn’t mapping correctly. I copied the exact same numbers from my Battlefield 2042 and Battlefield 4 config into the new game’s config file, but hip-fire now feels roughly one-third slower. Has anyone else noticed this, or can a dev double-check the conversion?

Yes, the calculated sens is slower.

My sens in other BF's are set to 4, for BF6 the calculator said 8, but I had to go to 12 to get the same distance for a 360 in hipfire.

4分钟前,zxy1273说:

After some time testing in the firing range, I’m pretty sure the current hip-fire sensitivity conversion isn’t mapping correctly. I copied the exact same numbers from my Battlefield 2042 and Battlefield 4 config into the new game’s config file, but hip-fire now feels roughly one-third slower. Has anyone else noticed this, or can a dev double-check the conversion?
在射击场进行了一段时间的测试后，我很确定当前的腰射灵敏度转换没有正确映射。我将《战地风云 2042》和《战地风云 4》配置中的完全相同的数字复制到新游戏的配置文件中，但腰射现在感觉慢了大约三分之一。有没有其他人注意到这一点，或者开发人员可以仔细检查转换吗？

Same, maybe they didn't test ,just copy 2042 way

1 minute ago, Cpeple said:

Same, maybe they didn't test ,just copy 2042 way

I’m already aware that using the same value in the config file now shows up as double the number in the in-game settings, but even after accounting for that, hip-fire still feels much slower.

To clarify my findings with concrete numbers:

• Config file parameter used: GstInput.MouseSensitivity 0.009687

  • In BF 2042, that same line matched an in-game setting of 6.5.

  • In the new Battlefield, the very same line now maps to an in-game setting of 12.9—so the UI scale is clearly doubled.

Despite this doubling, hip-fire still feels significantly slower—roughly 30-35 % down—compared with 2042.

So at this point it looks like they didn’t just copy-paste the 2042 maths and double the scale— they’re using an entirely different sensitivity algorithm under the hood.

49 minutes ago, Memphiss said:

Yes, the calculated sens is slower.

My sens in other BF's are set to 4, for BF6 the calculator said 8, but I had to go to 12 to get the same distance for a 360 in hipfire.

Yeah i ended up on the same lol. also used to use 4% with 800 dpi in other BF now on 12%.

Edited August 7Aug 7 by Sapper

42 minutes ago, zxy1273 said:

I’m already aware that using the same value in the config file now shows up as double the number in the in-game settings, but even after accounting for that, hip-fire still feels much slower.

To clarify my findings with concrete numbers:

• Config file parameter used: GstInput.MouseSensitivity 0.009687

  • In BF 2042, that same line matched an in-game setting of 6.5.

  • In the new Battlefield, the very same line now maps to an in-game setting of 12.9—so the UI scale is clearly doubled.

Despite this doubling, hip-fire still feels significantly slower—roughly 30-35 % down—compared with 2042.

So at this point it looks like they didn’t just copy-paste the 2042 maths and double the scale— they’re using an entirely different sensitivity algorithm under the hood.

Yeah maybe an effect on them completely rebuilding the movement in general from the ground up, with there kinesthetic system!?

Edited August 7Aug 7 by Sapper

Anyone else feel like there's some kind of aim acceleration / mouse smoothing even with raw mouse input on (default)?

trying to get a 1:1 sensitivity for all my scopes, but the converter is outputting values like 54 inches for 360 degrees when I want it at 7.2 inches for 360 degrees, any way the calculator can reflect that 1:1?

33 minutes ago, DPI Wizard said:

For this you need to set the calculator to Default mode and set ADS and Scope to 360 distance, but note that this is not recommended for scopes, and actually not even possible since it would require a zoom sensitivity higher than the game supports.

when I go into the calculator settings, it only shows the 4 selections in the top left of youir image, where would I find the highlighted boxes in your image? And thanks for the detailed explanations!

11 minutes ago, DPI Wizard said:

This seems like a bug, try to select simple mode, then default mode again. Will look into it!

that fixed it, thanks!

4 hours ago, itsPanic said:

Anyone else feel like there's some kind of aim acceleration / mouse smoothing even with raw mouse input on (default)?

yes, it does feel like something is wrong. I am also on 1000hz polling rate. just feels off.

this tool is great btw

Edited August 7Aug 7 by djb0990

With using uniform soldier aiming i cannot additonaly adjust the high scope zoom sens correct? I use 0 coefficient and the snipers just feel very slow and i cant find a proper go to setting. Without uniform im able to edit each zoom but is it worth? I try to have 1:1 aim across scopes but i think its not possible. Any recommendation for "best" coefficient on/off uniform?

1600dpi, 1000hz, 1920x1080, performance is great. Aiming just feels off and floary sometimes idk.

Thx 🫱🏻‍🫲🏼

Edited August 8Aug 8 by snyh1
grammar

5 minutes ago, DPI Wizard said:

Correct, but they keep their value from when Uniform Aiming is off, so if you need different values than 100, you can set it to off, adjust the values, then switch it to on. That's why I left the options in the calculator.

Thanks for your reply! So i guess keep uniform just on is best for building muscle memory in general? I think per each zoom lvl is a hassle and counter benefitial?

Does the config GstRender.FieldOfViewScaleADS take effect in current beta version?

Edited August 8Aug 8 by Journalist