Skip to content

Possibly incorrect 4CC data in VBSP #12

Open

Description

@TheRogueArchivist

After checking some VBSP files in HL2, I noticed that seemingly every lump in every file checked reports: 4CC: , , , .

This seems to require further investigation, and VBSP files of versions 19 and 20 were checked.

Activity

  1. TheRogueArchivist commented on Nov 16, 2024

    @TheRogueArchivist
    ContributorAuthor

    Further info on 4CC/FourCC:

    The first two integers contain the byte offset (from the beginning of the bsp file) and byte length of that lump's data block; an integer defining the version number of the format of that lump (usually zero), and then a four byte identifier that is usually 0, 0, 0, 0. For compressed lumps, the fourCC contains the uncompressed lump data size in integer form (see section [Lump compression](https://developer.valvesoftware.com/wiki/Source_BSP_File_Format#Lump_compression) for details). Unused members of the lump_t array (those that have no data to point to) have all elements set to zero.
    
    Lump offsets (and their corresponding data lumps) are always rounded up to the nearest 4-byte boundary, though the lump length may not be.
    

    https://developer.valvesoftware.com/wiki/BSP_(Source)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions