@herb_fargus Thanks herb!

No that I remember although it's an upgraded image as it use to be on 3.7.

Am I doomed? I was hoping not to have to build from scratch.

The lack of free GPU memory caused it. So either keep your split higher as you have done, or use a lighter theme like Carbon.

That would be sweet. One can hope.

Hiho,
So thanks to dankcushions advice i fixed this issue for the most part. However, i've discovered i now cant auto load states in the Prodrive(7800) core. It seems to be auto saving for the most part but i always get the Auto Load Failed dialogue when booting a rom back up. I have tried going via the RGUI and although the dialogue doesn't say failed in this case, it just seems to load in the usual boot up state. I have the auto load/save commands set up in the 7800 config. Again it was working before updating to 4.02. As ever, any help would be greatly appreciated.

Regards,
Grumbleduke.

I'm really pretty embarrassed right now, but it was because I only had my wireless keyboard plugged in and not any gamepads. Hooked my snes controller in and it booted right up. Thanks for your help and I hope this will help others who have this problem.

It was just that. I only had my wireless keyboard plugged in and it didn't recognize it as a game pad. Hooked up my snes pad and it booted right up. I had that realization in the middle of the night and then you confirmed my suspicions right before I got up and did it. Thanks man for everything.

@veteranj https://github.com/retropie/retropie-setup/wiki/runcommand#configuring-runcommand

@TheStrayMongrel I could help me with the same problem so that with the PSP emulator
/opt/retropie/supplementary/runcommand/runcommand.sh
args 0 SYS psp "[romfilename]"
does not work..

@Cole_48 no problem.

@Concat said in Run Command:

I didn't realize runcommand requires a specific naming convention

I think this convention was made to match the scraper one.

@Lyle_JP , Thanks for the reply!
I'll have to wait until tonight to check it out.

The TV is in fact 1360x768. But I believe I tried group=2, mode=39 last night , after checking some of the resolution modes on Pi's website. I don't believe I tried as high as 81 , though. I'll check it out this evening.

At this point you really need to start using the search feature. These questions are very basic setup ones.

Last freebie: Use TAB key to access Mame controller configuration. Yes, you should have a keyboard handy when configuring Mame.

@battlecat said in Config file creation:

Does this mean that if I need to reset the retroarch.cfg it too will reset to defaults if I remove it?

Your original post is about ...configs/all/retroarch.cfg. If you delete it, RetroArch won't create a new one for you.

If you don't believe me, you can test it and see. :D Rename retroarch.cfg to a different name and execute the emulator you want. Then look at your ...configs/all/ directory to see if there's a new retroarch.cfg there.

Be aware that if you delete/rename the retroarch.cfg, the RetroArch will use its own defaults (what is default in its source code), but not the RetroPie defaults. Do you get what I mean?

When you reinstall RetroArch, like I suggested in my first response, you get a brand new retroarch.cfg with some presets made for RetroPie using.

ooohkay, I have no idea what that non-stop stuttering noise is. It's not the flipper sound, that's for sure.

So I was able to get my buddies RPi3 running RetroPie 4.0.2 this weekend, and after configuring one PS3 gamepad on the RPi, plugging in the second PS3 via USB worked flawlessly! All the issues I read about must have been regarding older distro versions of RetroPie. I was also able to get both gamepads working on the onboard Bluetooth of the RPi3! Thank you for the help @obsidianspider and @Lyle_JP!

@Pirate

Ditto I have this when using a USB DAC, all other emulators are ok but no audio on any N64 ROM