Unreal tournament movement/performance all messed up

halfgaar · l33t Joined: 22 Feb 2004 Posts: 781 Location: Netherlands

Hi,

Suddenly, Unreal Tournament (1999 version) behaves very strangely on my PC. When I walk, I warp around the map like what happens when you have lag in a network game. But, I also have it in a offline game. And, it's not just in moving around, it's everything (animations, bots, etc). And, my view is pointing in all kinds of directions automaticly, as if the mouse is running away on it's own, which it never does normally (unlike some optical mice).

I have no idea what caused this. I played a succesful game last sunday or saterday. I haven't changed any software, drivers or configuration since then. It's also not cool'n'quiet, because I have disabled it (by setting it on 'performace', which causes the clock not to slow down). Cool'n'quiet normally has the effect on UT that it runs way too fast, probably because it does it's cpu speed estimation on the slow clock, which is later increased.

Anybody has suggestions?

Unreal-tournament version: 451

Emerge info:

RushPL · Posted: Wed May 17, 2006 5:24 pm Post subject:

Try out this script -> http://lux.one.pl/~rush/ut/ut instead of the default one. Just backup the one at /opt/unreal-tournament/ut and replace it with the new one. Furthermore you have to edit the script and set CPUFREQ="ON".

edit: sorry for not reading your post to the end at first .. now I noticed that you say you have disabled the fancy cool&quiet(or whatever it's called) .. anyway this script should allow you to run ut even if it's on. However as it wasn't tested it would be nice if you could confirm it.

halfgaar · l33t Joined: 22 Feb 2004 Posts: 781 Location: Netherlands

I don't think I like the way that script fixes it, by running "nice -n18 cat /dev/zero > /dev/null &" to keep the CPU at 100%. And, it needs a small adjustment because I have a dual core CPU, so the command needs to be run twice.

However, I did try running the cat job in the background. It did solve my problem. Don't ask me how it's possible, because the CPU clock should remain at 2000 all the time, for both cores. I will try disabling cool'n'quiet alltoghether in the kernel and see what happens.

halfgaar · l33t Joined: 22 Feb 2004 Posts: 781 Location: Netherlands

Hmm, for some reason, turning off the cpu scaling solved it. Either that, or the reboot itself fixed the problem. Oh well, since I didn't use scaling anyway, having it turned off is not so undesirable.