The game runs way too fast on AMD64. E.g. Players can run and shoot at least
twice as fast as on x86. The worst thing is that this even works over the
Internet.
Computer is an Athlon64 3000+ with SuSE 9.0/x86_64
Comment 1Andrew 'ashridah' Pilley
2004-02-19 16:12:10 EST
Hmm. have you tried checking that the 'slomo' command has been set to 'slomo
1'?
It's possible to run the game from 50% to 150-200% speed based on a
server-side setting, and i'm fairly certain it gets saved.
Andrew
It's not server side, the intro movie is already too fast. It was this way
when the game was first started and I didn't change any settings that are not
in the gui.
We found the problem. It's cpufreqd. A recent BIOS update enabled this
Cool-n-Quiet stuff, which causes cpufreqd to clock down the CPU when the
system is idle. During normal Desktop usage the CPU runs at 800MHz, when
running a game at 2000MHz. I guess UT based games have some calibration loop
at the beginning that gets confused if the CPU changes it's speed dynamically?
(Postal2 also runs too fast with cpufreqd enabled)
Hhm...we have some fixes for UnrealEngine3 so we don't rely on RDTSC (which
Cool'n'Quiet and other related technologies make unreliable)...will see about
backporting them to UnrealEngine2 (which ut2004 and postal2, etc, use).
--ryan.
I believe this to be fixed internally now...we now rely on gettimeofday()
instead of the rdtsc instruction; I trust that cpufreqd will alter the kernel's
gettimeofday() reponses appropriately?
I'll send on a new demo build for SuSE to test shortly.
--ryan.
Here's an unsupported binary (i.e. - don't package it in an .rpm or whatnot):
http://icculus.org/~icculus/tmp/ut2004demo-lnx-cpufreqd-fix.tar.bz2
Please test with and without cpufreqd and see if it fixes the issue.
This is for the 32-bit version of the game, but the same fix should apply to
amd64 if this takes care of the bug.
Thanks,
--ryan.
Here's an unsupported binary (i.e. - don't package it in an .rpm or whatnot): http://icculus.org/~icculus/tmp/ut2004demo-lnx-cpufreqd-fix.tar.bz2 Please test with and without cpufreqd and see if it fixes the issue. This is for the 32-bit version of the game, but the same fix should apply to amd64 if this takes care of the bug. Thanks, --ryan.