I am having the exact same issue with my Kintaro Kuma 9000. I'm using a retropie image that I downloaded from arcade punks. I had originally used another image which did not have these power issues and booted up fine with the power buttons and showed the red LED light. But then I switched to another image and now have this exact same problem. It starts up and then right when the splash screen ends, it shuts down. Did you ever get a fix for this issue?

@dugo3number2 You're replying to a 2 year old post with advice that doesn't apply to the topic at hand.

deleting the subfolder's (emulator) retroarch.cfg files made it work again on any emulator that had trouble finding my ontroller. on first start it recreated retroarch.cfg from the retroarch-folder. seems to be default setting.

@mitu said in NeoGeo not RUN lr-fbneo and any emulators:

have that BIOS file

Yes. Old bios not work. My friend resent me bios and him work. Thank you. IDK why old bios not work.

@Efriim said in PS3 Controller RP3+ issue:

sudo rpi-update

ok so I didnt have time to mess with this for a couple days but I started this morning by simply typing in sudo rpi-update and rebooting. bluetooth worked perfectly again on PS3 controller. Thanks for your help. If anyone else has this issue I would do this first and pardon the ignorance if this was obvious.

Mystic Mine is a Python game included in RetroPie. You can find it in the Experimental packages. I strongly recommend you to study how this game is programmed as it runs very well on the Raspberry Pi.

The scriptmodule that installs and configures this game in RetroPie is here: https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/ports/mysticmine.sh

it depends on the shaders you are using now. for example, assuming you use 240p with your new CRT, a scanline shader would be pointless because a) 240p already shows scanlines on a CRT and b) 240p is not enough vertical resolution to allow fake scanlines to be rendered.

shaders that adjust the colour or fidelity of the image may or may not be useful or provide the desired effect, depending on what they are doing and how you are connected to your CRT.

@PCKid The .cfg files don't go in the ROM folders. Remove the /home/pi/.atari800.cfg file, make sure you've copied the right BIOS files and then start a game.

@swimdad84 it looks like it. You can also plug your phone into that dongle too to test it I suppose or just plug the pi into it.

@mitu yes I pay $5 per month.

I will validate with checksums to see if anything stands out. I will give some examples of roms later on.

@chris_db said in Retropie + Raspberry PI 3A+ = KO:

Can you point me to a working image for the 3A+?

There isn't other image - if the weekly snapshot images are not working for you, then try the official Raspbian Lite image and install RetroPie manually - https://retropie.org.uk/docs/Manual-Installation/. Does the official Raspbian image works on your 3A+ ?

https://retropie.org.uk/forum/topic/22564/favorites-in-kiosk-mode-are-not-working

has the context.

@Lugzyboy82 said in Problems getting pi 3+ to load front end:

Please keep in mind that it onlu successfully scraped 50 out of 800 snes titles.

In this case please open a topic with details if you want to find out why. Include the information asked in https://retropie.org.uk/forum/topic/3/read-this-first and give a few example ROMs that are not successfully scraped.

@Efriim well thec64 mini doesnt even have a boot folder or 99.9% of linux in it. They made that thing absolutely bare bones as possible. I did discover that the ppsspp emulator on the pi uses a gamecontrollerdb.txt. I added theMayflash adapter to the gamescontrollerdb.txt and then tested in the emulator and the hats work fine. So i am not sure what the c64 mini’s problem is. I do however have a raphnet chip for wii classic controllers that i can solder up the wires to tomorrow to see if that one is working.

@quicksilver
'lr-mupen64plus-next'
Think i got it work not sure maybe it will got stuck again ..
update all from source think it helped .
and played again for half an hour nothing happend ...

@Felixoid said in Cannot configure 8BitDo M30 controller shoulder buttons:

@psyke83
Hello. I've built a binary from the master, but the shoulders still don't work on the M30 pad. Could you tell if they already should work?

It should work on the latest dev branch, yes. Is your controller definitely using axes 2 & 5 for triggers (considering differences in firmware/pairing mode)?

Note that the axis filtering is done only when defining the trigger buttons, so if you're doing non-standard mapping to buttons other than the triggers, it won't work.

@mitu so far I've changed every setting I can find to fix this but it's either fully stretched or displays in the far right bottom corner with most of the screen cut off including the retroarch menu
I gave up editing config files manually and just adjusted the screen from within retroarch gui, it ended up being an odd size resolution tho

@simongeoghegan
As long as you take a backup of the .srm you needn't worry about anything.
The network share is the easiest and it only shares user data folders for retropie like: roms bios and configs.

The folder will be displayed like a windows directory in explorer, the local network doesn't need any configuration, it could be either through a router or directly connected through the ethernet.

Okay,

I think I found the solution. There were a couple of roms without "[!]" in the name. Because I was trying anything I could think of, I deleted those files and now everything is fine. Emulation shows every N64 rom now.
Sorry for asking your help. Thank you for thinking with me for finding a solution.

Best regard to all of you!