Saturday, September 14, 2002

UT2K3 Benchmarks in Linux -- 12:30 pm CST, Update by A.T. Hun

With the help of Ryan "icculus" Gordon on the UT2K3 Linux mailing list, I managed to get benchmarks working in the Unreal Tournament 2003 demo in Linux. Here are the steps:

1. Edit the batch files in the Benchmark directory where you installed the demo. For example, I saved the botmatch-citadel.bat file as botmatch-citadel.sh and edited it so it contains the following:

   ../ut2003_demo ctf-citadel?spectatoronly=true?numbots=12?quickstart=true -benchmark -seconds=77 -exec=../Benchmark/Stuff/botmatchexec.txt $1

   From that you should be able to figure out how to alter any of the other batch files. Just change the slashes and have it point to ../ut2003_demo instead of ..Systemut2003. I also changed the %1 at the end to $1 so you can pass command line arguments to it.
2. Type this command to add the necessary directories: mkdir -p $HOME/.ut2003/Benchmark/Results
3. Go to the Benchmark directory where you installed the demo (the default is /usr/local/games/ut2003_demo/Benchmark) and run ./botmatch-citadel.sh
4. When the benchmark is done, the result will be written in $HOME/.ut2003/Benchmark/Results

My results are quite a bit slower than in Windows. In the Citadel botmatch I got 25.2 fps (33.1 in Windows) and in the Citadel flyby I got 48.9 (63.9 in Windows). I assume the main culprit is the difference between the OpenGL and D3D renderers. With so many variables, it's hard to say for sure. Those benchmarks were run at 1024x768x32 with all the options cranked. Dropping down to 800x600 gave me slightly better results than Windows at 1024x768.

icculus also noted that typing stat fps in the console will display your fps as you are playing. That should work in both the Linux and Windows versions of the game.

UPDATE! I found out that there is actually an OpenGL renderer in the Windows demo (check your UT2003.ini file if you are interested). With that renderer, I got 43.6 fps on the Citadel flyby and 24.2 on the botmatch. Besides being much slower, the OpenGL renderer also displayed a bunch of graphical weirdness, such as flashing textures. Therefore, it seems that the renderer is the main culprit. However, I also found out that the botmatches are different in Linux and Windows. Epic's Daniel Vogel made this post on the UT2K3 Linux mailing list:

Botmatches are OS/compiler dependent. Try the flybys.

Thus, the botmatches won't give a true Windows vs. Linux comparison. Nevertheless, it is clear that the OpenGL renderer is significantly slower than the Direct3D one--not that that's a big surprise. That's basically what Epic's been saying from the beginning.

News for 09/14/2002

The Haus is powered by:

All original information on this website is copyright © TheHaus.Net, 1999-2005. The use of original images, text, and/or code from this website without expressed written consent is prohibited. The authors of this site cannot be held responsible for any damage, real or imagined, which comes from the use of information presented on this site. All trademarks used are the properties of their respective owners. This site is not to be used as a floatation device (but if you try, I want a video tape of it).