sensitivity 13.37
accel 0
m_yaw 0.0084
m_pitch 0.0085
dpi 800 (i think)
in_mouse 2
m_filter 0 (might up it to 1 or 0.5 soon)

my internal sensitivity is 20.445 though

(your internal sensitivity is [sens * m_yaw * 65536 / 360])

i get about 6cm/360

sens 4.25
accel 0.1
yaw/pitch 0.018
dpi 450 (abyssus)

cypher fanboi :/

edit
26.562091503267975cm/360

u ain't the real fanboy..cypher uses sens 4.75, accel 0.08.:DD:

since when?? :O gotta stay updated then!

ugc settings dawg

Yeah, and you gotta switch back to russian style.

i actually played like that the last 2 weeks and it i don't feel like playing better or worse than having the keyboard on the desk :d

russian style is very comfortable, i played like that for many months.

however i have a new kb and the cable isnt long enough so its back up on the desk

sens 4.5
accel 0.2
yaw/pitch 0.018
dpi 450 @1000hz (abyssus+ goliathus speed alfa)

4.5 sens @ 400dpi - wmo

Mouse Razer DA
Mousepad qck+
Sens 1.1
accel 0.1
yaw/pitch 0.018
dpi 1800


OT: Im looking for a new mouse thats similar to Death Adder.. atleast the size of it. Any suggestions?

Zowie EC1

wmo
yaw/pitch 0.022
sens 4
accel 0.1

this + 1000hz

Using the divine WMO 1.1@400dpi
I think sens 5, accel 0.40, default yaw/pitch/that useless shit

Feels amazing.

wmo @ 500hz
pitch .021 yaw .022
sens 4.25
accel 0.2
pad is old black goli speed alpha version.
feels like robot :o

DA 3.5 @ 500hz

3.5 sens
.021 yaw/pitch
2 accel (accelstyle 1)

.. stable 31cm/360 until i move fast

what happens when you move fast?

accel begins to kick in after passing a speed defined by "offset" (with style 1 that is)

No, the mouse accel starts instantly, even with cl_mouseaccelstyle 1.

You can also approximately convert between the old and new accel styles. I say approximately because the old accel style has an extra term that gives mouse accel even if your sensitivity is 0, whereas the new accel decreases smoothly to zero as you lower your sens.

For comparison:

cl_mouseaccelstyle 0:
cl_mouseaccel controls the "multiplier" of the accel. The number that defines the "curve" is always 2.


cl_mouseaccelstyle 1:
cl_mouseacceloffset controls the "multiplier" of the accel, except for the sake of comedy it's approximately 1 divided by the multiplier from cl_mouseaccelstyle 0. Don't set this to zero.
cl_mouseaccel now controls the "curve". Set to 2 for the old style of behavior. If set to 1 you'll have approximately no accel, as your acceleration "curve" becomes a straight line. If set between 0 and 1 you'll have negative accel.

Sample conversion: sens 4, cl_mouseaccel .1, cl_mouseaccelstyle 0 --> sens 4, cl_mouseacceloffset 7, cl_mouseaccelstyle 1.

4 sens
0.022 pitch/yaw
no accel
m_filter 1
abyssus 450 dpi @ 1k hz
goliathus speed alpha

23 cm/360

WMO @ default Hz (400 DPI ofc)
default Pitch & Yaw
2.8 sensitivity
0.1 mouse accel
100 ingame FOV
about 45cm / 360 or length of QcK+

400 DPI ofc

Recently I've switched between WMO and Abyssus quite often but despite adjusting sens it didn't feel the same... so today I measured with a ruler and in fact my WMO has ~420 DPI

yeah, same with my 3.0. My wmo has 400 though.

sens 4.15
accel 0.006
wmo 1.1

4.2 sensitivity

logitech mx518

inverted mouse

I do it my way bitches!!!!! :D

sensitivity 57.14
accel 0.0043
m_yaw 0.0018
m_pitch 0.000002
dpi 5400
in_mouse 2
m_filter 1

