TMP - Revision history

MarkJFox: 16 revisions imported

2025-03-31T19:25:46Z

16 revisions imported

← Older revision	Revision as of 21:25, 31 March 2025
(No difference)

en>Crimsonum: Fixed footnote link.

2022-04-20T06:43:05Z

Fixed footnote link.

← Older revision		Revision as of 08:43, 20 April 2022
Line 71:		Line 71:
	The actual tile and extra graphics are encoded after the tile cell header.		The actual tile and extra graphics are encoded after the tile cell header.

	For ~~older~~ documentation reference, see [http://xhp.xwis.net/documents/TMP_TS_Format.html TMP documentation].		For old, potentially outdated documentation reference, see [http://xhp.xwis.net/documents/TMP_TS_Format.html TMP documentation].

	==See Also==		==See Also==
Line 78:		Line 78:
	==Footnotes==		==Footnotes==
	{{fn\|1\|Confusingly, these cells sometimes referred to as "tiles". This is especially true in {{td}} and {{ra}}, where a [[TileSets\|tileset]] refers to what [[#tiles\|tile]] does here (a collection of cells).}}		{{fn\|1\|Confusingly, these cells sometimes referred to as "tiles". This is especially true in {{td}} and {{ra}}, where a [[TileSets\|tileset]] refers to what [[#tiles\|tile]] does here (a collection of cells).}}
	{{fn\|1\|Sometimes referred to as terrain type (not to be confused with [[TerrainTypes]])}}		{{fn\|2\|Sometimes referred to as terrain type (not to be confused with [[TerrainTypes]])}}

	[[Category:General_Editing_Information]]		[[Category:General_Editing_Information]]

	[[Category:File Formats]]		[[Category:File Formats]]

en>E1 Elite at 05:54, 5 October 2020

2020-10-05T05:54:00Z

← Older revision		Revision as of 07:54, 5 October 2020
Line 61:		Line 61:
	* '''Z-Data''' contains the information for layering the graphics.		* '''Z-Data''' contains the information for layering the graphics.

	* '''Bitfield''' - The 3 least significant bits out of the 8 bits are used as boolean (0/1) flags for three tile cell attributes: <tt>HasExtraData</tt>, <tt>HasZData</tt>, and <tt>HasDamagedData</tt> respectively. The game checks these bits to process the extra-data or z-data or the damaged logic. If <tt>HasExtraData</tt>/<tt>HasZData</tt> bits are set to 0, the game won't use its respective extra-data or z-data even if present. If the <tt>HasDamagedData</tt> bit is set to 0, the game randomly picks the tile cell from one of the TMP variant files, if present. These variants are identified by a single character suffix (from A to G) at the end of the filename, e.g. clear01.tem, clear01'''a'''.tem, clear01'''b'''.tem etc. <tt>HasDamagedData</tt> bit is set to 1 for bridges, so that the bridge tiles are not randomized. The remaining leading 5 bits out of the 8 bits are not used irrespective of the values present in those. For example, a byte value of 0xCB or 0x03 or 0x83 or 0x4B, all have the same result of binary xxxxx011 which means <tt>HasDamagedData</tt> bit is not set, <tt>HasZData</tt> bit is set and <tt>~~HasDamagedData~~</tt> bit is set.		* '''Bitfield''' - The 3 least significant bits out of the 8 bits are used as boolean (0/1) flags for three tile cell attributes: <tt>HasExtraData</tt> (least significant), <tt>HasZData</tt>, and <tt>HasDamagedData</tt> respectively. The game checks these bits to process the extra-data or z-data or the damaged logic. If <tt>HasExtraData</tt>/<tt>HasZData</tt> bits are set to 0, the game won't use its respective extra-data or z-data even if present. If the <tt>HasDamagedData</tt> bit is set to 0, the game randomly picks the tile cell from one of the TMP variant files, if present. These variants are identified by a single character suffix (from A to G) at the end of the filename, e.g. clear01.tem, clear01'''a'''.tem, clear01'''b'''.tem etc. <tt>HasDamagedData</tt> bit is set to 1 for bridges, so that the bridge tiles are not randomized. The remaining leading 5 bits out of the 8 bits are not used irrespective of the values present in those. For example, a byte value of 0xCB or 0x03 or 0x83 or 0x4B, all have the same result of binary xxxxx011 which means <tt>HasDamagedData</tt> bit is not set, <tt>HasZData</tt> bit is set and <tt>HasExtraData</tt> bit is set.

	* '''[[LandTypes\|LandType]]'''{{fnl\|2}} - Numbering used for land characteristics. 0, 1 or 13 is used for Clear. Ice uses 0 to 4. Tunnel is 5. Railroad is 6. Rock uses 7 or 8 (15 is also used as rock in cliff tiles). Water is 9. Beach is 10. Road uses 11 or 12. Rough is 14. Cliff is 15. Wall, Tiberium and Weeds don't have numbers but are processed based on their overlay placed on the cells.		* '''[[LandTypes\|LandType]]'''{{fnl\|2}} - Numbering used for land characteristics. 0, 1 or 13 is used for Clear. Ice uses 0 to 4. Tunnel is 5. Railroad is 6. Rock uses 7 or 8 (15 is also used as rock in cliff tiles). Water is 9. Beach is 10. Road uses 11 or 12. Rough is 14. Cliff is 15. Wall, Tiberium and Weeds don't have numbers but are processed based on their overlay placed on the cells.

	* '''Radar colors''' - The top-left radar color and bottom-right radar color being different, enhances the demarcation in the minimap where the adjacent tiles/terrain change in the map. These also give a sense of the light source being at top-left in the minimap. Compare to [[LowRadarColor]] and [[HighRadarColor]].		* '''Radar colors''' - The top-left radar color and bottom-right radar color being different, enhances the demarcation in the minimap where the adjacent tiles/terrain change in the map. These also give a sense of the light source being at top-left in the minimap. Compare to the unused [[LowRadarColor]] and [[HighRadarColor]].

	* '''Padding''' bytes are used as fillers, could have any value, typically assigned with 0xCD in original game files.		* '''Padding''' bytes are used as fillers, could have any value, typically assigned with 0xCD in original game files.

en>Crimsonum: Moved TileSet info to its own page, and rewrote some stuff to use common nomenclature across this website.

2020-10-04T19:48:10Z

Moved TileSet info to its own page, and rewrote some stuff to use common nomenclature across this website.

← Older revision		Revision as of 21:48, 4 October 2020
Line 1:		Line 1:
	~~TMP~~ files are terrain files used in {{ts}} through {{yr}}. They constitute the solid, mostly indestructible terrain upon which [[TerrainTypes\|every]] [[OverlayTypes\|other]] [[TechnoTypes\|game object]] is layered. TMPs come in various shapes, each comprised of one or more [[#tiles\|tiles]]<ref>Confusingly, both TMPs and the tiles that make up a TMP file are both referred to as "tiles" in different contexts</ref>. Furthermore, TMPs are divided into [[#TileSets\|tilesets]], which define certain attributes that each TMP in the set should have.		TMPs or template files are terrain files used in {{ts}} through {{yr}}. They constitute the solid, mostly indestructible terrain upon which [[TerrainTypes\|every]] [[OverlayTypes\|other]] [[TechnoTypes\|game object]] is layered.

	TMP files use the same theater-specific file extensions as [[TerrainTypes]]: .tem, .sno, etc.		TMP files use the same theater-specific file extensions as [[TerrainTypes]]: .tem, .sno, etc.

	~~The maximum~~ tile ~~size~~ of ~~a TMP file is 10x10 tiles~~.		==Tiles==
			Each TMP file holds one terrain piece called '''tile'''. Tiles come in various shapes, each comprised of one or more [[cells]]{{fnl\|1}}.

	~~==Tiles==~~		Each tile cell has a normal image that covers the cell shape, plus an optional "extra" image perpendicular to the normal image. This extra image is essential for creating the illusion of a 3D-environment, as it allows for hiding terrain and objects behind it, thus creating a sense of depth, or the filling of space between cells at different height levels.

			In addition to graphics, each tile cell has several parameters encoded that specify characteristics such as [[Height#In_Maps\|height]], [[LandTypes\|land type]] and slope type.

	~~Tiles~~ are ~~the diamond-shaped (within 48x24 pixels for TS and 60x30 pixels for RA2), single-~~[[~~cell~~]] ~~pieces~~ that ~~make up a TMP file. Each~~ tile ~~is composed of a normal image that covers~~ the cell shape, plus an optional "extra" image perpendicular to the normal image. This extra image is essential for creating the illusion of a 3D-environment, as it allows for hiding terrain and objects behind it, thus creating a sense of depth, or the filling of space between tiles at different height levels.		Furthermore, tiles are divided into [[TileSets\|tile sets]], which define certain attributes that each tile in the set should have.

	~~In addition to graphics, each~~ tile ~~has several parameters that specify characteristics such as [[Height#In_Maps\|height]], [[LandTypes\|land type]] and slope type~~.		The maximum tile size is 10x10 cells.

	==File Format==		==File Format==

	A TMP file consists of two header parts, the file header and tile headers.		A TMP file consists of two header parts, the file header and tile cell headers.

	struct FileHeader		struct FileHeader
Line 23:		Line 26:
	};		};

	Following the file header is an index of pointers to each tile header.		Following the file header is an index of pointers to each tile cell header.

	struct ~~TileHeader~~		struct TileCellHeader
	{		{
	signed int ~~TileX~~; // tile offset		signed int X; // tile cell offset
	signed int ~~TileY~~;		signed int Y;
	unsigned int ExtraDataOffset;		unsigned int ExtraDataOffset;
	unsigned int ZDataoffset;		unsigned int ZDataoffset;
Line 39:		Line 42:
	BYTE padding[3];		BYTE padding[3];
	unsigned char Height;		unsigned char Height;
	unsigned char LandType; ~~// see [[LandTypes]]~~		unsigned char LandType;
	unsigned char SlopeType;		unsigned char SlopeType;
	RGB TopLeftRadarColor;		RGB TopLeftRadarColor;
Line 54:		Line 57:
	=== Explanation ===		=== Explanation ===

	'''Block''' is the size of a tile canvas. Its size is in practice fixed in each game: 48x24 pixels for TS and 60x30 pixels for RA2.		* '''Block''' is the size of a tile cell canvas. Its size is in practice fixed in each game: 48x24 pixels for TS and 60x30 pixels for RA2.

	'''Z-Data''' contains the information for layering the graphics.		* '''Z-Data''' contains the information for layering the graphics.

	'''Bitfield''' - The 3 least significant bits out of the 8 bits are used as 0/1 flags for HasExtraData, HasZData and HasDamagedData respectively. ~~Game~~ checks these bits to process the extra-data or z-data or the damaged logic. If HasExtraData/HasZData bits are set to 0, game won't use its respective extra-data or z-data even if present. If the HasDamagedData bit is set to 0, game ~~randomizes~~ the ~~tiles~~ from ~~its variants~~ if present. ~~Variants have filenames like~~ clear01.tem, ~~clear01a~~.tem, ~~... clear01g~~.tem. HasDamagedData bit is set to 1 for bridges, so that ~~its~~ tiles are not randomized. The remaining leading 5 bits out of the 8 bits are not used irrespective of the values present in those. For example, a byte value of 0xCB or 0x03 or 0x83 or 0x4B, all have the same result of binary xxxxx011 which means HasDamagedData bit is not set, HasZData bit is set and ~~HasExtraData~~ bit is set.		* '''Bitfield''' - The 3 least significant bits out of the 8 bits are used as boolean (0/1) flags for three tile cell attributes: <tt>HasExtraData</tt>, <tt>HasZData</tt>, and <tt>HasDamagedData</tt> respectively. The game checks these bits to process the extra-data or z-data or the damaged logic. If <tt>HasExtraData</tt>/<tt>HasZData</tt> bits are set to 0, the game won't use its respective extra-data or z-data even if present. If the <tt>HasDamagedData</tt> bit is set to 0, the game randomly picks the tile cell from one of the TMP variant files, if present. These variants are identified by a single character suffix (from A to G) at the end of the filename, e.g. clear01.tem, clear01'''a'''.tem, clear01'''b'''.tem etc. <tt>HasDamagedData</tt> bit is set to 1 for bridges, so that the bridge tiles are not randomized. The remaining leading 5 bits out of the 8 bits are not used irrespective of the values present in those. For example, a byte value of 0xCB or 0x03 or 0x83 or 0x4B, all have the same result of binary xxxxx011 which means <tt>HasDamagedData</tt> bit is not set, <tt>HasZData</tt> bit is set and <tt>HasDamagedData</tt> bit is set.

	'''LandType'''~~<ref>Sometimes referred to as terrain type (not to be confused with [[TerrainTypes]])</ref>~~ - Numbering used for land characteristics. 0, 1 or 13 is used for Clear. Ice uses 0 to 4. Tunnel is 5. Railroad is 6. Rock uses 7 or 8 (15 is also used as rock in cliff tiles). Water is 9. Beach is 10. Road uses 11 or 12. Rough is 14. Cliff is 15. Wall, Tiberium and Weeds don't have numbers but are processed based on ~~its~~ overlay placed on the cells.		* '''[[LandTypes\|LandType]]'''{{fnl\|2}} - Numbering used for land characteristics. 0, 1 or 13 is used for Clear. Ice uses 0 to 4. Tunnel is 5. Railroad is 6. Rock uses 7 or 8 (15 is also used as rock in cliff tiles). Water is 9. Beach is 10. Road uses 11 or 12. Rough is 14. Cliff is 15. Wall, Tiberium and Weeds don't have numbers but are processed based on their overlay placed on the cells.

	'''Radar colors''' - The top-left radar color and bottom-right radar color being different, enhances the demarcation in the minimap where the adjacent tiles/terrain change in the map. These also give a sense of the light source being at top-left in the minimap.		* '''Radar colors''' - The top-left radar color and bottom-right radar color being different, enhances the demarcation in the minimap where the adjacent tiles/terrain change in the map. These also give a sense of the light source being at top-left in the minimap. Compare to [[LowRadarColor]] and [[HighRadarColor]].

	'''Padding''' bytes are used as fillers, could have any value, typically assigned with 0xCD in original game ~~tiles~~.		* '''Padding''' bytes are used as fillers, could have any value, typically assigned with 0xCD in original game files.

	The actual tile and extra graphics are encoded after the tile header.		The actual tile and extra graphics are encoded after the tile cell header.

	For older documentation reference, see [http://xhp.xwis.net/documents/TMP_TS_Format.html TMP documentation].		For older documentation reference, see [http://xhp.xwis.net/documents/TMP_TS_Format.html TMP documentation].

	==~~TileSets~~==		==See Also==
			* [[IsoMapPack5]] – how tiles are stored in maps.
	TileSets define certain characteristics to a group of TMP files, such as [[AllowTiberium\|whether Tiberium/ore can grow on the tiles]], or whether they can be [[Morphable\|deformed]] or [[AllowBurrowing\|burrowed through]]. Each TileSet has its own section in the [[Terrain_Control_INI_files\|theater control file]].

	~~A TileSet has a practical limit of 99 TMPs.~~

	~~Check~~ [[IsoMapPack5]] ~~to know~~ how ~~the~~ tiles are stored in ~~TS/RA2~~ maps.

	==Footnotes==		==Footnotes==
	~~<references/>~~		{{fn\|1\|Confusingly, these cells sometimes referred to as "tiles". This is especially true in {{td}} and {{ra}}, where a [[TileSets\|tileset]] refers to what [[#tiles\|tile]] does here (a collection of cells).}}
			{{fn\|1\|Sometimes referred to as terrain type (not to be confused with [[TerrainTypes]])}}

	[[Category:General_Editing_Information~~]] [[Category:Map_Information~~]]		[[Category:General_Editing_Information]]

	[[Category:File Formats]]		[[Category:File Formats]]

en>E1 Elite at 04:49, 4 September 2019

2019-09-04T04:49:09Z

← Older revision		Revision as of 06:49, 4 September 2019
Line 45:		Line 45:
	BYTE padding2[3];		BYTE padding2[3];
	};		};
	RGB		struct RGB
	{		{
	unsigned char Red;		unsigned char Red;

en>Crimsonum: Slight reordering.

2019-08-16T20:15:51Z

Slight reordering.

← Older revision		Revision as of 22:15, 16 August 2019
Line 7:		Line 7:
	==Tiles==		==Tiles==

	Tiles are the diamond-shaped (within 48x24 pixels for TS and 60x30 pixels for RA2), single-[[cell]] pieces that make up a TMP file. Each tile is composed of a normal image that covers the cell shape, plus an optional "extra" image perpendicular to the normal image. This extra image is essential for creating the illusion of a 3D-environment, as it allows for hiding terrain and objects behind it, thus creating a sense of depth, or the filling of space between tiles at different height levels~~. Z-Data contain the information for layering the graphics~~.		Tiles are the diamond-shaped (within 48x24 pixels for TS and 60x30 pixels for RA2), single-[[cell]] pieces that make up a TMP file. Each tile is composed of a normal image that covers the cell shape, plus an optional "extra" image perpendicular to the normal image. This extra image is essential for creating the illusion of a 3D-environment, as it allows for hiding terrain and objects behind it, thus creating a sense of depth, or the filling of space between tiles at different height levels.

	In addition to graphics, each tile has several parameters that specify characteristics such as [[Height#In_Maps\|height]], [[LandTypes\|land type]] and slope type.		In addition to graphics, each tile has several parameters that specify characteristics such as [[Height#In_Maps\|height]], [[LandTypes\|land type]] and slope type.
Line 55:		Line 55:

	'''Block''' is the size of a tile canvas. Its size is in practice fixed in each game: 48x24 pixels for TS and 60x30 pixels for RA2.		'''Block''' is the size of a tile canvas. Its size is in practice fixed in each game: 48x24 pixels for TS and 60x30 pixels for RA2.

			'''Z-Data''' contains the information for layering the graphics.

	'''Bitfield''' - The 3 least significant bits out of the 8 bits are used as 0/1 flags for HasExtraData, HasZData and HasDamagedData respectively. Game checks these bits to process the extra-data or z-data or the damaged logic. If HasExtraData/HasZData bits are set to 0, game won't use its respective extra-data or z-data even if present. If the HasDamagedData bit is set to 0, game randomizes the tiles from its variants if present. Variants have filenames like clear01.tem, clear01a.tem, ... clear01g.tem. HasDamagedData bit is set to 1 for bridges, so that its tiles are not randomized. The remaining leading 5 bits out of the 8 bits are not used irrespective of the values present in those. For example, a byte value of 0xCB or 0x03 or 0x83 or 0x4B, all have the same result of binary xxxxx011 which means HasDamagedData bit is not set, HasZData bit is set and HasExtraData bit is set.		'''Bitfield''' - The 3 least significant bits out of the 8 bits are used as 0/1 flags for HasExtraData, HasZData and HasDamagedData respectively. Game checks these bits to process the extra-data or z-data or the damaged logic. If HasExtraData/HasZData bits are set to 0, game won't use its respective extra-data or z-data even if present. If the HasDamagedData bit is set to 0, game randomizes the tiles from its variants if present. Variants have filenames like clear01.tem, clear01a.tem, ... clear01g.tem. HasDamagedData bit is set to 1 for bridges, so that its tiles are not randomized. The remaining leading 5 bits out of the 8 bits are not used irrespective of the values present in those. For example, a byte value of 0xCB or 0x03 or 0x83 or 0x4B, all have the same result of binary xxxxx011 which means HasDamagedData bit is not set, HasZData bit is set and HasExtraData bit is set.

en>Crimsonum: Cleaned up formatting.

2019-08-16T11:20:04Z

Cleaned up formatting.

← Older revision		Revision as of 13:20, 16 August 2019
Line 1:		Line 1:
	TMP files are terrain files used in {{ts}} through {{yr}}. They constitute the solid, mostly indestructible terrain upon which [[TerrainTypes\|every]] [[OverlayTypes\|other]] [[TechnoTypes\|game object]] is layered. TMPs come in various shapes, each comprised of one or more [[#tiles\|tiles]]~~{{fnl\|1}}~~. Furthermore, TMPs are divided into [[#TileSets\|tilesets]], which define certain attributes that each TMP in the set should have.		TMP files are terrain files used in {{ts}} through {{yr}}. They constitute the solid, mostly indestructible terrain upon which [[TerrainTypes\|every]] [[OverlayTypes\|other]] [[TechnoTypes\|game object]] is layered. TMPs come in various shapes, each comprised of one or more [[#tiles\|tiles]]<ref>Confusingly, both TMPs and the tiles that make up a TMP file are both referred to as "tiles" in different contexts</ref>. Furthermore, TMPs are divided into [[#TileSets\|tilesets]], which define certain attributes that each TMP in the set should have.

	TMP files use the same theater-specific file extensions as [[TerrainTypes]]: .tem, .sno, etc.		TMP files use the same theater-specific file extensions as [[TerrainTypes]]: .tem, .sno, etc.
Line 52:		Line 52:
	};		};

	Bitfield - The 3 least significant bits out of the 8 bits are used as 0/1 flags for HasExtraData, HasZData and HasDamagedData respectively. Game checks these bits to process the extra-data or z-data or the damaged logic. If HasExtraData/HasZData bits are set to 0, game won't use its respective extra-data or z-data even if present. If the HasDamagedData bit is set to 0, game randomizes the tiles from its variants if present. Variants have filenames like clear01.tem, clear01a.tem, ... clear01g.tem. HasDamagedData bit is set to 1 for bridges, so that its tiles are not randomized. The remaining leading 5 bits out of the 8 bits are not used irrespective of the values present in those. For example, a byte value of 0xCB or 0x03 or 0x83 or 0x4B, all have the same result of binary xxxxx011 which means HasDamagedData bit is not set, HasZData bit is set and HasExtraData bit is set.		=== Explanation ===

	~~LandType/TerrainType{{fnl\|2}} - Numbering used for land characteristics. 0, 1 or 13~~ is ~~used for Clear. Ice uses 0 to 4~~. ~~Tunnel~~ is ~~5. Railroad is 6. Rock uses 7 or 8 (15 is also used as rock~~ in ~~cliff tiles). Water is 9. Beach is 10. Road uses 11 or 12. Rough is 14. Cliff is 15. Wall, Tiberium~~ and ~~Weeds don't have numbers but are processed based on its overlay placed on the cells~~.		'''Block''' is the size of a tile canvas. Its size is in practice fixed in each game: 48x24 pixels for TS and 60x30 pixels for RA2.

	~~Radar colors~~ - The ~~top~~-~~left radar color and bottom~~-~~right radar color being different~~, ~~enhances~~ the ~~demarcation in~~ the ~~minimap where~~ the ~~adjacent tiles/terrain change~~ in ~~the map~~. ~~These also give~~ a ~~sense~~ of the ~~light source being at top-left in the minimap~~.		'''Bitfield''' - The 3 least significant bits out of the 8 bits are used as 0/1 flags for HasExtraData, HasZData and HasDamagedData respectively. Game checks these bits to process the extra-data or z-data or the damaged logic. If HasExtraData/HasZData bits are set to 0, game won't use its respective extra-data or z-data even if present. If the HasDamagedData bit is set to 0, game randomizes the tiles from its variants if present. Variants have filenames like clear01.tem, clear01a.tem, ... clear01g.tem. HasDamagedData bit is set to 1 for bridges, so that its tiles are not randomized. The remaining leading 5 bits out of the 8 bits are not used irrespective of the values present in those. For example, a byte value of 0xCB or 0x03 or 0x83 or 0x4B, all have the same result of binary xxxxx011 which means HasDamagedData bit is not set, HasZData bit is set and HasExtraData bit is set.

	~~Padding bytes are~~ used as ~~fillers~~, ~~could~~ have ~~any value, typically assigned with 0xCD in original game tiles~~.		'''LandType'''<ref>Sometimes referred to as terrain type (not to be confused with [[TerrainTypes]])</ref> - Numbering used for land characteristics. 0, 1 or 13 is used for Clear. Ice uses 0 to 4. Tunnel is 5. Railroad is 6. Rock uses 7 or 8 (15 is also used as rock in cliff tiles). Water is 9. Beach is 10. Road uses 11 or 12. Rough is 14. Cliff is 15. Wall, Tiberium and Weeds don't have numbers but are processed based on its overlay placed on the cells.

	The ~~graphics are encoded after~~ the ~~tile header~~.		'''Radar colors''' - The top-left radar color and bottom-right radar color being different, enhances the demarcation in the minimap where the adjacent tiles/terrain change in the map. These also give a sense of the light source being at top-left in the minimap.

	~~Older~~ documentation reference, see [http://xhp.xwis.net/documents/TMP_TS_Format.html TMP documentation].		'''Padding''' bytes are used as fillers, could have any value, typically assigned with 0xCD in original game tiles.

			The actual tile and extra graphics are encoded after the tile header.

			For older documentation reference, see [http://xhp.xwis.net/documents/TMP_TS_Format.html TMP documentation].

	==TileSets==		==TileSets==
Line 73:		Line 77:

	==Footnotes==		==Footnotes==
	~~{{fn\|1\|Confusingly, both TMPs and the tiles that make up a TMP file are both referred to as "tiles" in different contexts.}}~~		<references/>
	~~{{fn\|2\|Sometimes referred to as terrain type (not to be confused with [[TerrainTypes]])}}~~

	[[Category:General_Editing_Information]] [[Category:Map_Information]]		[[Category:General_Editing_Information]] [[Category:Map_Information]]

	[[Category:File Formats]]		[[Category:File Formats]]

en>E1 Elite: Updates

2019-08-16T09:28:06Z

Updates

← Older revision		Revision as of 11:28, 16 August 2019
Line 7:		Line 7:
	==Tiles==		==Tiles==

	Tiles are the diamond-shaped, single-[[cell]] pieces that make up a TMP file. Each tile is composed of ~~two images:~~ a normal image that covers the cell shape, plus an optional "extra" image perpendicular to the normal image. This extra image is essential for creating the illusion of a 3D-environment, as it allows for hiding terrain and objects behind it, thus creating a sense of depth, or the filling of space between tiles at different height levels.		Tiles are the diamond-shaped (within 48x24 pixels for TS and 60x30 pixels for RA2), single-[[cell]] pieces that make up a TMP file. Each tile is composed of a normal image that covers the cell shape, plus an optional "extra" image perpendicular to the normal image. This extra image is essential for creating the illusion of a 3D-environment, as it allows for hiding terrain and objects behind it, thus creating a sense of depth, or the filling of space between tiles at different height levels. Z-Data contain the information for layering the graphics.

	In addition to graphics, each tile has several parameters that specify characteristics such as [[Height#In_Maps\|height]], [[LandTypes\|land type]] and slope type.		In addition to graphics, each tile has several parameters that specify characteristics such as [[Height#In_Maps\|height]], [[LandTypes\|land type]] and slope type.
Line 13:		Line 13:
	==File Format==		==File Format==

	A TMP file consists of two parts, the file header and tile headers.		A TMP file consists of two header parts, the file header and tile headers.

	struct FileHeader		struct FileHeader
Line 36:		Line 36:
	unsigned int ExtraWidth;		unsigned int ExtraWidth;
	unsigned int ExtraHeight;		unsigned int ExtraHeight;
	unsigned char Bitfield; ~~// three of the bits specify whether the tile has an extra image, Z data, and damaged art (applies only to bridges), respectively.~~		unsigned char Bitfield;
	BYTE padding[3];		BYTE padding[3];
	unsigned char Height;		unsigned char Height;
	unsigned char LandType; // see [[LandTypes]]		unsigned char LandType; // see [[LandTypes]]
	unsigned char SlopeType;		unsigned char SlopeType;
	RGB ~~LowRadarColor~~; // ~~color~~ to ~~show on~~ the ~~radar~~ for ~~this tile at~~ the ~~lowest map [[Height#In_Maps\|height]]~~		RGB TopLeftRadarColor;
	~~RGB HighRadarColor;~~ /~~/ color~~ to ~~show~~ on the radar ~~for this tile~~ at the ~~highest map [[Height#In_Maps\|height]]~~		RGB BottomRightRadarColor;
	~~BYTE padding[3];~~		BYTE padding2[3];
	}		};
			RGB
			{
			unsigned char Red;
			unsigned char Green;
			unsigned char Blue;
			};

			Bitfield - The 3 least significant bits out of the 8 bits are used as 0/1 flags for HasExtraData, HasZData and HasDamagedData respectively. Game checks these bits to process the extra-data or z-data or the damaged logic. If HasExtraData/HasZData bits are set to 0, game won't use its respective extra-data or z-data even if present. If the HasDamagedData bit is set to 0, game randomizes the tiles from its variants if present. Variants have filenames like clear01.tem, clear01a.tem, ... clear01g.tem. HasDamagedData bit is set to 1 for bridges, so that its tiles are not randomized. The remaining leading 5 bits out of the 8 bits are not used irrespective of the values present in those. For example, a byte value of 0xCB or 0x03 or 0x83 or 0x4B, all have the same result of binary xxxxx011 which means HasDamagedData bit is not set, HasZData bit is set and HasExtraData bit is set.

			LandType/TerrainType{{fnl\|2}} - Numbering used for land characteristics. 0, 1 or 13 is used for Clear. Ice uses 0 to 4. Tunnel is 5. Railroad is 6. Rock uses 7 or 8 (15 is also used as rock in cliff tiles). Water is 9. Beach is 10. Road uses 11 or 12. Rough is 14. Cliff is 15. Wall, Tiberium and Weeds don't have numbers but are processed based on its overlay placed on the cells.

			Radar colors - The top-left radar color and bottom-right radar color being different, enhances the demarcation in the minimap where the adjacent tiles/terrain change in the map. These also give a sense of the light source being at top-left in the minimap.

			Padding bytes are used as fillers, could have any value, typically assigned with 0xCD in original game tiles.

	The graphics are encoded after the tile header.		The graphics are encoded after the tile header.

	~~For more information on the file format~~, see [http://xhp.xwis.net/documents/TMP_TS_Format.html TMP documentation].		Older documentation reference, see [http://xhp.xwis.net/documents/TMP_TS_Format.html TMP documentation].

	==TileSets==		==TileSets==
Line 55:		Line 69:

	A TileSet has a practical limit of 99 TMPs.		A TileSet has a practical limit of 99 TMPs.

			Check [[IsoMapPack5]] to know how the tiles are stored in TS/RA2 maps.

	==Footnotes==		==Footnotes==

en>Crimsonum: Expanded the article with known information.

2019-08-15T15:58:31Z

Expanded the article with known information.

← Older revision		Revision as of 17:58, 15 August 2019
Line 1:		Line 1:
	TMP files are the terrain ~~files for C&C~~ [[~~Tiberian Sun~~]] ~~and C&C~~ [[~~Red Alert 2~~]], in ~~addition to their expansion packs~~, ~~Firestorm and Yuri's Revenge~~, ~~respectively~~. The TMP ~~files used for TS and RA2~~ are diamond-shaped, ~~and are designed to simulate~~ a ~~dimetric camera~~. It is a ~~common misconception~~ that the ~~camera used in TS and RA2~~ is ~~isometric~~, ~~when~~ it is in ~~fact~~ a ~~dimetric camera~~.		TMP files are terrain files used in {{ts}} through {{yr}}. They constitute the solid, mostly indestructible terrain upon which [[TerrainTypes\|every]] [[OverlayTypes\|other]] [[TechnoTypes\|game object]] is layered. TMPs come in various shapes, each comprised of one or more [[#tiles\|tiles]]{{fnl\|1}}. Furthermore, TMPs are divided into [[#TileSets\|tilesets]], which define certain attributes that each TMP in the set should have.

			TMP files use the same theater-specific file extensions as [[TerrainTypes]]: .tem, .sno, etc.

			The maximum tile size of a TMP file is 10x10 tiles.

			==Tiles==

			Tiles are the diamond-shaped, single-[[cell]] pieces that make up a TMP file. Each tile is composed of two images: a normal image that covers the cell shape, plus an optional "extra" image perpendicular to the normal image. This extra image is essential for creating the illusion of a 3D-environment, as it allows for hiding terrain and objects behind it, thus creating a sense of depth, or the filling of space between tiles at different height levels.

			In addition to graphics, each tile has several parameters that specify characteristics such as [[Height#In_Maps\|height]], [[LandTypes\|land type]] and slope type.

			==File Format==

			A TMP file consists of two parts, the file header and tile headers.

			struct FileHeader
			{
			unsigned int BlockWidth; // size in blocks
			unsigned int BlockHeight;
			unsigned int BlockImageWidth; // size of each block
			unsigned int BlockImageHeight;
			};

			Following the file header is an index of pointers to each tile header.

			struct TileHeader
			{
			signed int TileX; // tile offset
			signed int TileY;
			unsigned int ExtraDataOffset;
			unsigned int ZDataoffset;
			unsigned int ExtraZDataoffset;
			signed int ExtraX; // extra image offset
			signed int ExtraY;
			unsigned int ExtraWidth;
			unsigned int ExtraHeight;
			unsigned char Bitfield; // three of the bits specify whether the tile has an extra image, Z data, and damaged art (applies only to bridges), respectively.
			BYTE padding[3];
			unsigned char Height;
			unsigned char LandType; // see [[LandTypes]]
			unsigned char SlopeType;
			RGB LowRadarColor; // color to show on the radar for this tile at the lowest map [[Height#In_Maps\|height]]
			RGB HighRadarColor; // color to show on the radar for this tile at the highest map [[Height#In_Maps\|height]]
			BYTE padding[3];
			}

			The graphics are encoded after the tile header.

			For more information on the file format, see [http://xhp.xwis.net/documents/TMP_TS_Format.html TMP documentation].

			==TileSets==

			TileSets define certain characteristics to a group of TMP files, such as [[AllowTiberium\|whether Tiberium/ore can grow on the tiles]], or whether they can be [[Morphable\|deformed]] or [[AllowBurrowing\|burrowed through]]. Each TileSet has its own section in the [[Terrain_Control_INI_files\|theater control file]].

			A TileSet has a practical limit of 99 TMPs.

			==Footnotes==
			{{fn\|1\|Confusingly, both TMPs and the tiles that make up a TMP file are both referred to as "tiles" in different contexts.}}
			{{fn\|2\|Sometimes referred to as terrain type (not to be confused with [[TerrainTypes]])}}

			[[Category:General_Editing_Information]] [[Category:Map_Information]]

	[[Category:File Formats]]		[[Category:File Formats]]

en>Nighthawk200: Categorising.

2010-04-18T14:42:56Z

Categorising.

← Older revision		Revision as of 16:42, 18 April 2010
Line 1:		Line 1:
	TMP files are the terrain files for C&C [[Tiberian Sun]] and C&C [[Red Alert 2]], in addition to their expansion packs, Firestorm and Yuri's Revenge, respectively. The TMP files used for TS and RA2 are diamond-shaped, and are designed to simulate a dimetric camera. It is a common misconception that the camera used in TS and RA2 is isometric, when it is in fact a dimetric camera.		TMP files are the terrain files for C&C [[Tiberian Sun]] and C&C [[Red Alert 2]], in addition to their expansion packs, Firestorm and Yuri's Revenge, respectively. The TMP files used for TS and RA2 are diamond-shaped, and are designed to simulate a dimetric camera. It is a common misconception that the camera used in TS and RA2 is isometric, when it is in fact a dimetric camera.
			[[Category:File Formats]]