I move around with the keyboard, and turn / look with the mouse, thus I often press two keys at the same time, while moving the mouse.

Whenever two keys are pressed down simultaneously, it seems that mouse acceleration is in action, since the mouse movement is slower to a certain point, the suddently much faster.

This is so annoying that I'm almost reinstallign 1.17.

Anyone else had this problem?

In game, bring down the console by pressing the ~ key

Type the following, each followed by an enter

/r_swapinterval 0
/m_filter 0

Those two options alone can cause your mouse to lag excessively especially when you're in a firefight.

/cl_mouseaccel 0

quote:

---

Originally posted by fury:
Type the following, each followed by an enter

/r_swapinterval 0
/m_filter 0
/cl_mouseaccel 0

This will make sure you DON'T have mouse acceleration on

---

But I allready have these in my q3config.cfg file. I guess they aren't case sensitive.

I'll try to input these commands after the game have started to see if it makes any difference. (Have to wait after working hours..)

quote:

---

Originally posted by Lindi:
This isn't the "flipping out" that people have reported while using an optical mouse?

---

It might very well be. I've used an intellieye mouse in the past on both computers, with installed MS Intellipoint software (and DX8 if that matters), but one of the machines currently has a normal mechanical mouse. I'll try to uninstall the intellipoint software and try again.

Do you have any link to discussion on the "flipping out" topic?

This is a very serious problem. 1.27g is unplayable for me.

(Interview with Robert Duffy) We fixed the mouse wheel bug by properly initializing direct input. This appears to have caused the mouse acceleration settings from windows to show up in the game. You can fix this by either turning OFF mouse acceleration in windows or by adjusting the m_pitch, and sensitivity values until your mouse feels right. We have only had this reported on a few mice.

Hmm, seems it affects atleast Windows 2000 (with DX8) with microsoft mice.

I'mm try the m_pitch value then, but I actually thinks that it might be dropping motion commands (that's what it feels like).