MouseFix ?

[}TCP{Ramses]

Eek I am stuck, not sure what to do for best ....

We have a match on Sunday, so I re-installed Unreal and patched it up with Wolf's latest Uteamfix because I thought it fixed the dreaded XP mouse acceleration, which it did, worked great

But when I tried to join some servers (including the match server), I got the version mismatch thing ... so I reinstalled from scratch again to join the training session. Only problem is I get the wonderful whirling world of mouse acceleration.

I've looked for 227 patch but this seems to be in development.

I have a mouse patch that Wolf gave me ages ago, but I am not sure whether it patches only for Unreal or if it changes mouse settings for everything (I dont fancy having to recalibrate every other game again )

So .... what the best thing to do to fix that rodent ? I run the Unreal Gold (original not anthology). Any help appreciated, preferably before Sunday night

[Van]

Not sure if this would of helped but when I get the version mismatch thingy in Unreal, I type obj garbarge and then I am able to get in the server.

The mouse thing is beyond me.

[}TCP{Ramses]

Thanks Van , but that would not help me because I installed Teamfix rather than picking it up from the server, so "obj garbage" would not get rid of it for me. Thanks anyway

[}TCP{Wolf]

Ah...

Taz told me you had a problem and that's why I am showing up on the board today.

The mouse issue is as follows:


First off, the registry patch (also known as the "Counter Strike patch") basically affects "many" older games, that includes Half-Life, Unreal, UT.... strangely not Quake II or III. It is also irrelevant for newer games such as UT2k4.

So for you, install the registry fix since you play Unreal.

Next: UTF / 227 mouse fix.

Background:
http://www.oldunreal.com/cgi-bin/yabb2/ ... 1181243007

Summary for you:
Forget about 227 for now, since it isn't out yet. However, that feature will be in 227 - indeed 227 I have already has it

Rams, what you have todo is, set up 2 mouse sensitivities. One with UTeamFix 10C and one without.

First, configure the mouse normally so you can play ok on normal servers without UTF, or an old UTF. Then, load UTF 10C - or join a server that uses it - get to the UTF menu and adjust this:

http://wolf.tcpclan.net/projects/Unreal ... entOptions

Set "disable smoothing" to true and now comes the tricky part. Enter a good sensitivity value below. If you enter "0" the value of your "normal" mouse is used, however, since the movement de-acceleration is now GONE, you will have greater movement. So the value you enter there must be a bit smaller than your usual mouse sensitivity.

For your information, my normal sensitivity is this:
MouseX=Axis aMouseX Speed=1.0
MouseY=Axis aMouseY Speed=1.0
...
MouseSensitivity=13.770000
...

in UTF, the MouseX and MouseY stay untouched, but...
UTFMouseSensitivity=13.000000

This way, when I join a normal server (or any server without UTF 10C), 13.77 is used, when I join a UTF 10C server, it automatically switches to 13 with no smoothing.

When you have set this up, delete the UTF files from your system directory. Then you will able to join -any- server because any files you are missing will be in the cache. If you get version conflicts, either exit and restart Unreal, or type "open entry" and then "obj garbage", then rejoin the server you attempted to join.

Technical background to version conflicts:

http://www.oldunreal.com/UnrealReference/versions.htm

Enjoy....

[}TCP{Ramses]

Thanks Wolf ... that's made the mouse fix thing clear, I read a few googled items and wasn't sure what the best latest route to straight shooting was

I don't know why I found acceleration so vexing to fix when Taz clearly has it sorted so well. Its actually very handy that the registry patch also sorts older titles, I may well be tempted to replay Half Life, The Wheel of Time and others in the future

[PingKing]

wolf knows how to fix it handyman wolf