@Jezzer said in Compiling drivers for Deskpi:

I tried to install cmake from buildessentials but it appears that you need buster / bookworm / whatever it's called. I wasn't sure what I should be installing here... Anyone know how to do this?

cmake is already installed on the RetroPie image for the Pi4 and the buildessential metapackage is installed aswell, so compiling shoudn't be an issue. Did you try compiling and got an error - if so, can you post the actual error message here so that we can help fix it ? Do you have a link to the instructions/documentation of the drivers where the installation/compilation is explained ?

@mitu said in Large File in .git Folder on RetroPie. Is it safe to delete?:

@Didyman said in Large File in .git Folder on RetroPie. Is it safe to delete?:

... but after I indeed updated assets and shaders in RetroArch, but as far as I am concerned, those are .zip files that are then extracted.

Shaders and assets for RetroArch are also handled by RetroPie and they don't need to be updated from RetroArch's menu.

Did you copy the config folder from another installation ? I think a long time ago (not sure how far) the assets folder was cloned from https://github.com/libretro/retroarch-assets.git, but that's been changed and only a minimal set of assets for RetroArch are downloaded and installed by RetroPie.

I did a backup of the configs folder, but I didn't copy it back. I keep it as a reference point. I didn't want to "corrupt" the configs as they were coming from an old build (Stretch). I did copy the the bios and roms folders from my backup tho.

----- SOLUTION FOUND -----
Posting a solution here for any CTRL+F heroes

Retroarch Quick Menu > Core Options > HLE BIOS = ON

I don't know what the setting even does, I'm just glad autoload actually works now.
Gonna put some tags below for search engines to pick up on:

lr-flycast, flycast, autoload, auto-load, auto load, crash, savestate, black screen, saves, saving, loading, loads

@Lolonois I was with you all the way up to the word "binaries".

anyone no idea?
i wait for answer

@lesk said in Making a custom game that randomise NES games to play?:

My question... Is it possible to do a similar thing for retropie?

Not without creating a new game, which is what Nintendo did.

@Jolt said in Keyboard configuration issues with an IPAC2 in a Retropie/Pi/Mame arcade setup:

I tried to go into ../config/all/retroarch.cfg and update the configuration there back to the MAME default, but it ignores that an uses the incomplete mapping I did last night.

retroarch.cfg is not the MAME configuration file, it's RetroArch's, which happens to also run MAME cores.

I looked on forums a bit and it suggested to run the retropie_setup.sh, but I'm a bit concerned about how much that will roll everything back.

Running the setup script will not do any un-intended configurations. You can use the reset configuration menu and you'll be able to start over with the EmulationStation's input configuration.

Is there a way to reset all the keyboard controller work only? Or is there a way to manually hardcode the Emulation Station controls like I've done in the rertoarch.cfg?

You can manually add the configuration in EmulationStation, but it's better to go through the input configuration - see above on how to reset the configuration and start anew.

I see, thanks for trying

@sugarfree THANK YOU!
this is solved

never would have thought updating the retro-pie set up script was how I lost the external drive loading.
i got busy for a few days, was wondering what to do, this am I was able to get on the forum, seen others having same issue after the update of set up script, then remembered "I did that too!" I seen it's been fixed and re did the update, now i have the drive loading again.

thanks for taking the time and adding this info!
also thanks to all others who commented advice

SOLVED!!

I am not sure what to suggest, a Pi4 with 2GB would have been my answer in pre Pi5 times... and still, the Pi4 runs an official image, but the pi5 ain't such a newcomer nowadays and the official image is still based on (IIRC) buster and since then, even before the Pi5 was released, the discussions where about when there will be a "bullseye" image and whether it will be 64bit/32bit or still in support of 32bit ... sigh...

So the official image is missing debian 11, the 64 vs. and or 32 bit problematic still unsolved and now with the pi5 we are over the edge to 64bit and on bookworm as the current debian/raspi OS base...

I would say, it depends... if you want to play straight ahead and use the existing image, go for a pi4 with whatever mem you may need to reuse it after upgrading retropie to a newer device (for retropie on a RP4 2GB is IMHO more then enough, if you want to use it as a terraria or minecraft server afterwards, at least 4GB better 8 would be the way to go).

But if you are totally new to raspis and retropie... well, bad timing, if you simply can afford it, go for the above mentioned route of the pi4 and learn some *nix basics ... but be assured that all you learn for the nowadays official buster based image is void for the next official one, because too much on the underlying OS was changed (just to add a match of buzzword: config.txt vs. cmdline.txt) - if you are willing to experiment and learn on raspberry pi/*nix in general in the meantime, go for a pi5 with the memory you can afford!

@Lolonois said in Adding console Vircon32 to RetroPie:

Other than that I think your virtual console fits in well into Raspberry Pi and RetroPie universe as it allows everyone learning by inspecting and adapting the code.

That was my intention. The console is designed to be very simple and it is fully documented. All my programs and games are open source too. (And games are free, so no problem to distribute the roms).

About the Pi versions, this core has only been tested from Pi 3. I don't think the Pi 1 is powerful enough to run Vircon32. And I have no idea about the Pi 2.

My core builds for Pi 4 have always been done with flag -DENABLE_OPENGLES3=1, so that is what the binary at GitHub release v1.3 should be. In fact, if you try to build the core without GLES3 it will succeed, but it won't run (in my system at least). With GLES3 it does run the games.

EDIT: Still, if you need me to generate some other binaries from the Pi's I have (3 and 4), I will try to do it.

I swapped over to Hypseus, and was able to get everything running (tested on Dragon's Lair). Thank you again for the suggestion!