Trouble-shooting v3374 Preview 9 - Revision history

Piglet at 21:59, 21 February 2026

2026-02-21T21:59:31Z

← Older revision		Revision as of 21:59, 21 February 2026
Line 20:		Line 20:
	# <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.		# <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.
	# <span id="stats">If you get a message along the lines of <code>Must have stats enabled to join this server</code></span>, from the main menu go to Settings → Game, click the "Track Stats" checkbox, and put any username and password you like into the "UserName" and "Password" fields.		# <span id="stats">If you get a message along the lines of <code>Must have stats enabled to join this server</code></span>, from the main menu go to Settings → Game, click the "Track Stats" checkbox, and put any username and password you like into the "UserName" and "Password" fields.
	# <span id="programfiles">If you can't start the game on Windows and get a message like <code>Can't find 'ini:Engine.Engine.GameEngine' in configuration file</code> then you've probably installed the game into 'Program Files'. It needs to be installed somewhere else.		# <span id="programfiles">If you can't start the game on Windows and get a message like <code>Can't find 'ini:Engine.Engine.GameEngine' in configuration file</code> then you've probably installed the game into 'Program Files'. It needs to be installed somewhere else, or run as administrator.
	#: [[File:Image for touble shooting -9.png\|thumb\|none]]		#: [[File:Image for touble shooting -9.png\|thumb\|none]]
	#If you're trying to run UCC make on ARM, and get stuck with the message <code>"-------------------------Core - Release------------------------- Analyzing..</code> then try copying or symlinking all the .u files from your install location's System directory to your install location's SystemARM64.		#If you're trying to run UCC make on ARM, and get stuck with the message <code>"-------------------------Core - Release------------------------- Analyzing..</code> then try copying or symlinking all the .u files from your install location's System directory to your install location's SystemARM64.

Piglet at 21:59, 21 February 2026

2026-02-21T21:59:03Z

← Older revision		Revision as of 21:59, 21 February 2026
Line 21:		Line 21:
	# <span id="stats">If you get a message along the lines of <code>Must have stats enabled to join this server</code></span>, from the main menu go to Settings → Game, click the "Track Stats" checkbox, and put any username and password you like into the "UserName" and "Password" fields.		# <span id="stats">If you get a message along the lines of <code>Must have stats enabled to join this server</code></span>, from the main menu go to Settings → Game, click the "Track Stats" checkbox, and put any username and password you like into the "UserName" and "Password" fields.
	# <span id="programfiles">If you can't start the game on Windows and get a message like <code>Can't find 'ini:Engine.Engine.GameEngine' in configuration file</code> then you've probably installed the game into 'Program Files'. It needs to be installed somewhere else.		# <span id="programfiles">If you can't start the game on Windows and get a message like <code>Can't find 'ini:Engine.Engine.GameEngine' in configuration file</code> then you've probably installed the game into 'Program Files'. It needs to be installed somewhere else.
			#: [[File:Image for touble shooting -9.png\|thumb\|none]]
	#If you're trying to run UCC make on ARM, and get stuck with the message <code>"-------------------------Core - Release------------------------- Analyzing..</code> then try copying or symlinking all the .u files from your install location's System directory to your install location's SystemARM64.		#If you're trying to run UCC make on ARM, and get stuck with the message <code>"-------------------------Core - Release------------------------- Analyzing..</code> then try copying or symlinking all the .u files from your install location's System directory to your install location's SystemARM64.
	#If you're trying to use UCC to output content - for example <code>UCC make</code> or <code>UCC batchexport</code> on Linux, please be aware that on Linux everything UCC related is output relative to <code>~/.ut2004/</code> regardless of the path you run the executable from.		#If you're trying to use UCC to output content - for example <code>UCC make</code> or <code>UCC batchexport</code> on Linux, please be aware that on Linux everything UCC related is output relative to <code>~/.ut2004/</code> regardless of the path you run the executable from.

Piglet at 14:33, 20 February 2026

2026-02-20T14:33:52Z

← Older revision		Revision as of 14:33, 20 February 2026
Line 8:		Line 8:
	# <span id="arm9">If you're on ARM64 and using version 3374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.		# <span id="arm9">If you're on ARM64 and using version 3374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.
	#:		#:
	#: So, for a standard install on a Pi open a terminal and input the following in turn, and then start up the game:		#: So, for a standard OldUnreal install on a Pi open a terminal and input the following in turn, and then start up the game:
	#:		#:
	#: <syntaxhighlight lang="bash">		#: <syntaxhighlight lang="bash">

