Doh, forgot to say let us know if it works for your DA :)

upgraded, re-plugged and restarted the driver, firmware version was 1.10... BUT after the reboot the razer driver says it cannot find a mouse. Also it now shows firmware ver. N/A, the mouse is gone from device manager - all I have is generic Microsoft drivers running for the device. When I try to run firmware 1.5 boot loader it freezes and when I try that with 1.10 it says there's no need because the version matches my current f/w..........sigh


EDIT: reinstalling 1.03 drivers helped fix the issue

Let's hope this fixes the problem! :) If so ill buy the DA today..

Same here, and now I have an excuse as some of my MX518's feet are coming off :P

The first reply at Razerblueprints says the accel is gone!

Accel is gone for me

Yippie! \o/

It's sorted! :-)

2 down, 1 to go :]

A small question: once you load those drivers, do you still need to load them every time on boot to get rid of that positive accel or are the settings kept in the mouse?

edit: lol its firmware ignore the question :)

i want to buy a DA but now im not that sure , what problems still persists?

high lift off scanning

That's pretty much fixed :)

- Mousewheel-click can result in random cursor-movements in DirectInput games.
- negative acceleration increases inversely proportional to the DPI set (see DeathAdder-review)
- DPI ratio should be changed, so that 400 DPI are available (currently only 450/900/1800) - to avoid negative acceleration caused by the Windows API (in non-DirectInput based games)

Oh yeah and some other hardware-faults, which seem kinda random spread, some have it, others don't.

The negative accel is kind of a none issue though, as even at 450dpi it doesn't occur until speeds >2m/s.

don't forget holding down the right mouse button scrapes against the scroll wheel.

Doubt that can be fixed with a firmware upgrade.

I just bough the DeathAdder and brought it home for some tests. Currently the following issues has been fixed

- Positive acceleration (Firmware 1.10)

- Liftoff distance has been minimized (Firmware 1.05 and 1.10)
Funny thing though, i tested the lift off on a QcK+ before applying firmware, and it was around 3-5mm, like Sujoy tested it to be. So that may be why he didn't see any unusual results.

Now the following problems are still present

- When right mouse button is pressed, it scratches against the mouse wheel
However this is only fixable by wearing a bit on the mouse wheel, i heard from some users that it gets better over time.

- Mouse wheel is not assignable to "middle button"
I think this is a driver issue, I'll test later today if it's possible to assign middle button through the use of registry "hack".

- When right mouse button is pressed, it scratches against the mouse wheel
However this is only fixable by wearing a bit on the mouse wheel, i heard from some users that it gets better over time.

Was the same with the Diamondback for me, it seems razer ship their products very "tight" as it were, e.g. the DB buttons make a small squeeky sound for the first weeks/month(s).

Can you confirm with 100% certainty that there's absolutely no acceleration now neither positive or negative? When you move your mouse slowly to a position and then very fast back again, does the crosshair end up at the same spot?

I can conform that, i tested this quite extensively and couldn't find any trace of negative/positive acceleration (note i was using direct input)

Cool. If I buy it and it turns out to be shit, I'm coming after you man.

Hehe

DPI ratio should be changed, so that 400 DPI are available (currently only 450/900/1800) - to avoid negative acceleration caused by the Windows API (in non-DirectInput based games)

I think I have found the best solution: Mouse Force Revised

"enforcing DirectInput with compatible games."

Games like CS 1.6 or Q1/Q2 won't be affected if I understood correctly.

I don't know, but my posting wasn't about DirectInput.
It was about eliminating the cursor's limitation and thus possible "negative acceleration".

Mouse Force (a program to enforce DirectInput) will work with most id Software, non-DI engines, but some people didn't like it.
They considered this mouse feeling less responsive.

With my new approach, DirectInput isn't necessary anymore, because the cursor can move as much as you want*.

See the demonstration and you'll understand.


* effectively -32768 to +32767 per frame in game

where can I buy one?

at the deathadder store

i asked but they only had snakes, and said I should buy the mice at a pet food store. And the people there said they only have ordinary mice. Couldn't even tell me the DPI, those noobs! :(

Roflmao!!! that was one of the best jokes ive heard for a long time

