Hi. I just got my hands on a razer boomslang 2000. The guy said to me he had only used it for 1 hour. I can tell by the feet it was used for atleast 12 hours.... maybe more - but still it is in excellent condition (atleast visually). The mouse feels great and I REALLY WISH i could actually use it. but.
I am having a serious problem with tracking. I am very angry because I am really wanting to test this mouse the way it was and I had a friend who had it before and I can almost guarantee it didn't do what THIS ONE is doing.
ive tested it on the func F30.r pad and the steelseries qck hvy and it does the same thing so Im pretty sure its not pad related.
When I move the mouse even ... remotely quickly, the tracking fails and the cursor shoots up slightly. I want to strongly emphasize remotely ... I'm not talking about a "fast" or "quick" movement. I'm talking a 90 degree turn in game. Granted I play low sensitivity but there is no way this is how it is supposed to be. I'm playing at windows 6th notch, no enhanced pointer precision, default razer sens (installed driver - and even thought it allows me to access it it is not actually effecting the mouse (because i changed mouse4 to keyboard k and it doesn't work). im on vista. and in game counterstrike source at .4 sensitivity. its .4 cause this mouse is 2000 dpi. I cant possibly use it - I cant even turn a 90 degree turn unless i do it pretty/very slowly... when I move it to turn you can hear the ball spin but the mouse is not registering the motion. ... maybe there is something i can do to "clean" or "fix" it. I don't want to complain to the seller unless I know for SURE that it is messed up.
The original 3.0 microsoft explorer mouse at 6000 frames per second malfunctions at 1m/s or 2.5 feet a second. This feels like ... .3 m/s or 1.2 feet a second approx. No serious player would use this unless they were playing VERY high sensitivity.
Is this possibly how this mouse works - (in which case no one would ever use it... )...
Thanks for your time and energy and I really appreciate your reading this.
I am having a serious problem with tracking. I am very angry because I am really wanting to test this mouse the way it was and I had a friend who had it before and I can almost guarantee it didn't do what THIS ONE is doing.
ive tested it on the func F30.r pad and the steelseries qck hvy and it does the same thing so Im pretty sure its not pad related.
When I move the mouse even ... remotely quickly, the tracking fails and the cursor shoots up slightly. I want to strongly emphasize remotely ... I'm not talking about a "fast" or "quick" movement. I'm talking a 90 degree turn in game. Granted I play low sensitivity but there is no way this is how it is supposed to be. I'm playing at windows 6th notch, no enhanced pointer precision, default razer sens (installed driver - and even thought it allows me to access it it is not actually effecting the mouse (because i changed mouse4 to keyboard k and it doesn't work). im on vista. and in game counterstrike source at .4 sensitivity. its .4 cause this mouse is 2000 dpi. I cant possibly use it - I cant even turn a 90 degree turn unless i do it pretty/very slowly... when I move it to turn you can hear the ball spin but the mouse is not registering the motion. ... maybe there is something i can do to "clean" or "fix" it. I don't want to complain to the seller unless I know for SURE that it is messed up.
The original 3.0 microsoft explorer mouse at 6000 frames per second malfunctions at 1m/s or 2.5 feet a second. This feels like ... .3 m/s or 1.2 feet a second approx. No serious player would use this unless they were playing VERY high sensitivity.
Is this possibly how this mouse works - (in which case no one would ever use it... )...
Thanks for your time and energy and I really appreciate your reading this.
9373 Hits