Piglet at 14:33, 20 February 2026

2026-02-20T14:33:26Z

← Older revision		Revision as of 14:33, 20 February 2026
Line 6:		Line 6:
	# <span id="wrongexe">If you get a crash with message <code>Log: Splash screen filename is '..\Help\ut2004-win64Logo.bmp' Localization: No localization: ut2004-win64.General.Start</code></span>, you're running the wrong executable. See the line above.		# <span id="wrongexe">If you get a crash with message <code>Log: Splash screen filename is '..\Help\ut2004-win64Logo.bmp' Localization: No localization: ut2004-win64.General.Start</code></span>, you're running the wrong executable. See the line above.
	# <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].		# <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].
	# <span id="arm9">If you're on ARM64 and using version 3374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.		# <span id="arm9">If you're on ARM64 and using version 3374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.
	:So, for a standard install on a Pi open a terminal and input the following in turn, and then start up the game:		#:
			#: So, for a standard install on a Pi open a terminal and input the following in turn, and then start up the game:
	#:		#:
	#: <syntaxhighlight lang="bash">		#: <syntaxhighlight lang="bash">
Line 15:		Line 16:
	cp ~/.local/share/OldUnreal/UT2004/System/DefUser.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/		cp ~/.local/share/OldUnreal/UT2004/System/DefUser.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/
	</syntaxhighlight>		</syntaxhighlight>
			#
	# <span id="unrealed">If you can't see asset browser windows on Unrealed, try renaming <code>System\UnrealEd.ini</code></span> and starting Unrealed to get default settings.		# <span id="unrealed">If you can't see asset browser windows on Unrealed, try renaming <code>System\UnrealEd.ini</code></span> and starting Unrealed to get default settings.
	# <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.		# <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.

Piglet at 14:31, 20 February 2026

2026-02-20T14:31:33Z

← Older revision		Revision as of 14:31, 20 February 2026
Line 6:		Line 6:
	# <span id="wrongexe">If you get a crash with message <code>Log: Splash screen filename is '..\Help\ut2004-win64Logo.bmp' Localization: No localization: ut2004-win64.General.Start</code></span>, you're running the wrong executable. See the line above.		# <span id="wrongexe">If you get a crash with message <code>Log: Splash screen filename is '..\Help\ut2004-win64Logo.bmp' Localization: No localization: ut2004-win64.General.Start</code></span>, you're running the wrong executable. See the line above.
	# <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].		# <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].
	# <span id="arm9">If you're on ARM64 and using version 3374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.		# <span id="arm9">If you're on ARM64 and using version 3374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.
	#*So, for a standard install on a Pi open a terminal and input the following in turn, and then start up the game:		:So, for a standard install on a Pi open a terminal and input the following in turn, and then start up the game:
	<~~pre~~>rm ~/.ut2004/System/UT2004.ini		#:
			#: <syntaxhighlight lang="bash">
			rm ~/.ut2004/System/UT2004.ini
	rm ~/.ut2004/System/User.ini		rm ~/.ut2004/System/User.ini
	cp ~/.local/share/OldUnreal/UT2004/System/Default.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/		cp ~/.local/share/OldUnreal/UT2004/System/Default.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/
	cp ~/.local/share/OldUnreal/UT2004/System/DefUser.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/		cp ~/.local/share/OldUnreal/UT2004/System/DefUser.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/
	</~~pre~~>		</syntaxhighlight>
	# <span id="unrealed">If you can't see asset browser windows on Unrealed, try renaming <code>System\UnrealEd.ini</code></span> and starting Unrealed to get default settings.		# <span id="unrealed">If you can't see asset browser windows on Unrealed, try renaming <code>System\UnrealEd.ini</code></span> and starting Unrealed to get default settings.
	# <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.		# <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.

Piglet at 14:23, 20 February 2026

2026-02-20T14:23:20Z

