Overclock.net › Forums › Components › Mice › Deathadder Native DPI
New Posts  All Forums:Forum Nav:

Deathadder Native DPI

post #1 of 25
Thread Starter 
Okay so I just got my DA 2013 and I was looking for 2 hours, at least, last night for the native CPI/DPI rates for the DA. I only found one and that is 6400. I don't really want to run my mouse at 6400 and then have to scale it way back to be comfortable for aiming in CS:GO.


My question is, does anyone know the native DPI rates for the DA2013?
Updated Build
(13 items)
 
  
CPUMotherboardGraphicsRAM
E8400 @ 3.6GHz vcore 1.28 EVGA 750i FTW XFX 5830 Corsair and Gskill 6GB total 
Hard DriveOptical DriveOSMonitor
Western Digital 150GB 10,000RPM Boot Disk Sony Windows XP 22in Samsung 
KeyboardPowerCaseMouse
Logitech POS Corsair 750w HAF 932 Razor Dimondback 
Mouse Pad
Fellowes Microban 
  hide details  
Reply
Updated Build
(13 items)
 
  
CPUMotherboardGraphicsRAM
E8400 @ 3.6GHz vcore 1.28 EVGA 750i FTW XFX 5830 Corsair and Gskill 6GB total 
Hard DriveOptical DriveOSMonitor
Western Digital 150GB 10,000RPM Boot Disk Sony Windows XP 22in Samsung 
KeyboardPowerCaseMouse
Logitech POS Corsair 750w HAF 932 Razor Dimondback 
Mouse Pad
Fellowes Microban 
  hide details  
Reply
post #2 of 25
Umm I don't know if you mind me asking, but why do you care? Why does everyone bandwagon on hating Synapse? It's not that bad, you register for it, set up your mouse, and then you don't have to mess with it again... I can turn it off, uninstall, and my DA 2013 still works with the settings I've set.

If that's not the issue, and you just care about that native dpi, I don't even think it makes a difference, because the tracking pretty much feels the same throughout.

Anyways, to answer your question, the native is 1800 (On initial plug in) but 500hz unless changed in drivers.

All the settings on the DA 2013 are good, so you can use whatever and don't have to bother yourself with scaling back your dpi.
Edited by Nilizum - 6/4/13 at 11:42am
post #3 of 25
Yeah, I had a few problems with synapse in the past but honestly, it's not that bad and as Nilizum said, I'm pretty sure 1800 is the standard DPI, and even if it wasn't, that's personally what I would choose. The DPI you choose really doesn't matter I'm pretty sure as long as you're not a high in/360 user, you shouldn't be hitting the max perfect control limit.
HAF 912 Rig
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel 3570k delid Gigabyte Z77-D3H Galaxy GTX 680 Kingston Hyper X 4x2GB 
Hard DriveHard DriveCoolingOS
Toshiba 2TB HDD 90GB Corsair Force 3 H70 w/ push/pull panaflo W7 ult. 64 bit 
MonitorKeyboardPowerCase
BenQ XL2420T w/ lighboost hack 24/7 Coolermaster Quickfire with Cherry Browns Rosewill HIVE 750w Coolermaster HAF912 
MouseMouse PadAudio
Windows Mouse Optical Puretrak Talent Fiio E7 > Denon AHD2000 
  hide details  
Reply
HAF 912 Rig
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel 3570k delid Gigabyte Z77-D3H Galaxy GTX 680 Kingston Hyper X 4x2GB 
Hard DriveHard DriveCoolingOS
Toshiba 2TB HDD 90GB Corsair Force 3 H70 w/ push/pull panaflo W7 ult. 64 bit 
MonitorKeyboardPowerCase
BenQ XL2420T w/ lighboost hack 24/7 Coolermaster Quickfire with Cherry Browns Rosewill HIVE 750w Coolermaster HAF912 
MouseMouse PadAudio
Windows Mouse Optical Puretrak Talent Fiio E7 > Denon AHD2000 
  hide details  
Reply
post #4 of 25
yeah control speed is way overrated.. only matters for people 40cm/360 plus imo
even then I dont know.
tried dragging an IMO around as fast as possible and couldnt hit any neg accel.
post #5 of 25
Thread Starter 
I never once hated on synapse in this post so I don't know where you are getting that from. I am not talking about the default dpi setting...I know that. I am talking about the native setting for the 4g sensor. There should be multiple settings. The only known one, or one I know is 6400.

