@lurker that was the objective. not really how long the time is between a button clicked and received. but the delay time of the recorder in contrast to the button as GPIO. but if the delay time is so minuscule then you answered my question. its useless to compare. ty

I updated the driver via the Retropie-Setup and everythings workung fine. Thanks.

@kingradness can you please post your renamed file here for me? I'd love to get a good save of this game but I'm having a hard time.

@scabab1359

Running with ROMs from an external drive - https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/. If you remove the drive, then the system will read the ROms from the SD card. Kids mode - you can toggle Kids mode in Emulationstation, the frontend for the listing the games, and only games with the 'Kid Mode' flag will be shown, see https://retropie.org.uk/docs/Child-friendly-EmulationStation/#ui-modes

@fruitybit Seems the wiki page is not clear enough or offers some outdated (?) information. Glad it works out.

Ok, now i did the change by hand and created a second xml file with the additional custom data. Whenever I do scrape with Seten Selphs Scraper, I need to add the custom data by hand.

@chris419

My brother lives a block over and has been promising to bring my sling blade back for over a month. It's such a nice day out, I think I'll walk over there and borrow it back.

@mat said in lr-picodrive Cheats Broke?:

I am always leery of trying something outside of the default

What's important is what works best for you. The defaults are intended to cover a wide range of use cases, but quite often the alternatives can potentially work better for specific goals. One of RetroPie's biggest strengths is that it allows you to tailor your emulation experience to how you see fit.

Alright thanks. I will have to give this a shot this weekend.

@timbone316 You probably have save_on_exit in RetroArch. Try to open the RGUI (Select + X) while ingame and disable this.
To revert to the Mame2003 default retroarch.cfg file, re-install the package from the RetroPie-setup script.

@nilsholgersson pcsx-rearmed is known to have a lot of compatibility issues, being fast enough on arm processor came at a cost... and don't expect fixes for this, notaz (the main developper) has been quite inactive for years.
Your best bet is to use either the original hardware or a more accurate emulator (i would recommend beetle-psx-libretro) on a hardware more powerfull than the pi (i would say something with a cpu as close as possible to 3Ghz)

@thenetstriker said in Problems with xpad after update to Debian stretch:

I also get a lot of those error messages. So much that it is affecting the performance and I'm getting a lot of video freezes. I hope that will be fixed soon.

Thanks for digging through this issue, I guess the new 3B+ is more finicky about measuring the power consumption.

Ah that explains it. It's weird though, that it doesn't do that with every video. Is it only arcadeitalia scrapes that are like that? Maybe I'll just scrape with UXS. Not sure how to use Handbrake.

How do I "manually scrape and specify the -convert_video option?"

EDIT:
I'm giving this a shoot before attempting something else:
https://retropie.org.uk/forum/topic/15764/script-retropie-convert-videos

Hello Loxley,
I'm experiencing a very similar problem.
I edited the retrogame.cfg in the boot folder and then set up the controller in emulationstation.
Everything works in the menu like you described but when I jump into any game the controls have changed completely.
Have you figured out how to solve this problem?

Regards Jakob

This is what I did.

@markwkidd said in Need Help Configuring D-Pad to act as Analog Stick in Arcade Games:

This will be easier to accomplish with the new remapping system in RetroArch 1.7.2 -- probably RetroPie 4.5 though. Cold comfort today I know.

how would it work with this specific example? i don't know what the new retroarch stuff does, yet, so this will be an interesting example.

i'm thinking for retropie's initial binding, we give the users each abstracted retropad button, and they press the associated physical button they want to use for that, which seems logical so far. how would retroarch 1.7.2 change this approach?