Benchmarking

BenchMarking UT2004 renderers

Download the files linked below. Put the maps into your Maps directory and you can run maps from the command line.

e.g.

./UT2004 fps1?map=2 ini=UT2004.ini log=MyLog.log

• For fps1, map= is between 0 and 8
• Maps fps2 and fps 3 are stand-alone maps with no map= option
• Unless you use the ?quit=1 parameter the map will keep running in the background with the console showing results.
• Output is put into the log you specify.
• You can specify any configuration in the ini= file you select. The pack comes with high and low detail defaults to try.

Downloads

Get the files you need from this link

Automation

Windows

1. Extract the 7z zip into your ut2004 directory. The maps should end up in your Maps directory. The scripts to automate runs should be in your Benchmark\scripts directory.
2. Put the BenchmarkLow.ini and BenchmarkHigh.ini files from Benchmark/scripts/ini in to your System and edit them for the screen resolution you want to test in this section of each file:

   [WinDrv.WindowsClient]
   FullscreenViewportX=3440
   FullscreenViewportY=1440

3. From PowerShell, navigate to your UT2004 executable System directory and run:

powershell.exe -ExecutionPolicy Bypass -File "..\Benchmark\scripts\Benchmark.ps1"

1. You should see the game starting multiple times and running a flyby through a map each time.
2. Output is saved into benchmark_results.txt

Linux

1. Extract the 7z zip into your ut2004 directory. The maps should end up in your Maps directory. The scripts to automate runs should be in your Benchmark/scripts directory.
2. Put the BenchmarkLow.ini and BenchmarkHigh.ini files from Benchmark/scripts/ini in to your ~/.ut2004/System directory and edit them for the screen resolution you want to test in this section of each file:

   [SDLDrv.SDLClient]
   FullscreenViewportX=3440
   FullscreenViewportY=1440

3. Navigate to your UT2004 executable System directory and run:

   ../Benchmark/scripts/Benchmark.sh

4. You should see the game starting multiple times and running a flyby through a map each time.
5. Output is saved into benchmark_results.txt