Benchmarking: Difference between revisions

From Unreal Tournament 2004 MiA Wiki
Piglet (talk | contribs)
approved, Bureaucrats, Interface administrators, Administrators
162 edits
VisualWikitext
Created page with "== 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. <code>./UT2004 fps1?map=2 ini=UT2004.ini log=MyLog.log</code> * For fps1, <code>map=</code> is between 0 and 8 * Maps fps2 and fps 3 are stand-alone maps with no * Unless you use the <code>?quit=1</code> parameter the map will keep running in the background with the console showing results. * Output is put into..."
 
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
== BenchMarking UT2004 renderers ===
= BenchMarking UT2004 renderers =


Download the files linked below. Put the maps into your Maps directory and you can run maps from the command line.
Download the files linked below. Put the maps into your Maps directory and you can run maps from the command line.
Line 5: Line 5:
e.g.  
e.g.  


<code>./UT2004 fps1?map=2 ini=UT2004.ini log=MyLog.log</code>
<code>./UT2004 fps1?map=2 -ini=UT2004.ini log=MyLog.log</code>


* For fps1, <code>map=</code> is between 0 and 8
* For fps1, <code>map=</code> is between 0 and 8
* Maps fps2 and fps 3 are stand-alone maps with no  
* Maps fps2 and fps 3 are stand-alone maps with no <code>map=</code> option
* Unless you use the <code>?quit=1</code> parameter the map will keep running in the background with the console showing results.
* Unless you use the <code>?quit=1</code> parameter the map will keep running in the background with the console showing results.
* Output is put into the log you specify.
* Output is put into the log you specify.
* You can specify any configuration in the <code>ini=</code> file you select. The pack comes with high and low detail defaults to try.
* You can specify any configuration in the <code>ini=</code> file you select. The pack comes with high and low detail defaults to try.
N.B. The scripts provided here update any "RenderDevice=" lines in ini files to flip between renderers. The one that is used by the testing is in the  `[Engine.Engine]` section, but the Unrealed `[Editor.EditorEngine]` one is also updated. Please don't use this ini in unrealed without first resetting the value here.


== Downloads==
== Downloads==
Line 29: Line 32:
</syntaxhighlight>
</syntaxhighlight>
# From PowerShell, navigate to your UT2004 executable <code>System</code> directory and run:
# From PowerShell, navigate to your UT2004 executable <code>System</code> directory and run:
<pre>
#:<syntaxhighlight>
powershell.exe -ExecutionPolicy Bypass -File "..\Benchmark\scripts\Benchmark.ps1"
powershell.exe -ExecutionPolicy Bypass -File "..\Benchmark\scripts\Benchmark.ps1"
</pre>
</syntaxhighlight>
# You should see the game starting multiple times and running a flyby through a map each time.
# You should see the game starting multiple times and running a flyby through a map each time.
# Output is saved into <code>benchmark_results.txt</code>
# Output is saved into <code>benchmark_results.txt</code>
Line 45: Line 48:
FullscreenViewportY=1440
FullscreenViewportY=1440
</syntaxhighlight>
</syntaxhighlight>
# Put these ini files in <code>~/.ut2004/System</code> and edit for the screen resolution you want to test:
#* <code>./ini/BenchmarkLow.ini</code>
#* <code>./ini/BenchmarkHigh.ini</code>
# Navigate to your UT2004 executable <code>System</code> directory and run:
# Navigate to your UT2004 executable <code>System</code> directory and run:
<pre>
#:<syntaxhighlight>
../Benchmark/scripts/Benchmark.sh
../Benchmark/scripts/Benchmark.sh
</pre>
</syntaxhighlight>
# You should see the game starting multiple times and running a flyby through a map each time.
# You should see the game starting multiple times and running a flyby through a map each time.
# Output is saved into <code>benchmark_results.txt</code>
# Output is saved into <code>benchmark_results.txt</code>

Latest revision as of 12:05, 11 May 2026

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.

N.B. The scripts provided here update any "RenderDevice=" lines in ini files to flip between renderers. The one that is used by the testing is in the `[Engine.Engine]` section, but the Unrealed `[Editor.EditorEngine]` one is also updated. Please don't use this ini in unrealed without first resetting the value here.


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"
  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


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
Retrieved from "https://miasma.rocks/wiki/index.php?title=Benchmarking&oldid=241"