Value Database: Difference between revisions
(corrected file name capitalisation) |
AcuteSyntax (talk | contribs) (adapted burninrubber's vdb struct) |
||
Line 1: | Line 1: | ||
The '''Value Database''' file format is used to store raw values used by various functionalities in the game, such as the physics engine and the behavior of vehicles. It uses the filename of <code>DATA/VDB.BIN</code> (named <code>DATA/VDB.XML</code> in Takedown, likely due to the ValueDB's origin as a collection of XML-formatted text files.) |
The '''Value Database''' file format is used to store raw values used by various functionalities in the game, such as the physics engine and the behavior of vehicles. It uses the filename of <code>DATA/VDB.BIN</code> (named <code>DATA/VDB.XML</code> in Takedown, likely due to the ValueDB's origin as a collection of XML-formatted text files.) Each value the VDB contains is mapped to a unique hash, which tells the game which value it is and where to apply it. |
||
[[Burnout_Legends_(2005-06-06_build)#Debug_Export|Using debug functionality]], the values for the player's current vehicle can be exported to an XML file named <code>EXPORT/VALUEDB/VEHICLEPHYSICS/%s.CFG</code>, where <code>%s</code> is the name of the vehicle's class e.g. <code>HSPC</code>, followed by <code>CAR</code>, the index of the car in its class and the extension <code>.CFG</code>. For example, the Compact Type 1's data is exported to <code>COMPCAR1.CFG</code>. |
[[Burnout_Legends_(2005-06-06_build)#Debug_Export|Using debug functionality]], the values for the player's current vehicle can be exported to an XML file named <code>EXPORT/VALUEDB/VEHICLEPHYSICS/%s.CFG</code>, where <code>%s</code> is the name of the vehicle's class e.g. <code>HSPC</code>, followed by <code>CAR</code>, the index of the car in its class and the extension <code>.CFG</code>. For example, the Compact Type 1's data is exported to <code>COMPCAR1.CFG</code>. |
||
= Layout = |
|||
{|class="wikitable" |
|||
|- |
|||
! Offset |
|||
! Length |
|||
! Type |
|||
! Description |
|||
|- |
|||
| 0x00 || 0x01 || UInt8 || Version number |
|||
|- |
|||
| 0x04 || 0x04 || UInt32 || Number of entries in first data chunk |
|||
|- |
|||
| 0x08 || 0x04 || UInt32 || Number of entries in second data chunk |
|||
|- |
|||
| 0x0C || 0x04 || UInt32 || Number of entries in third data chunk |
|||
|- |
|||
| 0x10 || 0x04 || UInt32 || Offset of third data chunk |
|||
|} |
Revision as of 23:11, 26 January 2021
The Value Database file format is used to store raw values used by various functionalities in the game, such as the physics engine and the behavior of vehicles. It uses the filename of DATA/VDB.BIN
(named DATA/VDB.XML
in Takedown, likely due to the ValueDB's origin as a collection of XML-formatted text files.) Each value the VDB contains is mapped to a unique hash, which tells the game which value it is and where to apply it.
Using debug functionality, the values for the player's current vehicle can be exported to an XML file named EXPORT/VALUEDB/VEHICLEPHYSICS/%s.CFG
, where %s
is the name of the vehicle's class e.g. HSPC
, followed by CAR
, the index of the car in its class and the extension .CFG
. For example, the Compact Type 1's data is exported to COMPCAR1.CFG
.
Layout
Offset | Length | Type | Description |
---|---|---|---|
0x00 | 0x01 | UInt8 | Version number |
0x04 | 0x04 | UInt32 | Number of entries in first data chunk |
0x08 | 0x04 | UInt32 | Number of entries in second data chunk |
0x0C | 0x04 | UInt32 | Number of entries in third data chunk |
0x10 | 0x04 | UInt32 | Offset of third data chunk |