OBD:AKBA
(Redirected from AKBA)
|
|
|
| Offset | Type | Raw Hex | Value | Description |
|---|---|---|---|---|
| 0x00 | res_id | 01 4F 02 00 | 591 | 00591-.AKBA |
| 0x04 | lev_id | 01 00 00 06 | 3 | level 3 |
| 0x08 | char[20] | AD DE | dead | padding |
| 0x1C | uint32 | B7 06 00 00 | 1719 | array size |
| First element (black outline) | ||||
| 0x00 | uint32hb | 00 00 00 00 | 0, hig bit | plane index for this "side" (see AKEV / PLEA); high bit flips the plane |
| 0x04 | uint32 | 00 00 00 00 | 0 | AKAA range start (adjacencies for this side) |
| 0x08 | uint32 | 01 00 00 00 | 1 | AKAA range end (adjacencies for this side) |
| 0x0C | uint32 | 00 00 00 00 | 0 | ghost GQ start index; ignored |
| 0x10 | uint32 | 01 00 00 00 | 1 | ghost GQ end index; ignored |
| 0x14 | uint32 | 00 00 00 00 | 0 | BNV quad start index; ignored |
| 0x18 | uint32 | 01 00 00 00 | 1 | BNV quad end index; ignored |
- Plane
It appears that the plane is ignored by the engine. In particular if a side has adjacencies then it has ghost quads and any quad has an associated plane. Sometimes the ghost quads are inside the BNV (instead of being on the edge) and in that case the quad plane is different from the side plane.
- AKAA range
- These 2 fields make up a range of "adjacencies" (see AKAA). If the fields are equal then the range is empty.
| ONI BINARY DATA |
|---|
| AKAA << Other file types >> AKBP |
| AKBA : Side Array |
| Level file |