what joke?

y ruin

Is it possible for Logitech setpoint and Razer Da software to coexist (without corrupting the OS), or must you use one or the other exclusively?

I *think* they can go hand in hand.

SetPoint uses its own path or whatever you want to call it, whereas
Razer drivers use the native Windows 'path'.

Some time ago, I used a Razer DB and Logitech MX310 at the same time, with both drivers installed.
Mind you, MX310 uses MouseWare and not SetPoint.

Thanks for the info, McFly.
The DA software and Logi setpoint are working together.

Well it is fixed now. So yeah you can buy it now :)

The only thing now I can moan about is wheel. First it move more slowly when right mouse button is pressed, not big issue for me. Second sometimes wheel like to give you strange sounds, however its gone for me now probably it just gone after you move scroll enough. About wheel button you can assign it to like backspace and bind backspace in game, simple.

For non direct input games, I am not sure what this is about but it is rather not razer fault but rather game developers. I am using 1800 DPI, 500Hz, windows default sensitivity, changed razer sensitivity to "between 3 and 4" in driver and I have no problems at all. I had problems with 1000Hz and Q3 tho (thats why i use 500).

I don't know if anyone have lift issues still? I never had with my old black DKT pad.

After 1.10 firmware I would score mouse for 9/10 and I don't think there is another high dpi with side buttons mouse better than deathadder at the moment. Very good shape, non-sucking cord (not like crap in MX310), good placed 2 side buttons (thats rare!), no acceleration now, no problems with drivers or firmware for me.

So which pads have good lift-off distance with the DA now?

Steelpad QCK+, Razer Mantis (according to Hardwareluxx.de-forumposts)

I've head the following pads hav good lift off

- Steelpad QcK+
- Icemat 2nd Edition, Black

Though i've heard that the Mantis is performing not so good on the Razerblueprints.net forum, there may be "isolated" cases where people are very sensitive and don't think the lift off will get good no matter what .. :-P

DKT Pad, named now as "Everglide Titan MonsterMat DKT Edition".
Tho they could changed something in last 3 years beside name.

Isn't the DKT edition the same mat as the Titan but with a different logo?

Has anyone tried the mouse with vista, i cant get the razer program to detect the mouse, so its just running using a HID driver, on the box it says it is vista compatible yet the driver on razerzone says xp only. Has anyone got any ideas.
Mike

As anyone said on another post, you can use the current WinXP drivers for DA in Windows Vista.

The only thing you need to do is enable the winxp sp2 compatibility on the setup.exe(right click) an then run as administrator(also right click in setup.exe) and here you go, you will get the drivers working perfectly

Like malum said. MIne works fine in Vista.

Beware there is acc. in Vista though. Found a fix for it at razerblueprints. (some sys file needs replacing) And the mouse.reg file will not take care of it.

Can any1 with the death adder and qpad ct or xtrac hybrid, tell us what the liftoff distance is on those pads with the newest firmware.

Also would the liftoff distance be different between the black and the white version of the qpad?

the liftoff should be just fine.
i wonder why nobody whined with the liftofff on a mx-510.
its so terrible that i put the mx-500 sensor in the shell.
Also i heard that the diamondback, so called limited edition
has a high liftoff distance.
the DA has the lowest liftoff distance ever with a fitting mousepad.

nobody ever imagined that there are going to be mice with high liftoff distance, until 1 year ago, that's why
all mice were ok from this point of view

Some people actually prefer quite a lot of lift-off distance.
Some gamers lean/tilt their mouse a lot. Very low-lift off scanning is a handicap for these gamers.

I myself prefer something in between.

Is there any download site where you still get the original, initial firmware v1.03?

I just ask this because I would like to flash the firmware to version 1.10. But if there should be issues for me or if - on the other hand - I decide to send the mouse back to amazon (within the 14 days of checking out the product), I would like to flash back firmware version 1.03.

Is amazon (or other sellers) granting a send-back permission (don't know a better term) even if the firmware has been flashed by the user who checked out the product?

Any advice welcomed, especially by Germans knowing the legal issues with firmware updates within 14 days of testing a product bought online.

many thanks