Value Database: Difference between revisions
m
no edit summary
No edit summary |
AcuteSyntax (talk | contribs) mNo edit summary |
||
(17 intermediate revisions by 2 users not shown) | |||
Line 1:
The '''Value Database'''
Each value the VDB contains is mapped to a unique 32-bit hash ID, which acts as that value's descriptor and tells the game where to apply the value. Hashes are sorted numerically within the VDB.
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 are 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>
= Header =
{|class="wikitable"
|-
! Offset
! Name
! Type
! Value
! Notes
|-
| 0x00 || Version number || int || 0x02 ||
|-
| 0x04 || Number of entries in first data chunk || int || ||
|-
| 0x08 || Number of entries in second data chunk || int || ||
|-
| 0x0C || Number of entries in third data chunk || int || ||
|-
| 0x10 || Offset of third data chunk || int || ||
|}
= Entry =
=== Chunk 1 Entry ===
{|class="wikitable"
|-
! Offset
! Name
! Type
! Notes
|-
| 0x00 || Value || float<br>word* || Certain Chunk 1 values consist of offsets to entries longer than 32 bits.
|-
| 0x04 || Hash ID || GtHash ||
|}
=== Chunk 2 Entry ===
{|class="wikitable"
|-
! Offset
! Name
! Type
! Notes
|-
| 0x00 || Value || Vector3 || Padded to 0x10 in length.
|}
=== Chunk 3 Entry ===
{|class="wikitable"
|-
! Offset
! Name
! Type
! Notes
|-
| 0x00 || Value || int || Always <tt>0x00000001<tt>
|-
| 0x04 || Hash ID || GtHash ||
|}
[[Category:Formats_(Takedown-Dominator)]]
|