ModEnc is currently in Maintenance Mode: Changes could occur at any given moment, without advance warning.

MIX

From ModEnc
(Redirected from Mix)
Jump to: navigation, search

Mix files (file extension .mix) are archive files used by Westwood to store most game files from Tiberian Dawn to Renegade. For Generals and following, BIG files took this part.

Editing Mix Files

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 xhp.xwis.net.

Alternatively, there's a command line tool called ccmix by OmniBlade which can generate and extract from mix files.

Mix Types

There are several types of mix files, each for a specific purpose as detailed below. Using mix files correctly is important for the correct execution of your mod.

This list was generated for Yuri's Revenge 1.001. Red Alert 2 ignores the md mixes, and other games might use a different order, to be documented later.

Index Mix File Description
0 LANGMD.MIX Localized files for the Mission Disk (Yuri's Revenge): audio, cameos, etc.
1 LANGUAGE.MIX Localized files for RA2: audio, cameos, etc.
2 EXPANDMD##.MIX Expansion mix for YR: various files, more information below.
The ## is any two-digit number between 01–99, with higher numbers loaded first.
3 RA2MD.MIX Main mix file for YR. Most mix files are stored within this file, except for expansion mixes.
4 RA2.MIX Main mix file for RA2. Most mix files are stored within this file, except for expansion mixes.
5 CACHEMD.MIX Cached files for YR. Usually palettes and certain shape files.
6 CACHE.MIX Cached files for RA2. Usually palettes and certain shape files.
7 LOCALMD.MIX Voxels, most INIs, and certain UI graphics are stored here. YR only.
8 LOCAL.MIX Voxels, most INIs, and certain UI graphics are stored here.
9 AUDIOMD.MIX Audio files (except music) for YR.
10 ECACHE*.MIX Expansion cache. Works like cache.mix.
11 ELOCAL*.MIX Local files for an expansion pack. Works like local.mix.
12 CONQMD.MIX Infantry shapes and non-theater-specific, non-building animations. YR only.
13 GENERMD.MIX Generic, non-theater-specific building graphics, terrain objects, and overlay. YR only.
14 GENERIC.MIX Generic, non-theater-specific building graphics, terrain types, and overlay.
15 ISOGENMD.MIX Generic, non-theater-specific building and tile set graphics. Not cached. YR only.
16 ISOGEN.MIX Generic, non-theater-specific building and tile set graphics. Not cached.
17 CONQUER.MIX Infantry shapes and non-theater-specific, non-building animations.
18 CAMEOMD.MIX Cameo shapes. YR only.
19 CAMEO.MIX Cameo shapes.
20 MAPSMD03.MIX Mission maps. YR only.
21 MULTIMD.MIX Multiplayer maps. YR only.
22 THEMEMD.MIX Music files. YR only.
23 MOVMD03.MIX Video files. YR only.
24 ... Theater-specific mixes - see Theatres for a list.
25 SIDEC##.MIX Side-specific UI elements, like sidebar graphics. The ## stands for the side you're playing as: e.g. 01 for Allies, 02 for Soviets, etc.
26 SIDENC##.MIX Side-specific elements for the campaign progression/mission selection map screen. Unused in RA2/YR.

Loading Hierarchy

The game searches the mix files for contents in the above order. Once a file is found in a mix, the next mixes don't even get checked for its presence.

  • For ecache* and elocal* files, order is not guaranteed - standard WinAPI functionality is used to locate them, and no sorting is done.
Quoting 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.
Additionally, files that have any of the "Hidden", "System" or "Temporary" attributes set are not loaded.

Expansion Mix Files

As a result of their high priority and versatility, it is common to store mod assets in the so-called expansion mix files. There are three different expansion mix types as explained below.

Instead of using these mix files as catch-all archives, it is recommended to follow the original mix file organization where possible to avoid potential issues.

EXPANDMD##.MIX

## is a number between 01 and 99, and md is added if the the file is for Yuri's Revenge.

This file is used for addon or expansion purpose where new or modified files can be placed. Most filetypes can be placed in it, except the files from lang*.mix which are higher in loading hierarchy.

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.

ECACHE*.MIX

* can be any string for both Red Alert 2 and Yuri's Revenge. Tiberian Sun uses ecache##.mix where ## is 2-digit number.

As the name suggests, this is an expansion mix file for files that should be cached. This file is lower in file loading hierarchy 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.

ELOCAL*.MIX

RA2/YR only. * can be any string.

This file is practically not used in the community, but works for "unofficial SHP, VXL, HVA and MAP files" according to DeeZire's Red Alert 2 and Yuris Revenge INI Editing Guide. Since, in the original game, local.mix holds almost all object-related graphics, and elocal*.mix works for the same file types, it is likely it was originally conceived as an expansion file specifically for local.mix. It is unknown why the community started using ecache*.mix for unit graphics instead.

Loose Files

The following file types are usually not stored in a mix file:

  • CSF
  • PKT, Only 1 can exist loose, otherwise you get maps listed multiple times.
  • BAG
  • IDX
  • WAV
  • BIK

Note that, despite this common distribution of files, many files (especially graphics) work in an expandmd##.mix as well.

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 named correctly.

Using XCC MIX Editor

Click 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

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


Location of files in the game's mix files

RA2/YR

  • The INI files are in RA2.mix → local.mix and RA2md.mix → localmd.mix. rulesmd.ini and soundmd.ini for YR 1.001 are in expandmd01.mix.
  • Cameos (build icons), which are single frame SHPs, can found in language.mix → cameo.mix and in langmd.mix → cameomd.mix.
  • Infantry, which are multi frame SHPs, can be found in RA2.mix → conquer.mix and ra2md.mix → conqmd.mix.
  • The voxels (and their associated hva files), Tanks, naval vessels, and aircraft, can be found in ra2.mix → local.mix and ra2md.mix → localmd.mix.

See also

Retrieved from "https://modenc.renegadeprojects.com/index.php?title=MIX&oldid=21960"