what happened with the abyssus you used to praise?

zowie AM > abyssus > any other mouse :D

i still think that the abyssus is a really good mouse. But now i need to get used to the god tier zowie AM :D, 1 week or so that i have it now, and so far i'm loving it.

at Moscow LAN a month ago
pavel was using Xai + QCK
cooller was using Abyssus + Corepad Cerro XXX-Large

http://imgur.com/a/ajHGq

isn't spart1e using a xai aswell ?

so cooller still hasn't changed his mouse, unlike cypher it seems

are you sure that he's still using an abyssus ?

not rly, i heard he tried kinzu v2 from someone but i ain't sure

http://imgur.com/a/ajHGq#6
that's hilarious

to small :-o

what sensitivity should you use ? are we supposed to tell you what to eat, too ?

no!

just the sensitivity, cause i can't decide by myself

/callvote cointoss

Cooller's Sens, dpi, accel and accelOffset anyone? :)

i'm pretty sure he's using 450dpi with med sens and med-high accel

still wondering why he's playing on such a large mousepad tho, maybe he went strenx/evil's style and play with very low/ultra low sens now :D

He had strenx level low sens for years, just with accel.

3.1 w/ 0.25 accel. pitch -0.018, yaw 0.014 (or something similar, quite large difference).
Dunno about dpi and Offset though :)

edit: yaw/pitch fixed thanks to Tcm

yaw 0.014 iirc

Oh, then pitch must be 0.018.

(-) because of invert mouse.

Well yeah, forgot that immediately after I posted it the first time :)

thank you. with such sens and accel i think its safe to asume he uses around 400 dpi

Yeah, anything above 450 DPI with those settings would be ridiculous.

so guys, what's better : 28 or 38.5cm/360°??????

Between those two I'd definitely say 28.

For duel 28, for thunderstruck 38.5 cm.

and ofc: personal preference... damn.. I was the one that told you the obvious. :)

For me 19 feels too low in duel. I need to add some accel already.

posting in a heartless thread

they use what they like, and they do it everyday like 8 hours a day.

So pick you a sensitivity a random one, and adjust it till you get the feeling

the process should go like +-0,4 then +-0,1 then you play with it 8 hours a day.

I recommend 400dpi 2.4 sens .24 accel

okay guys i'm gonna play on 28cm/360° forever :p

what's best is being comfortable with changes (being able to adjust at least a bit). It is also a good measure to play the settings (changing sens and so on) instead of massively changing your comfort zone to adjust to adjust to the sens feeling wrong (change a number not your muscle memory). Cypher does both btw.

low sens = shit rockets
high sens = shit LG
mid sens = all "medium"(c)Pavel

try mouse accel

already tried it

in fact when i started playing quake i used a bit of mouseaccel, but that was with a shitty mouse on a func mousepad, that was around the year 2004

but now i play without mouse accel for like more than 5 years

and the zowie AM has a very 'pure' sensor, without any prediction, angle snapping or hardware accel

i used to play with a kinzu v1 some years ago, it was nice, i was kind of used to the hardware accel but i wanted something new, and considering the fact that the kinzu v1 won't be available because of the v2 version, it was time for me to change, that's why i bought the abyssus

the abyssus sensor is pretty similar to the am's, and very different than the one in the kinzu v1, i played on an abyssus for approximatively 11 months, without any mouseaccel

so let's say that playing with mouseaccel would be a pain in the ass to adapt, i'm feeling too old to adapt to a new sens, that's why i decided to stick to my good old ~30cm/360°, with this sens, overall i feel very comfortable, except maybe when i'm nervous, my aim kind of become shaky, that's why i tried to lower my sens, but without much success, got beat by many people with 38.5cm/360°

tl;dr 30 CM FOREVER

that's not optimal for duel. There's a reason why all (literally all) the greatest quake3 and onwards players used and use mouseaccel, on the cfg or inbuilt on the mouse.

There's more things than 1v1 ca on thunderstruck near that bridge that goes to nowhere.

tox ("quake3 and onwards"). He uses negative accel in wmo if anything :P

tox on his q4 prime used a very high sens though. In QL he lowered it immensely (must be the gym), bumping into walls on duel but hitting 50%+ on tdm (lowsens + zoomfov on lg can only be described as gay)

czm

fun fact:

in q4 he used 35cm/360 same as ql, until the last days where 1.4 patch was faster, he lost to av3k in wsvg louisville and it forced him after that tournament to raise it to 24cm/360 and then he didnt lose again (wsvg dallas, toronto, quakecon, i32)... best quote from tox about 1.4 and id software was at i32 "they try make me lose"

What, please link to this. That's a fucking awesome statement.

Its on esr demos, in toogood vs tox at i32. Can't find the vod uploaded anywhere (it used to be on quadv site and stage6), I'll reinstall Q4 and see if I cba to record and upload it.

>> Also, what sensitivity should i use ?

What's next? 'What is my shoe-size?"

Needed some attention again?

Zowie am, sens 1 highest dpi setting.

In my case low sens+low fov cause shit movements and i feel myself as i am in the water all the time (those t7 railplace you know). If u want to find optimal sens for duels ASAP then the best map is aerowalk imho. Peace

