Yup, that "Finish him" bug in mk.zip is a pain. It replaces all phrases with "Finish him"and makes the game feel like a bad hack.

I don't recall that being present in previous versions of the core.

@michael40475 said in Audio not working? How to fix problem??:

can I please get very detailed advice on how to fix this issue? Thanks so much in advance.

Not unless you provide very detailed descriptions of your entire setup. That only makes sense, right?

@tomume https://retropie.org.uk/docs/First-Installation/#installing-additional-emulators - choose to install the emulators for MSX - lr-bluemsx. Then restart ES and see if your ROMs (and the MSX folder) appear.
Check the file extension and make sure you use lowecase for the ROMs.

Ok. Thanks for the answers @BuZz and @mitu

@thebear123 Yes. It very much matters in MAME. The emulator is looking for a specific ROM name as MAME ROMs have a standard naming convention.

@ben-almonte Update to retropie 4.3. Reconfigure your controller. The last button to configure is the hotkey, so you can assign that to something other than select.

I found a workaround:

I added a .scm-File to the root aof the scummvm-games-folder.

For atlantis i have the atlantis.scummvm-file insidde the atlantis-folder and a atlantis.scm-file outside that folder.

In es_systems.cfg i changed the command:

<command>RetroArch\retroarch.exe -f -L "RetroArch\cores\scummvm_libretro.dll" "PATHTORETROGAMES\retro\ScummVM\games%BASENAME%%BASENAME%.scummvm"</command>

and changed the extension to scm.
<extension>.scm</extension>

This means EmulationStation sees the .scm-file as the rom and adds it to the gamelist without annoying subfolders.
When starting the rom, wo don't care about the fake .scm-file. We grab only the basename and assume there is a folder with the same basename with the scummvm-file inside it.

@herb_fargus Alright thanks.

Hi! Where you able to fix this? Im having the same problem here.. Does anyone have a solution?

@vladquebec If you cannot flash imgs to sd card, your sd card is dead. I have one that went dead and partitions/files cannot be changed anymore.

running

from a terminal is a good way to graphically browse/track down where the files might be

@solaris

No problem. I had the same experience in which everything seemed stable except N64 emulation. I guess it pushes the Pi harder than any of the other emulators.

Try to overclock only the GPU, or choose a more conservative overclock value. Also, be sure to try different N64 cores (and experiment with each of the N64's core settings) or the standalone mupen64plus emulator.

@horaceandspider

Thanks - The other thing that I have been testing is the abilty to swap the A & B buttons, as outlined in you replay below. I can't get this to work. Here is my .uae for Turrican II which section would I need to edit to swap these buttons around?

https://pastebin.com/nQsw61K4

@horaceandspider said in Amiberry & Ipac:

@tuki_cat Yes, it is meant to be that way.

Using the ReroArch layouts which are documented in RetroPie, B is the “bottom” button (Cross for a PS pad) ... which I would call “South”

On the Amiga Cd32 pad, this is always “Red” aka Fire and the East/Circle (Retroarch A) button is always Blue.

It therefore retains this layout position when using the normal Amiga joystick layout.

At the moment, I have “locked” the keyboard control this same way around.

You can read your controller layout in Amiberry from a seperate location, and manually chose to change the two around, if you prefer, and I will probably need to make the same allowance for keyboard mapping :)

@bosco As has been said by others, third party images are not supported here.
However, I would say the reason is that N64 is running on standalone mupen64plus and not the lr- libretro / RetroArch core.
Standalone mupen64plus does not support bezels / overlays.

Edited to add: This is the problem with using someone else's set-up. You have no idea how it was set up or how it is configured and when you run into issues you have no idea why or even where to start to fix the problem (Or non-problem in this case).

@ironj679 Look in /boot/config.txtChange your overscan setting from 1 to 0 or the other way around. This just depends on your monitor.
If it still off there are 4 individual overscan settings for each side of the screen. Have a play about with these. Remove the # before to activate. After any change you will need to reboot to invoke the changes made.