Welcome to Talk:VPK (file format)!
This is the start of the
To add a new message, click on "Add Topic/Reply" button below, and set the "Subject".
To add a Reply, do the same as above, but leave the "Subject" blank.
VPK (file format)
discussion page.To add a new message, click on "Add Topic/Reply" button below, and set the "Subject".
To add a Reply, do the same as above, but leave the "Subject" blank.
Nem 6:44, 5 August 2009 (UTC)
I think the bit ShaRose added about skipping refers to the same thing as the following sentence:
Each tree node begins with a null terminated ASCII string and empty strings are used to signify the end of a parent node.
Perhaps I should have been clear the leaf nodes were exempt from this; nonetheless, the pseudo-code covers it.
Pharap 23:42, 10 August 2013 (UTC)
Does anybody know whether the format is Big Endian or Little Endian?
Seems to be an important piece of info that has been overlooked.
Assumptions
BenLubar 20:05, 6 August 2022 (UTC)
I've been doing some reverse engineering/code research and a few assumptions made in this article are incorrect:
- The ArchiveIndex, EntryOffset, and EntryLength fields of VPKDirectoryEntry can be repeated if a file has fragmented contents. This explains why there is a terminator at the end of the entry header.
- In CPackedStoreFileHandle (Alien Swarm SDK) the data referred to by the article as "Preload" is referred to as "Metadata" instead. The actual file data and the metadata are never mixed, so the comment about vmt files being stored entirely in the directory is incorrect.