XML:TXMP - Revision history

Iritscen: I misinterpreted the previous wording of this as I was rewording it – these TXMPs have the flag set already, and the engine has a hardcoded use for them where it looks them up by name

2026-04-05T19:05:53Z

I misinterpreted the previous wording of this as I was rewording it – these TXMPs have the flag set already, and the engine has a hardcoded use for them where it looks them up by name

← Older revision		Revision as of 19:05, 5 April 2026
Line 66:		Line 66:
	: DisableUWrap		: DisableUWrap
	: DisableVWrap		: DisableVWrap
	: Unknown0010 (~~According to SRC, it was~~ used by Bungie's Importer ~~to determine the Pixel Type~~)		: Unknown0010 (only used by Bungie's Importer)
	: AnimUseLocalTime (to export an animated texture, extract the .oni file as XML)		: AnimUseLocalTime (to export an animated texture, extract the .oni file as XML)
	: HasEnvMap (don't use directly; used via tag)		: HasEnvMap (don't use directly; used via tag)
Line 74:		Line 74:
	: SwapBytes (defunct; this is automatically added in v0.9.56.0 and above, so you won't see the flag in an exported)		: SwapBytes (defunct; this is automatically added in v0.9.56.0 and above, so you won't see the flag in an exported)
	: AnimIgnoreGlobalTime		: AnimIgnoreGlobalTime
	: ShieldEffect (~~engine automatically assigns this to~~ TXMPSHIELD – which is not to be confused with [[:Image:TXMPshield.png\|TXMPshield]], also in level0_Final)		: ShieldEffect (only used by TXMPSHIELD – which is not to be confused with [[:Image:TXMPshield.png\|TXMPshield]], also in level0_Final)
	: InvisibilityEffect (~~engine automatically assigns this to~~ TXMPINVIS – which is not to be confused with [[:Image:TXMPinvis.png\|TXMPinvis]], also in level0_Final)		: InvisibilityEffect (only used by TXMPINVIS – which is not to be confused with [[:Image:TXMPinvis.png\|TXMPinvis]], also in level0_Final)
	: DaodanEffect (~~engine automatically assigns this to~~ TXMPDAODAN_SHIELD)		: DaodanEffect (only used by TXMPDAODAN_SHIELD)
	\|-		\|-
	\|valign=top\| <Format>		\|valign=top\| <Format>

Iritscen: case sensitive systems are a bitch; this cost me some time

2026-04-05T17:04:27Z

case sensitive systems are a bitch; this cost me some time

← Older revision		Revision as of 17:04, 5 April 2026
Line 74:		Line 74:
	: SwapBytes (defunct; this is automatically added in v0.9.56.0 and above, so you won't see the flag in an exported)		: SwapBytes (defunct; this is automatically added in v0.9.56.0 and above, so you won't see the flag in an exported)
	: AnimIgnoreGlobalTime		: AnimIgnoreGlobalTime
	: ShieldEffect (~~hardcoded usage~~, ~~reserved for TXMPshield~~)		: ShieldEffect (engine automatically assigns this to TXMPSHIELD – which is not to be confused with [[:Image:TXMPshield.png\|TXMPshield]], also in level0_Final)
	: InvisibilityEffect (~~hardcoded usage~~, ~~reserved for TXMPinvis~~)		: InvisibilityEffect (engine automatically assigns this to TXMPINVIS – which is not to be confused with [[:Image:TXMPinvis.png\|TXMPinvis]], also in level0_Final)
	: DaodanEffect (~~hardcoded usage, reserved for~~ TXMPDAODAN_SHIELD)		: DaodanEffect (engine automatically assigns this to TXMPDAODAN_SHIELD)
	\|-		\|-
	\|valign=top\| <Format>		\|valign=top\| <Format>

Paradox-01 at 15:03, 31 March 2026

2026-03-31T15:03:18Z

