No ideas on either question? Someone's gotta know...

if you lower your win sens to the 4th notch, it will apply a 1/2 multiplier to your mouse DPI and end up with an equivalent of 900 dpi, which is close to 800 :P
No idea about the driver anyway, never used them for any mouse.

True, but honestly I'd rather just get used to 1800dpi than use a neutered sens on 1800dpi. In the mean time I think I'll just install the drivers and play with them to see how it feels and whatnot.

Yea I guess the best way to decide what to do is to try everything :)

Razer drivers use a filter that lies between raw mouse input and either Direct Input or Windows mouse input (depending on the situation). Lowering the sensitivity in razer drivers will add calculations which are done in the filter layer. You will therefore not have 1:1 movement ratio. In addition you add extra software calculations in Direct Input games which bypasses windows sensitivity but is affected by the filter layer added by logitech and razer mousedrivers.

The best solution is to lower windows sensitivity, to get the desired desktop pointer speed, since games that use Direct input are supposed to bypass this layer. For games it is better to reduce the ingame sensitivity. This allows you have maximum precission, since the direct input games receive as the highest precission data possible from your mouse.

Personally I don't like to use razer mouse drivers. When they are on the button presses feel slightly lagged and mouse movement doesn't feel as responsive.

Ah, interesting. I'll have to go uninstall the drivers then. Looks like I'm just going to either get used to 1800dpi or break down and lower the windows sens. Thanks.

You don't need to uninstall the drivers, just disable the "razerhid.exe" startup entry. This prevents the filter driver from starting. That way you can use razerhid.exe whenever you need the drivers, but it won't be active until you start the program.

But if I'm not going to use the filter, and the best way to lower the sensitivity is to lower the windows sens, then why would I even want the drivers installed for it? Unless of course keeping the windows sens at 6 and lowering the Razer driver sens does something different.

If you don't play SP games then you probably don't need drivers. Unfortunatly there are plenty of SP games that don't allow you to set the sensitivity low enough if you use low sens. Fear is one example which bypasses the windows sensitivity (it doesn't bypass the filter drivers). Having the driver installed doesn't make any difference until razerhid.exe is loaded into memory.

how do you disable the filter for logitech mouses?

Stopping setpoint.exe and khalmnpr.exe from starting with windows will disable the filter completely. If you just want to remove the filter for mouse speed and acceleration part of the filter you can use the "OS implementation" under the third tab from the top on the right side in setpoint. Using the second method allows you to keep keybinds and setting DPI in hardware while keeping a mouse movement feeling which is about the same as no driver at all.

Here's another question for you.

Let's say that games that use DirectInput are supposed to bypass any changes that you make in windows. So you're saying that if I change my windows sens to something other than 6th notch I will still have pure 1:1 movement even though it will move slower in the game because I changed the sensitivity. Is this correct? Or will I still have skewed mouse movement because the mouse data the game is being fed is data that is altered by the non-default windows sens I told it to use?

As long as it bypasses windows sensitivity you will have 1:1 movement. There are some games built on older engines that don't do this for some reason. Especially a lot of games based on the Q3 engine. These include Q3 and COD series engines which are based on Q3 engine. Quake Live does bypass the windows sensitivity. Most, if not all, engines built after windows XP was released bypasses windows sensitivity. Doom 3 engine bypasses windows sensitivity, but has a bug which makes the mouse freeze if you have high dpi and move the mouse fast. If the game bypasses windows sensitivity then your ingame mouse movements should feel twice as fast unless you change your ingame sensitivity.

Why does Q3 not bypass windows, but has DirectInput?

Not sure why it doesn't. If I were to guess, it's because it was made for an old version of DirectX used on windows 98 and older where mouse input was handled differently. For an exact awnser you would probably have to ask someone who has worked with the Q3 engine or looked at the Q3 source code.

Makes sense I suppose. Thanks for all your help.

I'd assume cnq3 uses the newest directinput so it doesn't have those problems.

Last time I tried it, I had issues running it. It would crash q3 on me. I might give it another go for shitz n gigglz

Just out of curiosity, does anyone have a solution to remove all mouse acceleration from Windows Vista?

When I first tried it out, I never tried it on 1800dpi, I always used 800dpi because that's all I ever needed and didn't want any higher. Well I tried it on 1800dpi and the tracking is a whole world of difference. This thing tracks flawlessly as opposed to half-assed like it felt with 800dpi.

exactly what i did

i own the salmosa too, but i never noticed tracking inconsistencies when changing dpi. however, i noticed that the mouse buttons don't respond all the time when at 1000HZ.

also, it tracks a lot like the deathadder, but i think it's better (or my DA is too old). i still get high lift off on all my cloth pads, tho. it tracks the best on my icemat, but the lift off is really low on the icemat - it barely has to be off the mat to stop tracking.

maybe my case is rare, but that's what i experience.

oh, and i don't use the drivers either.

I went from G1 (800dpi) to the salmosa and use it at 1800@500hz, without drivers.
I cant lower windows sens since i use raw input (sens is same ingame no matter what I set sensitivity to)
With G1 i had sensitivity 4 and pitch and yaw 0.02 =0.08, and with the salmosa i use sensitivity 2 and pitch and yaw 0.018 = 0.036, its almost math correct since 1800/800= 2.25, 0.08/0.036 = 2.222. (to get same distance for 360)

The tracking is much better than the g1, i can move the mouse across pad (45cm) as slowly i can and then do same as fast i can and it always end up on the same spot +-1cm, the g1 would always do shorter distance at higher speeds. The grip is very similar but better than g1, so i will highly recommend this mouse for those who have used g1/g3/mx300 before
The bad thing is high liftoff distance, but one will get used to it in some days. Ups went maybe a bit off topic

I am experiencing a rather strange behaviour in ql. i reinstalled razer drivers and cleaned reg, because mine (krait) had no "back to default" switch. so i had back unchanged driver sens. in win i have 6, i am comfortable with that and i wanted also to take care of the case of q3.

but now somehow no matter which sens i enter in ql most it does on my normal size pad ( 25cm) is something like a 300 degree turn. no full 360. accel is off, in_mouse is2.

from sens 2 to 4 there is a rise in degree but from that on, even if i take sens 100 no change at all.....


any ideas?

and now i recognized in q3 the internal sens setting really does something, 10 instead of 2, moved really fast

as you would expect if you change in game the sens that something differs...in ql stays the same

lol it stays the same in all 3 in_mouse modes in QL?
that cannot be.....every sens above 4 i guess doesnt make it faster. you can only get slower with, at 1 its really lowsens...


whats that for a crap`? even reinstalled QL a moment ago. whats that for an error`?

cl_mousesenscap

lol, totaly forget about that one....guess i was a little bit too stoned yesterday ;D

thx man!

I changed to wmo. Better than salmosa. Seems razer mouse are kinda slow. like playing with tft screen. Salmosa track better than wmo, but wmo dont have prediction and feels "faster"

wmo = better rocket-mouse
salmosa = better rail-mose

maybe only for me.

dunno. :)