@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.

@buzz okay thanks

@lister-of-smeg
mmmmmmmm... otherwise i thinks this github it's not updated.

Infact i can read it's theme 4.0 instead on github it's write 1.7

I'm not sure it's the same theme......

@pietdummie quick menu > controls > port 2 controls > mapped port:1 should map the gamepad in port 2 to port 1, so that either one will work. (I don't know what happens when you press "start" on P2, though. Does it work as 2P start, or does it read as P1 input and just start 1P? You'll have to test...)

@theawfulone in-game, open the RGUI (RetroArch Graphical User Interface) with default Select + X ("north" face button). From there, navigate to quick menu (this should be where you start already) then to controls >> port 1 controls. Set up the buttons how you like, and then go back to the controls menu (one level up from port {n} controls) and "save core remap file."

Do this once each for GB and GBA. Saving it as a "core" remap file will apply the changes to every title on that system. You can also set overrides that will apply on a per-game basis (and override the core setting) by saving a "game remap file" instead. "Content directory remap" isn't very useful, in most situations, since the configs are already separated out by system anyway so they will already only apply to a single content directory, even using the core remap.

This means that even if you use the same lr-gambatte emulator core for GB and GBC games, you still have to remap them separately (unless, you put them all in the GB folder, which you can do with a simple edit to your custom es_systems.cfg file.

@mitu said in Getting picture when 2 screens are connected. 7" screen and 27"monitor:

I've tried swapping the cables, and it worked from the first try.

I now have picture on the 7" screen, which is now connected to hdmi1 and when I connect the 27" monitor to hdmi0, I get picture on the monitor. The 7" screen then displays a rainbow color screen and then goes blank.

The 7" screen only displays the launching screen, when I play a game.

I immediately tried an arcade game, the launching screen displayed, but then went back to the main menu.
I've tried other consoles, they all seem to work.

I've tried 2 other arcade games, which seems to work.

Coincidence or not, the game I tried first has a bezel overlay.
Maybe the monitor can't handle that for some reason ?

I will disable the bezel and see if it runs then.

@jamrom2 To summon it all ... build your own image, back it up, and develop it further and further ....

Sorry to bring up an old post like this, but to complement the solution above, you can set your system to look up for both systems (CD and not CD) but not others in es_systems.cfg : <platform>pcengine pcenginecd</platform>.
I found that from source code but in no documentation, so there is no guaranty it will keep working in case of future code change.

@kinget
i would recommend these folders:

/home/pi/RetroPie/roms
/home/pi/RetroPie/BIOS
/home/pi/.emulationstation/downloaded_images
/home/pi/RetroPie/splashscreens

All your save-files and highscores are included in the "rom"-folders.

Optional: Arcade-samples and -artwork-files, if saved in a different location, and the "gamelist.xml".

All these files are independent of the used OS/Retropie-Version and worth backuping ;)

@refazeshot1 yeah, the default in retropie was recently changed to alsa_thread for pi4, which should give a same/better improvement. however it needs latest retroarch to automatically apply, and an unchanged config file(s).

@whereismax123 If i recall correctly you have to shoot at the bottom of the screen, which is a bit problematic, cause you cant aim too far down and not 1 pixel higher.
It would have been so much better if you could bind a button to shoot offscreen.

The games is available as a Debian package - https://packages.debian.org/buster/lbreakout2. Just install the desktop and the package, then launch it from the menu.

@mitu

Thank you - that did the trick.+