I hit stable 45% shaft with this..
GO TRY IT OUT NOW!!!

obvious troll is obvious

I just don't believe in sensitivity changes....

Dude if someone plays with 100 or 0,000000000000000001 and changes to a solid 5 it'll work out better... but if someone is used to a value, there really is no point in switching unless it's far more comfortable, because his acc will drop until he gets used to the another value....

I've yet to see someone owning like strenx with the same setup

the only thing this thread can offer is that we can see what's the average sens

fixed my pyra now ;)

800dpi

sensitivity "1.35"
cl_mouseaccel ".25"
cl_mouseSensCap "5"
m_filter "1"
in_mouse "2"

abyssus 450 dpi
m_cpi 450
sens 14.4
25 cm/360
no accel

10 years of gaming, numerous threads about mice and sensors and you still can't say your sensitivities correctly...

400 dpi
11-12cm/360

5600dpi
24.5cm/360

I plused you, and I demand [+]! :<

CHAOS, I want [+], you spamming bastard!

;]

\ :D /

If we list dpi, it solves that issue

WMO @ 500Hz (Win7pointer @ 5 with Accelerationfix)
sensitivity "3.85"
seta cl_mouseAccel "0.0"
seta in_mouse "2"
seta in_mouseMode "raw"
seta cl_mouseSensCap "0"
seta cl_mouseAccelOffset "5"
seta cl_mouseAccelStyle "1"
seta m_filter "1"
seta m_forward "0.022"
seta m_pitch "0.022"

m_forward and m_side are completely unrelated to sensitivity

and if you use the default "0" values for any settings, dont even post them -_-

abyssus@450 dpi
pitch/yaw default
sens 3.25 (~28cm)
acc 0.082

<<<aimbotsettings>>>

IMO 1.1 @ 500hz
6/11
sensitivity "2.9"
cl_mouseaccel "0"
m_forward "0.022"
m_pitch "0.022"


