EmulationStation uses libSDL's joystick subsystem to recognize and work with joystick devices, maybe your device is not detected by libSDL as a gamepad/joystick.
In addition to jstest/evtest, install jstest-sdl2 (from https://github.com/Grumbel/sdl-jstest) and see if your device is working with it.

Deleting that file is not advisable, since it contains more than your input configuration. Either restore it from a backup (there should be a es_input.cfg.bak you can use) or re-install the EmulationStation package.
Once you have the .cfg file recovered, re-configure your I-PAC2 in EmulationStation and the configuration for RetroArch and other emulators should be created.

Can your run

ls -la /opt/retropie/configs/all/retroarch-joypads/

and post the output ?

I would like to note that on another RPI 4 unit running 4.7.11 that the gamepad configurations do not save and when you exit a rom the controller is unresponsive.

This means the configuration of the gamepad is not saved in the EmulationStation's configuration file. Can you post the contents of $HOME/.emulationstation/es_input.cfg ?

@loonyboi Great to hear I could help someone. I consider myself an old noob.

@dsquared said in Can’t Save|Load Games Without Going Through Retroarch Menu:

Do you have any ideas where hotkey pairings are created (such as Select + X = retroarch menu which is working)?

Usually they are in autoconfig/<controller>.cfg i.e. Microsoft X-Box 360 pad.cfg.

@calcu10n said in One controller connected, ES says there are two:

@calcu10n said in One controller connected, ES says there are two:

@mitu said in One controller connected, ES says there are two:

The 2nd controller appears because of xboxdrv - make sure it's uninstalled.

I just verified again, it is uninstalled. I have rebooted the host and that sorted it out. thank you!

Hmm... well I sort of spoke too soon. Now the controller isn't working right. After rebooting I have re-mapped the controls again, but the buttons aren't functioning correctly. As an example: it's taking the trigger as the start button, even though I mapped the buttons correctly. I remapped again and it's still the same. Suggestions?

hmm. just reinstalled xpad from source again, remapped and it seems to be working now. all good. thanks again!

@19whity81

Regarding the button configuration, will I need to configure the buttons for each single game or each single emulator or this is just a onetime configuration and it will work for all?

are you following our documentation? this point is covered here: https://retropie.org.uk/docs/First-Installation/#configure-controllers

@fentimanj hi! Let's continue the discussion here as I just posted on Amiberry's github. First of all I need to ensure you've read the "main" thread about Amiga and Amiberry (here). Then I'd need more inputs about your setup. For instance, which Retropie version you're using, have you updated the OS packages and/or Amiberry, etc? A full description about your setup always help as said in that post ;-)

If you got Amiberry logo and WHDload Autobooter screens this is not good. Especially for a game like Lotus 2 which has been heavily tested. Therefore I suspect you either do not have the very latest version of the WHD package of that game (should be Lotus2_v1.11_0497.lha as of typing) or you renamed the file. If you did the latter please don't and leave the name as-is.

Without further details from your setup I can't help much. Just ensure to get the latest Amiberry binary from Retropie Setup (or compile from source), check the names of your packages/.lha files and also double-check the Kickstart ROMs you got. They must match those listed here.

@mitu This was the fix, thank you! I think this might have been a remnant of my original setup cause I was having some HDMI issues with a black screen initially.

For some reason this fix broke my audio, but I was able to get that working again after about 30 minutes of tinkering.

Thanks for the assist!

@jrmymllr I ran into this same issue today. There is a symlink in the ti99sim directory that is looking for a file TI-994A.ctg in the RetroPie/BIOS folder. Ensure the file is the exact same case and NOT in the TI99 folder within the BIOS folder.
Good luck!

@lolonois Good call. Now I know what the hotkeybtn is used for.

@fadangalini

Well that disabled the onboard, but still no audio...
I can only laugh at all the problems I keep getting!

@cnoto For the ONOFFSHIM I used the default setup, proposed by Pimoroni. For the complete powercut you either need a systemd file or you set a dtoverlay to /boot/config.txt

You can take a look here to this tutorial

This doesn't look like the default RetroPie image - can you add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first ?

@sleve_mcdichael
Thanks for your answer! I was trying to create the script and I couldn't cause I'm a newbie haha. But I figured out that I was using wifi + ethernet cable, I thought it could be the wifi connection, so I disconected it. After that I used the purge option and re-scrape again some platforms and it worked. Got almost every platform working, but I couldnt do it with nintendo 64, it just wont work. When I was scrapping, i got these error messages saying the servers were overloaded, but its okay for me.
Thank you again !

@hellothere don't want to leave this unanswered.

Prereq:
Have a USB drive or SSD with same or larger capacity than your SD card.
When using an SSD SATA to USB adapter make sure it is fully UASP to get max. transfer/access speed. Here are some hints [1] - also this site has more details as I do provide below.

It goes like this:

Make a full backup of your SD-card (eg. with Win32DiskImager (<- easiest), Clonezilla, ...) to your desktop PC. Put that backup at your USB drive / SSD (again using Win32Diskimager or the tool of your choice) on your desktop PC. Resize the USB partition (only if the USB drive is larger than SD card). Advise the pi to use a different partition after initial booting from /boot, handing over to the USB drive.

When you are done with the backup (Step 1 and 2 from above) attach both (SD card and USB drive) to the Rpi.
Remove any additional USB storage attached to the pi to avoid confusion.
Boot/Power up.
Nothing has changed up to this point.

Note: Following steps are the crucial part - but no worries you have a backup. If something derails, you can back out by using the backup.

Step 3: Optional: Resize the USB partition (if USB drive is larger than SD card).

SSH to your pi as user pi. Type

sudo su

Issue blkid /dev/sda*

blkid /dev/sda* /dev/sda: PTUUID="e006ca92-3704-44b9-a15f-bc56e2171825" PTTYPE="gpt" /dev/sda1: UUID="4832bb70-bb77-4a4a-9d68-5541559df133" TYPE="ext4" PARTUUID="9ec38a7c-ff79-413f-bddc-fc66de260c13"

Note the partition number /dev/sdN on the left which has the TYPE="ext4".

Run with that number resize2fs /dev/sdN (replace N with your number identified, most likely it will be 2).
Wait for process to finish.

Step 4: Advise the kernel to mount a different partition as "root-filesystem".

I underlined the items to REMOVE in RED and those to ADD in GREEN.

The red and green values are different on your machine. Use those. Not those from the example!

SSH to your pi as user pi. Type

sudo su

gets you root.

Issue blkid /dev/sda*
B1.jpg

Will give you a similar output as above.
Note down the value of PARTUUID of partition with TYPE="ext4" (in the example 9ec38a7c-ff79-413f-bddc-fc66de260c13). There should be only one with this type.

Edit fstab (with editor nano (<-- easiest) (or editor of your choice)):

mount /dev/sda1 /mnt # <-- this should be the same sdN as used in resize2fs, will mount the partition from the USB drive. nano /mnt/etc/fstab

You will find something like this:

B2a.jpg

These current PARTUUID point to partitions on your SD card.( You can verify it with blkid /dev/mmcblk0*)

The second entry has to be altered to contain the PARTUUID you noted down before. For example:

B2b.jpg

Again: Use your identified PARTUUID value.
You don't have to keep the lines starting with # (=comment)
Save the file.

Almost done: Then edit cmdline.txt, last step before rebooting:

nano /boot/cmdline.txt

You will find something like:

B3a.jpg

This instructs the kernel to look for the root filesystem at the partition PARTUUID, currently the SD card.

Make it read, change only the PARTUUID, leave everything else as is:

B3b.jpg

Save the file. Reboot... Drum roll, please!

After reboot, ssh to your pi, then check with mount command:

mount | grep sda

Should output something like:

/dev/sda1 on / type ext4 (rw,noatime)

That's it. Revel in your success.

[1] https://jamesachambers.com/raspberry-pi-4-usb-boot-config-guide-for-ssd-flash-drives/

@sleve_mcdichael said in Mame-libretro marquee issue:

Theme: "TMNTurtleGuy/ComicBook" (/etc/emulationstation/themes/ComicBook). Same issue in "Arcade" (arcade/theme.xml and mame-libretro/theme.xml are identical).

I think I found it. Edit your mame-libretro/theme.xml file with:

sudo nano /etc/emulationstation/themes/ComicBook/mame-libretro/theme.xml

Step 1, line 46:

<image name "classic_logo" extra "false">

Change "false" to "true".

Step 2: comment or remove the "marquee" section from lines 60-64. Comment html with <!-- and -->, as in:

<!-- <image name "md_marquee"> <pos>0.74 0.086</pos> <maxSize>0.26 0.1</maxSize> <origin>0.5 0.5</origin> </image> -->

With these two changes, save the file and restart EmulationStation; you should be all set!

arcade/theme.xml has a "marquee" section that genesis/theme.xml, for example, lacks. However, commenting out this section, while it did remove the marquee game logo, also removed the system logo from behind it.

In addition, line 46 is set differently between the two. Changing this from "false" to "true" restored the system logo.

Additional notes:

I think wheels and marquees are enabled by default, so you need to explicitly make them "false" (not just comment out the "true") in config.ini if you don't want to download them.

You have marquees disabled in the command-line options; however, while that game logo is called "marquee" by EmulationStation, it's the "wheel" art from the scraper that goes here. So if you wanted to disable these logos, you need to disable "wheels" in the scraper instead of "marquees." Then you'll need to purge your cache of the already-downloaded wheel arts.

Of course, this isn't necessary now that you know how to fix the theme, but just for general knowledge.

I appreciate you helping me understand the difference between the marquees and wheel arts. I did what you said there and it fixed it! Thank you!

I've updated my config.ini to not cache marquees and wheelarts for now. Thank you again!

@mitu
Wow !!! solved !!! Thanks , you have hit the bullseye !

@damoos You can override the controller order on a per-game basis, you'll need a separate .cfg file for the game where you can change the order of the controllers:

input_player1_joypad_index=1 input_player2_joypad_index=0

The above will switch the controller order, so 2nd controller gets to be Player1 and vice-versa. See here how that works.