without, iam gonna assrape ID

Did Doom3?

Doom 3 to the best of my knowledge DID NOT have mouse accel.
It had some smoothness thing which actually seemed to lag the mosue.

You cna however set mouse accel in the Logitech drivers, not exactly sure if this will be the same as q3.
I made a choice to play with mouse accel off at the start of the year because of this very reason. Get used to it before q4 is here I say:)
The ESR q4 cfg whines are already starting, wait until you find out you probably wont be able to assign individual sensitivities to each weapons.
Raged pole/swede/usa/uk alert.

I hate every mouse accelleration "setting"(can't think of a better word) apart from quake 3's, they just don't feel correct.

agreed

I agree also, this is why I stopped using it long ago, because I knew eventually it would not be able to be re-done correctly... so I didn't wanna get used to something and have to lose it later :(

My old 0.02 accel config was damned comfy, though.

I stopped using accel because of that too.
I used to play sens 1.5 accel 0.25 on my MX510... Now I play sens 4.5.

I had untill earlier sens 1 accel 0.1 (Diamonback at 1600) upped it to 2 seems fine actually :o

About the same here, actually. The sad thing about not wanting to use accel is it just makes using a low sens so much more bearable!

Lately I absolutely cannot find a sensitivity I'm perfectly comfortable with. :(

got sens 3 accel 0.7 and i hope they dont only have cl_mouseaccel, but also in_mouse
and if they care about q3 players, they will have these commands.. i want in_mouse 1 und the sens settings im used to and just lean back and feel comfy

You can get the exact same accel in HL2 actually, and some other types as well. Too bad the game sucks though.

True.

who cares about what you play ...

answer the question

my sensitivity is 11 with mouseaccel 3

I live in a flat with windows and doors.

insane.

not sure if i just thought it..or actually posted somewhere..

but isn´t it possible..or

wouldn´t it be great..if they used the same "input" system for q4??like in

q3??

even easier for them..since they don´t have to bring one up?!

sounds good or sounds good?

crakka

AFAIK, the Q3 acc. code is fairly simple.
So simple that it only took ONE email from some random gamer to have the devs include it in Painkiller. Apparently it's easily added.

Maybe you acc. boys could make a small petition or just mass-email Raven about this.

gl

::painkiller sucks gag::

beard > sa > sucking gag

'So simple that it only took ONE email from some random gamer to have the devs include it in Painkiller. Apparently it's easily added.'

It was never added.

WHAT A CONSPERACY!!1

All right, I take it back, then.
I only heard it from the guy, who sent the email, that they told him they had added it after recieving his email.
But I guess they're a bunch of liars. :(

And yes, PK sucked dick, massively.
Could have been such a great game, but again they didn't listen to the beta testers and the quakers, and instead focused on single player (even though they claimed to be oh-so in touch with the 'pro' gaming community)

shouldn't be much of a problem for mod developers seeing as tho the q3 source has been released :D

Sensivity 7
Cl_mouseaccel 0.5
Mx300
Func surface 1030

so what?

You must be a devil with the ladies!

Luckily for me (if the lack of accel in q4 is true), I recently discarded the use of accel purely because it's a pain (or more precisely: you need to be good) to aim consistantly with it.

wouldnt it be possible to develop a standalone app that creates mouseaccel? or a driver etc..

a stnadalone app would be great. That way you could get the same feel in every game regardless of what mouse(driver) you have.

Logitech setpoint drivers do exactly that. Although the settings arent very flexible with only low/mid/high accel options. It also overrides the inherent win xp mouse accel if u want it to. The "CPL mouse accel fix" didnt really work properly anyway, so it's a welcome addition.

Someone with some coding skills should make such a tool, would be fucking great.

Or we make a petition to get Logitech to implement acc. values from like 1-100.
But that would leave out non-Logi gamers. :(

That guy that made that usb.sys thingie that killed all acc. amir(?) I bet he'd be able to code such a little tool for all acceleration addicts.

Anyone know where he can be contacted?
I saw him post somewhere in these forums, but can't find him anymore.

I mailed Logitech about a month ago and asked them to make accel in their drivers more flexible. I actually got an answer! "I understand you are having problems with acceleration in the Logitech drivers." I hope the guy forwarded that mail to one of the coders ....

It's unlikely we would be able to create Q3 type accel in a driver or external app. The reason is that Q3 acceleration doesn't directly affect the X/Y motion reported by the mouse, it affects the actual sensitivity value. It increases the sensitivity value depending on how far you moved the mouse and that is what makes Q3 style accel so good IMO. A driver or external app won't easily be able to change a game's sensitivity value, it might be possible to hack it for some games but for most games it would likely be impossible.

Couldn't it be the same form of acc. as the Logitech drivers have (which is good, too bad only 3 stages)?
And just allow to the user to set the value from 0 - 100.
Logitech acc. works with all games.

I wish Logitech would get their fingers out of their asses and add more acc. values. Low, med, high is simply not enough to choose from.
I, personally, woudl prefer something even lower than the Low in Logi driver.

It wouldn't be too hard to make a global acceleration driver and a GUI to control it. I don't know much about acceleration algorithms but maybe it is worth investigating.

amir, who made the "kill-all-acc-in-xp" thing, I bet, could do it.
I saw him post here a week ago or so. Know him from Razer forums.

Are you here, amir?

His nick is anir. I know him a little also from the Blueprints forum. I don't think he has kernel driver development knowledge yet and maybe he hasn't the free time to learn it, but like you say, if anyone could do it, I agree it would be him, and he would do a good job of it.

Indeed.

Hello,

A few month ago, Atalan did me a favour and implemented a simple acceleration algorithm in "mouclass.sys".

The algorithm is (pseudo code):
MickeysX(Y) := MickeysX(Y) * 2 -(+) 1;

The class driver "mouclass" usually applies to all connected mouses and modifies the reported information at a low level, so DirectInput is also affected.

You can download the modified file here: http://home.arcor.de/_aero/mouclass_accel.zip

The build is based on the Windows Server 2003 DDK and should work with Windows 2000, XP and Server 2003.

As you might know, there are many different kinds of mouse acceleration, so there is no guarantee you will like this one.

Very interesting.
As ther any way one can alter it into individual preference?
Or would that require your friend to do the whole file again?

Oh, and any chance, your mate would consider making a tool that alters this file in like 1-100 increasements? :)
Would fkin rock.

Atalan himself doesn't seem to like any kind of mouse acceleration, so it is not very likely he has any personal motivation concerning this subject.

He did me this one favour and I really appreciate his efford.

I don't want to bother him again, because he seems to be very busy with his job and his family.

There are two methods how you could alter it for individual preference:
1. Get the DDK and edit the source code yourself
2. Disassemble the existing modification and alter it there (very limited options, though)

It really depends on the variety of algorithms you prefer.

Personally, I think Quake 3's implementation is rather flawed, because both data of the X- and Y-axis are accumulated and applied without axis-specific differentiation.

I don't know how you imagine optional increments in this algorithm.

The problem with floating-point numbers or "sub-pixilation" is either a remainder or rounding it to integers.

I have chosen this algorithm, because all possible results are always integer.

hello,

I have always wondered what exactly is in quake3 acceleration code. I have looked for what cl_mouseaccel actually does in google but have been unable to find it.

Could somone explain it here? Or email it to me at [email protected]?

thanks.

h3rf

If you mean how it's coded, check the source, I'm sure it's in there somewhere ;) http://www.esreality.com/?a=post&id=868894

I had a look at the source and it starts of with the mouse smoothing code:

if ( m_filter->integer ) {
mx = ( cl.mouseDx[0] + cl.mouseDx[1] ) * 0.5;
my = ( cl.mouseDy[0] + cl.mouseDy[1] ) * 0.5;
} else {
mx = cl.mouseDx[cl.mouseIndex];
my = cl.mouseDy[cl.mouseIndex];
}

When m_filter is set to 0 it just takes the latest mouse movement and stores it in the mx and my variables but when m_filter is not 0 it takes the mouse movement made in the previous frame as well as the current frame and adds it together then divides it by 2.

I'll do an example with mouse smoothing disabled and a 400 DPI mouse which has been moved diagonally in a single frame giving us:

mx = 100
my = 100

If it had been a 1600 DPI mouse the above would instead be mx = 400 and my = 400 for the same diagonal mouse movement.

The following is the start of the mouse acceleration code:

rate = sqrt( mx * mx + my * my ) / (float)frame_msec;

The above calculates the euclidean distance (straight line distance between two points) giving us 141.421356. It then divides that distance by the frame_msec which is 8ms when using 125fps. So rate will be:

rate = 141.421356 / 8 = 17.6776695

The following calculates the sensitivity value to use for this frame:

accelSensitivity = cl_sensitivity->value + rate * cl_mouseAccel->value;

This code takes the sensitivity value we use and adds the calculated rate multiplied by the cl_mouseaccel we use. For this example we will use sensitivity 3 and cl_mouseaccel 0.25 giving us:

accelSensitivity = 3 + 17.6776695 * 0.25 = 7.419417375.

So in this frame our sensitivity of 3 has been accelerated and is now 7.419417375.

with mx=100 and my=100
sqrt( mx * mx + my * my )
sqrt (100*100+100*100)
sqrt (10000+100000) =~141.42 and not 100
Now redo the rest of the math =)

Have you seen American Dad season 2 episode 1? ;)

Seriously though that was awful of me so thanks for pointing it out and I'll try to curb lazy shortcuts in future especially when math is involved. :D

Aha, no I have not =) Glad you enjoy the correction :)

It's good entertainment and funny too. :)

Interesting.

What made you did you decide on such an algorithm? What's good about or what benefit is there with such a change to the motion values?

I've got sensitivity 2 and mouseaccel 0.8 hope i can get something like that in Q4

i've never had a problem going from game to game with different sensitivities and accels(and lack there-of). she'll be right.

Seriously Q4 should improve when it comes to user friendlyness, would be ridicilous if u would need lots of extra programs to play it..

Even without accel or suitable tweaks i'll still blame lag for my inaccuracy :P

omg, i'm not the only stryder on esr :`(