|
Post by phoon on Dec 30, 2010 14:02:18 GMT -5
just bought bad company 2, and my nerdy obsessive compulsive issues with mouse sensitivity are carrying over from the previous games that I have played. can I just roughly measure out the same sensitivity and be happy? absolutely not.
If possible, please define the following modifiers/terms (If I am not correct):
GameSettings.ini
Sensitivity0 (sensitivity modifier used to combine infantry, land, and air sensitivity?)
Sensitivity1/2 (yaw and pitch scaling for independent axis sensitivity preferences)
Sensitivity3/4/5 (joystick settings, irrelevant to me)
Scheme0Sensitivity (sensitivity modifier used to combine infantry, land, and air sensitivity?)
Scheme1Sensitivity (GameSettings.bin) (currently displayed as .2 for me)
infantry.dbx
The following are under ConceptYaw and ConceptPitch, in the MouseInputActionData sections:
NegateValue (set to both false and true in two separate settings under MouseInputActionData, and I have no idea what they do)
NormalizeInput (Mouse smoothing, similar to m_filter in quake based games? both were set to false for me by default, but I see many guides suggesting these to be CHANGED to false)
ScaleValue (defaulted at 0.00030000001, seems to be the base sensitivity modifier for infantry)
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
the previous games that I have played (cs:s, tf2, quake engine games) are only effected by sensitivity and pitch/yaw settings. I assume the reason for this game's many scaling factors is due to the addition of vehicles. I'm looking to get my infantry sensitivity to be the same as the previous game sensitivities. the best result I have gotten is by doing the following:
ALL GameSettings.ini sensitivity settings set to 0 ScaleValue settings under ConceptYaw and ConceptPitch set to 0.0968
(Default pitch/yaw values) * (Sensitivity) = base sensitivity value (0.022) * (4.4) = 0.0968
It still appears to be slightly faster than the other games. does this game use a different scaling method for sensitivity than the other engines? edit: was being an idiot and using the wrong number of counts to move the mouse, it is the same sensitivity scaling method as the other games
How do the GameSettings.ini sensitivity settings mesh with the infantry/land/air ScaleValue settings? It can't be simple multiplication, as I have mine set to 0 (OR CAN IT?!?!?!)
what makes a tank turret turn slowly? it is not solely due to the land.dbx ScaleValue settings.
|
|
|
Post by infininja on Dec 30, 2010 16:39:15 GMT -5
I started tinkering around in those values once.
Never again.
|
|
aranshada
True Bro
But woe betide thine enemies, for thee hath created thine Bullet Hose.
Posts: 231
|
Post by aranshada on Dec 30, 2010 16:51:51 GMT -5
I would just like to point out that there is also some amount of negative acceleration inherent in BC2. This is why if you crank sensitivity all the way up and throw your mouse across the desk, the turret will still hit a max speed while turning. I've seen evidence that it's the same for infantry combat, too - turning faster will have you turn less than if you had slowly dragged the mouse across.
I'm also curious as to how I would achieve at least infantry sensitivity similar - hell, I don't even know how the sensitivity scales within the in-game slider - .25 is definitely WAY less than half of .50, and even going from .50 to .40 is a massive jump. Then again, BF2 is the same for me - took me 20 minutes of trying different sensitivity/dpi settings to finally match my turning speed from CoD.
P.S. If this is the same phoon that I've seen around, I love the mouse page on your website. Used the calculator to tweak my sensitivity to exactly 25cm.
|
|
|
Post by phoon on Dec 30, 2010 17:31:04 GMT -5
I would just like to point out that there is also some amount of negative acceleration inherent in BC2. This is why if you crank sensitivity all the way up and throw your mouse across the desk, the turret will still hit a max speed while turning. I've seen evidence that it's the same for infantry combat, too - turning faster will have you turn less than if you had slowly dragged the mouse across. I'm also curious as to how I would achieve at least infantry sensitivity similar - hell, I don't even know how the sensitivity scales within the in-game slider - .25 is definitely WAY less than half of .50, and even going from .50 to .40 is a massive jump. Then again, BF2 is the same for me - took me 20 minutes of trying different sensitivity/dpi settings to finally match my turning speed from CoD. P.S. If this is the same phoon that I've seen around, I love the mouse page on your website. Used the calculator to tweak my sensitivity to exactly 25cm. as far as negative accel goes, I know of two ways to get it. one is from the game's mouse input, and it can be calculated at www.phoon.us/mousehowever, BFBC2 does not use WM_MOUSEMOVE/GetCursorPos, so I believe that is useless in this case. the only other way that I know of would be directly related to the mouse hardware, which is different for everyone. as infantry, I have to try incredibly hard to give myself neg accel in this game. this requires an unnaturally fast movement in which I would not expect to be precise in the first place. the max speed my mouse can handle is 1.55 m/s, which I would not normally hit, so neg accel is not my concern. I haven't even tried messing with the tank/helicopter settings yet, as I don't really want to use them anyway what evidence have you seen as far as neg accel for infantry goes? also the mouse website won't work for this game (from what I know so far), and I have never played CoD so I am not familiar with the settings of that game either.
|
|
aranshada
True Bro
But woe betide thine enemies, for thee hath created thine Bullet Hose.
Posts: 231
|
Post by aranshada on Dec 30, 2010 17:51:06 GMT -5
I know that the mouse page doesn't work for BC2 or BF2, but since CoD is based from the Quake engine, it works for all CoD variants on the PC. When I mentioned using it to tweak sensitivity to 25cm, I was talking about for CoD BO. Turns out that 2.07818 sensitivity on 800 dpi ends up working rather nicely. Also, if I ever need lower sens, I can drop it to 50cm by switching the mouse to 400 dpi, with everything still within acceptable ranges for pixel perfect accuracy.
At the risk of making myself sound like an idiot - I've seen a video or two where someone (claims) they are moving the mouse slowly across the mouse pad. They then move the mouse quickly back, and they are in a completely different spot. In fact, one person moved the mouse slowly across the pad and managed to do 3 full spins. He then moved it quickly back and it did about a 90 degree turn before stopping.
Above all, I've noticed it myself - it seems like even as infantry, when I want to move my mouse fast, it never turns as far as it would if I had casually turned to look in that direction. This is all with an MX518 and Xtrac Ripper XL pad, so neg. accel. imposed by the mouse shouldn't be a problem for me, either.
Overall, I gave up on finding a "good" sensitivity and just set it to .45 at 400 dpi. I can do everything moderately well except for snipe, and I could snipe perfectly at .50 sensitivity with my Logitech Optical Mini Mouse. But after moving to the MX518 (hard to get used to palming the mouse after clawing for 8 years), I can no longer snipe moving targets effectively, and stationary targets take time to line up - I've lost the ability to flick shot. If I even knew how the sensitivity in BC2 was scaled with itself, such as if I switch from 400dpi to 800dpi, what sensitivity setting should I drop to from .50, because it sure as hell isn't .25, it'd be a little more manageable.
|
|
|
Post by phoon on Dec 30, 2010 18:05:22 GMT -5
At the risk of making myself sound like an idiot - I've seen a video or two where someone (claims) they are moving the mouse slowly across the mouse pad. They then move the mouse quickly back, and they are in a completely different spot. In fact, one person moved the mouse slowly across the pad and managed to do 3 full spins. He then moved it quickly back and it did about a 90 degree turn before stopping. Above all, I've noticed it myself - it seems like even as infantry, when I want to move my mouse fast, it never turns as far as it would if I had casually turned to look in that direction. This is all with an MX518 and Xtrac Ripper XL pad, so neg. accel. imposed by the mouse shouldn't be a problem for me, either. I'd have to see which mouse they were using in order to make any sense of that. as far as your case goes, the mx518 is known to hit a shorter maximum speed if you are using setpoint drivers. if you're using them, I'd try uninstalling, overclocking to 500hz, and seeing if you still have the same issues.
|
|
aranshada
True Bro
But woe betide thine enemies, for thee hath created thine Bullet Hose.
Posts: 231
|
Post by aranshada on Dec 30, 2010 18:32:53 GMT -5
I have setpoint installed, but I'm pretty sure I have it overridden with the HIDUSBF driver (for the MX518, anyway) that allows me to overclock to 500Hz. I mainly used setpoint to set the polling rate on my G5 (which I actually never use now because I can't stand the feel of the material the shell is made out of - doesn't grip my hand how I like it, so I find it impossible to pick up and reposition reliably, accurately, and repeatedly).
I've read a LOT about mouse tweaking, and I even sat down and made myself read through every word of the ESReality article about testing mice.
[Edit] Took your advice and nuked SetPoint. The mouse stopped responding during the uninstall, and then windows "detected" the mouse and installed the default drivers, so I guess even with the HIDUSBF tweak it was still ultimately using the SetPoint drivers. Even if this solves my problem, though, there is still the problem of how the hell the sensitivity numbers are scaled. Currently, I'm thinking it's somewhat of an exponential scaling - hence why there's so much of a difference going from .50 to .45, but not so much from .20 to .15.
[Re-Edit] I'm not sure whether I was just imagining it or what, but after testing it out, I am sure that there is no negative acceleration, imposed by anything (game, OS, hardware) at this point. And after uninstalling the drivers and re-overclocking to 500Hz, it seems generally more responsive and easier to handle in-game than when I had the SetPoint drivers installed.
|
|
|
Post by senethro on Jan 4, 2011 7:26:40 GMT -5
Possibly related, one thing I've noticed is that at low sensitivities and DPI, theres a threshold for mouse movement below which nothing is registered. I'm guessing its related to console/joystick controls. I had to set my DPI to max and lower ingame sensitivity even further to minimize the impact of this effect. I use the following link to adjust my vehicle controls forum.ea.com/eaforum/posts/list/446923.page
|
|