FONT (File Format): Difference between revisions
no edit summary
>Aruki m (→Textures) |
imported>Antidote No edit summary |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 42: | Line 42: | ||
| u32 | | u32 | ||
| 4 | | 4 | ||
| '''Vertical offset''' | | '''Vertical offset''' ''(note: not present in version 1)'' | ||
|- | |- | ||
| 0x14 | | 0x14 | ||
| Line 50: | Line 50: | ||
|- | |- | ||
| 0x18 | | 0x18 | ||
| bool | |||
| 1 | |||
| {{unknown|'''Unknown'''}} | |||
|- | |||
| 0x19 | |||
| bool | |||
| 1 | |||
| {{unknown|'''Unknown'''}} | |||
|- | |||
| 0x1A | |||
| u32 | | u32 | ||
| 4 | | 4 | ||
| {{unknown|'''Unknown'''}} | |||
| {{unknown|'''Unknown'''}} | |||
|- | |- | ||
| 0x1E | | 0x1E | ||
| Line 112: | Line 117: | ||
The kerning index value is the index of the first kerning table entry for the given character. Since the table is sorted in alphabetical order, this can be used to speed up lookup time. | The kerning index value is the index of the first kerning table entry for the given character. Since the table is sorted in alphabetical order, this can be used to speed up lookup time. | ||
This section of the file changes somewhat from version 2 to 4. Starting in version 4, | This section of the file changes somewhat from version 2 to 4. Starting in version 4, font textures are able to be split up into multiple layers, which allows multiple glyphs to be encoded in the same space on the texture. A "layer index" value was introduced to track which layer the glyph is on. Additionally, a lot of 32-bit values were reduced to 8- or 16-bit. Aside from that, though, the actual layout is still the same, with the same values in the same places. | ||
==== Version 2 (Metroid Prime NTSC) ==== | ==== Version 2 (Metroid Prime NTSC) ==== | ||
| Line 180: | Line 185: | ||
| u32 | | u32 | ||
| 4 | | 4 | ||
| '''Kerning index''' | | '''Kerning start index''' | ||
|- | |- | ||
| 0x2E | | 0x2E | ||
| Line 186: | Line 191: | ||
|} | |} | ||
==== Version 4 (Metroid Prime PAL) ==== | ==== Version 4 (Metroid Prime PAL/Trilogy) ==== | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 222: | Line 227: | ||
| u8 | | u8 | ||
| 1 | | 1 | ||
| ''' | | '''Layer index''' | ||
|- | |- | ||
| 0x13 | | 0x13 | ||
| Line 250: | Line 255: | ||
|- | |- | ||
| 0x18 | | 0x18 | ||
| u8 | |||
| 1 | |||
| '''Vertical offset''' | |||
|- | |||
| 0x19 | |||
| u16 | | u16 | ||
| 2 | | 2 | ||
| '''Kerning index''' | | '''Kerning start index''' | ||
|- | |- | ||
| | | 0x1B | ||
| colspan=3 {{unknown|End of glyph definition}} | | colspan=3 {{unknown|End of glyph definition}} | ||
|} | |} | ||
| Line 287: | Line 297: | ||
{{research|minor|Someone should look at the code to make sure the info in this section is accurate.}} | {{research|minor|Someone should look at the code to make sure the info in this section is accurate.}} | ||
Textures used by FONT files are encoded in a bit of an unorthodox manner. The font format allows for multiple glyphs to be encoded in the same spot on the texture by splitting up the texture into multiple layers. The way this is handled on the textures is by encoding the textures with palettes (as C4), but modifying the palette indices at runtime and loading each layer one at a time as a separate | Textures used by FONT files are encoded in a bit of an unorthodox manner. The font format allows for multiple glyphs to be encoded in the same spot on the texture by splitting up the texture into multiple layers. The way this is handled on the textures is by encoding the textures with palettes (as C4), but modifying the palette indices at runtime and loading each layer one at a time as a separate texture. Each bit of the palette index corresponds to a layer, so up to four layers per font are supported. The MSB refers to layer 0, while the LSB refers to layer 3. In DKCR, font textures are encoded as C8, so theoretically the game could use up to eight layers per font; however, it still never actually uses more than four. | ||
The texture format is determined by a value in the header. These are the possible settings: | The texture format is determined by a value in the header. These are the possible settings: | ||