← Older revision		Revision as of 14:23, 20 February 2026
Line 7:		Line 7:
	# <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].		# <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].
	# <span id="arm9">If you're on ARM64 and using version 3374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.		# <span id="arm9">If you're on ARM64 and using version 3374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.
	#*So, for a standard install on a Pi ~~openup~~ a terminal and input in turn, and then start up the game:		#*So, for a standard install on a Pi open a terminal and input the following in turn, and then start up the game:
	#**rm ~/.ut2004/System/UT2004.ini		<pre>rm ~/.ut2004/System/UT2004.ini
	#**rm ~/.ut2004/System/User.ini		rm ~/.ut2004/System/User.ini
	#**cp ~/.local/share/OldUnreal/UT2004/System/Default.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/		cp ~/.local/share/OldUnreal/UT2004/System/Default.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/
	#**cp ~/.local/share/OldUnreal/UT2004/System/DefUser.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/		cp ~/.local/share/OldUnreal/UT2004/System/DefUser.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/
			</pre>
	# <span id="unrealed">If you can't see asset browser windows on Unrealed, try renaming <code>System\UnrealEd.ini</code></span> and starting Unrealed to get default settings.		# <span id="unrealed">If you can't see asset browser windows on Unrealed, try renaming <code>System\UnrealEd.ini</code></span> and starting Unrealed to get default settings.
	# <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.		# <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.

Piglet at 14:17, 20 February 2026

2026-02-20T14:17:49Z

← Older revision		Revision as of 14:17, 20 February 2026
Line 6:		Line 6:
	# <span id="wrongexe">If you get a crash with message <code>Log: Splash screen filename is '..\Help\ut2004-win64Logo.bmp' Localization: No localization: ut2004-win64.General.Start</code></span>, you're running the wrong executable. See the line above.		# <span id="wrongexe">If you get a crash with message <code>Log: Splash screen filename is '..\Help\ut2004-win64Logo.bmp' Localization: No localization: ut2004-win64.General.Start</code></span>, you're running the wrong executable. See the line above.
	# <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].		# <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].
	# <span id="arm9">If you're on ARM64 and using version ~~33374~~ patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.		# <span id="arm9">If you're on ARM64 and using version 3374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.
	#*So, for a standard install on a Pi openup a terminal and input in turn, and then start up the game:		#*So, for a standard install on a Pi openup a terminal and input in turn, and then start up the game:
	#**rm ~/.ut2004/System/UT2004.ini		#**rm ~/.ut2004/System/UT2004.ini

Piglet at 14:16, 20 February 2026

2026-02-20T14:16:51Z

