MxCh: Difference between revisions
Jump to navigation
Jump to search
(Created page with "MxCh is the 32-bit identifier for a Lego Island data chunk. They are seen extensively in SI Files to allow interleaving of several different data types. MxCh chunks c...") |
No edit summary |
||
| Line 1: | Line 1: | ||
[[MxCh]] is the | [[MxCh]] is the identifier for a [[Lego Island]] data chunk. They are seen extensively in [[SI Files]] to allow interleaving of several different data types. | ||
MxCh chunks contain partial data of various different data types intended to be joined together continuously to form a complete file (an MxDa section). The chunks can also contain solely header data. A chunk will almost never contain a complete file on its own. | MxCh chunks contain partial data of various different data types intended to be joined together continuously to form a complete file (an MxDa section). The chunks can also contain solely header data. A chunk will almost never contain a complete file on its own. | ||
Revision as of 13:02, 18 April 2019
MxCh is the identifier for a Lego Island data chunk. They are seen extensively in SI Files to allow interleaving of several different data types.
MxCh chunks contain partial data of various different data types intended to be joined together continuously to form a complete file (an MxDa section). The chunks can also contain solely header data. A chunk will almost never contain a complete file on its own.
Specification
NOTE: This information is incomplete and requires more research and information.
The MxCh header is 20 bytes long and specifies the length of the chunk with other data.
| Bytes | Offset | Description |
|---|---|---|
| "MxCh" | 0 | 4-byte chunk identifier |
| Chunk Size | 4 | 4-byte integer |
| Unknown | 8 | Unknown data |
| Data | 20 | Arbitrary data no more than "Chunk Size" in bytes |