Homebrew Official Retroarch WiiU (wip.)

  • Thread starter Thread starter aliaspider
  • Start date Start date
  • Views Views 2,718,077
  • Replies Replies 15,207
  • Likes Likes 93
As do I, but we have to start somewhere, no better place than to screenshot and then consolidate the pics and put them on GitHub. B-)
Didn't we do that a while ago?

Somewhat related.. I'm sure I read somewhere that @QuarkTheAwesome was re-writing the WiiU rpl loader? I think it was a tweet he made a couple days ago?
 
Last edited by ploggy,
Didn't we do that a while ago?

We did, but I don't even remember what page it's on, I can't be arsed to wade through who knows how many pages to find it. What do you suggest we do? I don't want to not do anything to help, you know? Do we know
when it started? I think sometime after 1.6.0 and beyond, I seem to remember 1.5.0 being pretty stable (or whatever the first one to have XMB was). *sigh*.
 
We did, but I don't even remember what page it's on, I can't be arsed to wade through who knows how many pages to find it. What do you suggest we do? I don't want to not do anything to help, you know? Do we know
when it started? I think sometime after 1.6.0 and beyond, I seem to remember 1.5.0 being pretty stable (or whatever the first one to have XMB was). *sigh*.
We've always had Dsi Errors in some way or another but I started taking pictures when Quark added his error handler (not sure what version of retroarch he added it)?
I'll Have to try to trigger the Errors again and take new pics :P
 
Well last time it was only the Genesis one wasn't it? So only that one got fixed?

I don't seem to recall, I've been out of the Wii U loop for a bit, about to get back in and testing the latest stable release. I won't be testing any nightly builds for simplicity's sake.
We've always had Dsi Errors in some way or another but I started taking pictures when Quark added his error handler (not sure what version of retroarch he added it)?
I'll Have to try to trigger the Errors again and take new pics :P

Right, and these need to be repeatable, reproducible to see what factors are taken into consideration. :P
 
I don't seem to recall, I've been out of the Wii U loop for a bit, about to get back in and testing the latest stable release. I won't be testing any nightly builds for simplicity's sake.


Right, and these need to be repeatable, reproducible to see what factors are taken into consideration. :P

I'm going to take a stab at triggering the Errors again (repeatedly) If your going to do the same I suggest you don't use the Retroarch channel. Easier to trigger the Errors :P
 
  • Like
Reactions: A Plus Ric
I'm going to take a stab at triggering the Errors again (repeatedly) If your going to do the same I suggest you don't use the Retroarch channel. Easier to trigger the Errors :P

Wait, what? Oh, so I just load it via the Homebrew Launcher channel then? Huh, weird, okay.
 
I'm going to take a stab at triggering the Errors again (repeatedly) If your going to do the same I suggest you don't use the Retroarch channel. Easier to trigger the Errors :P
Question so i know. Are you guys using as the channel the one from brien or a new one and if so is it just a forwarder or what? Just curious to know what to use for testing to re-create any problems. (also make sure always using stable iirc for error reports.)
 
Question so i know. Are you guys using as the channel the one from brien or a new one and if so is it just a forwarder or what? Just curious to know what to use for testing to re-create any problems. (also make sure always using stable iirc for error reports.)

Yup, using 1.6.7 stable, no nightly builds involved. The forwarder from Brien I believe, at least I think it is. I do have the HBL channel installed as well, so I can use that, I suggest you do the same :P
 
Was using Briens channel but for the tests I'd suggest not using it and just load through the HBL since the Retroarch channel reduced the Errors and we WANT to trigger the Errors :)
 
Was using Briens channel but for the tests I'd suggest not using it and just load through the HBL since the Retroarch channel reduced the Errors and we WANT to trigger the Errors :)
I meant use it also so that way of both give errors we have a way to confirm as in some errors might be repeatable on both. But if one is using something different it might not. therefore finding problems easier.
 
  • Like
Reactions: ploggy
I meant use it also so that way of both give errors we have a way to confirm as in some errors might be repeatable on both. But if one is using something different it might not. therefore finding problems easier.

What do you propose? HBL method may be easier to reproduce errors on, and easier for the devs to replicate.
 
  • Like
Reactions: ploggy
I meant use it also so that way of both give errors we have a way to confirm as in some errors might be repeatable on both. But if one is using something different it might not. therefore finding problems easier.
Its entirely up to you, but personally I'm going to to do it as close to clean install as possible :)
 
  • Like
Reactions: the_randomizer
I would say Homebre channel first. Then try on retroarch channel. Just so we can say an error that occurs occurs on both, or just one. I still feel something is wrong with the Homebrew Launcher that doesn't close properly. Especially when dealing with RPX files. Because if you open Retroarch RPX. then exit it and then try to open a .elf, it will not always work. It will just go back to homebrew launcher.
 
Ok first problem... I cant get Retroarch to launch through the HBL.. Just a black screen? (completely fresh install)
 

Site & Scene News

Popular threads in this forum