I see, we'll I think I may try it out again when I get home but can anyone here give me a tip incase it goes wrong like it decides to not wanna update and just hang there.

@7asman i think retropie image is under maintenance

@s1naloa10 without more info about your setup we would need to be psychics to help you. There is a read this first link at the top of the page that tells you the info we need to help you

@TMNTturtlguy yup. But if i need a bulk set of games that use the same core options or same retroarch.cfg options, i have their individual configs pointing to a different core-options or retroarch.cfg file that i created. So for example psx games that use analog option, i would point their individual config to a different core-options config that i created just for psx that has the analog enabled. That way if the core options ever have any changes made, i dont have to change each config, just the one.

@edmaul69

Nice. That's a great middle ground solution.

Thank you very much. I will try now.

@Mu0n

There are some annoyances from xboxdrv: it can detect the L2 and R2 triggers as ABS stuff, but jzintv refuses to detect it, since it'd want a button behavior there instead. This severely reduces the amount of maps I can do.

You can convert your controller's analog trigger input to digital by adding:

--trigger-as-button

to your xboxdrv command. It's detailed more thouroughly in the guide here.

@BuZz said in Kodi 17.3 Crashes when detecting x265 files:

@maxbeanz they do the same thing. You must have chosen not to update system packages.

I have updated my 4.x Retropie image at least twice since installing. I chose 'Update All Installed packages' and when it asked if I also want to update the dependencies etc. I chose yes. I never saw it say anything about upgrading Raspian Kernal during the process. Since Kodi 17 it's never been able to play x265 files until I chose 'Raspian Tools / Upgrade Raspian Packages'. Maybe the script isn't fully working ? Can @Rascas confirm this ? Anyway, Kodi can play the files now.

@N-Game-Arts said in Retropie won't boot up anymore after installing Shutdown script:

I've done all the updates a few days back (how to tell what update version, I haven't clue

When you run retropie_setup, take a look at the top of that dialog box, as in the example below:
rpsetup

@TMNTturtlguy Well thankfully it was okay, my only irrational is that the mirror I use does go down sometimes, anyway I can check my mirror status or change my mirror in ssh?

@s1naloa10 that answer is incorrect. It is very unlikely you need bios files for your Mame roms rather you need the correct romset. This is all very clearly detailed in the documentation.

I suggest you give the docs a read and you'll find your questions will be answered.

Any luck? Also, (I'm new to RetroPie) what are the steps you took to get the cocktail shader? I've been looking around, but have yet to figure out how to find it, let alone get it running. Help?

@edmaul69 Tried it (I updated retroarch and all the other cores), and now it magically works! Thanks a bunch, edmaul :)

@paulo Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@creol123

FWIW, I was able to get my Matricom XYBA gamepads working, but only after switching to a fresh RetroPie install. I tried every suggestion I could find, and gave up after a couple hours of effort. I got to the point where the controllers worked in Emulation Station, but not with any of the ROMs. In my case, I believe the issue was that I had previously enabled the PS3 drivers, and that somehow affected the configuration such that the ROMs wouldn't recognize the Matricom gamepads.