← Older revision		Revision as of 15:03, 31 March 2026
Line 2:		Line 2:

	==General notes==		==General notes==
	* The XML on this page was tested with OniSplit '''v0.9.61.0'''.		* The XML on this page was tested with OniSplit '''v0.9.61.0'''. But it will very probably work with other versions too.
	* Textures' X and Y dimensions are typically powers of two (e.g. 128, 256, 512). Oni and OniSplit will accept textures with dimensions that are not power-of-two, however there can be issues with them (see [[User talk:Neo/Archive5]], search "power"), so it's best to avoid them.		* Textures' X and Y dimensions are typically powers of two (e.g. 128, 256, 512). Oni and OniSplit will accept textures with dimensions that are not power-of-two, however there can be issues with them (see [[User talk:Neo/Archive5]], search "power"), so it's best to avoid them.
	* A texture's height and width don't need to be equal, e.g. you can use 128x256.		* A texture's height and width don't need to be equal, e.g. you can use 128x256.
	* The camera can look at 2049 transparent textures at once; one more, and Oni crashes.		* The camera can look at 2049 transparent textures at once; one more, and Oni crashes.
			* For tutorials see:
			** [[Modifying_textures\|Modifying textures]]

	==Tag hierarchy==		==Tag hierarchy==

ValBot: replaced Oni Central Forum link with archive.org snapshot URL

2025-12-26T06:14:03Z

replaced Oni Central Forum link with archive.org snapshot URL

