MIX - Revision history

Mah boi: Add link to the windows build of ccmix

2025-04-22T07:19:38Z

Add link to the windows build of ccmix

← Older revision		Revision as of 09:19, 22 April 2025
Line 4:		Line 4:
	Mix files can be read, edited and created using the [[XCC Mixer]] and the [[XCC MIX Editor]], both created by [[Olaf van der Spek]]. They can be downloaded at [http://xhp.xwis.net/ xhp.xwis.net].		Mix files can be read, edited and created using the [[XCC Mixer]] and the [[XCC MIX Editor]], both created by [[Olaf van der Spek]]. They can be downloaded at [http://xhp.xwis.net/ xhp.xwis.net].

	Alternatively, there's a command line tool called [https://github.com/OmniBlade/ccmix ccmix] by [[OmniBlade]] which can generate and extract from mix files.		Alternatively, there's a command line tool called [https://github.com/OmniBlade/ccmix ccmix] by [[OmniBlade]] which can generate and extract from mix files. You can download it [https://github.com/OmniBlade/ccmix/issues/8 here]

	==Mix Types==		==Mix Types==

MarkJFox: 26 revisions imported

2025-03-31T19:23:31Z

26 revisions imported

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

en>DeathFish at 22:03, 3 February 2025

2025-02-03T22:03:57Z

← Older revision		Revision as of 00:03, 4 February 2025
Line 398:		Line 398:

	===RA2/YR===		===RA2/YR===
	*The [[INIs\|INI files]] are in {{Tt\|RA2.mix}} {{arr\|r}} {{Tt\|local.mix}} and {{Tt\|RA2md.mix}} {{arr\|r}} {{Tt\|localmd.mix}}. {{Tt\|rulesmd.ini}} and {{Tt\|soundmd.ini}} for YR 1.001 are in ~~{{Tt~~\|expandmd01.mix}}.		*The [[INIs\|INI files]] are in {{Tt\|RA2.mix}} {{arr\|r}} {{Tt\|local.mix}} and {{Tt\|RA2md.mix}} {{arr\|r}} {{Tt\|localmd.mix}}. {{Tt\|rulesmd.ini}} and {{Tt\|soundmd.ini}} for YR 1.001 are in <tt>[[Reserved_Mix_Files#expandmd01.mix\|expandmd01.mix]]</tt>.
	*[[Cameo]]s (build icons), which are single frame [[SHP]]s, can found in {{Tt\|language.mix}} {{arr\|r}} {{Tt\|cameo.mix}} and in {{Tt\|langmd.mix}} {{arr\|r}} {{Tt\|cameomd.mix}}.		*[[Cameo]]s (build icons), which are single frame [[SHP]]s, can found in {{Tt\|language.mix}} {{arr\|r}} {{Tt\|cameo.mix}} and in {{Tt\|langmd.mix}} {{arr\|r}} {{Tt\|cameomd.mix}}.
	*Infantry, which are multi frame [[SHP]]s, can be found in {{Tt\|RA2.mix}} {{arr\|r}} {{Tt\|conquer.mix}} and {{Tt\|ra2md.mix}} {{arr\|r}} {{Tt\|conqmd.mix}}.		*Infantry, which are multi frame [[SHP]]s, can be found in {{Tt\|RA2.mix}} {{arr\|r}} {{Tt\|conquer.mix}} and {{Tt\|ra2md.mix}} {{arr\|r}} {{Tt\|conqmd.mix}}.

en>Crimsonum: Updated list.

2023-10-26T07:42:19Z

Updated list.

Show changes

en>Crimsonum: Restructured and updated.

2022-07-13T20:52:05Z

Restructured and updated.

Show changes

en>Crimsonum at 09:27, 13 July 2022

2022-07-13T09:27:19Z

← Older revision		Revision as of 11:27, 13 July 2022
Line 1:		Line 1:
	.mix ~~is the extension for the~~ files used by [[Westwood]] to store most game files ~~up until~~ [[~~YR\|Yuri's Revenge~~]]. For [[Generals]] and following, [[~~big-~~files]] took this part.		Mix files (file extension .mix) are archive files used by [[Westwood]] to store most game files from {{td}} to [[Renegade]]. For [[Generals]] and following, [[BIG\|BIG files]] took this part.

	==Editing Mix~~-files~~==		==Editing Mix Files==
	Mix-files ~~are~~ read, edited and created using the [[XCC Mixer]] and the [[XCC ~~Mix~~ Editor]], both created by [[Olaf van der Spek]]. They can be downloaded at [http://~~xccu~~.~~sourceforge~~.net ~~http~~://~~xccu~~.~~sourceforge.net~~].		Mix files can be read, edited and created using the [[XCC Mixer]] and the [[XCC MIX Editor]], both created by [[Olaf van der Spek]]. They can be downloaded at [http://xhp.xwis.net/ xhp.xwis.net].

			Alternatively, there's a command line tool called [https://github.com/OmniBlade/ccmix ccmix] by [[OmniBlade]] which can generate and extract from mix files.

	==File Names and Loading Hierarchy==		==File Names and Loading Hierarchy==
	~~Naming your MIX~~ correctly is important for the correct execution of your mod.~~<br>~~		There are several types of mix files, each for a specific purpose. This article will cover the mix types available in {{ts}} to {{yr}}.
	There are three ~~names/~~naming ~~systems~~
			Using mix files correctly is important for the correct execution of your mod.

			A common approach is to include mod assets in '''expansion mix files'''. There are three different expansion mix types, each with a different naming system:
	;{{tt\|expand{{co\|md\|#D2691E}}##.mix}}		;{{tt\|expand{{co\|md\|#D2691E}}##.mix}}
	:Where ## is a number between 01 and 99, and {{tt\|{{co\|md\|#D2691E}}}} is added if the the file is for {{yr}}.		:Where ## is a number between 01 and 99, and {{tt\|{{co\|md\|#D2691E}}}} is added if the the file is for {{yr}}.
Line 12:		Line 17:
	:Where * can be any string for both {{ra2}} and {{yr}}. {{ts}} uses {{tt\|ecache##.mix}} where ## is 2-digit number.		:Where * can be any string for both {{ra2}} and {{yr}}. {{ts}} uses {{tt\|ecache##.mix}} where ## is 2-digit number.
	;{{tt\|elocal*.mix}}		;{{tt\|elocal*.mix}}
	:~~Where~~ * can be any string.		:RA2/YR only. * can be any string.

	===Loading Hierarchy===		===Loading Hierarchy===
	The game searches the ~~MIX~~ files for contents in this order. Once a file is found in a mix, the next ~~MIXes~~ don't even get checked for its presence.		The game searches the mix files for contents in this order. Once a file is found in a mix, the next mixes don't even get checked for its presence.
	* A higher-numbered {{tt\|expand{{co\|md\|#D2691E}}##.mix}} has a higher level than a lower numbered one.		* A higher-numbered {{tt\|expand{{co\|md\|#D2691E}}##.mix}} has a higher level than a lower numbered one.
	* For {{tt\|ecache}} and {{tt\|elocal}} files, order is not guaranteed - standard WinAPI functionality is used to locate them, and no sorting is done.		* For {{tt\|ecache}} and {{tt\|elocal}} files, order is not guaranteed - standard WinAPI functionality is used to locate them, and no sorting is done.
Line 22:		Line 27:
	:: Additionally, files that have any of the "Hidden", "System" or "Temporary" attributes set are not loaded.		:: Additionally, files that have any of the "Hidden", "System" or "Temporary" attributes set are not loaded.

	{{HorizontalBar\|This list was generated for Yuri's Revenge 1.001 . Red Alert 2 ignores the {{co\|md\|#D2691E}} ~~MIXes~~, and other games might use a different order, to be documented later.}}		{{HorizontalBar\|This list was generated for Yuri's Revenge 1.001 . Red Alert 2 ignores the {{co\|md\|#D2691E}} mixes, and other games might use a different order, to be documented later.}}

	# LANGMD.MIX		# LANGMD.MIX
Line 48:		Line 53:
	# THEMEMD.MIX		# THEMEMD.MIX
	# MOVMD03.MIX		# MOVMD03.MIX
	# theater-specific ~~MIXes~~ - see [[Theatres]] for a list		# theater-specific mixes - see [[Theatres]] for a list
	# SIDEC##.MIX '';the {{tt\|##}} stands for side you're playing as - 1 for Allied''		# SIDEC##.MIX '';the {{tt\|##}} stands for side you're playing as - 1 for Allied''
	# SIDENC##.MIX		# SIDENC##.MIX
Line 83:		Line 88:
	Note that, despite this common distribution of files, many files (especially graphics) work in an expand{{co\|md\|#D2691E}}##.mix as well.		Note that, despite this common distribution of files, many files (especially graphics) work in an expand{{co\|md\|#D2691E}}##.mix as well.

	==How to make a new ~~MIX~~ file ==		==How to make a new mix file ==
	'''Important:''' In order to be read by the game, your new mix has to reside in the game's folder, and has to be [[#File Names and Loading Hierarchy\|named correctly]].		'''Important:''' In order to be read by the game, your new mix has to reside in the game's folder, and has to be [[#File Names and Loading Hierarchy\|named correctly]].

	===Using [[XCC ~~Mix~~ Editor]]===		===Using [[XCC MIX Editor]]===
	Click {{Tt\|New}} and choose where to save it. To add files to a mix file you can go to import or you can use the faster method of "drag 'n drop" you can select files from explorer and drag them into the XCC ~~Mix~~ Editor window. Next press the "Compact" button, this saves and compresses the file.		Click {{Tt\|New}} and choose where to save it. To add files to a mix file you can go to import or you can use the faster method of "drag 'n drop" you can select files from explorer and drag them into the XCC mix Editor window. Next press the "Compact" button, this saves and compresses the file.

			'''Note:''' XCC MIX Editor is known to sometimes corrupt mix files. It is therefore recommended to use XCC Mixer instead, as it can perform all the same functions and more.

	===Using [[XCC Mixer]]===		===Using [[XCC Mixer]]===
	Click {{Tt\|File - New}} and select where to save it. Then, navigate there and open that file in the ~~Mixer~~. Now you can actually drag and drop files to the ~~Mixer~~ as well to add them, there is an option to compact in the context menu that appears when you right click on a file in that mix.		Click {{Tt\|File - New}} and select where to save it. Then, navigate there and open that file in the mixer. Now you can actually drag and drop files to the mixer as well to add them, there is an option to compact in the context menu that appears when you right click on a file in that mix.


Line 102:		Line 109:

	==See also==		==See also==
	*[[File Types#.~~MIX~~\|.mix on the File Types Page]]		*[[File Types#.mix\|.mix on the File Types Page]]
	*[http://xccu.sourceforge.net/documents/~~MIX_Format~~.html Explanation of the ~~MIX~~ format by Olaf van der Spek]		*[http://xccu.sourceforge.net/documents/mix_Format.html Explanation of the mix format by Olaf van der Spek]
	*[[Reserved ~~Mix~~ Files]]		*[[Reserved mix Files]]
	*[[~~MIX~~ protectors]]		*[[mix protectors]]

	[[Category:General Editing Information]]		[[Category:General Editing Information]]
	[[Category:XCC Tutorials]]		[[Category:XCC Tutorials]]
	[[Category:XCC ~~Mix~~ Editor Tutorials]]		[[Category:XCC mix Editor Tutorials]]
	[[Category:File Formats]]		[[Category:File Formats]]

en>E1 Elite: ECache mix naming.

2021-12-27T15:24:16Z

ECache mix naming.

← Older revision		Revision as of 17:24, 27 December 2021
Line 10:		Line 10:
	:Where ## is a number between 01 and 99, and {{tt\|{{co\|md\|#D2691E}}}} is added if the the file is for {{yr}}.		:Where ## is a number between 01 and 99, and {{tt\|{{co\|md\|#D2691E}}}} is added if the the file is for {{yr}}.
	;{{tt\|ecache*.mix}}		;{{tt\|ecache*.mix}}
	:Where * can be any string.		:Where * can be any string for both {{ra2}} and {{yr}}. {{ts}} uses {{tt\|ecache##.mix}} where ## is 2-digit number.
	;{{tt\|elocal*.mix}}		;{{tt\|elocal*.mix}}
	:Where * can be any string.		:Where * can be any string.

en>E1 Elite: Reverted edits by Fallendow (talk) to last revision by E1 Elite

2021-12-27T15:12:58Z

Reverted edits by Fallendow (talk) to last revision by E1 Elite

← Older revision		Revision as of 17:12, 27 December 2021
Line 9:		Line 9:
	;{{tt\|expand{{co\|md\|#D2691E}}##.mix}}		;{{tt\|expand{{co\|md\|#D2691E}}##.mix}}
	:Where ## is a number between 01 and 99, and {{tt\|{{co\|md\|#D2691E}}}} is added if the the file is for {{yr}}.		:Where ## is a number between 01 and 99, and {{tt\|{{co\|md\|#D2691E}}}} is added if the the file is for {{yr}}.
	;{{tt\|ecache~~{{co\|md\|#D2691E}}~~*.mix}}		;{{tt\|ecache*.mix}}
	:Where * can be any string~~, and {{tt\|{{co\|md\|#D2691E}}}} is added if the the file is for {{yr}}~~.		:Where * can be any string.
	;{{tt\|elocal*.mix}}		;{{tt\|elocal*.mix}}
	:Where * can be any string.		:Where * can be any string.
Line 17:		Line 17:
	The game searches the MIX files for contents in this order. Once a file is found in a mix, the next MIXes don't even get checked for its presence.		The game searches the MIX files for contents in this order. Once a file is found in a mix, the next MIXes don't even get checked for its presence.
	* A higher-numbered {{tt\|expand{{co\|md\|#D2691E}}##.mix}} has a higher level than a lower numbered one.		* A higher-numbered {{tt\|expand{{co\|md\|#D2691E}}##.mix}} has a higher level than a lower numbered one.
	* For {{tt\|ecache~~{{co\|md\|#D2691E}}~~}} and {{tt\|elocal}} files, order is not guaranteed - standard WinAPI functionality is used to locate them, and no sorting is done.		* For {{tt\|ecache}} and {{tt\|elocal}} files, order is not guaranteed - standard WinAPI functionality is used to locate them, and no sorting is done.
	:: Quoting [http://msdn.microsoft.com/en-us/library/aa364428(VS.85).aspx MSDN - FindNextFile]:		:: Quoting [http://msdn.microsoft.com/en-us/library/aa364428(VS.85).aspx MSDN - FindNextFile]:
	:::: ''The order in which this function returns the file names is dependent on the file system type. With the NTFS file system and CDFS file systems, the names are usually returned in alphabetical order. With FAT file systems, the names are usually returned in the order the files were written to the disk, which may or may not be in alphabetical order. However, as stated previously, these behaviours are not guaranteed.''		:::: ''The order in which this function returns the file names is dependent on the file system type. With the NTFS file system and CDFS file systems, the names are usually returned in alphabetical order. With FAT file systems, the names are usually returned in the order the files were written to the disk, which may or may not be in alphabetical order. However, as stated previously, these behaviours are not guaranteed.''
Line 27:		Line 27:
	# LANGUAGE.MIX		# LANGUAGE.MIX
	# EXPANDMD##.MIX '';( 99, 98, ... 02, 01)''		# EXPANDMD##.MIX '';( 99, 98, ... 02, 01)''
	~~# ECACHEMD*.MIX~~
	# RA2MD.MIX		# RA2MD.MIX
	# RA2.MIX		# RA2.MIX
Line 66:		Line 65:
	In RA2, even though expand##.mix is above ecache.mix in loading hierarchy, the SHP files of buildings/infantry/trees etc. which already exist in original game mix files becomes invisible in-game when those files or files with the same filenames are placed in expand##.mix. Modified files of those should be placed in ecache.mix for RA2.		In RA2, even though expand##.mix is above ecache.mix in loading hierarchy, the SHP files of buildings/infantry/trees etc. which already exist in original game mix files becomes invisible in-game when those files or files with the same filenames are placed in expand##.mix. Modified files of those should be placed in ecache.mix for RA2.

	=== {{tt\|ecache~~{{co\|md\|#D2691E}}~~*.mix}} ===		=== {{tt\|ecache*.mix}} ===
	As the name suggests, this is a cache file. This file is lower in file loading heirarchy than many other mix files. So the game will read new or modified SHP files from it but only VXL/HVA files with different filenames over the original mix files. Both RA2 and YR read the files placed in ecache*.mix, so it could be used as common resource file.		As the name suggests, this is a cache file. This file is lower in file loading heirarchy than many other mix files. So the game will read new or modified SHP files from it but only VXL/HVA files with different filenames over the original mix files. Both RA2 and YR read the files placed in ecache*.mix, so it could be used as common resource file.
	*[[SHP]]s (normal buildings, infantry etc.)		*[[SHP]]s (normal buildings, infantry etc.)

en>Fallendow at 07:37, 26 December 2021

2021-12-26T07:37:49Z

← Older revision		Revision as of 09:37, 26 December 2021
Line 9:		Line 9:
	;{{tt\|expand{{co\|md\|#D2691E}}##.mix}}		;{{tt\|expand{{co\|md\|#D2691E}}##.mix}}
	:Where ## is a number between 01 and 99, and {{tt\|{{co\|md\|#D2691E}}}} is added if the the file is for {{yr}}.		:Where ## is a number between 01 and 99, and {{tt\|{{co\|md\|#D2691E}}}} is added if the the file is for {{yr}}.
	;{{tt\|ecache*.mix}}		;{{tt\|ecache{{co\|md\|#D2691E}}*.mix}}
	:Where * can be any string.		:Where * can be any string, and {{tt\|{{co\|md\|#D2691E}}}} is added if the the file is for {{yr}}.
	;{{tt\|elocal*.mix}}		;{{tt\|elocal*.mix}}
	:Where * can be any string.		:Where * can be any string.
Line 17:		Line 17:
	The game searches the MIX files for contents in this order. Once a file is found in a mix, the next MIXes don't even get checked for its presence.		The game searches the MIX files for contents in this order. Once a file is found in a mix, the next MIXes don't even get checked for its presence.
	* A higher-numbered {{tt\|expand{{co\|md\|#D2691E}}##.mix}} has a higher level than a lower numbered one.		* A higher-numbered {{tt\|expand{{co\|md\|#D2691E}}##.mix}} has a higher level than a lower numbered one.
	* For {{tt\|ecache}} and {{tt\|elocal}} files, order is not guaranteed - standard WinAPI functionality is used to locate them, and no sorting is done.		* For {{tt\|ecache{{co\|md\|#D2691E}}}} and {{tt\|elocal}} files, order is not guaranteed - standard WinAPI functionality is used to locate them, and no sorting is done.
	:: Quoting [http://msdn.microsoft.com/en-us/library/aa364428(VS.85).aspx MSDN - FindNextFile]:		:: Quoting [http://msdn.microsoft.com/en-us/library/aa364428(VS.85).aspx MSDN - FindNextFile]:
	:::: ''The order in which this function returns the file names is dependent on the file system type. With the NTFS file system and CDFS file systems, the names are usually returned in alphabetical order. With FAT file systems, the names are usually returned in the order the files were written to the disk, which may or may not be in alphabetical order. However, as stated previously, these behaviours are not guaranteed.''		:::: ''The order in which this function returns the file names is dependent on the file system type. With the NTFS file system and CDFS file systems, the names are usually returned in alphabetical order. With FAT file systems, the names are usually returned in the order the files were written to the disk, which may or may not be in alphabetical order. However, as stated previously, these behaviours are not guaranteed.''
Line 27:		Line 27:
	# LANGUAGE.MIX		# LANGUAGE.MIX
	# EXPANDMD##.MIX '';( 99, 98, ... 02, 01)''		# EXPANDMD##.MIX '';( 99, 98, ... 02, 01)''
			# ECACHEMD*.MIX
	# RA2MD.MIX		# RA2MD.MIX
	# RA2.MIX		# RA2.MIX
Line 65:		Line 66:
	In RA2, even though expand##.mix is above ecache.mix in loading hierarchy, the SHP files of buildings/infantry/trees etc. which already exist in original game mix files becomes invisible in-game when those files or files with the same filenames are placed in expand##.mix. Modified files of those should be placed in ecache.mix for RA2.		In RA2, even though expand##.mix is above ecache.mix in loading hierarchy, the SHP files of buildings/infantry/trees etc. which already exist in original game mix files becomes invisible in-game when those files or files with the same filenames are placed in expand##.mix. Modified files of those should be placed in ecache.mix for RA2.

	=== {{tt\|ecache*.mix}} ===		=== {{tt\|ecache{{co\|md\|#D2691E}}*.mix}} ===
	As the name suggests, this is a cache file. This file is lower in file loading heirarchy than many other mix files. So the game will read new or modified SHP files from it but only VXL/HVA files with different filenames over the original mix files. Both RA2 and YR read the files placed in ecache*.mix, so it could be used as common resource file.		As the name suggests, this is a cache file. This file is lower in file loading heirarchy than many other mix files. So the game will read new or modified SHP files from it but only VXL/HVA files with different filenames over the original mix files. Both RA2 and YR read the files placed in ecache*.mix, so it could be used as common resource file.
	*[[SHP]]s (normal buildings, infantry etc.)		*[[SHP]]s (normal buildings, infantry etc.)

en>E1 Elite at 10:22, 12 June 2018

2018-06-12T10:22:15Z

← Older revision		Revision as of 12:22, 12 June 2018
Line 63:		Line 63:
	*[[HVA]]s		*[[HVA]]s

	In RA2 expand##~~, game doesn't accept some filetypes placed~~ in ~~it like SHPs (Buildings~~, ~~infantries~~ etc.~~) or Tree~~ files~~, those would become~~ invisible in-game. ~~Such~~ files ~~could~~ be placed in ecache*.mix.		In RA2, even though expand##.mix is above ecache.mix in loading hierarchy, the SHP files of buildings/infantry/trees etc. which already exist in original game mix files becomes invisible in-game when those files or files with the same filenames are placed in expand##.mix. Modified files of those should be placed in ecache.mix for RA2.

	=== {{tt\|ecache*.mix}} ===		=== {{tt\|ecache*.mix}} ===