G5 Problems
both the g5 and razor share this issue at times. there is a buffer used for these mice and it seems to get backlogged so to speak. Actually I use the razor and switched from the g5 and find the razor to have more issues. But it also is more accurate. Remove the logitech software and reboot and see if it happens without software. then re-install and play with the rates for the mouse. There is also a setting in q3 for setting this buffer. You can find the setting at razors support page under copperhead. This will correct the issue for the g5 as well.
i have searched for this article on razer supportpage and i found this ...
PROBLEM
I mainly play Quake III (CPMA mod) and when I move the mouse rather quickly and shoot (left click) at the same time, it is frequent that the mouse does not detect the click. It has become practically impossible to rocket jump...
Another problem is that when I fire once by simply left clicking, the mouse often acts as if I was keeping the left click button pressed, and will fire continuously until I click the left mouse button again.
This also happens when I play Quake III in another mod (OSP/baseQ3/etc).
These things happen really often and make the game unplayable...
I am using the latest drivers ( 6.09) and firmware (6.17i).
SOLUTION
"Try typing this in the Q3 console:
\in_mouse -1
\in_restart
Or just put the variable seta in_mouse "1" in ur q3config to -1
The standard input method for Q3 is buffered DirectInput (in_mouse 1), and it receiveing mouse reports at 1000 times a second could cause the buffer to chocke up and disregard some mouse events, as the buffer size is pre-defined and IIRC not dynamic.
in_mouse -1 reverts Q3 back to standard Win32 mouse handling, which is event based an has no buffer.
Use in_mouse -1, as the DI implementation has about 12ms lag, and the non-DI implementation has no lag. The only problem with in_mouse -1 is the risk of mouse movement being clipped by the edge of the screen, which is a fairly large problem in CPMA. At 640x480 at 125 FPS you will most likely will run into this problem, and the best way around it seems to be using On-the-Fly sensitivity to reduce your mouse to about 800dpi (or you might be able to do just that thru the Razer control panel) and adjust your Q3 sensitivity accordingly.
edit: i have played 3-4 1on1's and some freeze and it seems like the problem is solved with this here ... nice thx budman ... should be made as sticky
./Base
Hm es kommt aba auch draf an welche razer er nimmt!
Also ich habe keine probleme mit der razor Diamonback ^^