← Older revision		Revision as of 06:14, 26 December 2025
Line 80:		Line 80:
	\| '''A'''RGB formats are used for reflective textures (Alpha Red Green Blue)		\| '''A'''RGB formats are used for reflective textures (Alpha Red Green Blue)

	ARGB8888 can be used only if you use an updated engine (which comes with the AE). (When Macs were still on the PowerPC processor, Oni's textures needed to have [http://oni.bungie.org/forum/viewtopic.php?pid=29967#p29967 their color channels swapped] or else they would appear color-inverted, but after the move to Intel Macs, both platforms used the same Windows-format textures.)		ARGB8888 can be used only if you use an updated engine (which comes with the AE). (When Macs were still on the PowerPC processor, Oni's textures needed to have [http://web.archive.org/web/20160225211918/http://oni.bungie.org/forum/viewtopic.php?pid=29967#p29967 their color channels swapped] or else they would appear color-inverted, but after the move to Intel Macs, both platforms used the same Windows-format textures.)

	{\|class="wikitable" width="100%"		{\|class="wikitable" width="100%"

Iritscen: link fix

2023-11-20T01:20:14Z

link fix

← Older revision		Revision as of 01:20, 20 November 2023
Line 147:		Line 147:
	# When using XML to import, OniSplit can only accept TGA images.		# When using XML to import, OniSplit can only accept TGA images.
	# AdditiveBlend should only be used on things that are supposed to glow — otherwise you might think that the object ignores its vertex shading. In the case of the billboard at the right, this was an improvement; now it's a transparent OLED billboard.		# AdditiveBlend should only be used on things that are supposed to glow — otherwise you might think that the object ignores its vertex shading. In the case of the billboard at the right, this was an improvement; now it's a transparent OLED billboard.
	# Long animations in high quality (512x512, RGB) produce VERY big .oni files. The source billboard GIF is 1.7MB and the resulting .oni file is 273MB. That's because TXAN doesn't support variable timing like the GIF format, so a smooth animation like this one will have a ton of duplicate frames in it. Even as a ZIP, the .oni file was still 66MB, which is unreasonably large. The billboard could possibly be broken into 3 static and 3 transitional images, and then animated "manually" via a [[~~XML:ONLV~~#~~Texture_exchange~~\|BSL loop]]. The conclusion is to use animated images with lower quality settings and to avoid long periods of duplicate frames which waste space.		# Long animations in high quality (512x512, RGB) produce VERY big .oni files. The source billboard GIF is 1.7MB and the resulting .oni file is 273MB. That's because TXAN doesn't support variable timing like the GIF format, so a smooth animation like this one will have a ton of duplicate frames in it. Even as a ZIP, the .oni file was still 66MB, which is unreasonably large. The billboard could possibly be broken into 3 static and 3 transitional images, and then animated "manually" via a [[Creating a level#Texture exchange\|BSL loop]]. The conclusion is to use animated images with lower quality settings and to avoid long periods of duplicate frames which waste space.

	[[Creating animated images\|HERE]] is some information on how to create an animated texture within various graphics programs.		[[Creating animated images\|HERE]] is some information on how to create an animated texture within various graphics programs.

	{{XML}}		{{XML}}

Paradox-01 at 20:55, 7 May 2022

2022-05-07T20:55:17Z

← Older revision		Revision as of 20:55, 7 May 2022
Line 125:		Line 125:
	\|valign=top\| <EnvMap>		\|valign=top\| <EnvMap>
	\|valign=top\| link		\|valign=top\| link
	\| TXMP''name'' (without suffix)		\|
			:TXMP''name'' (without suffix)

	This tag is used if the XML file is meant to create a reflective texture. File suffixes like .tga or .oni are not used in the EnvMap link.		This tag is used if the XML file is meant to create a reflective texture. File suffixes like .tga or .oni are not used in the EnvMap link.
Line 132:		Line 133:
	\|valign=top\| link		\|valign=top\| link
	\|		\|
	: TXMP''name''.tga		:TXMP''name''.tga

	Creating a texture from a JPEG, PNG or DDS is only supported via the command line's "-create:txmp" argument.		Creating a texture from a JPEG, PNG or DDS is only supported via the command line's "-create:txmp" argument.
Line 141:		Line 142:
	[[Image:Animated_level_texture.gif\|200px\|thumb\|Original animated texture.]]		[[Image:Animated_level_texture.gif\|200px\|thumb\|Original animated texture.]]

	It's tiresome to manually create an XML file with a large number of <Image> tags. Skip that work by using [http://~~paradox~~.oni2.net/~~programs~~/~~Simple_OniSplit_GUI.zip~~ Simple OniSplit GUI]. (Normal TXMP creation is also supported.)		It's tiresome to manually create an XML file with a large number of <Image> tags. Skip that work by using [http://mods.oni2.net/node/332 Simple OniSplit GUI]. (Normal TXMP creation is also supported.)

	Some advice:		Some advice:

Iritscen: /* General notes */ OniSplit does allow non-p.o.t. textures, so adjusting note

2021-10-30T19:36:12Z

General notes: OniSplit does allow non-p.o.t. textures, so adjusting note

← Older revision		Revision as of 19:36, 30 October 2021
Line 3:		Line 3:
	==General notes==		==General notes==
	* The XML on this page was tested with OniSplit '''v0.9.61.0'''.		* The XML on this page was tested with OniSplit '''v0.9.61.0'''.
	* Textures' X and Y dimensions are typically powers of two (e.g. 128, 256, 512).		* Textures' X and Y dimensions are typically powers of two (e.g. 128, 256, 512). Oni and OniSplit will accept textures with dimensions that are not power-of-two, however there can be issues with them (see [[User talk:Neo/Archive5]], search "power"), so it's best to avoid them.
	** The engine does support textures ~~of any dimension, however there may be issues~~ with dimensions that are not power-of-two (~~2<sup>x<~~/~~sup>~~) so it's best to avoid them~~. OniSplit itself may require you to supply textures of 2<sup>x</sup> dimensions. Using 2<sup>x</sup> also avoids potential math issues in the 3D code (e.g. mipmapping)~~.
	* A texture's height and width don't need to be equal, e.g. you can use 128x256.		* A texture's height and width don't need to be equal, e.g. you can use 128x256.
	* The camera can look at 2049 transparent textures at once; one more, and Oni crashes.		* The camera can look at 2049 transparent textures at once; one more, and Oni crashes.

Iritscen: clarifying why power-of-two textures are recommended

2021-10-23T12:39:11Z

clarifying why power-of-two textures are recommended

← Older revision		Revision as of 12:39, 23 October 2021
Line 3:		Line 3:
	==General notes==		==General notes==
	* The XML on this page was tested with OniSplit '''v0.9.61.0'''.		* The XML on this page was tested with OniSplit '''v0.9.61.0'''.
	* Textures' X and Y dimensions ~~must be~~ powers of two~~: 512~~, 256, ~~128, 64, etc. (The TXMPs used to compose [[XML:TXMB\|TXMBs]] seem to be an exception~~.)		* Textures' X and Y dimensions are typically powers of two (e.g. 128, 256, 512).
	** ~~But~~ engine ~~really supports non~~-~~standard~~ textures~~, such as 512x288, 256x144, etc~~.		** The engine does support textures of any dimension, however there may be issues with dimensions that are not power-of-two (2<sup>x</sup>) so it's best to avoid them. OniSplit itself may require you to supply textures of 2<sup>x</sup> dimensions. Using 2<sup>x</sup> also avoids potential math issues in the 3D code (e.g. mipmapping).
	** However the height and width don't need to be equal, e.g. you can use 128x256.		* A texture's height and width don't need to be equal, e.g. you can use 128x256.
	* The camera can look at 2049 transparent textures at once; one more, and Oni crashes.		* The camera can look at 2049 transparent textures at once; one more, and Oni crashes.

Mai X: Adding info about non-power-of-two textures. I've checked it during 'Engine demo' creation.

2021-10-12T21:20:16Z

Adding info about non-power-of-two textures. I've checked it during 'Engine demo' creation.

← Older revision		Revision as of 21:20, 12 October 2021
Line 4:		Line 4:
	* The XML on this page was tested with OniSplit '''v0.9.61.0'''.		* The XML on this page was tested with OniSplit '''v0.9.61.0'''.
	* Textures' X and Y dimensions must be powers of two: 512, 256, 128, 64, etc. (The TXMPs used to compose [[XML:TXMB\|TXMBs]] seem to be an exception.)		* Textures' X and Y dimensions must be powers of two: 512, 256, 128, 64, etc. (The TXMPs used to compose [[XML:TXMB\|TXMBs]] seem to be an exception.)
			** But engine really supports non-standard textures, such as 512x288, 256x144, etc.
	** However the height and width don't need to be equal, e.g. you can use 128x256.		** However the height and width don't need to be equal, e.g. you can use 128x256.
	* The camera can look at 2049 transparent textures at once; one more, and Oni crashes.		* The camera can look at 2049 transparent textures at once; one more, and Oni crashes.

Iritscen: wording; no need to sign non-talk pages, we will use the page history to see who did what :-)

2021-09-27T16:05:21Z

wording; no need to sign non-talk pages, we will use the page history to see who did what :-)

← Older revision		Revision as of 16:05, 27 September 2021
Line 125:		Line 125:
	\|valign=top\| <EnvMap>		\|valign=top\| <EnvMap>
	\|valign=top\| link		\|valign=top\| link
	\| TXMP''name'' (~~file~~ suffix ~~.oni/.tga not allowed~~)		\| TXMP''name'' (without suffix)

	This tag is used if the XML file is meant to create a reflective texture. File suffixes like .tga or .oni are not used in the EnvMap link.		This tag is used if the XML file is meant to create a reflective texture. File suffixes like .tga or .oni are not used in the EnvMap link.
Line 149:		Line 149:

	[[Creating animated images\|HERE]] is some information on how to create an animated texture within various graphics programs.		[[Creating animated images\|HERE]] is some information on how to create an animated texture within various graphics programs.
	~~<br>~~
	~~<br>~~
	~~<br>~~
	~~<br>~~
	~~<br>~~
	~~<br>~~
	~~<br>~~
	~~<br>~~
	~~<br>~~
	~~<br>~~
	~~<br>~~
	~~<br>~~
	~~Last edit by: <code>Mai-X</code> <br>~~
	~~17:16, 27 September 2021 (CEST)~~

	{{XML}}		{{XML}}