Homebrew Official Retroarch WiiU (wip.)

  • Thread starter Thread starter aliaspider
  • Start date Start date
  • Views Views 2,689,367
  • Replies Replies 15,197
  • Likes Likes 93
The channel doesn't use anything located inside the apps folder, it only loads the rpx cores found in retroarch/cores. i think the problem stems from the apps folder.
Also it autoloads the last core you used.

Why do some builds work fine but others don't?
 
The best thing to do is try out the cores, and make notes of what works good, and the ones that don't, try the previous or the next build.
 
The RA forwarder channel just loads the most recently used RPX at the start of the session...

I think this might be a factor in the 160-2203 issues people are getting. This is all just guesswork (haven't been able to run the newer builds, let alone replicate the issue!) but I'd say that this standalone RetroArch you guys keep mentioning has an incorrect method of loading a core on startup; which leads to the loader getting fed a bad RPX thus triggering the 2203. My best guess for the trigger at this point is the "libretro_path" section of the config files. Shadow's one looks like the following:
libretro_path = "sd:/retroarch/cores/mgba_libretro.rpx"
I would think that RA sees that path in the config and attempts to load the core, then (mumble mumble mumble mumble mumble) and the loader throws the 2203. For a quick acid test, can someone remove/clear/fiddle with that line in their config and see how RetroArch reacts? If it will work without loading a core on startup, then that narrows the bug right down.
 
I think this might be a factor in the 160-2203 issues people are getting. This is all just guesswork (haven't been able to run the newer builds, let alone replicate the issue!) but I'd say that this standalone RetroArch you guys keep mentioning has an incorrect method of loading a core on startup; which leads to the loader getting fed a bad RPX thus triggering the 2203. My best guess for the trigger at this point is the "libretro_path" section of the config files. Shadow's one looks like the following:

I would think that RA sees that path in the config and attempts to load the core, then (mumble mumble mumble mumble mumble) and the loader throws the 2203. For a quick acid test, can someone remove/clear/fiddle with that line in their config and see how RetroArch reacts? If it will work without loading a core on startup, then that narrows the bug right down.

Interesting, while I admit I haven't tested out the builds past the last working one (5/22), I should be able to test this, hopefully @ShadowOne333 @A Plus Ric can test it out as well.
 
I think this might be a factor in the 160-2203 issues people are getting. This is all just guesswork (haven't been able to run the newer builds, let alone replicate the issue!) but I'd say that this standalone RetroArch you guys keep mentioning has an incorrect method of loading a core on startup; which leads to the loader getting fed a bad RPX thus triggering the 2203. My best guess for the trigger at this point is the "libretro_path" section of the config files. Shadow's one looks like the following:

I would think that RA sees that path in the config and attempts to load the core, then (mumble mumble mumble mumble mumble) and the loader throws the 2203. For a quick acid test, can someone remove/clear/fiddle with that line in their config and see how RetroArch reacts? If it will work without loading a core on startup, then that narrows the bug right down.

Line removed and no 2203 error (I had it before) but quit and restart, 2203 error...
 
Last edited by NgXAlex,
  • Like
Reactions: ShadowOne333
I open mgba usually and load right to other cores from it and use playlists. It's why the retroarch main rpx not working isn't bothering me lol
Yeah, renaming a copy of mgba core as "retroarch.rpx" in the apps seems to do the trick, not getting 160 of death so far.
 
Nestopia is the Nes emu of choice as for PC engine I tend to use the Super Grafx Core :)
Ok thanks ploggy that was the two I have been using but just wanted to check they were the recommended ones thanks.
 
  • Like
Reactions: ploggy
Yes so following the advice of others here I have deleted the standalone retroarch launcher thingy and replaced it with a renamed mGBA.rpx and no more system memory errors and now the game and watch core I could never get to work now works perfectly. Happy days lol
 
  • Like
Reactions: cucholix
Yes so following the advice of others here I have deleted the standalone retroarch launcher thingy and replaced it with a renamed mGBA.rpx and no more system memory errors and now the game and watch core I could never get to work now works perfectly. Happy days lol

Huh, weird that doing this is a workaround, but that it works so well, this is good news to getting around issues :P
 
Huh, weird that doing this is a workaround, but that it works so well, this is good news to getting around issues :P
Yep the workaround has now gave me zero issues I have loaded it then switched off the wiiu several times and it loads every time now.
 
  • Like
Reactions: the_randomizer
Yep the workaround has now gave me zero issues I have loaded it then switched off the wiiu several times and it loads every time now.

Interesting, so if i ever encounter a Wii U OS crash, I delete the main RetroArch RPX, get another (like Snes9x 1.54), rename that to the main one, and it works just fine? I'll be damned. What's weird is that you can switch cores which is odd seeing as the cores are in other folders.
 
Interesting, so if i ever encounter a Wii U OS crash, I delete the main RetroArch RPX, get another (like Snes9x 1.54), rename that to the main one, and it works just fine? I'll be damned. What's weird is that you can switch cores which is odd seeing as the cores are in other folders.
Yep don't know how or why it works but it does and you can still switch cores ect.
 
  • Like
Reactions: the_randomizer

Site & Scene News

Popular threads in this forum