← Older revision		Revision as of 14:16, 20 February 2026
Line 1:		Line 1:
	== Trouble-shooting ==		== Trouble-shooting ==

	* <span id="libs">The Linux patch ships with its own libSDL3</span>, and if you already have this installed or you want to use a newer version you can delete the included one and use/install a system provided libSDL3 and/or libopenal instead.		# <span id="libs">The Linux patch ships with its own libSDL3</span>, and if you already have this installed or you want to use a newer version you can delete the included one and use/install a system provided libSDL3 and/or libopenal instead.
	* <span id="openal">As we're using OpenAl for audio, you can use [https://openal-soft.org/#download this software]</span> to adjust sound settings.		# <span id="openal">As we're using OpenAl for audio, you can use [https://openal-soft.org/#download this software]</span> to adjust sound settings.
	* <span id="blackscreen">If you get a black screen you're probably running the wrong executable.</span> It should be <code>UT2004</code> on Linux and <code>UT2004.exe</code> on Windows.		# <span id="blackscreen">If you get a black screen you're probably running the wrong executable.</span> It should be <code>UT2004</code> on Linux and <code>UT2004.exe</code> on Windows.
	* <span id="wrongexe">If you get a crash with message <code>Log: Splash screen filename is '..\Help\ut2004-win64Logo.bmp' Localization: No localization: ut2004-win64.General.Start</code></span>, you're running the wrong executable. See the line above.		# <span id="wrongexe">If you get a crash with message <code>Log: Splash screen filename is '..\Help\ut2004-win64Logo.bmp' Localization: No localization: ut2004-win64.General.Start</code></span>, you're running the wrong executable. See the line above.
	* <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].		# <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].
	* <span id="arm9">If you're on ARM64 and using version 33374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.		# <span id="arm9">If you're on ARM64 and using version 33374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.
	* <span id="unrealed">If you can't see asset browser windows on Unrealed, try renaming <code>System\UnrealEd.ini</code></span> and starting Unrealed to get default settings.		#*So, for a standard install on a Pi openup a terminal and input in turn, and then start up the game:
	* <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.		#**rm ~/.ut2004/System/UT2004.ini
	* <span id="stats">If you get a message along the lines of <code>Must have stats enabled to join this server</code></span>, from the main menu go to Settings → Game, click the "Track Stats" checkbox, and put any username and password you like into the "UserName" and "Password" fields.		#**rm ~/.ut2004/System/User.ini
	* <span id="programfiles">If you can't start the game on Windows and get a message like <code>Can't find 'ini:Engine.Engine.GameEngine' in configuration file</code> then you've probably installed the game into 'Program Files'. It needs to be installed somewhere else.		#**cp ~/.local/share/OldUnreal/UT2004/System/Default.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/
	*If you're trying to run UCC make on ARM, and get stuck with the message <code>"-------------------------Core - Release------------------------- Analyzing..</code> then try copying or symlinking all the .u files from your install location's System directory to your install location's SystemARM64.		#**cp ~/.local/share/OldUnreal/UT2004/System/DefUser.ini ~/.local/share/OldUnreal/UT2004/SystemARM64/
	*If you're trying to use UCC to output content - for example <code>UCC make</code> or <code>UCC batchexport</code> on Linux, please be aware that on Linux everything UCC related is output relative to <code>~/.ut2004/</code> regardless of the path you run the executable from.		# <span id="unrealed">If you can't see asset browser windows on Unrealed, try renaming <code>System\UnrealEd.ini</code></span> and starting Unrealed to get default settings.
			# <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.
			# <span id="stats">If you get a message along the lines of <code>Must have stats enabled to join this server</code></span>, from the main menu go to Settings → Game, click the "Track Stats" checkbox, and put any username and password you like into the "UserName" and "Password" fields.
			# <span id="programfiles">If you can't start the game on Windows and get a message like <code>Can't find 'ini:Engine.Engine.GameEngine' in configuration file</code> then you've probably installed the game into 'Program Files'. It needs to be installed somewhere else.
			#If you're trying to run UCC make on ARM, and get stuck with the message <code>"-------------------------Core - Release------------------------- Analyzing..</code> then try copying or symlinking all the .u files from your install location's System directory to your install location's SystemARM64.
			#If you're trying to use UCC to output content - for example <code>UCC make</code> or <code>UCC batchexport</code> on Linux, please be aware that on Linux everything UCC related is output relative to <code>~/.ut2004/</code> regardless of the path you run the executable from.

	==Preview 10 additions==		==Preview 10 additions==

	The Community->Mods page on Linux should be working from preview 10. Just install the mods relative to ~/.ut2004 rather than relative to the executable path to avoid the pop-up when it tries to load the spash screen for the mod.		The Community->Mods page on Linux should be working from preview 10. Just install the mods relative to ~/.ut2004 rather than relative to the executable path to avoid the pop-up when it tries to load the spash screen for the mod.

Piglet at 10:30, 20 February 2026

2026-02-20T10:30:19Z

← Older revision		Revision as of 10:30, 20 February 2026
Line 13:		Line 13:
	*If you're trying to run UCC make on ARM, and get stuck with the message <code>"-------------------------Core - Release------------------------- Analyzing..</code> then try copying or symlinking all the .u files from your install location's System directory to your install location's SystemARM64.		*If you're trying to run UCC make on ARM, and get stuck with the message <code>"-------------------------Core - Release------------------------- Analyzing..</code> then try copying or symlinking all the .u files from your install location's System directory to your install location's SystemARM64.
	*If you're trying to use UCC to output content - for example <code>UCC make</code> or <code>UCC batchexport</code> on Linux, please be aware that on Linux everything UCC related is output relative to <code>~/.ut2004/</code> regardless of the path you run the executable from.		*If you're trying to use UCC to output content - for example <code>UCC make</code> or <code>UCC batchexport</code> on Linux, please be aware that on Linux everything UCC related is output relative to <code>~/.ut2004/</code> regardless of the path you run the executable from.

			==Preview 10 additions==

			The Community->Mods page on Linux should be working from preview 10. Just install the mods relative to ~/.ut2004 rather than relative to the executable path to avoid the pop-up when it tries to load the spash screen for the mod.

Piglet at 17:15, 19 February 2026

2026-02-19T17:15:53Z

