Jump to content
Compatible Support Forums
Sign in to follow this  
Zaragon

Keyboard lag in NFS 3

Recommended Posts

Anyone else having keyboard lag problems? It's not the frame rate or the drawing speed, the game seems really smooth and runs fast. It's just like a delay between when I push a key and get a response. I find myself turning into walls, off the road, etc and redlining for a few seconds before the shift takes. Running it in any sort of compatibility mode caused horrible pausing in the game play and menus. (like half a second every 2 seconds).

 

It doesn't SEEM to be a problem in Porsche Unleashed or High Stakes. I couldn't tell you offhand what mode PU is running in, but High Stakes and Hot Pursuit are running in D3D mode.

 

Problem didn't exist in Win98SE which I had up until saturday when it spontaneously imploded.

 

System:

WinXP Home Edition

Athlon 750

512MB RAM

DPT 2144UW SCSI Host Adapter

Plextor CD ROM (40max I think it is)

Voodoo 5500 video board (I have a set of 3rdparty drivers from voodoofiles).

 

Haven't had too much trouble installing things, though.

Share this post


Link to post

Not NFS specifically (I don't own it) but I'm having the same problem here - although you can add the mouse 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 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

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

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×