Forum
Razer mice clipping problems
Created 18th February 2010 @ 11:58
Add A Reply Pages: 1 2 ... 4 Next »
I want to know if I’m the only one having this problem. I’ve had this problem with the Diamondback G3, Deathadder 3500dpi and now also with the Abyssus. If I flick right hard my mouse aim downward, if I flick really hard it goes all the way down and I end up looking at my feet and RJ-ing straight up. If I flick left it does the same, except my aim goes up and if I flick hard enough I look at the sky. This happens on both my Qck as my Destructor, so it’s not a surface problem.
These problems only show up during rocketjumps, I don’t really notice them during normal play (Link says he does gets some negetive acceleration at my settings (1800dpi, 0.85, 10sens driver, 6 win, cplmousefix) and he also confirms the flicking problem).
Could some people with Razer mice test if they have the same problem (all the new gen ones, starting with the original DeathAdder, my old Diamondback Plasma didn’t have the problem afaik. Could test it later on).
But then again, maybe it’s just me that has this problem. If I look at the sens most soldiers play on I play on such a low sens for solly.
EDIT:
Example of what happens
Start: http://i48.tinypic.com/2ur7cxj.jpg
Results:
http://i49.tinypic.com/2epjyiq.jpg
http://i46.tinypic.com/szbbr7.jpg
Last edited by Koeitje,
I don’t have any problems with my Deathadder 3500DPI @ 3500DPI, default win sens, 3 driver sens, 1000Hz, ingame sens 1. Also I use low sens while playing soldier so I move my mouse far and fast. I also get a little neg accel but not enough to notice.
However I did buy a G5 and the laser couldn’t keep up with fast movements and it would skip and also twitch to look up or down.
Last edited by Swarley,
To exclude a problem with the razer drivers or other mouse filters, please test if you still have it using this: http://www.digitalise.net/2009/04/19/rinput-131-sequential-edition-released/
Quoted from Arie
To exclude a problem with the razer drivers or other mouse filters, please test if you still have it using this: http://www.digitalise.net/2009/04/19/rinput-131-sequential-edition-released/
How does this work?
Fadestep just confirmed the DA 1800dpi does the same with my settings (it looks up, but he can’t get it to look down by moving the other way. Maybe’s to slow).
I’ve tried fiddling with the settings, like setting razer sens to minimal and compensate with in-game sens. But that didn’t make any difference. Changing DPI to 3500 also doesn’t make a difference. Try flicking faster Swarley?
Last edited by Koeitje,
Ive got an deathadder who hits its Malfunction Speed when playing with lower dpi than 1800 (deafult). TF2 is a non-direct input game which makes the mouse go to the centre of the screen every time u hit the desktop boundry. Making the only solution to
1. lower win sensitivity.
2. playing with highresolution.
In my experience lower win sensitivity works fine in winxp but win7 makes the mouse feel unprecise.
Figured it out Arie: have to point to hl2.exe. Doesn’t make jack difference though.
@ mavve: so I can use this as an excuse to buy a 30″ Dell screen?
Last edited by Koeitje,
Is this program VAC safe? As it does inject into hl2.exe.
haha no im not working for dell :)~~ lower ur win sensitivity now and shine. Or dpi @ 400 Perhaps it wont be as bad as old DA http://www.esreality.com/?a=longpost&id=1300293&page=3
U are the only one who has this problem cause ur using so low sens. I guess this is not a problem in quake for u cause its a direct input game. If it is new DA sucks :)=
Last edited by mavve,
It’s VAC safe, but I have to add ‘for now’, since Valve has a knack for killing projects like this.
It basically turns TF2’s cursor-based mouse system into a DirectInput based system. Eliminating negative acceleration caused by the cursor hitting the side of the screen of fast movements.
Have an old DA and the destructor myself, I rocket jump by flicking right myself and have never experienced this.
I also have this problem. I have a Lachesis at 3000dpi, 6 win sens and 1.4 in-game, 1240×1024 resolution (7.5cm for 360 turn). I think it happened when I was moving the mouse really fast, but now I did that r-input thingy and no matter how fast I move the mouse around I can’t seem to replicate the result. So I guess that fixed it?
Oh and I wasn’t experiencing this when rocket jumping, rather when trying to aim.
BTW, I guess that once you run r-input, the dll stays “injected”? If so, how can I remove it? Sorry, but there was no readme in the downloaded archive.
Last edited by metalpiss,
Quoted from Anathema
Have an old DA and the destructor myself, I rocket jump by flicking right myself and have never experienced this.
Sens? Because I have like a 35-40cm 360 (guess, I’m @ uni now so can’t test it)
I’m also curious about other mice brands.
Last edited by Koeitje,
Quoted from metalpiss
I also have this problem. I have a Lachesis at 3000dpi, 6 win sens and 1.4 in-game, 1240×1024 resolution (7.5cm for 360 turn). I think it happened when I was moving the mouse really fast, but now I did that r-input thingy and no matter how fast I move the mouse around I can’t seem to replicate the result. So I guess that fixed it?
Oh and I wasn’t experiencing this when rocket jumping, rather when trying to aim.
BTW, I guess that once you run r-input, the dll stays “injected”? If so, how can I remove it? Sorry, but there was no readme in the downloaded archive.
Restart TF2. It just injects in memory.
Quoted from Arie
[…]
Restart TF2. It just injects in memory.
Oh…well in that case, even without that dll I can’t replicate the result o_O…strange.
Add A Reply Pages: 1 2 ... 4 Next »
content rss