Recently tried upping it a bit. Still getting used to it :[

-

set in_mouse "2"
set sensitivity "1.67" (on rail & lg 1,5 ^^)
yaw/pitch default and no accel
DPI: 800

Damn, I can't hit anything when my sense is as high as the posts above :'(

I.E 3.0 (400dpi ofc)
Sensitivity 2.4
m_yaw and m_pitch 0.020
cl_mouseaccel 0.1
in_mouse 1
125hz (used 500hz for ages, but I seem to aim more consistently with 125, don't ask me why :S)
+zoom config, cg_fov 90 base fov, with a nice little script which has helped me out quite a bit aim wise:

bind mouse1 "+attack;+enemy"

alias +enemy "cg_forceenemymodel tankjr/bright;cg_zoomsensitivity 1"
alias -enemy "cg_forceenemymodel keel/bright;cg_zoomsensitivity 0"

^^This means my sense gets slightly lowered when I click shoot (plus the larger model for lg etc), and I get a slightly higher sense for movement and such. It works really well :)

7,20896 / 360

mouse accel is about to be changed due to them breaking it with recent larger then life hitbox update. its even more broken now, u will see come apirl 8th

what do the hit cylinders have to do with mouse accel?

it doesn't, the last update was simply the biggest influx of reports of the sens/accel bug.

sens is so different between players (because of their entire computer setups), that these values are almost meaningless.

internal sens is pretty much as precise as you can get, and cm/360 is as accurate as you can get.

those 2 values should be in every post, along with m_yaw/sens/etc.

the only variant is accel, which cant be helped at all.

yes and no, if people aren't complete retards they know what external parameters affect sensitivity accel and will actually get rid of them ( in_mouse 2 ( even though 1 and -1 do the job too but there are more parameters ) / no drivers lulz )

Then it's simple SCIENCE WITH FORMULAS AND SHIT.

what if they use the aforementioned external parameters?

they can still calculate it in most cases.
win sens is a known multiplier, so do most drivers I've seen ( they usually either follow the exact same pattern than win or -as razer driver work- sens 10 is 1:1 and anything under is 0.xx*input )
Then it's only a matter of multiplying dpi by that factor to get the "virtual dpi" processed by the game and do the usual calculations.

inb4 accel.

still, internal sens is the more useful number when it comes to ingame settings.

and cm/360 is the most _accurate_, assuming you dont use any accel. and if you do use accel, even a little bit, then this stuff is pretty useless.

lets say my internal sens is 20, and yours is 15, i can see the difference better than if your m_yaw and sens are lowered by 0.0001

pop wincalc up. got both ingame settings rescaled if needed / cm by 360.
problem solved.

You're actually considering a different operation and its result won't mean shit to anyone else than you. cause nobody is used to that system.

if more people knew about internal sensitivity it would be a lot more meaningful, but i guess as-is nobody here knows what it is, so ill just give up :(

oh when you put it like that it makes total sense instead of typing just one line...

I know, it usually works better to keep people focused on what I'm saying.

Or at least that's what they try to look like.

Sensor location can affect sens a lot aswell, my pyra is a lot faster than my imo at the same sens, because the sensor is further forward. If I use the same settings on both mice it feels very different.

What is internal sens btw?

internal sens is just the sensitivity that the engine calculates and uses.

Ah right, is there a way to see it?

kinda. its not something you can see ingame or in your config or anything. you have to do the math (not that hard).

m_yaw * sens * 65536 / 360

WMO 1.1a @ 500 hz (400 dpi) pad QcK
sens 5
accel 0.5
m_filter 1
other m_stuff at default

WMO @ 1000Hz
sensitivity "4.5"
cl_mouseaccel "0"
m_pitch "0.022"
m_yaw "0.022"

IE 3.0 @500 hz
400 DPI
7.95 sens
.1 accel
.0095 yaw

ie 3.0 @ 500hz
420ish dpi
sens 3.2
accel 0.1
yaw/pitch 0.022
30.9 cm/360

IE 3.0 (plug and play with logitech mouseware 9.79 :P)
sens 3.5
m_yaw and pitch 0.022
mouseaccel 0
800*600 reso (ppl say it matters)
30-35 cm / 360

res doesn't matter in the actual distance you have to move your mouse, it's only a matter of how it feels.

ah ok :)

3500dpi
1000hz
~27cm/360
no accel, no yaw/pitch disparities

Abyssus @ Mantis speed ( best mat I found for abyssus)

1800DPI
1000Hz

sens 1.5
accel 0
yaw/pitch 0.022 / 0.028
r_texturemode GL_NEAREST (makes alot of difference in feeling ,why is this never mentioned?)

played bf42 for 6 years with 60+ cm , took me 2 years of fucking around with sense before i realised that ql is not a game of precision but of prediction and speed.

Kinzuadder @ 450 DPI

sens 2.3
accel 0
m_yaw/pitch 0.022

~36cm@360°

sens 4.75
pitch/yaw 0.018
(~26cm)
accel 0.05
m_filter 0
400dpi 500hz
kinzu :(

NOT LIKE IT MATTERS

with 400dpi i'd have the following, using 900dpi right now:

sens 4
accel 0.1
m_filter 0
in_mouse 2
500hz usb
pitch/yaw default
~26cm/360 (without accel)

recalculated with http://phoon.us/mouse

400dpi (mx518 or IMO 1.1)
4.5 sens
no accel
raw input
m_filter 0
500hz

that's 23cm/360 methinks

DPI: 1800
Sens: 1.45
Accel: No
Raw input: Yes
m_filter: No
500Hz: Yes

Something about: 30cm for 360°

wouldn't that be around 16 cm?

you prly haven't measured with a ruler or got some other setting in drivers/..

DA @ 450dpi @ 1000hz

sensitivity 4.7
cl_mouseaccel 0.32
m_pitch 0.025
m_yaw 0.022
m_filter 0
in_mouse 2

How can you go from a low sense (4.7 and 0.008 yaw iirc) to a sense as high as this?

Did your lg suffer? Can't hit anywhere near my normal accuracies if I up my sense.

Ahhh, you remember that my sens was low when I left europe. Yeah that was about a year ago. Well what was your highest sens you've ever played with?

I started on 15 (400dpi), which was crazy and stupid but I was 16. I soon dropped to 9.5, then 7.5, then back up to 9.5. Then I stopped playing for 4 or 5 years, then I dropped my sens until I was hitting 40% lg, which was 4.7. I wasn't particularly happy with not being able to turn quickly, so I added accel, 0.32 seemed to be the sweet spot.

I then tried to lower my sensitivity to get more of a aim boost, but it didn't work. I dropped it down to like ~1.6 and ~0.1 (the low pitch and yaw that you are talking about) but I was aiming the same and wasn't able to move very well, so after I got my new mouse I went back to normal pitch and yaw.

I've been changing my sens every now and again, just for experiments, but I've stuck with the one above for a long time. Anyway, to answer your question, I started on a very high sens and started lowering it. I played with 9.5 for like 4 years, so for me what I'm currently using is low for me. (Although I can't go back to 9, maximum I'll be able to play on is 6 now.)

On a side note I lowered my sens to strenx like sens, to 2 without accel or something similar, and I got a huge aim boost, but couldn't turn, and adding accel got rid of the boost.

Honestly I really shouldn't want to change anymore when I'm hitting more than I ever have in my life, I should just stick with my current settings, although I do want to change my mouse.

I really like your idea about changing enemy models btw, however I have tried to do the different sens thing before, your instinct will never be able to settle.

The highest sense that I played with for a few months at the start of QL would be:

Sense 6
Accel 0.1
pitch and yaw 0.018
with WMO @ 500hz + Qck heavy

Every weapon was really, really good apart from lg, which was abysmal. Never used anything higher :)
Movement was really easy too, it was a sense that I could play for hours on consistently.

This bit here:
"On a side note I lowered my sens to strenx like sens, to 2 without accel or something similar, and I got a huge aim boost, but couldn't turn, and adding accel got rid of the boost."


bind mouse1 "+attack;+enemy"

alias +enemy "cl_mouseaccel 0"
alias -enemy "cl_mouseaccel 0.32"

You may as well try it!

I got used to small sense changes like this really quickly, but I use a +zoom config so i'm used to this, perhaps someone who doesn't is far more sensitive to continual small sense changes like this.

Well my accs with or without accel on 4.7 are the same, I couldn't play on 2 with accel, that will just feel weird. But I will play around with it, I made a script to do the same thing before, as I said.

sens 4
accel 0
yaw/pitch default
dpi 450

http://users.kymp.net/feuer/etcomic/061.jpg

hehe

haha classic.

yaw/pitch -0.0000000000000666
sens 150
accel 12

I use Gamesense. I don't use DPI because I don't have a printer, I'm not a printing kind of guy.

sens 1.71
yaw and pitch 0.022
m_filter o
450 dpi
not going to tell accel:p :F

internal sens is about 7 ;)

SteelSeries Xai
CPI: 800
Polling Rate: 500hz

Windows Sensitivity: 6/11
Using Cheese's Mousefix for 120hz (refresh rate)

//// Mouse
set in_mouse "2"
set sensitivity "1.6"
set cl_mouseSensCap "0"

set cl_mouseAccel "0.01"
set cl_mouseAccelStyle "0"
set cl_mouseAccelOffset "5"

set m_filter "0"
set m_pitch "0.022"
set m_yaw "0.022"

~32.5cm/360

Microsoft Wheelmouse Optical
400 DPI @ 125hz

~26cm/360

Absolutely dumb to type in cm/360 because then YOU CANT REPLICATE THAT without having to calculate and all that crap. Nor can you measure it easily without using something like (http://www.notalent.org/sensitivity/sensitivity.htm).

Just say :
sensitivity
accel
DPI
myaw and mpitch only if it is changed from 0.022
windows sensitivity

This allows people to recalculate if they want to use it.

So when heartless posts his sensitivity I can copy it and get 50% shaft.

fov is important too (or zoomfov if +zoom)

fov on it's own isn't.

-- Hardware --
Mouse: Microsoft Wheel Mouse Optical 1.1a,
Mouse DPI: 400,
Mouse Frequency: 1000hz,
Monitor: Samsung SM2233Rz,
Monitor Frequency: 120hz,

-- Software --
OS: Windows Seven,
Mouse Drivers: Nope, l@l,

-- Game Settings --
FOV: 130,
M_speed/Sensitivity: 2.3,
m_accel/acceleration: 0.0255
Windows: 6/11,
m_yaw/m_pitch: default (0.022),

-- USING INJX FORMULAS N SHIT DAWG --
~45cm/360
~17"/360
~0.0139128 Real Acceleration

EDIT -- I'll be editing this post quite often, I'm at that stage in my life where I just go from one sensitivity to another. Within one month I've used over 20 different sensitivity settings going from 8 sens to 1.5 sens.
FFS WHY AM I SO FUSSY.

Let's see a demo or yt of that 84 % lg

HARDWARE:
Abyssus
450 DPI / 125HZ

SOFTWARE:
XP PRO SP3
razer drivers - NO.

QL SETTUP:
In_mouse 2
FOV: 93
Sens: 3.8
Accel: .135
m_yaw: 0.022
m_pitch: 0.022

And guys, how do u calculate ur 360* move to cm ?

I use Injx's formula's...
http://phoon.us/mouse/

g9x

sens "1.8"
windows "6/11"
dpi "400"
accel "0"
in_mouse "2"
yaw / pitch "0.022 / 0.020"

somewhere around 50-60 cm/360° haven't checked in a while.

sensitivity 5.0
accel 0.5
filter 1
yaw/pitch 0.015
dpi 400
polling rate 500
in_mouse 2
mousesenscap 0
mouseAcceloffset 5
mouseaccelstyle 0

MX518 no drivers

WMO 1.1a @ 500hz 400dpi (derp)
Giant cloth pad

in_mouse 2
sensitivity 1.3
cl_mouseAccel 1.6
cl_mouseAccelStyle 0
cl_mouseSensCap 2
m_yaw .022
m_pitch .022

79cm / 360 before accel
52cm / 360 with accel

1600x900
FOV 130

I don't use sens.

i dont use resolution.

WHAT NOW?

10-28 cm / 360 (use accel)

If you're posting settings with accel, at least use injx's method.

This?
http://www.esreality.com/index.php?a=post&id=1370847

I think you meant " at least don't be retarded "

yes, http://phoon.us/mouse/ will compute both the base sens (cm/360) and the real accel for you in a few clicks.

These numbers can be directly compared on a like-for-like basis with other players and setups.

Having a list of cvars and the mouse cpi is only half of the story - you also need to know how to combine all of the settings to get a meaningful number.

sens 0.35
dpi 5040
360/cm ~23.56

4.5sens, wmo1.1a, qck+
?

my sens is anywhere from about 3.2 to 0.5 as it fluctuates randomly during play. hard to tell at any given time

its a secret :s

0.45
900dpi
0.01 accel

dpi 400
accel 0.05
55 cm on the mousepad

Razer Salmosa @ 500 Hz
800 cpi
no driver, Win 6/11, MarkC accelfix, Enh. Point. Prec. OFF
Razer Mantis Speed

r_mode 5 r_displayrefresh 75
cg_fov 95-105 (110)
seta in_mouseMode "win32(Raw)"
seta in_mouse "2"
seta m_cpi "800"
seta sensitivity "7"
seta cl_mouseAccel "0.2"
seta cl_mouseAccelStyle "0"
seta cl_mouseAccelPower "2"
seta cl_mouseAccelOffset "5"
seta m_pitch "0.020"
seta m_yaw "0.020"
seta cg_zoomSensitivity "1"
seta m_filter "1"


But maybe change something..

Logitech G300 + Roccat Taito
no Logi driver
1680x1050 on Samsung 2233rz 120hz
MarkC MouseFix

500 dpi
1000hz

sensitivity 4
cg_fov 100

all the rest to standard values

PS: around 20cm for 360