Hi! New player here.

[khumreyo]

Hello all.. I am new to your community - just played few games on tastyspleen servers after 10 years break.
It's cool that there are still q2 servers in the world

I have a question - I got win7 and some microsoft mouse with blue laser, it says - ms comfort 6000.
Acceleration in widows is disabled and in q3 everything seems to be ok,
but when I launch q2, I have some crazy mouse accel, it is almost unplayable.
Do you have any suggestions, how to fix that thing?
I played today and some player told me I will need a pak in order to fix mouse accel problem.
Is that true? Which q2 pak is good to download?
Also - can someone give me a good cfg? Mine are lost.

Thanks and hopefully see you on the servers! 

[haunted]

make sure you have an updated mouse driver for your mouse / win7, with mouse accel turned off in wherever / especially if it has a gaming settings option.

the cmd in q2 is m_accel 0, i think. and of course have it turned off in any windows option

I play as e|ipa usually, btw.. I think I saw you earlier. maybe I was using the name Pepe Lopez, either way, welcome.

[khumreyo]

my q2 is without any custom pak and it doesn't recognize the cmd you mentioned.

Yep, I saw you on the server, nice to meet

[khumreyo]

thanks.. found this one: http://www.esreality.com/?a=post&id=1846538

[VaeVictis]

Those registry based fixes can work, but they're not necessary with game clients that already have built-in DirectInput / Raw mouse input support.

I'm glad you found a solution that works for you though.

i still seem to notice a difference :/

[khumreyo]

Those registry based fixes can work, but they're not necessary with game clients that already have built-in DirectInput / Raw mouse input support.

I'm glad you found a solution that works for you though.

Yeah, registry fix works fine. I'll also might give r1q2 a try. Thanks for help.

[VaeVictis]

Those registry based fixes can work, but they're not necessary with game clients that already have built-in DirectInput / Raw mouse input support.

I'm glad you found a solution that works for you though.

i still seem to notice a difference :/

Care to elaborate?

can definitely notice when ever i dont have a registry fix in place... the built in client solutions just dont seem to cut it though it is possible its in my head

mouse input in windows is a total bitch anyway, even different registry fixes will feel different

[VaeVictis]

can definitely notice when ever i dont have a registry fix in place... the built in client solutions just dont seem to cut it though it is possible its in my head

mouse input in windows is a total bitch anyway, even different registry fixes will feel different

Have you tried comparing your results with those registry fixes against m_directinput 1 (and 2) in either R1Q2 or Q2Pro? Keep in mind that AprQ2's DirectInput support doesn't seem to work properly. It's also normal to have to adjust your in-game sensitivity after the change.

Those registry fixes are really meant as a last resort - it's almost always a better solution to take advantage of built-in support rather than trying to hack your way around it.

It could also be that you're just accustomed to your current setup and any change to it feels wrong.

well the registry fix is nice overall cause i play a lot of different games and i find mouse accel extremely irritating even to normally navigate through things... only downside to the registry fix is that it might seem really sluggish to some people on the desktop, not an issue for me

[haunted]

your sens is too low.

[ReCycled]

If it is of any value here I have found there are inherent problems with the Microsoft "Comfort" series of mice. They are not gamer friendly mice. I had a Comfort 3000 mouse that would not recognize MOUSE3 in Quake 2. I use that button (scroll) for jumping. Nothing I did could fix it. I only bought because it had a decent DPI (1000). If you search other forums, there are many gamers who have had various problems with the Comfort line.
Buy a Razor Death Adder or a good Logitech.