Files
libretro/emulators/fs-uae.yml
T
Abdessamad Derraz bb19a6d5cf feat: profile what RetroBat and RetroPie run
100 emulator names the two platforms run had no profile, so their packs carried nothing for them. Each was read from the platform's own launcher or scriptmodule: the same program as an existing profile takes the name in cores:, a different build gets its own profile read from that version, a launcher or self-contained game goes to remove_cores, and the rest are new profiles written from their source or shipped binary. The files they need that the collection lacked are collected from the upstream distributions. Bungie and splitwolf trees are read by path and stay out of dedup.
2026-10-20 06:14:10 +02:00

65 lines
2.8 KiB
YAML

emulator: FS-UAE 3.1
type: standalone
core_classification: other
source: "https://github.com/FrodeSolheim/fs-uae"
profiled_date: "2026-10-20"
source_commit: "596d803944f6498c305ac48d338f6252cbde7ecb"
core_version: "3.1.64"
display_name: "Commodore - Amiga (FS-UAE 3.1)"
cores: [fs-uae]
systems: [commodore-amiga]
notes: |
FS-UAE 3.1.64 by Frode Solheim, the build published in the stable
repository of the author's openSUSE Build Service project for Debian 11
and 12 and Ubuntu 20.04 to 25.04 (BASEVERSION.FS:1). RetroPie installs
that package rather than building the source. Its launcher refuses to
start without kick13.rom in the BIOS directory and starts the emulator
with --kickstart_file pointing at it, an A500 configuration and the
floppies of the game.
A kickstart_file other than "internal" is expanded, resolved against the
ROM search paths and handed to UAE as kickstart_rom_file, and
kickstart_ext_file the same way as the extended ROM
(src/fs-uae/config.c:80-101). Unless kickstart_file is "internal", the
Kickstarts directory and AmigaForever/Amiga Files/Shared/rom under the base
directory are scanned for .rom and .bin files, so that a model chosen
without a kickstart_file finds its ROM there (src/fs-uae/config.c:121-140,
src/fs-uae/main.c:431-470).
load_kickstart opens the named file and falls back to roms/kick.rom,
kick.rom, ../shared/rom/kick.rom and ../System/rom/kick.rom under the data
path, then to a guess from the ROM list (src/memory.cpp:1583-1612). A ROM
that is not in the table still loads, a known one is only logged by name
(src/memory.cpp:2374-2385). With no ROM at all the error is logged and the
built-in AROS replacement is loaded instead (src/memory.cpp:2374-2379,
1512-1581), whose ext and rom halves come from share/fs-uae in the
installed package.
rom.key is looked for next to the kickstart file and in each scanned
directory, to decrypt Cloanto ROMs (src/rommgr.cpp:803-819,
src/fs-uae/main.c:443-461).
files:
- name: "kick13.rom"
system: commodore-amiga
required: true
hle_fallback: true
size: 262144
crc32: "c4f0f55f"
sha1: "891e9a547772fe0c6c19b610baf8bc4ea7fcb785"
source_ref: "src/rommgr.cpp:141-142, src/fs-uae/config.c:80-101"
note: >-
KS ROM v1.3 (A500, A1000, A2000), ROM id 6, the one the A500 quickstart
selects. The RetroPie launcher exits with a dialog when the file is
absent from the BIOS directory, so the game never starts. FS-UAE alone
loads the AROS replacement in its place.
- name: "rom.key"
system: commodore-amiga
required: false
source_ref: "src/rommgr.cpp:803-819, src/fs-uae/main.c:443-461"
note: >-
Cloanto Amiga Forever key, read from the directory of the kickstart
file. Needed only when that kickstart is an encrypted Cloanto dump.