Overclock.net › Forums › Components › Mice › Roccat Savu - Unstable poling rate
New Posts  All Forums:Forum Nav:

Roccat Savu - Unstable poling rate - Page 2

post #11 of 28
Thread Starter 
Quote:
Originally Posted by Czarnodziej View Post

I think it is faulty hardware. Have you tried contacting Roccat tech support? They are very responsive.

Should be the next step, i just wanted to check what results other Savu users here get.
post #12 of 28
Quote:
Originally Posted by Thunderbringer View Post

Should be the next step, i just wanted to check what results other Savu users here get.

I think a macro key froze on me once, and I had to press it again to release it. I'm on 1000Hz.
It's a preset macro, which I think is the Ctrl+R combo for browser refresh.
post #13 of 28
Quote:
Originally Posted by Thunderbringer View Post

Freeze o.b. situation: happens to me ingame about every 3-7 minutes that either the m1 or* m2 freezes (remains active- fires etc.) until i click it again, im not 100% sure here but i think it is related with fast mousemovement/actions, for example when i do rocket jumps, or fast swipes and very shortly after it use either m1 or m2, this is the typical situation. This with the Savu only when set at 1000hz.
*sry, my bad
Yes i have already done that, my neighbours pc (win7Pro32) another (win7 64 bit) pc and my pc tongue.gif. All with the same results.

Sounds like in_mouse 1 is being used tongue.gif

I'll test it when I'm in front of the pc
post #14 of 28
Thread Starter 
Indeed, in 1.32c in_Mouse 1 is set (directinput). In cnq3 and dfengine there is a raw input option aswell. Is this the way to go?
post #15 of 28
Quote:
Originally Posted by Thunderbringer View Post

Indeed, in 1.32c in_Mouse 1 is set (directinput). In cnq3 and dfengine there is a raw input option aswell. Is this the way to go?

in_mouse 1 is the "broken" DirectInput method in Q3 1.32

You might wanna test again with in_mouse -1, or, if using any other client executable, whatever it is that does not use the original DI implementation on Q3.

As far as I remember, I had the bugs you experience with absolutely every mouse on Q3 with in_mouse 1, some were better and some worse, but they all were glitched in a way, but it wasn't the fault of the mice.
post #16 of 28
Thread Starter 
No freezes anymore at 1000hz with raw input! Cant ask for more. I owe you a drink! teaching.gifyessir.gifthumb.gif
post #17 of 28
I readed the title and was like - "hardware-related issue on Savu? how? this is the most thing about this mouse!" biggrin.gifrolleyes.gif
post #18 of 28
Quote:
Originally Posted by DeMS View Post

in_mouse 1 is the "broken" DirectInput method in Q3 1.32
You might wanna test again with in_mouse -1, or, if using any other client executable, whatever it is that does not use the original DI implementation on Q3.
As far as I remember, I had the bugs you experience with absolutely every mouse on Q3 with in_mouse 1, some were better and some worse, but they all were glitched in a way, but it wasn't the fault of the mice.

Didnt Q3's Direct input use windows calls for sensitivity? :\
post #19 of 28
Quote:
Originally Posted by Skylit View Post

Didnt Q3's Direct input use windows calls for sensitivity? :\

That is in_mouse -1
in_mouse 1 used DI to capture mouse movement

Always talking about vanilla q3 here, no mods.
post #20 of 28
Quote:
Originally Posted by DeMS View Post

That is in_mouse -1
in_mouse 1 used DI to capture mouse movement
Always talking about vanilla q3 here, no mods.

Ya. I actually loaded it up, no mods. Windows sensitivity effects in_mouse 1 and in_mouse 2. ;o
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Mice
Overclock.net › Forums › Components › Mice › Roccat Savu - Unstable poling rate