well configs under might work if the entry didn't exist in the global retroarch.cfg, but you could run into trouble. I don't think the order is relevant to the problem - we are debugging in the other thread.

Perhaps, if possible, allow the amount of ticks/time required to activate the system menu to be changeable or allowed to be tweaked. Currently, the time to activate the system menu is relatively short. If I could make it longer, then all will be good.

So i cant remember if the audio had static before but before trying linapple today i went into audio settings and chose "restore to defaults" even though i have never been in the audio settings before. So now there is no loud audio with the audio mixer screen flickering every few seconds. So that may have been how i fixed it. Not sure where the screen it flickers is from but i am curious.

You may not want our xpad, as it may cause problems with Kodi on OSMC or other issues. We have some support for OSMC but I don't think I can help get xpad working if they are managing their own kernels that won't work with dkms.

The code is here

https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/supplementary/xpad.sh

It's this driver we are building - which contains newer xpad code than is in the currentl Raspbian 4.4 kernel - https://github.com/paroj/xpad.git

However due to problems with ES and the triggers, I have patched it so the triggers are forced to act as buttons (can be switched off via module param).

@Rural said in RetroPie binary issues:

@BuZz Fair enough, but under 4.0, I'm also not seeing any of the emulators that are visible on a virgin 3.8 install. In particular, Ports' absence was wined about by my main users. Is that an intentional change? With the exception of Ports, I like it.

When I find/buy another microSD card, I'll try making some .cue files.

Yes. A smaller selection of stuff is added by default, since it is now easy to add and remove individual packages. This keeps the image size down, and allows more flexibility - there were a lot of complaints in the past that we shipped with things people didn't want.

Thanks Herb. I think the Dreamcast strangeness was carried over from 3.8 and I only just noticed it later. Seemed to have swapped player 1 to player 2 joypad, but I've fixed that after some head-scratching.

Will try 4.0 when I get some spare time. Cheers anyway.

Phew!
phew

Can you post your controller file on pastebin, it should be in
/opt/retropie/configs/all/retroarch-configs/

Please also include this info here:
https://retropie.org.uk/forum/topic/3/read-this-first

@nemo93 because it is not "active" until buttons are pressed I guess. Not much we can do about that really.

@Drakaen391 you can use markdown to format your posts (code blocks etc)

@Sinkyboy2000 i found a fix. make sure your bios is all caps

https://retropie.org.uk/forum/topic/3483/i-found-a-cause-and-a-fix-bandaid-for-psx-no-bios-no-controller-issue

I updated to 4.0.1 today and i too get bios not found and controller not configured. The controller problem is because it keeps overwriting the /opt/retropie/config/psx/retroarch.cfg file. I put the old lr-pcsx-rearmed on and it still does all the same problems. :(

@Jeromy

Guide you should have used: https://github.com/retropie/retropie-setup/wiki/Game-Boy-Advance

@Necrobot20XX said in Not very user friendly.:

I am an above average computer user and have been using emulators for years.

This is hard to believe as I know there isn't a single emulator that would work for all systems RetroPie has or even half of it...

Also Above average Computer user would know the difference between a console and computer board...

Something very odd went on, not sure what (tried different power up modes, different boot modes, just wouldnt take the input from SFC30).
Just wrote RetroPie 4 final to a card. Chose basic install.

Added controller with hack off, added udev rule, left the boot mode where it was, didnt choose "boot" or "background".
Turned controller off after it registered and connected.
Rebooted.
Waited until fully in ES, turned SFC30 on, connected automatically.
ES happily saw its inputs - wrote the correct values. All power ons were with Start+R here.

All good! :)

Now just trying to work out how I managed to get ES to not see inputs from a SFC30 but see the FC30 Pro....

thanks nicapi, I had already updated my packages so I just went into option 1, '1 select default emulator for dreamcast (reicast)' and the option for oss-audio was there.

@BuZz
Thanks. Once I get home I will try this.