You might not even have to do that, look up the max current draw of your drive. Mine was only 220mA. If USB protocols are being followed your USB current should be at least 500mA with no changes required.

@elbitxo our preference is to not support third party images in any capacity. please respect the rules of this forum going forward, and do not seek further support until you are running our image.

for the record, on standard retropie updating should not damage an existing theme, but as per https://retropie.org.uk/docs/Updating-RetroPie/, you must take a backup before updating.

With analog controller it works.
It is weird if i have a RETRO pie that i have to connect a PS4 controller...
There is more weird things, i have lots of advice for the programmers to make it more user friendly.

@ Daistaar : thanks, only way to complicated.
@ YFZdude thank you very much.

it does vt03 and vt09 support, which others don't do at all

@Jshhh Try using a RetroPie image and see if that works. If it does, the problem may be the kernel/firmware version in OSMC.

Thank you very much to you both sorted

@Rodc hi, to clarify i don't doubt there is a software issue running it in 2010 on ARM, rather than a retropie settings issue, and the log reflects that. i don't want to get involved in MAME development anymore but you could log the issue here: https://github.com/libretro/mame2010-libretro/issues

@mitu Thanks but it seems my issue fixed.
I just backup all my roms and bios and format the sd card and reinstall the latest retropie.

Thanks for helping me... This issue is solve by backing up my roms and bios and reinstall the latest retropie image.

I checked the resolution of my RetroPie and found it's already 1080p. So I did nothing to the configuration.

I updated RetroPie and the sound came back.

It's so weired. I still don't know where the problem was and how the problem was solved.

But I can play games with sound anyway.
@lostless @MegaTimX

@ShinxtheMorpeko I fixed the problem with not getting into RetroArch. I configured keyboard 2 but it still moved player 1 in Super Bomberman 2.

I'd advise you to use the official RetroPie image when installing RetroPie and not some 3rd party image.

@Bryan the guide is wrong as mentioned earlier in this discussion.

@jthomas5150 you should be using the default which is the neon renderer. what image are you running?

Hey Bam,

Did you ever get this working in the end? I have the exact same issue, same controller as yourself but running on a Pi4.

Wondering if it can be solved or if I should look at purchasing another controller.

Thanks!

@enira said in Final Fantasy Tactics PSX - Text issues:

I am one of the owners of a GPi Case. I got as base image Super Retropie Rev. E (found it working with the unit). The unit is based on a Raspberry Pi Zero.

We don't support 3rd party images, as outlined in https://retropie.org.uk/forum/topic/3/read-this-first.

As for your sound problem, which Pi do you have and which version of Retropie?

There's currently an issue after the Linux OS "Raspbian" which Retropie 4.6 is based on changed the mapping of audio devices in the system.

If you have RetroPie 4.6, you can try two workarounds until Emulation Station is updated, but it requires editing two configuration text files:

Edit the file /boot/cmdline.txt and add the following line to it: snd-bcm2835.enable_compat_alsa=1.

or

Choose RetroPie-Setup in Emulation Station, then audiosettings, and select "Headphone" as audio output. Edit the file /opt/retropie/configs/all/emulationstation/es_settings.cfg and change the "PCM" in the line <string name="AudioDevice" value="PCM" /> to "Headphone".

If neither of those work alone, try them together.

Samba is enabled by default in RetroPie and the shares are automatically created. Did you use the RetroPie image to install your system ?

@alanjds The original poster hasn't been active for 3 years and bumping 3 years old topic is not proper forum etiquette. I suggest you open a new topic if you have a specific support question - mentioning the info about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first. Thank you.

Should be fixed now, just update your RetroPie-Setu script and re-install (from source).