Curse

moriz · Aug 01, 2008, 03:57 PM // 15:57

i recently purchased a razer deathadder, and as a whole i'm pretty satisfied.

however, there's one small problem: keybinds.

on my logitech mx400, i bind my two interrupts (d and e) to the side buttons, which allowed me to twitch interrupt on my right hand (which can react faster than my left). i've been trying to do the same on the deathadder, but it doesn't quite work the same way.

in the deathadder driver software, i can set the two side buttons to "advanced function", which allows for a rather dizzying array of settings. there's two main settings in advanced function: simple keystroke, and macro.

i first tried simple keystroke, and assigned d and e to the buttons. however, i can never activate skills with it. if i go into the chat bar and press the buttons, it inputs d and e just fine. it just cannot activate skills.

i then tried macro. it did allow me to activate skills, but with one problem: it only activate skills on release, and not on click. that adds a delay to all my interrupts, which is obviously not good.

so, does anyone have a deathadder, and can help me solve this problem?

Satu-Wyvern · Mar 30, 2009, 05:36 PM // 17:36

I resurrected this post because I am having the same problem.

Has anyone found the solution to this as I am having the same problem with my new death adder.

It works in all other applications.

moriz · Mar 30, 2009, 06:20 PM // 18:20

yeah. GW actually allows you to keybind to mouse buttons. basically, you add additional keybinds to the two side buttons. no need to mess with the mouse's control panel.

Satu-Wyvern · Apr 01, 2009, 10:29 PM // 22:29

Quote:

Originally Posted by moriz

yeah. GW actually allows you to keybind to mouse buttons. basically, you add additional keybinds to the two side buttons. no need to mess with the mouse's control panel.

Thanks for the help..

I wanted to have the wheel = space bar when I depressed it. I found the Razer will work if you set it as a macro but it has an odd lag.

moriz · Apr 01, 2009, 11:04 PM // 23:04

that's because the macro is only executed once you've RELEASED the button, and not on CLICK.

it's pretty awkward sometimes. though in my case, i abused the on release mechanic to "store" interrupts, which allows me to interrupt slightly better. but it quickly became to awkward to use.

Satu-Wyvern · Apr 02, 2009, 03:29 PM // 15:29

Thanks Moriz for the explanations!! I appreciated the knowledge...