Hello Marky,

thanks a lot for your support! I'll search for the thread you point me...

Best Regards Giampaolo

@Dochartaigh disconnect your Xbox controller and you'll see it doesn't crash. Either you have to manually sort your configs or wait til kodi 17 is included as it doesn't have the janky controller issues.

No, I just meant I haven't tried to tackle setting it up yet. I will definitely open a new thread if I have issues. :) Thanks again!

@gioelem3 It was the newest version. 4.1 I think.

Did you ever figure out how to do this? I'm interested in the same thing - controlling screen brightness via retropie or some raspian command. Thanks!

I resolved the issue by doing the following:

RetroPie -> RetroArch -> Settings -> Input -> Input Hotkey Binds

Then I bound "enable hotkeys" to the Logitech button and "quit retroarch" to the start button.

Make sure to save your configs before exiting retroarch. After that everything works.

@Lyle_JP
But the MAME files have a well defined and unique filename, as far as I know. So hashing would not be needed. You could say the filename itself is the hash.

@BuZz
Oh, thanks for the info!

Seems like this is just a bad time for scraping MAME. I am hoping that it is getting better soon! Summoning Sselph for the rescue! ;)

well... after the apt-get upgrade it started working again perfectly

I have got them showing up in emulation station by unzipping them. Knew it would be something simple. Thanks for the help.

M3 work great

Try another card. Maybe the one you are trying is not compatible!!!!

@BuZz Thanks !!!! I am using the correct image now.

@Solid-One

I did actually. It's not too bad but I didn't want to switch to it at this point because of a couple of reasons:

For some reason it picks up my old save file on my external drive rather than my actual backed up saves on the SD card.

It messes up my controls, the buttons are wrong (though I could change this if I wanted).

Performance was really very nice on 4.0.2 with GlideN64 and I don't see a need to swap unless it is being deprecated by the devs here.

I'm quite happy to stay on 4.0.2 for the time being, but I was happy also to try out 4.1.3 and see the progress being made. :)

@BuZz said in Pcsx-Rearmed slowdown:

the meantime to build from a fixed fork until they accept the fix (details on the link above) and have built new binaries. If you upd

Thanks!:)