didn't gave error when removed then again using rem cant harm
uh-huh.. okay I'll give it a tryZero!. wrote:
you have to put "rem" in front of those otherwise it will case errorsTeeZ75 wrote:
ControlMap.addAxisToTriggerMapping c_PINextItem -1 IDFMouse IDAxis_2 0
ControlMap.addAxisToTriggerMapping -1 c_PIPrevItem IDFMouse IDAxis_2 0
remove those 2 lines and the mouse wheel will no longer work
so it would be
rem ControlMap.addAxisToTriggerMapping c_PINextItem -1 IDFMouse IDAxis_2 0
rem ControlMap.addAxisToTriggerMapping -1 c_PIPrevItem IDFMouse IDAxis_2 0
Thx for help but none of this works. I'm gonna send my mouse in for repair/reclamation. Probably get a new one. Still love Copperhead. It's just this problem that annoys the hell out of me.
Just wondering, does it do it in other games/apps?
If it's just doing it in BF2 then there's no need to repair the mouse.
If it's just doing it in BF2 then there's no need to repair the mouse.
Dude just pop the base off and give it a clean, sounds like it just got shit jammed in it.
Yes the base is meant to come off (you can buy weighted replacement bases so it is actually meant to come off lol)
Yes the base is meant to come off (you can buy weighted replacement bases so it is actually meant to come off lol)
I've sent the mouse in for repair. The problem was not just for BF2, it happened in other apps as well (such as fireforx that I'm using now. Only thing I fear now is that the problem can be related to windows and not the mouse. I'm using a old HP mouse right now and the problem has ocurred also here.
Wasnt the mouse then my friend ;(
Should have checked it with the other mouse first. Common sense with hardware issues is that you test the problem by swapping out parts before deciding that the 'problem piece' needs replacing