..::G5 Question::..
Hey all. I was wondering if you could help a girl out. I have been having this issue with my G5. Let me start off by saying that I did exchange it and am still having the same issue. The issue is that while in quake, it will at times not fire or continually fire, as if the button were stuck (although i know it is not). It is very sporadic. I will say that it can happen 5-6 times during a game. The problem of continually firing seems to be fixed if i click fire quickly. I have talked to Logitech, they ultimately told me to try exchanging the mouse- I had only had it for 4 days. I returned it and got this current G5, and it started with the same problem the night I took it out of the package. I have tried the mouse with and without the various versions of Setpoint software that Logitech offers with the G5. Any guidance would be greatly appreciated.
Thanks in advance,
Keres
Taken from the Razer FAQ:
Try typing this in the Q3 console:\in_mouse -1
\in_restartThe 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.
this problem is when in background is ruing programs which are using cpu too. q3 is very sensitive on it and when one program uses cpu time and u will press fire button it will be holded its not only problem with g5 but with other mouse runing on usb port rate 500 hz or more I happend on my all g5s and mx 518.
u can change usb port rate in setpoint (versions 3.30 and up - if u good remmber) to 125 hz or 250 hz.
this problem is when in background is ruing programs which are using cpu too. q3 is very sensitive on it and when one program uses cpu time and u will press fire button it will be holded its not only problem with g5 but with other mouse runing on usb port rate 500 hz or more I happend on my all g5s and mx 518.
u can change usb port rate in setpoint (versions 3.30 and up - if u good remmber) to 125 hz or 250 hz.
I have a Razer Diamondback and it
Happens too
FEL!X wrote:this problem is when in background is ruing programs which are using cpu too. q3 is very sensitive on it and when one program uses cpu time and u will press fire button it will be holded its not only problem with g5 but with other mouse runing on usb port rate 500 hz or more I happend on my all g5s and mx 518.u can change usb port rate in setpoint (versions 3.30 and up - if u good remmber) to 125 hz or 250 hz.
I have a Razer Diamondback and it
Happens too
like i said on every mouse ruing on higher usb port rate than default even on default i can happen. Its not mouse problem but quake 3 and oversensitivity on fps drops. It never happpend when i was playing cs even when i have mouse set on 1000hz
Thank you so much for the quick reply, Anemic! I will give it a whirl and see what's up. You are DA MAN!