@mitu said in Error updating to the latest version of Retroarch:

You can delete the cores folder and it the .info files will be re-downloaded on future updates.

Awesome. Thank you!

@sleve_mcdichael said in Why do some versions of Retroarch look so different?:

@TPR that's the "menu driver" setting. RP default use the rgui driver cause it lightweight and perform well on low powered hardware like RasPi. I think the blue one in your picture is xmb. Other choices are glui or ozone.

retroarch.cfg excerpt:

# Menu driver to use. ("rgui", "xmb", "glui") menu_driver = "rgui"

Found it! Awesome... thanks! For some reason I never knew this was an option.

@mitu hey! sorry, school started so I've been busy. here's the requested info:
Raspberry Pi 4 Model B Rev 1.5
RetroPie 4.8.8
Installed from the SD image on the website
All that's connected rn is the one dragonrise controller
I get a not configured error message from retroarch

About the config files, I was the one who mistakenly deleted them after trying to fix different control issues (it was a long night and at that point every button except select was unresponsive). I might try going from retropie-setup and seeing if that works?

there's a chance I disabled autoconfiguration, but I have no clue how I did that or how I would turn it back on. I definitely did not mess w es_input.cfg though, I never touched the es folder anyways.

I'll get back to you if the reset via retropie_setup helps, I didn't know that was a thing at all. thank you for your help :)

Luckily I got another memory card with version 1.9.7 which worked perfectly 1.19.0 utterly sucks and has so many bugs and issues. I think I'll stick with the older version and never upgrade retroarc again. if it ain't broken don't fix it.

@DjDiabolik said in Input Lag - How can "CHECK" if present in Retroarch core / Standalone emulator?:

anyway for my next arcade kit I was considering buying something similar:
RP2040 Advanced Breakout Board on Aliexpress

Nice. That creates added value to a plain RP2040, pinheaders and Dupont wires. FWIW, here is the non-commercial link with all the tech specs.

Great you have some takeaways/learnings, that's the Raspberry/RetroPie spirit.

PS: The Sanwa's do have a high price tag but I never regret my invest: Mechanical still precise after ~5yrs, no maintainance needed, colors fresh as of the first day (my setup is partially exposed to sunlight during the day).

I have a Raspberry Pi 4 running the latest version of Retropie

Which is version ... ?

[..] I deleted the Retroarch.cfg file and now NES and Snes won't allow me access in game to retroarch.

That's never a good idea, since RetroArch would then create a default configuration for the system, which trumps the RetroPie configurations and leads to all sorts of errors.

Any ideas on how to fix? Thanks in advance!

Remove the retroarch.cfg file for the NES/SNES system then immediately re-install the NES/SNES emulators so that RetroPie will add the correct RetroArch configuration - otherwise you'll get into issues again when starting from a stock RetroArch configuration.

@shift

Thanks, good to hear.
I am playing with it a bit and I could add it for more drivers this way from EXTRAS.
I will see how it evolves.

@CobraDesign47 said in Retroarch no Core installer:

. Could someone help?

RetroPie doesn't have a 'standard' RetroArch installation w.r.t. cores. Cores are managed manually from RetroPie setup and they're automatically set to be started depending on the system where the ROM/game is located. You don't need to start RetroArch and then open a core/content like you'd normalluy do on a bare RetroArch installation, instead you launch the game/ROM directly from EmulationStation.

As for the original question - did you configure your keyboard in EmulationStation - as an input/controller ? It should automatically configure the keyboard for RetroArch also.

@mitu , thanks a lot! was indeed the retroarch folder.

@mitu said in AI Service Crashing on lr-Flycast and lr-PPSSPP:

@TPR said in AI Service Crashing on lr-Flycast and lr-PPSSPP:

Should I be concerned about that error?

I'm not familiar with the error, I've updated a couple of times from an older version and didn't encounter it. This happens when you've modified some files outside of git, which shouldn't happen if you only used the RetroPie setup to update RetroArch's core configuration files.

I've only ever used the RetroPie setup so for now since everything seems to be working I'll ignore the error and cross my fingers that everything is okay!

@mitu i reinstalled the sdl2 page of the dependencies in the retropie menu

Is the controller configuration saved in /opt/retropie/configs/all/retroarch-joypads ? Do you see a .cfg flie there for the controller ? If yes, can you post the contents of the file surrounded by code tags here, in the topic ?

@mrmadcatz

UPDATE: I was able to fix the issue by going to RetroPie Setup > Core Packages and returning both the Retroarch hot keys and EmulationStation controls back to their defaults. Once I remapped the controllers again in ES, they carried over to RA.

@mitu Thank you! That was exactly the step I was missing!

@mitu i discovered that the file i was trying to play had H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
codec

i tried playing a video from really old times whose pixel layout was the exact same as my spi display 320x240 codec of that file was Xvid this time it didnt play anything it just crashed

Hello! I realised that maybe you guys are assuming that my usb keyboard is a gaming keyboard. It isn't. I think I'll have to buy an actual video game controller eventually. Thanks anyway for your guys' help!