← Older revision		Revision as of 17:15, 19 February 2026
Line 2:		Line 2:

	* <span id="libs">The Linux patch ships with its own libSDL3</span>, and if you already have this installed or you want to use a newer version you can delete the included one and use/install a system provided libSDL3 and/or libopenal instead.		* <span id="libs">The Linux patch ships with its own libSDL3</span>, and if you already have this installed or you want to use a newer version you can delete the included one and use/install a system provided libSDL3 and/or libopenal instead.

	* <span id="openal">As we're using OpenAl for audio, you can use [https://openal-soft.org/#download this software]</span> to adjust sound settings.		* <span id="openal">As we're using OpenAl for audio, you can use [https://openal-soft.org/#download this software]</span> to adjust sound settings.

	* <span id="blackscreen">If you get a black screen you're probably running the wrong executable.</span> It should be <code>UT2004</code> on Linux and <code>UT2004.exe</code> on Windows.		* <span id="blackscreen">If you get a black screen you're probably running the wrong executable.</span> It should be <code>UT2004</code> on Linux and <code>UT2004.exe</code> on Windows.

	* <span id="wrongexe">If you get a crash with message <code>Log: Splash screen filename is '..\Help\ut2004-win64Logo.bmp' Localization: No localization: ut2004-win64.General.Start</code></span>, you're running the wrong executable. See the line above.		* <span id="wrongexe">If you get a crash with message <code>Log: Splash screen filename is '..\Help\ut2004-win64Logo.bmp' Localization: No localization: ut2004-win64.General.Start</code></span>, you're running the wrong executable. See the line above.

	* <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].		* <span id="dx9">If you're on Windows and DX9 doesn't work, then you're probably missing libraries.</span> Install [https://www.microsoft.com/en-us/download/details.aspx?id=35 from here].

	* <span id="arm9">If you're on ARM64 and using version 33374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.		* <span id="arm9">If you're on ARM64 and using version 33374 patch 9, there's a couple of old files that slipped into the package.</span> You may crash at startup with the message "<code>Failed to enter Entry: Can't find file 'Entry'</code>". To fix this delete ~/.ut2004/System/User.ini and UT2004.ini, then copy Default.ini and DefUser.ini from the install System directory to the install SystemARM64 directory and start the game.

	* <span id="unrealed">If you can't see asset browser windows on Unrealed, try renaming <code>System\UnrealEd.ini</code></span> and starting Unrealed to get default settings.		* <span id="unrealed">If you can't see asset browser windows on Unrealed, try renaming <code>System\UnrealEd.ini</code></span> and starting Unrealed to get default settings.

	* <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.		* <span id="oldu">If you are on Linux and can't run, and get messages along the lines of <code>Critical: IpDrv C++/UnrealScript class size mismatch</code> or <code>x Failed to find object 'Class GUI2K4.UT2K4MainMenuWS'</code> in your <code>~/.ut2004/UT2004.log</code></span> you have old .u files in a System directory the executable is trying to use. Delete the old files and re-extract from the patch.

	* <span id="stats">If you get a message along the lines of <code>Must have stats enabled to join this server</code></span>, from the main menu go to Settings → Game, click the "Track Stats" checkbox, and put any username and password you like into the "UserName" and "Password" fields.		* <span id="stats">If you get a message along the lines of <code>Must have stats enabled to join this server</code></span>, from the main menu go to Settings → Game, click the "Track Stats" checkbox, and put any username and password you like into the "UserName" and "Password" fields.

	* <span id="programfiles">If you can't start the game on Windows and get a message like <code>Can't find 'ini:Engine.Engine.GameEngine' in configuration file</code> then you've probably installed the game into 'Program Files'. It needs to be installed somewhere else.		* <span id="programfiles">If you can't start the game on Windows and get a message like <code>Can't find 'ini:Engine.Engine.GameEngine' in configuration file</code> then you've probably installed the game into 'Program Files'. It needs to be installed somewhere else.

	*If you're trying to run UCC make on ARM, and get stuck with the message <code>"-------------------------Core - Release------------------------- Analyzing..</code> then try copying or symlinking all the .u files from your install location's System directory to your install location's SystemARM64.		*If you're trying to run UCC make on ARM, and get stuck with the message <code>"-------------------------Core - Release------------------------- Analyzing..</code> then try copying or symlinking all the .u files from your install location's System directory to your install location's SystemARM64.
	*If you're trying to use UCC to output content - for example <code>UCC make</code> or <code>UCC batchexport</code> on Linux, please be aware that on Linux everything UCC related is output relative to <code>~/.ut2004/</code> regardless of the path you run the executable from.		*If you're trying to use UCC to output content - for example <code>UCC make</code> or <code>UCC batchexport</code> on Linux, please be aware that on Linux everything UCC related is output relative to <code>~/.ut2004/</code> regardless of the path you run the executable from.