Did you properly quit out of Retroarch? I recall one of the devs (can’t remember which) saying that Retroarch only writes to .srm at quit.[/quote]
I suppose that would be the problem! But I’ve never needed to do that before…
Did you properly quit out of Retroarch? I recall one of the devs (can’t remember which) saying that Retroarch only writes to .srm at quit.[/quote]
I suppose that would be the problem! But I’ve never needed to do that before…
@thelostskeleton Some games use SRAM as scratch space, so there’s no way for RetroArch to know whether that’s happening or if it’s writing a save, so it only writes to file when you quit. However, there’s an autosave option you can enable via RGUI that will write to file periodically (every 5 seconds or so, maybe?).
autosave_interval, ye. It spawns a thread that checks SRAM every N seconds. If it changes, it flushes SRAM to disk.
I’m not sure why it’s a problem if games use SRAM as a scratch pad… you’d have the same problem on real hardware, wouldn’t you? I’m not sure I understand why that’s an issue.
I’ll see about enabling the auto-save, though. It’s not easy because I am writing this from a Linux Live CD - my main PC is out of comission for the next week, and the last time I tried to edit retroarch.cfg here it told me the file couldn’t be accessed, even though I can copy data to and from the SD card just fine.
The “intuitive” thing to do with SRAM is to write it to file every time it changes; that’s where games using it as scratch becomes a problem. Constantly writing to disk is going to send performance to hell, so it’s simply not practical. Auto-save offers a compromise between constant writes and no writes (risking loss of progress).
File I/O is disastrously slow on consoles - and even more so on the Wii.
I’m not sure we will want to pursue this from that perspective.
Hi allons, great software.
On my pal Wii, an annoying bug is arising all the time (0.9.9-fix) : main menu should show 512x228i but screen is streched out of the screen, i go to video settings, change résolution one step ahead and back and It is fixed until next main core reloading.
Another one … input settings are lost when using GameCube controllers.
Thanks anyway … i use it both Android and Wii.
Hello there. After a long testing with neo geo core on gamecube (they work around 40 roms so far, all of them below 4mb in size) I returned to use the traditionsal cores to see something but the roms I choosed seems to have problems to boot. I summon you, gamecube users from this comunity to test the following roms to see if they work for you: Donkey Kong Country Series, Megaman X3, Kirby Dream Land 3, WWF Wrestlemania:The arcade game and other games of your selection.If you make them work please share with me your settings, I’d really like to play them through RA Gamecube. Thanks in advance.
I advise you not to play SNES games via RA since the SNES core of RA is slow on Gamecube. Try Snes9x 1.43 - GX Edition 0.1.1beta @ gc-forever :http://www.gc-forever.com/forums/viewtopic.php?f=13&t=1219 Snes9x 1.43 - GX Edition 0.1.1beta based on SNES9X 1.43 is faster than Snes9xGX based on SNES9X 1.50 or higher versions.
I advise you not to play SNES games via RA since the SNES core of RA is slow on Gamecube. Try Snes9x 1.43 - GX Edition 0.1.1beta @ gc-forever :http://www.gc-forever.com/forums/viewtopic.php?f=13&t=1219 Snes9x 1.43 - GX Edition 0.1.1beta based on SNES9X 1.43 is faster than Snes9xGX based on SNES9X 1.50 or higher versions.[/quote] I do not say they are slow, I say they do not even boot. I am not an expert but looking to the rom sizes of the roms I have already played and the ones that do not work I think it could be a rom size issue. That is why I asked you to test them out and be sure is not a problem with my gamecube.
Will the MAME 0.78 core be included in the 0.9.9.4 Wii release?
You guys have done a fantastic job. Keep it all up! I wanted to request a few features. I know someone else before had requested the .ogg support be re-implemented into the pcengine emulator, I would like to second this request. I have 63 pccd games, which only takes up 2.5 gigs on my sd card, verses the 30+ gigs needed for full cd isos. A huge savings of space for very little sacrifice in quality. I won’t press the matter, just trying to make a convincing argument.
My second request, is to make it so each core can save a different roms directory (perhaps as an override to the default setting). This will make sorting through the roms a little easier. I actually have it set up where each core has its own homebrew channel button, instead of switching cores from within, so that my parents, who are not so tech savy, can use the system with ease, but they still tend to get lost in the directories.
I have one more request, tho I must admit, I have no idea how it could be implemented. The file names for FBA arcade roms can sometimes be vague or confusing. I would love it if there were someway for the FBA cores to show the game name, rather than the file name. Alternatively, some method that would allow me to rename the roms myself, but still have the emulator execute the game properly (perhaps a kind of .bat file). This request might be more trouble than it is worth, but would be quite convenient.
I hope to see support for Lynx, MSX, and others in the future! Thank you!
Thanks, looking forward to updates!
Hello there.
Its fantastic to have a lot more emulators on the GameCube now. I’ve already tested the Snes9x next, Gambatte and Nestopia. But there is a problem with VBA next:
It will startup from my SDML fine, but after selecting a ROM it crashes instantly and gives me an ISI Exception. Settings have also been reset. The ROM will not load, neither from commercial dumps nor my or other homebrew games/apps. Is the GBA BIOS file needed? If yes, why is it not listed in the cores manual or the readme? The error screen is similar to that of duiza89 and Protoman-X.
The debug info from RA with VBA next core is as following (after clean startup): FPS: 0.0 Frames: 0 (counting up about 60 frames per second) MEM1: 7647248 / 25165824
Which is about 7.3 MBytes used of 24 MBytes MEM1 available.
Even with small files this will not consume all available RAM on the GameCube.
Just wondering if 0.9.9.6 will be pushed to Wii or will it be a later release?
Nothing will be pushed until we get the control issues under control.
Control issues with the Wii port?
Any news about new builds of Retroarch for Gamecube/Wii ?
An ongoing issue with the Wii/GameCube port has been the generation of spurious inputs, the cause of which has not yet been tracked down. This results in things like characters moving without any command from the player: obviously a pretty busted situation for a project like RA to be in.
Slappy, yes, this show-stopping bug which has plagued the Wii and GC version of RetroArch since launch was solved in the three hours between its last mention and your reply. But not really.
Ok, I haven’t experienced any issues with controls anyway. Thanks for clarifying.
There are some Months I’m not updated about retroarch builds and issues so I don’t know of which problem you are talking about. In any case you have to learn to be more respectful.