The dpi does matter because I want no negative or positive acceleration when I turn around. It is high cm/360 for me I have to pick up my mouse and quick turn again in order to 360, but that is the way I like it. So again...does anyone know the native dpi settings for the DA 2013?
Updated Build
(13 items)
 
  
CPUMotherboardGraphicsRAM
E8400 @ 3.6GHz vcore 1.28 EVGA 750i FTW XFX 5830 Corsair and Gskill 6GB total 
Hard DriveOptical DriveOSMonitor
Western Digital 150GB 10,000RPM Boot Disk Sony Windows XP 22in Samsung 
KeyboardPowerCaseMouse
Logitech POS Corsair 750w HAF 932 Razor Dimondback 
Mouse Pad
Fellowes Microban 
  hide details  
Reply
Updated Build
(13 items)
 
  
CPUMotherboardGraphicsRAM
E8400 @ 3.6GHz vcore 1.28 EVGA 750i FTW XFX 5830 Corsair and Gskill 6GB total 
Hard DriveOptical DriveOSMonitor
Western Digital 150GB 10,000RPM Boot Disk Sony Windows XP 22in Samsung 
KeyboardPowerCaseMouse
Logitech POS Corsair 750w HAF 932 Razor Dimondback 
Mouse Pad
Fellowes Microban 
  hide details  
Reply
post #6 of 25
No one outside of Razer R&D can give you a 100% assured answer.

I can give you theory based on typical usb/res data and experimenting, in which case, synapse implementation on 3.5G and 3G only scales the highest native registry across every alternative CPI value while allocated data or IPS speed does not change.. Typically happens when you have or switch to multiple registry values.

3.5G is actually bottlenecked to slower speeds as synapse does not swap to the lower 1800 res.

The 3G model only has its single 1800 CPI res and is not effected, in fact performs at higher speed than it would with previous implementation on lower resolution.

4G like above does not have any speed / data variation throughout the entire range, but it's a bit different as the specific controller is very common with synapse based products. Lets say optimized and boots special features like profile saving across many computers. Unlike ghetto implementation on 3/3.5G wink.gif
Edited by Skylit - 6/4/13 at 1:07pm
post #7 of 25
I can normally spot the native DPI on a mouse easily in a blind test just by moving the cursor around. The Krait 2013 I bought (same sensor), has some kind of cursor smoothing applied which gives the cursor the same weird/laggy feel that you would get while using an interpolated setting.

So for all intents and purposes, you are *not* getting native cursor movement using any setting on this mouse and should just set it on fire and throw it out the window. It's inferior to previous generation Deathadder unless they remove the smoothing (which may or may not be possible).
post #8 of 25
Quote:
Originally Posted by r0ach View Post

I can normally spot the native DPI on a mouse easily in a blind test just by moving the cursor around. The Krait 2013 I bought (same sensor), has some kind of cursor smoothing applied which gives the cursor the same weird/laggy feel that you would get while using an interpolated setting.

So for all intents and purposes, you are *not* getting native cursor movement using any setting on this mouse and should just set it on fire and throw it out the window. It's inferior to previous generation Deathadder unless they remove the smoothing (which may or may not be possible).

Try previous gen DA w/ synapse. have fun biggrin.gif

What is your opinion on 3090 Zowie mice? They're interpolated via a more common method.
post #9 of 25
Quote:
Originally Posted by Skylit View Post


What is your opinion on 3090 Zowie mice? They're interpolated via a more common method.

I use 800 DPI so I'm allergic to Zowie. Their mice never made sense to me since Logitech lowered Avago 3090 LOD without altering DPI to some weird, unusable numbers.
post #10 of 25
Quote:
Originally Posted by r0ach View Post

I use 800 DPI so I'm allergic to Zowie. Their mice never made sense to me since Logitech lowered Avago 3090 LOD without altering DPI to some weird, unusable numbers.

Logitech didn't lower anything. They've been on the same hardware setup for years.

Sensor IC does not dictate lift off. LED and lens refraction methodology do.
Edited by Skylit - 6/4/13 at 2:16pm
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Mice
Overclock.net › Forums › Components › Mice › Deathadder Native DPI