Axis aMouseX/Y Speed

[Mang Nux]

What do these do?

MouseX=Count bXAxis | Axis aMouseX Speed=2.0
MouseY=Count bYAxis | Axis aMouseY Speed=2.0

Especially when compared to the in game sensitivity or MouseX/YMultiplier ?

 

[Plumb_Drumb]

Without tweaking that, I couldn't get smooth mouse movement at all in the game - it would skip pixels making long distance shots impossible.
Try it out! I think I set mine to .5, then upped the sensitivity so I didn't have to row my mouse 5 times to do a 360, lol.

The mouse I was using at the time was only 800dpi, so that may have made a difference.
I haven't tried the game with my new one, which is 3600dpi.

 

[Mang Nux]

Without tweaking that, I couldn't get smooth mouse movement at all in the game - it would skip pixels making long distance shots impossible.
Try it out! I think I set mine to .5, then upped the sensitivity so I didn't have to row my mouse 5 times to do a 360, lol.

The mouse I was using at the time was only 800dpi, so that may have made a difference.
I haven't tried the game with my new one, which is 3600dpi.

0.5 is actually pretty good, but why does 0.0 disable the mouse altogether? Seems strange...

What about MouseX/YMultiplyer? Mine was like this by default:

MouseYMultiplier=0.000000
MouseXMultiplier=0.000000

But many others seem to have 1.000000 as default... What should it be to keep it 1:1 unaltered? Trying not to have multiple filters acting on the mouse input at once.

And as for MouseSamplingTime, what should that be for a 1000Hz polling mouse. I calculate it to be around 0.001000, but I've seen posts where people have recommended specifically 0.001333 and 0.001041. Why?

 

[Plumb_Drumb]

I never messed with the other two, so I can't tell ya.
All I needed was that X/Y Axis Speed tweak and I was golden - fraggin like a winner!

It always befuddled me that the actual "Smoothing" option in the game menu did absolutely nothing at all, as if Epic didn't even know about the aforementioned setting at all, instead opting for a placebo slider.

 

[Mang Nux]

How about pixel skipping whilst zoomed (say, Lightning Gun)? Has anyone found a way to eliminate this? With the 0.5 axis and 1.25 sens in game I have accuracy to the single pixel, but zoomed it's completely hopeless. The crosshair moves about 5 pixels at a time, and I can literally traverse the mousepad without any movement on screen if I move my hand slow enough.

 

[xMurphyx]

How about pixel skipping whilst zoomed (say, Lightning Gun)? Has anyone found a way to eliminate this? With the 0.5 axis and 1.25 sens in game I have accuracy to the single pixel, but zoomed it's completely hopeless. The crosshair moves about 5 pixels at a time, and I can literally traverse the mousepad without any movement on screen if I move my hand slow enough.

I have the exact same problem in Operation Flashpoint (and higher DPI don't help either!), but in UT2004 my mouse is butter smooth.

I'm guessing it's a DirectInput issue. If you have a mouse driver but never bothered to install it, try installing it. If you have one installed, try deinstalling it and using the default. Didn't help me, but I read of people that solved their problem with this.

It has something to do with acceleration being registered wrong, I think. Not sure. In Operation Flashpoint it helped when I kept the ingame mouse sensitivity high and turned down my dpi instead to get to my desired sensitivity. At the default ingame setting the acceleration at least didn't have the cursor not moving at all and pixel skipping was less bad. But still there.

Anyway, if you do find a solution for this, be sure to post it because I would be very interested in this as well.

 

[Mang Nux]

...but in UT2004 my mouse is butter smooth.

How does your configuration compare with mine:

Mouse: Razer Deathadder (Original 1800DPI Version)
Active DPI: 1800
Polling Rate: 1000Hz

Razer Driver/Firmware: 3.03/1.39(NDC)
Razer Sensitivity: 10/10 (Default 1:1 Movement)
Razer Acceleration: Off

Windows: 7 x64
Windows Sensitivity: 6/11 (Default 1:1 Movement)
Windows Enhance Pointer Precision aka. Acceleration: Off
MarkC Mouse Acceleration Fix applied.

UT2003:
MouseYMultiplier=0.000000
MouseXMultiplier=0.000000
MouseX=Count bXAxis | Axis aMouseX Speed=0.5
MouseY=Count bYAxis | Axis aMouseY Speed=0.5
MouseSamplingTime=0.001000
MouseSensitivity=1.250000

I only have UT2003 on me at this point, but it should be all but identical in this case.

 

[Mang Nux]

Interesting, changing MouseX/YMultiplierfrom 0 to 1 doesn't seem to do anything whatsoever... Changing them to 2 definitely does something though.

 

[xMurphyx]

How does your configuration compare with mine:

Mouse: Razer Diamondback (1600 dpi)

Razer Sensitivity: 10/10 (Default 1:1 Movement)
Razer Acceleration: Off[/SIZE]

Windows: 7 64bit
Windows Sensitivity: 6
Windows Enhance Pointer Precision aka. Acceleration: Off
No special registry fix.

UT2004:
MouseYMultiplier=1.000000
MouseXMultiplier=1.000000
MouseX=Count bXAxis | Axis aMouseX Speed=2.0
MouseY=Count bYAxis | Axis aMouseY Speed=2.0
MouseSamplingTime=0.008333
MouseSensitivity=1.25

Also (these might be UT2004 only. I don't have UT2003 installed so I can't check):
MouseSmoothingMode=0
MouseSmoothingStrength=0.000000
MouseSensitivity=1.000000
MouseAccelThreshold=0.000000

I never had the pixel skipping problem in UT2003 either though, except very lightly with my old 400 dpi mouse, which was most likely due to the mouse.
Nothing as extreme as in Operation Flashpoint though, where I too can move my mouse without moving the crosshairs if I'm slow enough.

 

[Mang Nux]

I'm going to try and replicate those settings, but these is one problem:

MouseSensitivity=1.25

MouseSensitivity=1.000000

^This shouldn't be possible. Those two settings are tied to each other, so 1.25 in the game menu translates to MouseSensitivity=1.250000. I tried it in UT2004 too (my brother has it).

And one critical thing I forgot to note was screen resolution/FOV. Mine is 1920x1080 FOV100, what's yours?

 

[xMurphyx]

Yeah, I checked again and it's 1.00. I used to have it on 1.25 and forgot I changed it.

I have the same resolution and FOV.

 

[Mang Nux]

Thanks for the info.