SCAN (Metroid Prime): Difference between revisions
>Aruki m (→Header) |
>Sdmr m (grammar correction and minor improvements in readability) |
||
| Line 1: | Line 1: | ||
The '''.SCAN file format''' describes scannable objects | The '''.SCAN file format''' describes scannable objects and has references to several resources. It is a relatively simple format and has a static size. | ||
{{researchmoderate|reason=Too many unknowns.}} | {{researchmoderate|reason=Too many unknowns.}} | ||
| Line 7: | Line 7: | ||
== Format == | == Format == | ||
The SCAN format is very simple; it has a header with data that contains general settings related to the scan, and then four structs defining how the scan images work. Even if a scan doesn't use four images, there | The SCAN format is very simple; it has a header with data that contains general settings related to the scan, and then four structs defining how the scan images work. Even if a scan doesn't use four images, there are always four image structs, which means that the SCAN format has a static size; every SCAN file is 0x89 bytes (or 0xA0 bytes padded). | ||
=== Header === | === Header === | ||
| Line 52: | Line 52: | ||
==== Logbook Category ==== | ==== Logbook Category ==== | ||
There | There are five possible values: | ||
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 13:32, 30 January 2015
The .SCAN file format describes scannable objects and has references to several resources. It is a relatively simple format and has a static size.
|
This file format needs more research Too many unknowns. |
Format
The SCAN format is very simple; it has a header with data that contains general settings related to the scan, and then four structs defining how the scan images work. Even if a scan doesn't use four images, there are always four image structs, which means that the SCAN format has a static size; every SCAN file is 0x89 bytes (or 0xA0 bytes padded).
Header
The header is rather simple, and consists of the following:
| Offset | Size | Description |
|---|---|---|
| 0x0 | 4 | Version; 3 for the demo, 5 for the final |
| 0x4 | 4 | Magic; always 0x0BADBEEF |
| 0x8 | 4 | FRME ID |
| 0xC | 4 | Scan text STRG ID |
| 0x10 | 4 | Scan Speed Flag; 0 = normal fast scan, 1 = slower scan (usually found in boss fights) |
| 0x14 | 4 | Logbook Category; see below |
| 0x18 | 1 | Scan Icon Flag; 0 = orange icon, 1 = red icon |
| 0x19 | End of header | |
Logbook Category
There are five possible values:
| ID | Category |
|---|---|
| 0 | Not a logbook scan |
| 1 | Space Pirate Data |
| 2 | Chozo Lore |
| 3 | Creatures |
| 4 | Research |
Scan Images
Following the header is an array of four structs that contain settings for up to four scan images. Although there can be anywhere from 0 to 4 scan images attached to a scan, there are always four scan image entries here. Entries that aren't used have their TXTR ID set to 0xFFFFFFFF, with the rest of the settings mostly left at defaults. They follow this format:
| Offset | Size | Type | Description |
|---|---|---|---|
| 0x0 | 4 | long | TXTR ID |
| 0x4 | 4 | float | Appearance %; image will appear when the scan is this% complete. Should range from 0 to 1. |
| 0x8 | 4 | long | Unknown (Fade in duration?) |
| 0xC | 4 | long | Unknown |
| 0x10 | 4 | long | Unknown |
| 0x14 | 4 | long | Unknown |
| 0x18 | 4 | float | Unknown |
| 0x1C | End of entry | ||