i have 3.0 and i get 0 negative acceleration
i have it on 125hz tho x:

i have 3.0 500hz 360 ~25cm no negative accel ...i tried both wmo and 3.0 they dont track same...3.0 is more smooth ...

how can be IE 3.O smoother than wmo . its not same sensor ?

it "feels" smoother because its heavier. it glides across a pad in a different way than the wmo due to its weight

yes this . but i see lot of IE3.O have 45O dpi . so maybe its realy diff

and maybe he compare wmo 4OOdpi and IE45O dpi and sensitivity changed . i realy wana hear from him in what way its smoother.

its a false reading, they only have 400 just like all the other ones.

e: I have imo 1.1a, wmo, and 3.0 legends edition. i can have them all plugged in @ 500hz and they all are the same when i move them across mousepad w/ no accel

than explayn how can ppl have difrent sensitivities with this same mouse .

I ask vo0 if he can measure hes sens he measure it twice he say 22 cm for 360 and sensitivity is 4.5

i have wmo and i need for 22cm 4.7 sens.

there are 430 dpi wmo´s

cnq3.exe cpma . no accel same pith and yaw

also there is lot of this shit on google. am not only 1 who say it

I'm not even going to bother...

cause u cant explain :D

Because it's no use and you've got the idea in your head.

Surfaces affect sensor tracking, hell even fov/resolution can change the way your sensitivity is perceived. Are your windows settings EXACTLY THE SAME AS HIS? Unless you're directly using exactly the same shit, it's going to look and feel different no matter what you do.

Why the hell are you copying settings anyways? Are you 12 and think its cool to use pr0 settingz0rs? Fucks sake.

fuck saké .

cnq3.exe dont count windows settings . It no matter 1/11 or 6/11 or 11/11 same sens in q3 ...

yes i was think about this > Surfaces affect sensor tracking ,

i play same fov and ress like him cause he pro :D ;D . when i start play any game i google some pro cfg and i keep it . pro cfg = +5 % skill for sure .

i wana buy another wmo so i let u know if its same or not

what pitch/yaw? ill try with all my mice on a steelseries experience i-2.

seta m_speed "4.7"
seta m_pitch "0.022"
seta m_yaw "0.022"
seta m_filter "0"

raw input no accel .

measure it with very low sensitivity like 40 cm for 36O if u can deppend how big your pad is . U got more accurate result.

I got ~22 cm/360 with those settings on all 3 mice. Surface seems to be a big factor. :p

i realize ^^ i play on 21 cm lol . but thanx :D

// i measure again . sensitivity 2.5 and it take and it take 39 cm for 36O . http://www.notalent.org/sensitivity/sensitivity.htm also on goliathus and on wood desk [table]

maybe it realy depend on surface or samo1 say on monitor refresh rate . i have 75

I dont think refresh matters, I'm using 140 on a crt. o.O

he is right btw, read: http://www.esreality.com/?a=post&id=2045906#pid2045906

I done my own extensive testings and I'm 100% sure.

but there is absolutely no difference between the sensor of all those mice.

long time ago a read somewhere wmos and imos have 6000fps and IE3.0 have 9000fps . maybe another difrence . but am totaly not sure and i dont care any more . heh

I read the same I think.. but I'm sure on my measurements. The FPS would only change the smoothness, not the DPI.

you are right, I have 2 wmos, 2 imos and 1 ime and all of them are 430 (done my own measurements)

how old are they?
do you know if the old IE3.0s are really 400dpi?
i've got a few newish IE3.0s and WMO1.1as and they all do over 400dpi - only realised this after comparing them to my MX518s which actually do 400dpi. i just assumed they did 450.

I have no idea when they were manufactured : /

Potentially all of them can be pretty new ones, but I'm pretty sure that the sensor stayed the same, if they somehow increased the DPI in the newer revisions, then they simply used another lens.

Are you sure your Mx518 is actually 400 DPI?

Some of Avago's sensors track more distance than others, while others track less. Switch to a different sensor manufacturer and it's the same story.

I've come to the conclusion that no sensor is 100% accurate in regards to dots or counts per inch. More than likely it's an estimate given by the company.

No!

explain

It's not a false reading, those mice have different dpi ranging from 400 to 450

Don't think so, I have the same problem (even though I'm med-sens)
Especially making quick 180 turns

It only means your sens is too low for the mouse then ( I guess more than 30cm/360 ? )

i measured and it came out to like 51cm moving my mouse as slow as possible. seems kind of ridiculous because my sens feels medium (at least aiming, like LG) and i'd like to lower it more. i cant imagine raising it any higher.

You're either strenx or crazy. Normal sensitivies range between 20 and 40cm, and usually with above 30cm ppl use accel. WMO and IE 3.0 suffer from neg accel with over> 45cm/360 but most people don't have their sens that low.

edit: perhaps you have windows accel enabled and thats why it feels so high? Since you said something about moving it slower.. that shouldn't make any difference unless you have accel.

wmo/ime3.0 hits a point of negative acceleration at 1m/s (1.55m/s overclocked)

measure out your sensitivity or calculate your real sensitivity at http://phoon.us/mouse/

measure the time it takes to complete your turn (i.e. 150ms for a 180) and see how many times it goes into a second (1s/150ms=6.66666667)

real sensitivity * 6.66666667 = max speed for desired turn

if it is greater than the mouses maximum speed before negative acceleration, you will have negative acceleration when you move it at that speed

thats the prob of 1.1/3.0. neg accel&scroll bug

*noshitsherlock.jpg*

you mean 'm/s', ms is already taken by milliseconds :p

i have corrected this crucial error

nice

In ql try in_mouse 2
Its raw mouse input, the other settings can have problems like what you describe. There is also the CQ3 client for q3/cpma which has raw mouse input.

WMO/3.0/1.1 only have a 1.55m/s perfect control rate on cloth.

It's the sensor and nothing else.

Mess around with cl_mouseAccel

is it possible to have both positive accel and negative accel going at once? or does it cancel the neg accel?

won't cancel it, but you're not likely to hit the speed at which neg accel kicks in if you use accel.