Config Yaml

The config yaml sets up various options, offsets, and directories for Torch to use.

579c48e211ae952530ffc8738709f078d5dd215e:
  name: Mario Kart 64 [US]
  path: yamls/us      # Place yamls for asset extraction here
  config:
    gbi: F3DEX_MK64   # F3DEX version
    sort: OFFSET
    output:
      binary: mkcube.otr
      headers: include      # Location of generated header files
      code: assets/code     # Location of generated code files
  tables: [yamls/courses]   # Generates tabled data
  segments:
    - 0x000000
    - 0x000000
    - 0x12aae0
    - 0x000000
    - 0x000000
    - 0x000000
    - 0x825800
    - 0x000000
    - 0x000000
    - 0x88cd70
    - 0x729a30
    - 0x821D10
    - 0x7fa3c0
    - 0x132b50
    - 0x000000
    - 0x145470

A more indepth explanation of tables are required.

Segments

Segments should contain the rom addr of every segment used in the game. The index of the segment needs to be correct. For instance, 0x825800 is the sixth entry in the segments node. This tells Torch that rom data for segment 0x06 is located at 0x825800.

Now, some games load multiple files into the same segment. The asset yaml needs to specify its specific location in order for Torch to grab the correct rom address. If a segment is not specified in the asset yaml, torch will look at the address in the segments node in the config.yml