GPi Zero 2 v1.52 & GPi Zero v1.15(Retropie Images for Pi Zero/Zero2 + GPi Case 1 & GPi Case 2W)
-
Why are you replacing the entire file rather than selectively adding what you're trying to set up?
I'm willing to support the setup I built, but you're straying outside of that at this point. Standard Retropie documentation should be sufficient to figure out what you're attempting to accomplish.
-
If someone can share one copy of the es_cfg in the proc/retropie its the only way i can correct my problem for replacing the advanced settings. This is a good system but there are litle things ...... and i'm begining to use and learning.
-
@Sliver-X Thanks for the fantastic work! I've just upgraded my GPi Case to Zero 2, using your RetroPie image, on a new microSD card. I manually copied over all my ROMs and saved .states, from old card to the new, using my RPi4.
I'm having one issue; the ROMs load and play just fine,
but cannot recognize/load the saved .state files.I can Save, and Load new .state files. Can't figure out what is wrong with the copied ones. Any help would be appreciated. Cheers!
EDIT: Upon further testing, it seems it's only Nintendo NES that cannot load saved .state files.
gb and megadrive do it fine... hmmm... -
This post is deleted! -
@scotthw said in GPi Zero 2 v1.4 (Retroflag GPi Image for Pi Zero 2 W):
EDIT: Upon further testing, it seems it's only Nintendo NES that cannot load saved .state files.
Alright, seems to be a known issue, stemming from emulator core updates, rather than something specific to this build.
Unrecognized nes state file
https://retropie.org.uk/forum/topic/20167/unrecognized-nes-state-file
1 Dec 2018Includes a link to the github issue.
.
And there's this discussion
Upgrading to Retropie 4.4 makes old lr-fceumm SaveStates incompatible
https://retropie.org.uk/forum/topic/17518/upgrading-to-retropie-4-4-makes-old-lr-fceumm-savestates-incompatible
25 Apr 2018mediamogul [Global Moderator]
The best you can hope for is to load the save state from the previous core version and work your way to an area that allows for a normal memory save. Afterwards, update the core load the save and make a new save state. I realize this wouldn't be possible for all games and it's a major hassle, but it's really the only option. It's best to only utilize save states for very casual use and at no time when it's crucial to keep them for long periods of time. Save state formats can change at any time depending on development. You might see an emulator/core keep its format throughout its lifespan, or you might see it change several times a year. -
It may be be worth trying to transplant the core .so file from the build the save states were created with to my image and see if that works: With a core as mature as fceumm I doubt any functionality/compatibility with various MMCs/etc would be missing between them.
If that works, just avoid updating the fceumm core in the future if possible.
-
@Sliver-X any chance of adding Dreamcast to the list of available emulators? I know the pi0 can’t handle much but, I do know the game I want to play is playable on it (Wind and Water Power Battles).
-
@celly I mean you can download Reicast and lr-flycast from RetroPie Setup. But obviously don't expect much
-
@retropieuser555
flycastis not enabled on Pi 0 in RetroPie-Setup, it can't be installed.@celly you'll have to manually modify the
lr-flycastscriptmodule to have the module available to be installed and you'll need to install from source. Note that in order to be able to update RetroPie-Setup, the changes will need to be reverted (but that will not remove the installedlr-flycast). -
@mitu ok thanks. Sounds like a lot more involved and I really don’t want to break anything for just one game really.
-
Hello i using retropie and i flashed to a new 64 gb sdcard but after i installed some neew emulators and transfering the roms the system stop to boot - corrupted sd card.
The question i have is i will flash retropie to a new 64gb card , can i expand the share partition on gparted and copy some roms before i boot the card on the rasperry pi ?
Can i have problems with this ?
-
@joao76 said in GPi Zero 2 v1.4 (Retroflag GPi Image for Pi Zero 2 W):
The question i have is i will flash retropie to a new 64gb card , can i expand the share partition on gparted and copy some roms before i boot the card on the rasperry pi ?
You can do that, but you'll need a Linux system to do it. On 1st boot RetroPie will automatically expand the Linux partition anyway.
-
And i can start to copy some roms for their folders whitout problems?
-
@joao76 said in GPi Zero 2 v1.4 (Retroflag GPi Image for Pi Zero 2 W):
And i can start to copy some roms for their folders whitout problems?
Since the Linux partition on the image is faily small, without resizing it first you'll not be able to copy much. Do you have any problems using one of the documented transfer methods ?
-
I have 1 one card 32 gb retropie the only problems i can not go into ssh .
This i verify and put an ssh file if not exist then i will boot on linux resize partition copy some roms and i hope do not have problems i this.I don't have problems transfering roms but i transfer over wifi and that way is a pain.
Thanks for your help. -
This image will be updated for the latest released version of retropie ? Or that don't make sence ?
-
Yesterday i flashed the image to a new sdcard resizing partitions and copy roms. First all working fine then emulationstation crash, im forced shutdown don't have solution. Then the system start ok because the problem i have i'm updating all. The system crash because of new kernel and dtb files i forget this last and big update a few days ago.
So i have to do all again , and i'm asking this image will be updated or is too much work involved ? Thanks for your help and thanks for your work. If wil be and 1.5 version it's better for me to wait.
-
@joao76 said in GPi Zero 2 v1.4 (Retroflag GPi Image for Pi Zero 2 W):
So i have to do all again , and i'm asking this image will be updated or is too much work involved ?
I think the author mentioned earlier it will not be updated. Set it up and get it working as is. If you update the OS/kernel, then you have to be careful to keep the GPI specific files.
-
I'm probably going to create one last version based on RetroPie 4.8, mainly due to it fixing the hideously bad "Dirty Pipe" vulnerability the v1.4 image I released is susceptible to. I built a 4.8 image for a Zero 2 based console machine I designed recently and overall 4.8 seems a lot more stable than the weeklies I was using before as well.
To go ahead and get this out of the way now, @joao76
I am not a RetroPie developer. I have no ties to the RetroPie developers. I've only been using RetroPie for about six months, total. 9 out of 10 questions you keep asking me here and on Reddit are general RetroPie problems that can be resolved by posting a general thread here or elsewhere, or by bothering to read RetroPie's excellent documentation.
I am not your personal RetroPie/Linux/Computer Usage troubleshooter. Please understand this.
-
I've tested and created an archive for v1.5. The first post in this thread has been updated accordingly.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.