I think he brought it up because, usually, texture files are the biggest kind of files in a game.

: "When we build the final resource file, which we call a cache file, we
: simply dump all loaded tags into a giant buffer and write that out to a
: single file. At runtime, we just need to read that file into a fixed
: address before we start the level "

: The tags, which are data structures, are where you would find pointers. Eg,
: the root of a render_model tag has a tag-block for the model's markers.
: That tag block, as of Halo4's tag system implementation, contains two
: pointers plus a 32-bit 'count' for the number of elements in the block.
: One of those pointers is the (fixed) memory address of the first element
: of that block (ie, the first marker).

Woah. Thanks. That's actually pretty cool to know about. It's almost as if it were a reverse memory-dump I like to use at my programs' crashes.