dpi 450
yaw/pitch 0.018
sens 3.35
accel 0.1

He4rTL3sS > Cypher.

When I see people asking sensitivity and mouse settings to try out new things, I can only think of m_cpi to make it easier for everyone.

I've been using this for a while now and whenever I switch from PC to laptop and use a different mouse, all I need to change is the m_cpi value. So please read this next wall of text, I have highlighted the interesting part.

In regards, I am using sensitivity 25, no accel. I have a mouse set to 800 and a mouse set to 1600 DPI.


m_cpi

When configuring mouse sensitivity and acceleration, the physical meaning of the values you enter depends on factors outside of the game itself, namely the mouse's CPI (counters per inch, also referred to as DPI by most hardware manufacturers) and anything which manipulates the mouse input before it gets to the game (e.g. a driver-level sensitivity setting). A result of this is that one player cannot directly compare his in-game settings with another player - the external factors must also be taken into account for such a comparison to be meaningful. Changing from one mouse to another can also be a pain. In the past, players would perform a physical measurement with a ruler, or use a calculation to determine values which are meaningful (e.g. sensitivity in terms of cm/360). Although this procedure isn't too bad when talking about the base sensitivity, for more complex settings like acceleration, things can get rather messy.

In this update, a new cvar has been added (m_cpi) to solve this problem. By setting m_cpi to the effective CPI of your mouse, the input code can perform scaling in meaningful `natural' units (cm, degrees, seconds), rather than the arbitrary hardware-dependent units of `counts'. The default value is 0, which turns off the feature.

If two players are both using their correct values of m_cpi, they can compare their mouse settings directly from the cvars - this applies to both the base sensitivity and ALL acceleration cvars.For example, the sensitivity will be in units of degrees per cm, and cl_mouseAccelOffset will be a mouse speed in cm/s. This also means that if you are using m_cpi and you change to another mouse, m_cpi is the *only* cvar you have to change.

In order to set m_cpi correctly, it should take into account any driver-level sensitivity setting. For example, you have a 1000cpi mouse with a driver setting of x0.6 - you would set m_cpi to 600, not 1000. I refer to this as the `effective CPI'. If you do not have any driver settings, then just set m_cpi to the cpi of your mouse. Note that the value quoted in your mouse's documentation may differ very slightly in practice depending on the mouse surface, additional mouse feet, etc.

This feature is designed to be used with m_yaw at its default value of 0.022 (using another value will still function, but will no longer benefit from using the natural scale). You can still use m_pitch to provide your vertical axis with a different scale factor.

Old to New Conversion

In order to convert your existing sens and accel settings to the new scheme with m_cpi, there are some existing calculators out there that will do the conversion. If you want to do this manually, you can use the following formula for conversion from old to new.

new_sens = old_sens * (old_yaw * m_cpi / 2.54)
new_sensCap = old_sensCap * (old_yaw * m_cpi / 2.54)
new_accel = old_accel * ( old_yaw * (m_cpi/2.54)^2 ) / 1000
new_pitch = old_pitch * (0.022 / old_yaw)
new_yaw = 0.022

This assumes the old settings are style 0 (power=2 and offset=0).

That's actually worse than using the old settings, you have no idea how many retards keep tweaking their drivers or use in_mouse -1 and massively fucked up settings. Let's not add another layer of wrongdpilol bullshit to that stuff.

http://media.tumblr.com/tumblr_mcx9gzIlbJ1rxl1gv.gif

I don't think m_cpi is very usefull.
Why do you even switch the mouse if you try to make it feel as close as possible to the old one?
Different mice have different shapes, sensors, we grip them and use them differently therefore imo you should find settings that suits you best with new mouse instead of trying to replicate some parameters.

These parameters - sens and accel are here to tweak the mouse to our needs but we perceive the "mouse feeling" differently, in a more uniform way. Other factors I mentioned have big impact on mouse perception so replicating only sens and accel doesn't guarantee replicating the mouse feeling. Or making your old muscle memory work with new mouse.

m_cpi is useful for comparing settings from different players (as in this thread) and being able to do a simple 360/sens=cm for a 360° :)

if i wouldn't be using it i'd still recalculate my (and everyone elses) sens to their 400dpi equivalent to have a indicator of where i am in terms of sens.

If it's all so different, why share your values? Everyone's values here mean less without m_cpi just because of your point that all mice are different. When I switch from my RAT7 to my G5 with m_cpi it feels pretty much the same, besides the way the mouse is held.

If you think m_cpi is useless because all mice have different sensors, weights and shapes then this whole thread is useless because you can't replicate what a user feels. But m_cpi can close that gap, not completely (hardware related) but enough to make comparison easier (software related).


edit:
Why do you even switch the mouse if you try to make it feel as close as possible to the old one?
Laptop with G5 and desktop with RAT7. I'm not going to disconnect the RAT7 all the time now that I have tidied up my cables with perfect cable management.

I tried that when it was implemented, calculated my new values but it didnt feel the same as old settings so I reverted. Measured cm/360 was same but something was off, accel maybe.