@hawkes_84 It comes with more experience in config files to recognise or guess the different comment characters as well as section titles in square brackets. 🤓

I just stumbled upon this post...is this about getting 5200(and 800) carts to auto-launch? I am getting ready to build out an 800 and 5200 section on my build. I started with the 5200 and I spent the better part of this afternoon trying to work through the RetroPie documentation of loading carts, extracting, saving, etc. and I only got three to autoload so far...

Though in fairness, it was a busy day for me building JavaScript rules for online ordering templates for some of our customers, lol....among other things...

The mame cores I have installed are:
a) lr-mame2000
b) lr-mame2003
c) lr-mame2010
d) advmame
e) mame4all

Most of the arcade game mappings in the emulators.cfg file point to either lr-mame2003 or lr-mame2010.

The contents of the retroarch.cfg file in /opt/retropie/configs/mame-libretro/ is as follows:

input_overlay = "/opt/retropie/configs/all/retroarch/overlay/MAME-Horizontal.cfg" input_overlay_opacity = "1.000000" input_remapping_directory = "/opt/retropie/configs/mame-libretro/" # include "/opt/retropie/configs/all/retroarch.cfg"

So I don't see anything here that should override the global controller settings.

The runcommand.cfg file located on /opt/retropie/configs/all/ does not contain any code for the "launch menu joystick control" function right now - it does have:

disable_joystick = "0" disable_menu = "0"

...plus three other lines of code for use_art, governor, and image_delay.

I have tested the controller on the following console menus (accessed via the retropie configuration menu, from the screen where you would otherwise select a console & game):
a) Configuration Editor
b) ES Themes
c) Raspi-Config
d) Retropie Setup
...essentially every one I have tried that takes me to one of those blue menu screens the controller has not worked on.

The controller also does not work on the "File Manager" page (which appears to be a different type of interface than the other console menu pages - but I assume is still in LINUX space).

The controller does work on the Retroarch GUI when I launch it from this Retropie menu (just as it works when I am able to access RGUI from other emulators where the hotkey functionality is intact).

Thanks

Looking at the dpkg output, looks like you have the latest versions for the Bluetooth related packages - so no issue here.

@mitu I just figured it out moments ago after a lot of testing this morning. I have a third party music player that fades the volume before starting a game. I think what happens is it fades the system volume to fade the music before starting emulation. Then, when returning to ES, the System Volume remains what it was faded to prior to emulating the game.

This can be marked as resolved. I'll report this bug to the creator of the music player. Thank you!

@jamesvvic said in Could not initialize OpenGL /GLES library....:

Found this online, maybe this will help?

I doubt it.

ok, thanks for your help and patience responding to my questions

I've ordered a cable to physically connect my speaker to the PI and will use that for sound in the future.

@crafunzio Sorry, I dont think i have a hdmi to rf modulator. Mines a rca / av to coax. I used the pi`s 3.5 jack with a AV cable into the modulator. But you'll find hdmi to coax RF modulators on ebay / aliexpress etc for ca 10 bucks.

(But i would def recommend paying a bit extra for a pi2scart or similar if you have a european / scart crt set.)

@dankcushions

Yes. Got it. Well, it is what it is I guess.

My problem with other games turned out to be because I did not switch from Analog to Standard. Once I switched to standard all buttons started to work except for the L2 and R2 of course. Some games are playable this way.

Thank you @mitu!

It's working for me now as well, thank you.

@mitu I am not in front of my computer right now but inside my patch folder their are two lua scripts. T edition is now maintained someone else so maybe that is why your not familiar with them. One adds the toggle menu for sprint in the options and a bunch of other small quality of life changes and their is a pause menu script as well. On the bright side of things I was able to msu patch Ff6 and that took care of all my music issues.

@adamg thanks for sharing this. I just updated to Buster and my old fix for mapping the generic n64 didn't work. Mapping a hotkey for the menu did the trick. Weird though, I only had to map my A and Z buttons, everything worked fine.

@mitu

After some testing it disconnects when have rumble enabled. Without rumble no problem at all. It only does that when in use. The problem starts when it have rumble enabled.

I have notice this also. When in dualschock mode on retroarch it disconnects far more times per minute from when having on standard mode which seems to be working with less rumble effect( probably one motor is working not both like on dualshock)

Regards.