- Dec 31, 2007
- 14,462
- 1
- 40,780
Its an old Geforce2pro on a KT333 running win2k... latest detonator drives 42.81 or something similar.
Ive had this problem for ages.
To keep things simple i experience.
A. Laggy/sluggish 3d behavior, but not "choppy" (the framerates are acceptable)
B. mostly when playing certain 3d games and moving using the mouse... movement seems to lagg behind actual mouse movement in a wierd fashion.
C. seen it in many games, under many chipset driver revisions, 2 different win2k service packs and at least 10 different Detonator revisions.
D. most noticible in serious sam, less so but still there in serious sam the second encounter. Also badly in Unreal Tournament (the original). In serious sam the problem is worse in openGL. With UT its much worse in direct3d. Return to castle wolf seems unaffected, UT2003 demo is only minorly effected. Need for speed porsche is unaffected.
E. increasing resolution or graphics detail makes the problem alot worse (increases lag time and makes accurate aiming impossible) even as low as 800x600 can be significantly effected while the framerate is still between 60-80.
F. going from 32bit gaming to 16bit helps a little, but not allways.
G. ive also gone from p2 kb + mouse to usb kb + mouse stll having the same problem.
WHY IS THIS SO???
Ive tried everything under the stars with no efect. Im thinking it could be IRQ sharing.
Dones anyone have any info on how that can effect gaming.
Most devices including the video card, sound card, NIC and others are assigned IRQ11 by win2k.
any other out of the world ideas?
<b>Anyone claiming they can see the difference
between 450 and 500 FPS in Quake3 deserves to
be severely beaten with a rock.
</b>
Ive had this problem for ages.
To keep things simple i experience.
A. Laggy/sluggish 3d behavior, but not "choppy" (the framerates are acceptable)
B. mostly when playing certain 3d games and moving using the mouse... movement seems to lagg behind actual mouse movement in a wierd fashion.
C. seen it in many games, under many chipset driver revisions, 2 different win2k service packs and at least 10 different Detonator revisions.
D. most noticible in serious sam, less so but still there in serious sam the second encounter. Also badly in Unreal Tournament (the original). In serious sam the problem is worse in openGL. With UT its much worse in direct3d. Return to castle wolf seems unaffected, UT2003 demo is only minorly effected. Need for speed porsche is unaffected.
E. increasing resolution or graphics detail makes the problem alot worse (increases lag time and makes accurate aiming impossible) even as low as 800x600 can be significantly effected while the framerate is still between 60-80.
F. going from 32bit gaming to 16bit helps a little, but not allways.
G. ive also gone from p2 kb + mouse to usb kb + mouse stll having the same problem.
WHY IS THIS SO???
Ive tried everything under the stars with no efect. Im thinking it could be IRQ sharing.
Dones anyone have any info on how that can effect gaming.
Most devices including the video card, sound card, NIC and others are assigned IRQ11 by win2k.
any other out of the world ideas?
<b>Anyone claiming they can see the difference
between 450 and 500 FPS in Quake3 deserves to
be severely beaten with a rock.
</b>
Facebook
Twitter
Instagram