the-bruce 0 Posted October 20, 2001 Have installed xp everythings running fine, but when i play q3 online i'm gettin mouse lag (delays in turning etc) i have a microsoft optical mouse, with the latest xp drivers,i have had to go back to winme for just now without any probs. any help would be much appreciated Regards Share this post Link to post
pmistry 0 Posted December 2, 2001 I have this exact same problem and it is one of the only reason I have WinME still lying around. I use a PS/2 mouse, generic brand, no problems turing in WinME or Win2k, in XP even with a ping of 50 I feel like I am playing on a 150 server. Share this post Link to post
bsleek 0 Posted December 4, 2001 Same problem here - although you can add the keyboard to my lagged out controls. They overreact as well. I've turned off mouse accel'n and updated my drivers with Logitech's supported ones. I'm using the cordless Desktop keyboard (PS2) and Logitech Optical Wheel mouse (USB). I've updated XP with the compatibility updates and enjoyed no success. Interestingly RTCWolfenstein works perfectly. Hmmmm. Any advice? Share this post Link to post
bsleek 0 Posted December 5, 2001 I posted this under the NFS lag thread as well. ----------------------------------------------- OK, I've fixed my problem - although chances are slim that we're in the same situation. I was running the program from a batch file under windows 2000 in order to specify a process priority of 'high'. Even though I had removed the process priority switch I was still calling quake3.exe from the batch file. Running the program directly solved the problem. I guess me can assume that XP handles DOS batch files (and therefore command interpreters like cmd) diffrerently from 2K. Not hugely, but enough to play havoc with my inputs. Cheers, bsleek Share this post Link to post
pmistry 0 Posted December 5, 2001 I was running Q3 natively by double clicking it in Explorer or off of the start menu. Mouse lag is there and very annoying. I want to run XP solely and not put up with a dual boot anymore, but these little quirks are preventing, hopefully a fix or an acknowledgement from MS or a mouse vendor can clear this issue up. Share this post Link to post