its the first gen 3g, 1800 model. by usable i mean its way too sensitive unless i lower it. even on 1300 i move the mouse ~3cm and its the other side of the screen. yes, adapting ingame sens was unavoidable, not what i wanted when i was just trying to fix it, but better in the end if im no longer using 'bad' settings.

i did manage find something on this topic after posting this actually:
http://www.urbanterror.info/forums/topic/19939-razer-deathadder-3500-dpi-on-the-fly-sensitivity/

an urbanterror (quake mod) forum nontheless, nerds they say about it causing interpolations, which makes sense. wish i'd understood this 5 years ago.
i think i remember skull saying he used this mouse with max dpi and sens, on a crt? for someone i believe had a low sensitivity, it never made sense to me how he controlled windows with it this high.

i put off installing the cloud based crap for years, but i have no option now. i see alot of people dis-like the drivers and remove them, but i dont have such issues. just wondered why they removed functionality.

@gmz the drivers and their options are different depending which mouse you have. i have a mamba with legacy drivers on another machine and it looks verry different.

The mouse broke when another usb device was constantly connecting/disconnecting due to a bad cable, suddenly the light on the mouse went out and no movement - unplugged it and plugged back in and still no power to the mouse.
I uninstalled the driver (I still had the same exe to re-install it afterwards), widows detected a new device and installed a random driver unrelated to the mouse. Perhaps the firmware had become corrupt. re-flashing it allowed windows to detect and install the correct driver again. (maybe I'm remembering this wrong, it was a few months ago and late at night, I found a forum with some very specific instructions to resolve this)

I don't have any older versions of the driver or firmware, just the latest legacy driver from their site. They install fine and it appears to work, but every 10 seconds it would stop responding for a second and if u watch the pulse led it would also cut out for a split second. I think it's a combination of more recent firmware and legacy driver. not sure, too much hassle to worry about. Synapse driver works flawlessly with it, so I suck it up and adapt to it.

I can now see it a gd thing they removed that option, it should never have been there in the first place really. Now users get the sensitivity they set from Windows and the dpi chosen in the driver without the added complexity of an aditional sensitity option that causes interpolation and ultimately screws up precision. Conflicts with your dpi setting I assume.

So here are some scenarios:
Windows sens always 6 for known reasons.

-If using legacy driver and 1800 model, max sens in driver, and dpi of your choice
(bear in mind the possible negative accel at less than 1800 - mirc mentioned)

-If using synapse, you're forced to use max sens anyway. Select comfortable dpi for windows, and change it when gaming.

If you can use no razer driver at all and its comfortable - thumbs up, you're gd to go.

At least I learnt something from the rant. This all happened months ago so I already got used to it, but changing dpi just when launching q3 sucks a bit.
i still feel like im doing something stupid with the dpi, oh well.

Yes im using that too, thanks Gd link worth trying if anyone hasn't heard of it. Includes an undo option aswell.