File formats used by MM2 are described under this section.
- 1 Common formats
- 2 Cities
- 3 Vehicles
- 4 Pedestrians
Several file formats are used for many things. For example, the PKG format is used for vehicle models, props, monuments, facades and even the hud map. This section describes several of these common formats.
3D Object models (PKG)
The geometry of small 3D objects are defined by PKG files. These files are divided into several sections, or chunks. The structure has similarities with the standard wave/riff format.
The PKG-files define the objects using triangle or quad facets, each facet is grouped into a facet group that is assigned a shader. The shader defines colour attributes and, if needed, a texture map name. More...
Texture maps (TEX)
Texture mapping is the most commonly used method to apply colour to an MM2 city and the objects within it. It has been shown that MM2 can use some variants of the Targa (TGA) file format. Because this format is a public one, it has been the preferred texture format for new cars and cities.
Still, most original textures are encoded in a custom file format, known as TEX. This file format has many features, but the most significant one is the possibility to store mip-maps for the texture. Mip-maps are scaled copies of the original texture map. When surfaces are distant, a smaller scale is used and the surface looks less cluttered. More...
Each city has one PSDL file. This file defines roads, ground surface and buildings. In addition, the PSDL file also provides an easy way to automatically place props along roads etc. This is particularly good for placing street lights, parking meters and similar objects.
The geometry of a city is divided into blocks. A block is a small section of the city, similar to the regular definition of a city block. One difference, though, is that roads and intersections are also placed in their own blocks.
The block structure is used for all kinds of things in the game. Most obvious are visible surface identification, collision detection, ambient "intelligence", etc. All of these are calculated with respect of the block structure. More...
Each city can have one INST file, the INST file describes where to place monuments and other objects modeled in a PKG model file. Each placement allows a selection of paint job, scale and orientation as well as location of a PKG. More...
Ambient paths (BAI)
Each city can have one BAI file to define paths for controlling ambients such as pedestrians and automated traffic. More...
A city can have any number of pathset files. These place series of props or decals around a city. A prop is a PKG object that usually can be knocked down or even broken, such as small trees, cones, park benches, et.c. More...
Each city has ambient sound sources placed all around. The files controlling this are mostly unexplored. More...
The vehicles in MM2 are PKG objects with some specifics.
The file formats for pedestrians are mostly ASCII based, this implies that Angel Studios were rushed when completing the game - there was no time to create a binary, more efficient format for the information.
Pedestrian skeleton (.skel)
All the parts of a pedestrian model are bound to a skeleton. A skeleton is constructed by a number of bones that are attached with joints. In MM2 the skeletons are defined using a tree structure. More...
The pedmodel_*.mod files define the actual 3D model of a pedestrian. It defines vertices, some material attributes and the surfaces of the model. More...