NOTES ON FIXING THE 13 JAN 2024 USB-DVG BUILD FOR RASPBERRY PI 5:
Here's what I did to fully enable (AFAICT) this image for my build. YMMV, but this works for me. Unless otherwise noted, these are all changes to the /home/pi/.advance/advmame.rc file.
NOTE: {Characters in these brackets indicate the prior settings to be changed}
CONTROLS:
To enable multiple keyboards/keyboard emulators and mouse/spinner/dial/trackballs:
device_mouse {auto} raw
device_keyboard {auto} raw
device_raw_mousedev[0] {auto} /dev/input/mouse0
device_raw_mousedev[1] {auto} /dev/input/mouse1
device_raw_mousedev[2] {auto} /dev/input/mouse2
device_raw_mousedev[3] {auto} /dev/input/mouse3
device_raw_mousetype[0] {pnp} ps2
device_raw_mousetype[1] {pnp} ps2
device_raw_mousetype[2] {pnp} ps2
device_raw_mousetype[3] {pnp} ps2
input_map[p1_dialx] {auto} mouse[0,x] mouse[1,x] mouse[2,x] mouse[3,x]
input_map[p1_dialy] {auto} mouse[0,y] mouse[1,y] mouse[2,y] mouse[3,y]
input_map[p1_mousex] {auto} mouse[0,x] mouse[1,x] mouse[2,x] mouse[3,x]
input_map[p1_mousey] {auto} mouse[0,y] mouse[1,y] mouse[2,y] mouse[3,y]
input_map[p1_paddlex] {auto} mouse[0,x] mouse[1,x] mouse[2,x] mouse[3,x]
input_map[p1_paddley] {auto} mouse[0,y] mouse[1,y] mouse[2,y] mouse[3,y]
input_map[p1_trackballx] {auto} mouse[0,x] mouse[1,x] mouse[2,x] mouse[3,x]
input_map[p1_trackbally] {auto} mouse[0,y] mouse[1,y] mouse[2,y] mouse[3,y]
You can also make these input_map changes for p2, p3, etc. if you need/want to.
DISPLAYS--ENABLE MAME TAB MENU ON NON-VECTOR SECOND SCREEN:
device_video {none} auto
AUDIO (better performance in Star Wars, TESB and Major Havoc-The Promised End):
debug_rawsound {no} yes
sync_resample {auto} emulation
sound_samplerate {44100} 22050
To enable sound for Armor Attack, Barrier, Eliminator, Rip Off, Solar Quest and Space Wars, add the MAME samples for those games (easily available) to the /usr/local/share/advance/sample directory.
VECTREX:
Copy the content of the vectrex roms folder in the Pi 4 build to /usr/local/share/advance/image/vectrex/.
Add the following lines to the end of the /home/pi/.advance/advmess.rc file:
vector_aux_renderer dvg
vector_aux_renderer_dual_display no
vector_aux_renderer_port /dev/ttyACM0
display_adjust generate_yclock
device_video_format 30000 0.872727 0.04 0.02 0.0672727 0.96 0.00355556 0.00444444 0.032
device_video_clock 4-170 / 30-80 / 50-60
misc_quiet yes
You'll need to delete any duplicates of these commands (i.e. misc_quiet) that were previously in the file before MESS will launch; if you have a second monitor connected the CLI will tell you which lines have duplicates when you try to launch a Vectrex game.
MISC:
Any MAME control configuration changes you've made (i.e., dial sensitivity, button changes) will be stacked up at the end of the /usr/local/share/advance/advmame.rc file. If you do a clean reload of the Pi 5 image, you'll want to save that text first and add it back in for the new build (unless you just want to redo those settings manually). Fair warning: you'll need to be root to change that file for the Pi 5 (I have no idea why it's set up that way), so proceed with caution.
Working /home/pi/.advance/*.rc files (USE AT YOUR OWN RISK):
mega.nz
