[iMoRt4l (old)]

I finally discovered today that use On The Fly Sensitivity instead of swapping my DPi's was a better way to be more accurate (Yes. I Fails.)

Only thing is, I'd like to know if the bar it shows when you use it can appear ingame. Like an overlay.

[|it|Nexu]

In my experience with Razer products it's best to leave the sensitivity alone at default (10) and changes the in game sensitivity. The reason for that is that the sensitivity settings you can change with Razer software is all (obviously) software based instead of hardware based (software based means you are dealing with interpolations). Which cause in-accuracy in minor changes, which can cause the difference between over aiming your target or hitting their torso instead of the head which you are trying to aim at.

But than i'm using DA 1800 instead of the DA 3500 (which the DA 1800 is 'better' than the 3500 from what i have read).

[Mod ObScUrE]

Nexu, on 17 January 2010 - 03:48 AM, said:

But than i'm using DA 1800 instead of the DA 3500 (which the DA 1800 is 'better' than the 3500 from what i have read).

eventually you can add your 2cents to this thread here new-razer-mouse-and-updated-deathadder-sensor/

I agree with nexu you should set it to 10 it's recommended from many players.

and adjust the dpi + in game sensitivity for your needs.

the best way to do this in game is over the console (shift+esc) /sensitivity 5

[iMoRt4l (old)]

K Thanks.

[s.e.t.i.]

i've been using razer products for years. the on the fly sensitivity works pretty good. i use 500dpi normaly with my lachesis, but i play with the settings a bit and push it to 1000dpi occasionaly. honestly, i don't think you will see all that much improvement by pushing it any higher. i could be wrong, though

make sure you add the line to your config:
seta in_mouse "-1"

this turns off buffering of mouse events and will prevent serious issues (such as a gun that won't stop firing)

[Mod ObScUrE]

Important mouse settings:

in_mouse                          "-1"                                 // 1=Directx(12ms lag/don't buffer 1000hz) -1=Windows Pointer Input (edge clipping on high dpi or low resolution)
r_finish                          "0"                                  // If You Experience The FPS Induced Keyboard/Mouse Input Lag (on trees,...) Set This To 1 (but less fps and delayed input!)

this two settings

[s.e.t.i.]

ObScUrE, on 22 January 2010 - 05:51 PM, said:

Important mouse settings:

in_mouse                          "-1"                                 // 1=Directx(12ms lag/don't buffer 1000hz) -1=Windows Pointer Input (edge clipping on high dpi or low resolution)
r_finish                          "0"                                  // If You Experience The FPS Induced Keyboard/Mouse Input Lag (on trees,...) Set This To 1 (but less fps and delayed input!)

this two settings

lol... never even seen the setting r_finish neat