@BeanFT And... Drastic has an interface that is lagging one frame, which means that the “real” selected menu item isn’t what is shown on the screen. It’s the previous item that is shown. You’ll figure it out when you’re there.
@mitu thank you for helping, the raspberry pi is a 3B+ made to look like a gameboy so it hasn’t a screen of its own connected to the raspberry pi inside a gameboy shell. The screen is black (but there is an indication that it is on since the blackness glows when in darkness) and when I turn on the console, the introduction plays without the screen - I can hear the PlayStation intro sound that it makes - and then it stops and the 4 blinks occur. I haven’t modified the console at all and it was working perfectly for the past 4 months. It did do this thing where it would start to glitch and freeze or the console would completely shut off, but I could always just turn it back on and it would start up again. However, I was playing it and what happened was the console just fell slightly onto a pillow then the screen went black but the sound still played. Now when I turn it on, the screen stays black, the intro plays, and then it stops running. Does retropi or emulation station stop running (does it shut off) if there is no hdmi output? I’m thinking maybe the screen got bumped out of place, but it doesn’t explain why the sd card stops running or that when I click a button, the games don’t start and make noise at least.
@mitu So, you can't move the ini file into retropie. But are there .ini files in the retropie version of mame that I can fiddle with ?
I'm not sure at which version MAME started using .ini files for settings, but for instance MAME2003 (based on Mame 0.78) uses .cfg files to store the settings. I'm not sure if any other MAME emulator used in RetroPie accepts .ini files for configuration - take a look at the available versions here.
yeah i had a dreamcast backup game image with the dreamcast bios on a usb stick, just like the guide told me to, then i put it in the pi, but reicast didn't show up. then i look at the guide and it says to install the emulator you want using the package manager and whatnot. so i guess that's what happened.
AWESOME!!! Just testing it out, when I went into RetroPi configure controller it recognized it as 2 gamepads right away, configured each and was instantly playing some Street Fighter Alpha 3 with my 5 year old. I works great! Thanks for the help, should have notice my mistake, the devil is in the details as they say. I read so much I have developed a tendency to be lays and just speed read without even realizing I'm doing it. I my brain just saw 'add to it's own line' for some reason. Anyways the device should be included by default and hopefully this will be fixed in a new version so folks don't have mess with it manually. Guess my wiring job was spot on, I don't have any issues now. Thanks again.
@mitu I did find the menu, but I couldn't find any option to scale it down. Full screen is not even ticked, but it's still going full screen. Couldn't find anything about custom resolution or anything.
Edit:// I've finally found it. It's in the Display Layout editor, which doesn't want to accept directional input properly.
Runcommand also prepares the console like hiding the cursor and even can display a splash screen art if configured. This is the way EmulationStation launches games and you also get the benefit of error messages being logged to /dev/shm/runcommand.log for debugging.
If you want to change the boot screen and tune or enable splash video, edit the file:
sudo nano /etc/init.d/asplashscreen (in plain terminal) OR
sudo pluma /etc/init.d/asplashscreen (in Desktop mode terminal)
comment/uncomment lines in do_start function (remove or add #)"
Worked like a charm. Hopefully this might help anyone who runs into the same issue.