Skip to content

fix(ti99): correct TI-99/4A config (speechsyn topology, Game Focus, on-board controls)#86

Open
agiacalone wants to merge 4 commits into
knulli-cfw:knulli-mainfrom
agiacalone:fix/ti99-speechsyn-slot
Open

fix(ti99): correct TI-99/4A config (speechsyn topology, Game Focus, on-board controls)#86
agiacalone wants to merge 4 commits into
knulli-cfw:knulli-mainfrom
agiacalone:fix/ti99-speechsyn-slot

Conversation

@agiacalone

Copy link
Copy Markdown

Summary

Corrects the TI-99/4A (ti99) configuration: the right MAME command, keyboard input that actually reaches the core, and full on-board (handheld) controls. Validated on a TrimUI Brick Hammer (Allwinner A133P, aarch64), scarab 20260511, from a clean deploy of this branch.

Scope (honest): these are configuration-layer fixes — necessary and correct, but not sufficient alone. On scarab 20260511 the stock mame_libretro core itself SIGSEGVs running ti99_4a even with the corrected command — tracked separately in #85 (and same family as #81). Playable TI-99 also needs a working MAME core; validated here against MAME 0.287.

Changes

  1. libretroMAMEConfig.py + mameGenerator.py — correct TI-99 slot topology. -ioport:peb:slot3 speech is invalid (speech is not a PEB-slot card; the synth is speechsyn on the console ioport, PEB chains through its extport). lr-mame failed to load the machine on the bad option. Fixed so speech + 32K RAM coexist.
  2. libretroConfig.pyinput_auto_game_focus = '2' (general fix). Without Game Focus, RetroArch never forwards keyboard input to the core, so no MAME computer system can receive keys in-game. Detect mode enables it only for keyboard cores (other systems keep hotkeys). Benefits every MAME computer system (apple2, bbc, coco, atom, electron, fm7, … and ti99); cherry-pickable on its own. Likely also helps Conflicting/buggy hotkey behavior on MAME 2003-plus RetroArch core (and possibly other MAME cores) #82.
  3. board/fsoverlay/usr/share/evmapy/ti99.keys — default on-board control map. The libretro MAME core routes the pad only to MAME joystick inputs, never the keyboard matrix; evmapy (no-grab) emits real KEY_* via uinput → reaches the core once Game Focus is on. d-pad = joystick, A/B = fire, L1/R1/L2/R2/X = 1–5, Select = 0, hotkey+Start = exit.

Testing (TrimUI Brick Hammer, A133P)

Deployed this branch to real install paths, restored the stock core, stripped all runtime overrides, launched a-maze-ing:

Related

lr-mame rejects '-ioport:peb:slot3 speech' ('speech' is not a PEB-slot
card), which made every TI-99/4A title fail to launch (older mame_libretro
builds segfaulted on the bad slot option). The synth is 'speechsyn' on the
console ioport; the PEB chains into its 'extport' pass-through, so the 32K
RAM expansion and speech can coexist. Batocera fixed the crash upstream but
drops 32K when speech is on (second -ioport overrides peb); this keeps both.
…alone mame)

Same fix as the libretro generator, for the standalone mame path. 32K RAM
stays enabled by default here, chained through the speech synth's extport.
…rd cores

Without Game Focus, RetroArch swallows keyboard input and never forwards it
to the core, so TI-99/4A (and other MAME computer systems) are unplayable even
after the launch fix -- no keypress reaches the emulated keyboard, and evmapy
pad->key output is dropped too. Detect mode (2) auto-enables Game Focus only
for cores that request a keyboard, leaving other systems' hotkeys intact.
The libretro MAME core only routes the pad to MAME joystick inputs, never the
keyboard matrix, so TI-99 menus (cart select, in-game number options) need real
key events. evmapy (no-grab) emits them via uinput; with Game Focus on they
reach the core. Map: d-pad=joystick, A/B=fire, L1/R1/L2/R2/X=1-5, Select=0,
hotkey+Start=exit. Makes TI-99 fully playable on handheld controls (no keyboard).
@agiacalone
agiacalone force-pushed the fix/ti99-speechsyn-slot branch from 0ad54e4 to 6298702 Compare June 17, 2026 00:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant