@retrotarta i made the same experience with screenscraper.
Usually he finds the metadata for a rom by the third to fith try.
I dont know why, maybe too much traffic for a small server?

Weeks later...

Since this "Game Focus Mode" feature was definitely not practical (the user has to press a key to use the keyboard, and then press a key again to access the shortcut to return to EmulationStation, it's a pain...), I found it much more useful to remove all the shortcuts that RetroArch assigned to the keyboard keys.

(Honestly, I wonder WHO thought it would be a good idea to use all the keys on a keyboard to provide shortcuts that nobody ever uses... when you're emulating a machine that needs a keyboard to work)

(especially when one of those shortcuts is used to display... a virtual keyboard).

So, I edited the /opt/retropie/configs/amstradcpc/retroarch.cfg file, and changed (or added) all the following 'input' lines to 'null':

input_exit_emulator = "nul" input_player1_l = "nul" input_player1_r = "nul" input_hold_slowmotion = "nul" input_rewind = "nul" input_cheat_index_minus = "nul" input_cheat_index_plus = "nul" input_cheat_toggle = "nul" input_netplay_game_watch = "nul" input_movie_record_toggle = "nul" input_pause_toggle = "nul" input_player1_y = "nul" input_player1_x = "nul" input_toggle_fullscreen = "nul" input_reset = "nul" input_frame_advance = "nul" input_hold_fast_forward = "nul" input_player1_start = "nul" input_player1_b = "nul" input_player1_a = "nul" input_shader_prev = "nul" input_shader_next = "nul" input_player1_select = "nul" input_toggle_fast_forward = "nul" input_player1_up = "nul" input_player1_left = "nul" input_player1_right = "nul" input_player1_down = "nul" input_volume_down = "nul" input_volume_up = "nul"

I'm now doing the same for all the other emulators that have the exact same problem (all the libretto cores that emulate a computer: lr-atari800, lr-bluemsx, lr-fuse, lr-theodore, lr-vice...)

If you're wanting exactly what is in that video you posted.

mGBA

In Options:

Be sure to select GBC and not auto detect for Gameboy titles.

Also have a gbc_bios.bin file correctly placed in the bios folder.

And don't skip the bios start up screen (Nintendo logo animation).

In Gambatte, change Emulated hardware to GBC.

If you don't want to use the line ssh pi@raspberrypi.local 'DISPLAY=:0 retropie' and still want to run my retropie script through SSH but NOT inside your established connection, then:

Do nano /usr/bin/retropie or nano /usr/bin/gamepad

And add this line below #!/bin/bash or wherever it works for you.

export DISPLAY=:0

Sometimes emulationstation crashes but I don't want to go that deep.

My job is completely done here. Have fun and stay safe.

@mitu Thanks...this just might work. I'll give it a go and let you know.

I appreciate the support.

Solved it.

For anybody wondering, you must delete the fle SDLPoP.ini
run prince to generate it again (rename to .ini)
uncomment the gamecontroller line
download the file https://github.com/gabomdq/SDL_GameControllerDB/blob/master/gamecontrollerdb.txt
into the same folder where prince is.

Voila'!

@luckyluca
Solved it.

For anybody wondering, you must delete the fle SDLPoP.ini
run prince to generate it again (rename to .ini)
uncomment the gamecontroller line
download the file https://github.com/gabomdq/SDL_GameControllerDB/blob/master/gamecontrollerdb.txt
into the same folder where prince is.

Voila'!

@goldmansex778 Sorry I know this thread is old but I was hoping you could help me. I'm just finishing up an image to release to the community but the only thing that is wrong is the volume is too loud on the splashscreen and it's distorting. I'm not an expert with Linux so if you could walk me through a possible solution I would really appreciate it. I tried adding the --vol -3000 to the omxplayer file but it won't allow me to save the changes. Any help would be appreciated. Thank you so much for your time!!! -Chuck

@dankcushions , @Romfrosk Thanks guys!))

@ciel Please provide details from your set-up and a log of the errors you are getting (See RetroPie-Setup/logs). Please put the logfile on a pastebin site rather than directly in the forum.

https://retropie.org.uk/forum/topic/3/read-this-first

@mitu Yep, cheat works in mame2003-plus (and you can make a savestate for each version to save future faffing). The one place I didn't think of looking, cheers :D

@mitu thankyou

@cir-engineering I’m using six axis and custom hid Sony. Not sure if I need both, but it’s working. I don’t have the ps3 driver installed. Anyway, I started my pi and synced my ps3 controller via Bluetooth as usual, no issue. Turned the controller off by holding down the ps button (important because it will stay as blutooth with charging only) and plugged the usb cable in and the buttons were all messed up. Reconfigured with the usb cable and it was now working fine with usb. Unplugged and Resynced to Bluetooth, and still had no issue.
Try configuring it with the usb cable, make sure the controller is off when you plug it in to be sure your in usb mode.

@mitu said in How shutdown Retropie in Kid-Mode ? (or is Kiosk mode needed for this) ?:

@purpledragon478 said in How shutdown Retropie in Kid-Mode ? (or is Kiosk mode needed for this) ?:

By default the start menu is disabled for the 'Kid' UI mode, but you can enable it. To do this, complete the following steps:
...

EmulationStation has now an option in the UI Settings menu to control whether to show the menu or not in the Kid mode, so there's no need to edit any configuration file. It's been added more than 1 year ago.

Oh sorry, I didn't realise that. I had experienced this problem with the start menu myself just recently, and tried looking for a solution online but to no avail (that's when I found this unanswered question). I hadn't even tried looking through the start menu for a solution tbh because I assumed that if I couldn't find a solution online, then it must just be impossible to access the start menu in the 'Kid' UI mode. So when I stumbled across this solution while just browsing through the RetroPie menu for any general useful settings, I was really excited, and thought I'd come back and answer this question in order to help anyone else who was also having difficulty with it.

I had planned to look through the start menu settings next to see if I could find anything useful there too, so I guess I should've held off on posting this answer until I had done that, since I would've discovered this more efficient solution then. Oh well, at least both these methods are available here online now for anyone who is still having difficulty with this (and who, like myself, hadn't bothered looking through the start menu for a solution). Plus I'm just glad to learn that there is this more user-friendly method of enabling the start menu in the 'Kid' UI mode.

So for anyone reading this who still wants to know how to do enable the start menu in 'Kid' mode, complete the following steps instead:

First make sure you're in the regular 'Full' UI mode Press the start button to bring up the start menu Click 'UI Settings' Scroll down to the option 'Disable Start Menu in Kid Mode' and set it to 'Off' Exit the start menu

Then you can enable the 'Kid' UI Mode and the start menu will be available. You don't have to first turn off the Raspberry Pi and then turn it back on again, like with the first method I posted.

@vic-viper-001 They should be updating again (I generated a new image earlier today also)

@dankcushions I have dreamcast/3do/ps1. god of war for example can improve dramatically when overclocking. although it missed the point of retro

@sirhenrythe5th Got it! So it does supported it just not my file names. I changed them from CD1 back to CHD works like a charm.

@sleve_mcdichael said in Is there a guide somewhere to create install scripts if you can get a game to compile?:

What is the significance of the CMakeLists.txt param in ...

The correct way to invoke cmake is

cmake <PARAMS> <path_to_folder_containing_CMakeLists.txt>`

... the && cd build part didn't do anything, so it tried to cmake & make from the wrong dir and, predictably, failed.

Don't use && then, just have the 2 commands separately.

.. this one just built it right there in the main tmp/build/module folder. Do I want to leave it in or out? Does it make a difference?

No, but some programs enforce a separate build folder (out-of-tree build) so you may get an error when building directly in the source folder.

Also, it still made the same file, but it put it in the wrong place. So if I were to use retropie_packages.sh <module> install after this, it would be installing the old one from the "build" dir and not the new one I just built in the wrong place, so this isn't a solution.

If you change the build parameters, then do a cleanup first.

I think I could begin the build function with a [[ -d build ]] && rm -rf build to remove the dir if it exists?

I don't think that when building with cmake this step is necessary, so that's why is not enforced. This is an issue only when repeatedly re-building without cleaning up, so it's more of an artifact of re-trying the build with a 'dirty' state.
You should first compile the program separately - not as a scriptmodule - to get the cmake build options right, then add it to the build function and try it from retropie_packages.sh.