@mitu thank you but it seems complicated for me....

@mitu Thanks for your reply.

@treysonik said in Trouble Updating Retropie on 3b+:

I’d like to let them know and possibly donate more if the problem gets solved. As I said before I don’t change any settings in the emulators themselves and the difference was night and day.

Make sure you use the latest RetroPie version and test again your N64 game(s), then open a separate topic and add the info from https://retropie.org.uk/forum/topic/3/read-this-first. A verbose log - as explained in the aforementioned topic - should be helpful - post it on pastebin.com and provide the link in your topic.

@y-ello said in How to add a GPIO button to a Retropie (Rpi 3B+) build?:

Can I use a GPIO wired push button for exit emulator? how?

Assuming you have a the button wired to a GPIO (there's tons of tutorials and documents on using a RPI with a button), you can use something like GPIONext to run a script whenever you press the button.
RetroArch has a network control interface, to which you can send commands from the script you attach to the button press (pause RA, open the menu, exit, etc.) - see more details here. Since most emulators in RetroPie are just libretro cores and run within RetroArch, it might be enough to cover most emulators, but you can also simulate a keyboard with GPIONext and simulate a key press for the button push (i.e. for opening the MAME menu).

The PS4 Dualshock controller should work without any additional driver installation - the ds4drv is an old and un-maintained driver and it shouldn't be used.
If you configured your controller in EmulationStation, you don't need to do any configuration in RetroArch. The configuration for RetroArch is automatically generated from EmulationStation - see https://retropie.org.uk/docs/Controller-Configuration/. You can check if your auto-configuration for RetroArch has been generated by looking into the \\retropie\configs\all\retroarch-joypads folder (over file shares). Do you have a .cfg file for your controller there ?

Aside, you should be using a proper power source for your Pi, a mobile phone charger is not enough for most cases, especially on a 3b+. Do you get the low voltage sign when you start a game ?

Get a verbose log and post it on pastebin.com, then provide the link. Looks like missing or misplaced BIOS file(s).

Not sure from where the lr-fba-neocd comes from, but RetroPie configures the FBNeo libretro core as lr-fbneo-neocd. Also note that FBNeo doesn't support CHD as format - see https://github.com/libretro/FBNeo/tree/master/src/burner/libretro#neogeo-cd-doesnt-work-why- for the supported formats.

Can you post a verbose log from running the emulator (on pastebin.com) ?

I'm glad to hear everything is working for you now!

@mitu got it, thank you! thumbsup

@dgar The link I posted for verbose log has instructions on how to enable it.

@CodeKing Try installing the desktop first - https://retropie.org.uk/docs/FAQ/#where-did-the-desktop-go - and then selecting the boot to desktop - https://retropie.org.uk/docs/FAQ/#how-do-i-boot-to-the-desktop-or-kodi.

Make sure you're package list fully updated first - run sudo apt update from a terminal or use the RetroPie-Setup update function to update the OS/packages.

i had something similar happen with my roku / TV .... LG pushed out some sortof update that didnt work well with roku.. i had to connect to another TV memorize the key strokes to set the resolution to a lower resolution. It worked fine after that ... dont know if i ever increased the resolution again.

Possibly adjust resolution lower and see if that resolves the problem.

Keyboard Defaults for Standalone Stella
F1 > Select Game
F2 > Reset/Start
F3 > Color TV
F4 > B&W TV
F5 > Left Diff A
F6 > Left Diff B
F7 >Right Diff A
F8 > Right Diff B
F9 > Save State
F10 > Change State
F11 > Load State
F12 > Save PNG
Escape > Quit Emulator
Backspace > Fry Cart
Pause > Pause Emulator

Welcome to this forum.

Try this: https://retropie.org.uk/forum/post/170381

I´m learning too to do some things, but Thank you anyway.

What is the better performance n64 emulator for pi3B+

@mitu OK

@deskjobo

@deskjobo said in SAVE STATE STUCK AT 0% ISSUSES:

@theotherdan Thank you so incredibly much for your response. I followed both sets of steps you gave, and my results are as follows:
After using df -h my available storage is shown to be 785M out of 3.3G size.
For the command ls -al /home/pi/RetroPie/roms/ all the emulators appear to have 'pi' in both the user and group, as well as all the correct modebits.

Is 785M enough of an available storage or could that be the cause of the problem?

ps. All my roms are stored in a usb drive instead of in the sd card with the image.

@deskjobo
785M will be 785 Megabytes, so a decent amount of space. For save states, I would say that space is not an issue..
Now, since you are not using the default location for saving, you will need to adjust the process a bit.
You can look at /opt/retropie/configs/all/retroarch.cfg by running 'cat /opt/retropie/configs/all/retroarch.cfg'. This file should show you where the save states and saves games are stored:

#Save all save files (*.srm) to this directory. This includes related files like .bsv, .rtc, .psrm, etc ...
#This will be overridden by explicit command line options.
savefile_directory = "/media/usb0/savefile" <--

#Save all save states (*.state) to this directory.
#This will be overridden by explicit command line options.
savestate_directory = "/media/usb0/savestate" <--

Based on the output, and where the USB device is loaded, you will have to append the command to meet it:

sudo chown -R pi:pi /media/usb0/<emulator>

Let me know how that turns out.

@mitu thanks a lot now works again😊😊😊

https://uploaddeimagens.com.br/imagens/03tjgKA
a piece of the conquest image is missing. The game is properly centered so I can't touch it.!