Mouse has mind of it's own in Q3A on WinXP system...

[FlyingPenguin]

This is beginning to piss me off. I've got my 900 Mhz Athlon LAN party system all setup, and it was working fine until now.

Suddenly the mouse is acting up al LOT in Quake3.

Sometimes (and usually only when holding down the fire button while pressing another key - life crouching or strafing) the view suddenly rotates 180 degrees.

This isn't the mouse lag problem in XP, the mouse has a mind of it's own. Neither is it a sensitivity issue (I know that optical mice don't like high sensitivity or acceleration and it's turned off).

Even wierder - sometimes while I'm making adjustments to the key bindings using the key binds menu, the mosue will stop working altogether. Then the only way to get it back is to exit to the desktop and restart the game.

- Rebooting doesn't help

- Disabling all background apps didn't help

- Reinstalled Intellimouse (and tried it without Intellimouse installed) and it's the same.

- Tried the mouse in the PS/2 jack instead of the USB - same deal


I'm ready to restore it to an older ghost image to see if it goes away. After that all I can do is a clean install.

It seems to be a directinput issue and I've found some mention of this in the forums but no solutions.

Only other games in this system are SOF2, HL & JK2 and they all seem to be working fine.

Any suggestions?

Specs:

Athlon 900
Epox 7KXa Mobo
Geforce2 GTS
256 Mb
Onboard AC97 sound
Netgear PCI NIC
Diamond Supra Express 56K ISA modem
Microsoft Explorer optical mouse (using USB)
WinXP Pro

[Jim Z]

I've had something similar happen with my Logitec optical mouse, on nearly any system I use it on... sometimes the cursor will jump to the lower left corner of the screen for no apparent reason.

Only on XP, though... have you tried a ball mouse to see if the same thing happens?

[FlyingPenguin]

JIMZ: Optical mice are notorious for losing control when you either have acceleration turned on or use a very high sensitivity. Under those conditions moving the mouse rapidly will make the pointer shoot into a corner of the desktop, or in a first person 3D game make you look straight up at the sky during sudden turns.

All optical mice do that be they Logitech or MS. I recommend never using acceleration on an optical mouse and then keep the sensitivity at a reasonable setting.

That sound like what your problem was, but that's not my problem.


ANYWAY AS TO MY PROBLEM:

Well I THINK I fixed it.

First of all, I forgot to mention that I also deleted the q3config.cfg file which often fixes most problems. That didn't work either.

ANYWAY, since Q3 is working fine on my home workstation I just deleted the game folder on the LAN party system and copied the folder from the workstation and it seems to be working fine now - at least I can't make it act up and it used to act up VERY consistently.

Doesn't explain why it happened, but as long as it works....

[grumpy 1]

fp i guess since your using a amd system you would have a socket a m/b with a via chipset

Ive come across 3 occassions now where optical mouse suddenly leave you staring at the floor or ceiling

Dos nt happen if you put it in the ps2 port

I still think via s usb implementation is kinda buggy

Cheers

[Busby]

Have you tried the VIA USB Filter patch? http://download.viahardware.com/usbf_110.zip

[grumpy 1]

tried all the tweaks known to man
still havnt got on top of things

vias usb implementation is buggy
I like via but only for enthusiasts
If i build a box for a buisiness iLL use a celeron or something similar and a intel chipset
anything to avoid the via woes

Cheers

[FlyingPenguin]

Running SLOT A not Socket A here.

The problem I had was definately with Q3 itself. It's working fine now.

[grumpy 1]

What sort of mobo is it fp abit or something is it a amd or via chipset???
Cheers

[FlyingPenguin]

Epox 7KXa Mobo - using VIA chipset

[grumpy 1]

just for your info fp
i only use the via agp driver if i use win2k i dont wory about the bus masters or any thing else

Cheers

[FlyingPenguin]

This is an XP system and originally I was using the VIA drivers that WinXP installed.

Last week Windows Update recommended newer VIA drivers and I let it install those.