First of all it's really amazing getting a working MAME 0.224 on a Raspberry Pi 4, many thanks for your effort and time!
I just tested your image and have some feedback/questions/issues:
Somehow the software list per system won't get recognized automatically which means you cannot load the game instantly in the software list menu. For example the game system "VIDEOPAC" has a voice module which has to get loaded in -cart1 and then the actual game in -cart2. I can only select one slot (cart, floppy or whatever the system needs). That's because somehow the system can't see its software.
Maybe this setting or feature is manually turned off or not yet implemented?
Further issues/questions:
- How can I change "Video Options"? Somehow I cannot enter it. I would like to have "bilinear filtering" off.
- Under "Machine options" when I set "UI Active ON", MAME is freezing (nothing can be edited).
- When I connect a USB Joystick it doesn't get recognized and cannot be mapped. Do I need to set it manually in the "cfg" folder (default.cfg)?
First, let me say that I am very happy to hear comments and feedback like yours, teller!
I will try to answer your issues/questions the best I can.
For MESS emulation, I did not made tests, as this part of the code has been enabled very recently (as you know). Can you explain me how to reproduce your problem? Do I need to download the BIOS of the Phillips Videopac+ system first? What voice module does need loading from cartridge1 and what game are you trying to emulate in cartridge2? I will try to reproduce your issue and see what I can do.
The "Video Options" menu is unfortunately not working for me too (I get a Segmentation fault when I try to use it). If you want to turn off "bilinear filtering" globally, just ajust mame.ini in that way:
#
# OSD ACCELERATED VIDEO OPTIONS
#
filter 0For your "Machine Options" issue, do you mean the "Configure Machine" from the main selection screen?
For the USB Joystick to be recognized, you first need to be in read/write mode (use the alias "rw" in an SSH session) when connecting it. This way, Linux will be able to write the values to the root filesystem persistently. Also make sure your joystick is supported natively by the Linux kernel (lsusb -t). Once recognized by the Linux kernel, you assign the joystick configuration file (mappings) in /data/ini/mame.ini:
#
# CORE INPUT OPTIONS
#
ctrlr <name-of-cfg-file-without-extension>The mapping file is ending with a .cfg extension and should be placed in "/data/ctrlr" folder.
I hope these answers helps you a bit!