Benchmarking - Revision history

Piglet: /* BenchMarking UT2004 renderers */

2026-05-11T12:05:15Z

BenchMarking UT2004 renderers

← Older revision		Revision as of 12:05, 11 May 2026
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

Piglet: /* BenchMarking UT2004 renderers */

2026-05-11T11:47:21Z

BenchMarking UT2004 renderers

← Older revision		Revision as of 11:47, 11 May 2026
Line 12:		Line 12:
	* 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==

Piglet: /* Automation */

2026-05-09T22:05:56Z

Automation

← Older revision		Revision as of 22:05, 9 May 2026
Line 29:		Line 29:
	</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>

Piglet: /* Linux */

2026-05-09T21:01:54Z

Linux

← Older revision		Revision as of 21:01, 9 May 2026
Line 46:		Line 46:
	</syntaxhighlight>		</syntaxhighlight>
	# 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>

Piglet at 21:01, 9 May 2026

2026-05-09T21:01:19Z

← Older revision		Revision as of 21:01, 9 May 2026
Line 45:		Line 45:
	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>		<pre>

Piglet at 20:59, 9 May 2026

2026-05-09T20:59:37Z

← Older revision		Revision as of 20:59, 9 May 2026
Line 8:		Line 8:

	* 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.

Piglet at 19:35, 9 May 2026

2026-05-09T19:35:26Z

← Older revision		Revision as of 19:35, 9 May 2026
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.

Piglet: 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. `./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 * Unless you use the `?quit=1` parameter the map will keep running in the background with the console showing results. * Output is put into..."

2026-05-09T19:34:37Z

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

New page

== 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 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.

== Downloads==

Get the files you need from [http://oldunreal.miasma.rocks/downloads/Benchmarking.7z this link]

==Automation==

=== Windows ===

# 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 <code>Benchmark\scripts</code> directory.
# Put the <code>BenchmarkLow.ini</code> and <code>BenchmarkHigh.ini</code> files from <code>Benchmark/scripts/ini</code> in to your <code>System</code> and edit them for the screen resolution you want to test in this section of each file:
#:<syntaxhighlight>
[WinDrv.WindowsClient]
FullscreenViewportX=3440
FullscreenViewportY=1440
</syntaxhighlight>
# From PowerShell, navigate to your UT2004 executable <code>System</code> directory and run:
<pre>
powershell.exe -ExecutionPolicy Bypass -File "..\Benchmark\scripts\Benchmark.ps1"
</pre>
# 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>

=== Linux ===

# 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 <code>Benchmark/scripts</code> directory.
# Put the <code>BenchmarkLow.ini</code> and <code>BenchmarkHigh.ini</code> files from <code>Benchmark/scripts/ini</code> in to your <code>~/.ut2004/System</code> directory and edit them for the screen resolution you want to test in this section of each file:
#:<syntaxhighlight>
[SDLDrv.SDLClient]
FullscreenViewportX=3440
FullscreenViewportY=1440
</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:
<pre>
../Benchmark/scripts/Benchmark.sh
</pre>
# 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>