Line (File Format): Difference between revisions
From Wexos's Wiki
Jump to navigationJump to search
(Imported from avsys wiki) |
No edit summary |
||
| Line 1: | Line 1: | ||
'''Line''' BIN files from [[Mario Kart Arcade GP]] and [[Mario Kart Arcade GP 2]] control route data used by CPUs. | '''Line''' BIN files from [[Mario Kart Arcade GP]] and [[Mario Kart Arcade GP 2]] control route data used by CPUs as well as checkpoints. | ||
= File Format = | = File Format = | ||
| Line 8: | Line 8: | ||
! Offset !! Type !! Description | ! Offset !! Type !! Description | ||
|- | |- | ||
| 0x00 || Int32 || {{Unknown-left|'''Unknown'''. Always 6.}} | | 0x00 || Int32 || {{Unknown-left|'''Unknown'''. Always 6. Maybe number of CPU paths?}} | ||
|- | |- | ||
| 0x04 || Int32 || {{Unknown-left|'''Unknown'''. Always 6.}} | | 0x04 || Int32 || {{Unknown-left|'''Unknown'''. Always 6. }} | ||
|- | |- | ||
| 0x08 || Int32 || '''N''' number of paths. Always 7. | | 0x08 || Int32 || '''N''' number of paths. Always 7. | ||
| Line 18: | Line 18: | ||
== Path Offsets == | == Path Offsets == | ||
At the start of the file there are '''N''' path offsets, relative to the start of the file. The data afterwards is aligned to 0x10. | At the start of the file there are '''N''' path offsets, relative to the start of the file. The data afterwards is aligned to 0x10. The first path is always a checkpoint path, while the rest are CPU paths from left to right from the pole position. | ||
{|class=wikitable | {|class=wikitable | ||
| Line 46: | Line 46: | ||
| 0x00 || Int32 || {{Unknown-left|'''Unknown'''. Always 1.}} | | 0x00 || Int32 || {{Unknown-left|'''Unknown'''. Always 1.}} | ||
|- | |- | ||
| 0x04 || Float[3] || Point position. | | 0x04 || Float[3] || Point position. The Y value seems to be used as the point's radius (?) | ||
|} | |} | ||
Latest revision as of 13:37, 4 May 2024
Line BIN files from Mario Kart Arcade GP and Mario Kart Arcade GP 2 control route data used by CPUs as well as checkpoints.
File Format
The file byte order is always big endian. It starts being read with a 12 byte footer.
| Offset | Type | Description |
|---|---|---|
| 0x00 | Int32 | Unknown. Always 6. Maybe number of CPU paths? |
| 0x04 | Int32 | Unknown. Always 6. |
| 0x08 | Int32 | N number of paths. Always 7. |
| 0x0C | End of footer | |
Path Offsets
At the start of the file there are N path offsets, relative to the start of the file. The data afterwards is aligned to 0x10. The first path is always a checkpoint path, while the rest are CPU paths from left to right from the pole position.
| Offset | Type | Description |
|---|---|---|
| 0x00 | Int32[N] | Offsets to Path Data sections. |
Path Data
Each path has a footer that determines the number of points.
| Offset | Type | Description |
|---|---|---|
| 0x00 | Int32 | Negative number of points of the path. To obtain the actual number of routes, multiply by -1. |
| 0x04 | Byte[12] | Padding. |
Point Data
Each route point has its own 0x10 byte long entry.
| Offset | Type | Description |
|---|---|---|
| 0x00 | Int32 | Unknown. Always 1. |
| 0x04 | Float[3] | Point position. The Y value seems to be used as the point's radius (?) |
Tools
The following tools can handle Line files:
- (none)
