Blur Busters Forums

Well, that's interesting. At least now I know for sure to set pre-render to 1 instead of "use application setting".

Might come down to roughly the same with both... now that I know why the cursor feel changes so drastically I am less skeptical about the drivers. It is however a fact that benchmarking and all that concentrates exclusively on raw framerate performance and a bit on frametime performance on the side....

But in 1.6 the framerate is synchronized to tickrate. You notice that when you lag and drop frames and when you go above tickrate amount of frames via developer 1 - which changes the physics of the game. In GO every client frame is not a tick frame but an interpolated frame, which has its advantages...

I knew the cursor was treated differently in the rendering process, but I didn't think about the possibility that proprietary drivers sync the cursor to vblank while default don't. Do you know if the desktop is always vsync'd or only with aero? I guess the explorer/interface simulation steps are tie...

That would explain that... Is the cursor position update rate in Windows equal to polling rate? What is the simulation interval (framerate) of a desktop environment without VSync?

@ flood: It's not that I disagree with you but when you have the time you should check lag with and without NVIDIA drivers. Sure, it doesn't affect input lag, rather perceived input lag or "output lag", but it's very obvious both from a "cursor feel" perspective and 1kfps footage. In general I think...

NVIDIA drivers cause input lag. Easy to notice when you uninstall them and use the Windows default driver. I have no desktop experience with AMD cards so I cannot say anything about that. In regards to what shish_KEbOB said about pre-rendering, it does sound reasonable that NVIDIA compromises respon...

Cannot confirm transfer size dependencies as I'm limited to numpad keys. When I actuate a second key without releasing the first I'm seeing large variance in the results, but in rare cases it does indeed go as low as ~1.5ms.

Two keys. I know that it isn't where the matrix scan caps out because with USB I can hit 1ms.
Either PS/2 operation changes something there or it's simply PS/2 having a maximum sample rate of 360Hz.

Thanks for the results. I have been using PS/2 over USB despite my keyboard having 1kHz support because I don't like the processor having to maintain strict intervals for both the mouse and keyboard. Although I'm convinced 1kHz USB is faster than PS/2 (over the latter my keyboard maxes out at ~2.7ms...