Jump to content

Last Tide

In-game and config file sensitivity added for this aquatic royale!
Read more...

Monster Hunter: World

An update added a new camera control type which solved all the issues with this game!
Read more...

Ring of Elysium

Most aims are added now!
Read more...

Swarmlake

Added!
Read more...

Hunting Simulator

Use the config file calculations for best range and accuracy.
Read more...
Sign in to follow this  

Battlefield: Bad Company 2

Bad Company 2 is back! Took some time to analyze, but this new addition is verified 100% correct for the Origin version, which does not suffer from any acceleration.

Edited by DPI Wizard


Report Update
Sign in to follow this  

User Feedback




Any particular reason converting BC2 sensitivity to BF3/BF4 isn't anywhere close to accurate? Tried going backwards BF3/BF4 to BC2 and the dpi value can't be changed for BC2.

Share this comment


Link to comment
Share on other sites

Have you modified the .dbx files under %USERPROFILE%DocumentsBFBC2input? If so, calculations will be off. Also, what do you mean by the dpi value can't be changed?

Share this comment


Link to comment
Share on other sites

Nothing was modified in any input file, only the sensitivity in game was changed. And it's not a little bit off it's almost 180 degrees off when converting BC2 to BF3 or BF4.

 

Seems to be off when converting BF3 or BF4 to BC2 sensitivity. No worries, I haven't seen anyone get the conversions right for converting sensitivity for BC2 to something else.

 

Before it wasn't letting me change the DPI value of the ""new game"" when that new game was set to BC2, seems to be working now. Probably just a fluke or the notifyproperty change not being triggered.

Share this comment


Link to comment
Share on other sites

BC2 has some terrible acceleration you won't get rid of, however it should not result in a 180 degree difference. I'm sure the calculations are correct on the system I test on, but there might be some variables I'm missing for it to be universally correct. If you don't mind, what numbers do you put in, and what is the actual result in distance/360? What I need is current game, fov, wps, dpi, sensitivity/distance, and output fov, wps and dpi. Thanks!

Share this comment


Link to comment
Share on other sites

I don't believe acceleration is the issue I was only doing slow mouse movements across the pad to see the amount needed to 360. Also it's unchecked in the options for BC2 and I noticed BC2 uses raw input by default at the very least windows bar doesn't affect it.

 

Current game sensitivity .28, dpi 800, fov 70 although it's got the X on it on here so that shouldn't matter right?, wps 6, distance on here says around 98 cm.

 

New game sensitivity is 0.004046, dpi 450, fov 96, wps 6, distance on here says 98 cm.

 

Actual distance in game seems to be around 108 however that's sort of close to what it says on here. I think the problem might be the calculation for the starting sensitivity. Because there is no way that sensitivity for BC2 is 98 cm for a 360. Does this site take in account the default ""yaw/pitch"" factor that are available in BC2's in-game settings? These might be what are affecting the starting sensitvity, default is 1 by the way.

Share this comment


Link to comment
Share on other sites

Did some testing now, and believe it or not, but the acceleration in BC2 is actually this bad. The calculations are correct when 1 count is sent at a time, but when a bunch of counts like 100 are sent at a time, the movement gets accelerated almost 50%. I'll see if I can tune the calculations to reflect the accelerated (real life) movement instead of the theoretical correct movement. I'll also update what yaw/pitch are used for calculations.

Share this comment


Link to comment
Share on other sites

I have updated the BC2 calculations to better reflect the actual distance now, and updated the notes field regarding the yaw and pitch. Mouse movement registration in BC2 is terrible though, the crosshair will move a different distance every time even if you move your mouse the exact same distance :(

Share this comment


Link to comment
Share on other sites

As mentioned in the notes, BC2 has so much acceleration it is impossible to do the calculations accurately. It's a rough estimate, but it will vary depening on DPI, polling rate, sensitivity and the speed you move your mouse at.

Share this comment


Link to comment
Share on other sites
Guest 000Rudolf

Posted

There is no way to remove the acceleration and have an accurate misuration, right?

Share this comment


Link to comment
Share on other sites

Correct, BC2 will do acceleration even if you turn it off in the menus :( That makes calculations impossible to do accurately since the actual distance/360 depends on how fast you move your mouse.

Share this comment


Link to comment
Share on other sites

Battlefield Bad Company 2 is definitely wrong. I am using the same DPI and 360 distance as BF4 and BF3 and sensitivity feels 1.5x as high in BC2.

Share this comment


Link to comment
Share on other sites

BC2 has so much acceleration that I have considered removing it. That's why you are not getting the distance calculated. Actually, if you try moving your mouse very slow to the right, and then quick back left to the exact sport you started, see that the crosshair ends up a completely different place :/

Share this comment


Link to comment
Share on other sites

Did something with the BC2 calculation get broken? 800 dpi + 0.27 = 157 cm, that can't be right.

Share this comment


Link to comment
Share on other sites
Guest Asher Hunt

Posted

There's mouse acceleration in that game, can't do much about it sadly. I really wonder why devs force acceleration in some games...

Share this comment


Link to comment
Share on other sites

The correct base distance for 800 dpi + 0.27 sensitivity is closer to 110 cm, but since the game has so much acceleration I've added 40%. Also make sure the pitch values are 0.5. Even so, the acceleration makes an accurate calculations impossible :(

Share this comment


Link to comment
Share on other sites

Well I can tell you that neither 110 nor 152 are anywhere near the numbers I'm measuring manually. It's more around 50-60 something cm. Which is why I mentioned what was calculated on here not being right, at the very least it's way way off.

Share this comment


Link to comment
Share on other sites

Yes, even deleted them and reset to default. I guess I'll just have to do it manually.

Share this comment


Link to comment
Share on other sites

they left acceleration in BC2 becouse it was shity console port. at that time Dice started chasing IW tail on fight with COD so they left out PC version. Still for me sensitivity is right and i play snipers only so yea... don't see big of a problem here.

Share this comment


Link to comment
Share on other sites

Hey, just been trying out Bad Company 2 and am pretty sure the sensitivity calculation isnt correct if you could perhaps check it. 0.54 sensitivity is definitely not 15inches at 400dpi

Share this comment


Link to comment
Share on other sites


×