-
Notifications
You must be signed in to change notification settings - Fork 2
CHR.BIN
D. Debonair edited this page Jan 29, 2025
·
4 revisions
{{< // >}}
- Lookups
- Offset has to be shifted to the left by 11 (or multiply by
0x800) - Size has to be shifted left by 2 (or multiplied by 4)
- Offset has to be shifted to the left by 11 (or multiply by
- These are continuous files. Between them are
00patches only [Could be used to map out the rest ofCHR.BINif consistent] - The value of the offset is the address stored.
- If you ever have to edit those files (I think they are mostly textures) you would have to edit the overlay (i.e. slot
020) at those addresses.
- If you ever have to edit those files (I think they are mostly textures) you would have to edit the overlay (i.e. slot
We believe it could be:
- Following the same pattern as
OVR.BINas it:- follows the mentioned pattern
- Count checks out
- table pattern visibly stops after selected area
- columns only contain increasing values in an unbroken pattern
- The offset should only be shifted by 2, the size also shifted by 2.
- This one may not be the table for the whole BIN file, but maybe just one blob of many.
- Shifting the offset here doesn't make much sense beyond 2, and never coincides with clear
00patches.

Base Adresses for overlays:
| Type | Address |
|---|---|
| ProgOverlay | 0x80153eb0 |
| BaseOverlay | 0x80158138 |
| CnstOverlay | 0x8015f328 |
| SubOverlay | 0x80156CA4 |
All entries are base 0.
LoadOverlay calls at addresses:
| Type | Address |
|---|---|
| Slot 000 | "DEMO PLAY" Overlay |
| Slot 002 | "DEMO PLAY" Overlay |
| Slot 020 | Intro text crawl |