I've got 2 installs of quake on my pc, one on D: other on C:.
On the C: side is for offline play and screwing around with quake in general, D: is the side I use for online play. Problem is the mouse seems to drag while playing while over on the C: side all is fine.
So far I've tried making a new config and moving the config from C: to D:. Mouse still drags...
Anyone had this problem before?
edit: All mods as well. When I move the mouse slow it doesn't even respond, but when I move it "faster" it seems normal...
Mouse problem
-
[xeno]Julios
- Posts: 6216
- Joined: Fri Dec 10, 1999 8:00 am
what do you mean by drag exactly?
It would be good if you could quantify your mouse dynamic to see the difference.
On a C: instance, measure how many inches you need to move your mouse to do a 360.
Do it slow, then medium, then fast. See if the results are consistent.
Do the same on D: and compare.
Also, be sure that you really are running a clean config. Delete the q3config.cfg in all your quake3 folders (including baseq3), and make a new one.
Only other thing I can think of is harddrive performance which is introducing choppiness.
It would be good if you could quantify your mouse dynamic to see the difference.
On a C: instance, measure how many inches you need to move your mouse to do a 360.
Do it slow, then medium, then fast. See if the results are consistent.
Do the same on D: and compare.
Also, be sure that you really are running a clean config. Delete the q3config.cfg in all your quake3 folders (including baseq3), and make a new one.
Only other thing I can think of is harddrive performance which is introducing choppiness.
Well, I got it working.
I just put D's config over on C and made D my mapping install and C the online install. Seems to be something borked in the pak files or sommat?
But it's working fine for now (the one that matters anyway) The mapping install I'm not worried about too much as this problem doesn't bother while testing a map.
I just put D's config over on C and made D my mapping install and C the online install. Seems to be something borked in the pak files or sommat?
But it's working fine for now (the one that matters anyway) The mapping install I'm not worried about too much as this problem doesn't bother while testing a map.