Homebrew Official Retroarch WiiU (wip.)

  • Thread starter Thread starter aliaspider
  • Start date Start date
  • Views Views 2,697,941
  • Replies Replies 15,203
  • Likes Likes 93
That would be up to him if I used his artwork or not, but I'm really just waiting on verification that everyone really wants this and everyone is happy with the icons and splash screens before I make this release official. It will at least get us by until there is a main app made that contains all the cores. I'm waiting for an official one from Retroarch to be made with whatever they have planned.
Its completely fine to use my meta but they are really just the assets of retroarch (xmb's retroactive (not content) for icon with the backgroud color of the splash from here)
I'm also fine with making the rest for you too.
 
Last edited by xtheman,
Its completely fine to use my meta but they are really just the assets of retroarch (xmb's retroactive (not content) for icon with the backgroud color of the splash from here)
I'm also fine with making the rest for you too.
Oh, those are kind of cool, I can make the tgas from those, that's no problem. My only problem now is deciding on good boot sounds for each system. I already found a good one for the SNES. I need to find some good ones for the other systems now. A 10 second boot sound is about the perfect length too.
 
  • Like
Reactions: ShadowOne333
Ok, I think I've finally got a final version, everybody look at this and see if this is what you want - http://www.mediafire.com/file/oxa3evq3486vpay/Libretro_SNES9x.7z

BTW, I replaced the core with the same one they released under 1.4.0 here - https://buildbot.libretro.com/stable/1.4.0/nintendo/
I didn't see the meta files (time to sleep), but I want to put the "WiiU" logo on the right of "RetroArch". Why? Because I love this port over the other ones and it had an special developement and support, so it deserves to be officially named as "RetroArch WiiU" :')
 
  • Like
Reactions: the_randomizer
  • Like
Reactions: brienj
Then make a GitHub report?
My first report got closed once because supposely it wasn't a RA issue but a core issue, I opened a new one but I don't have too much hope for a fix xD. IDK my experience in the Github hasn't been all good :unsure:

https://github.com/libretro/RetroArch/issues/4505

EDIT: Can you check if the PC or other platform have the same problem? We could make a case if it's isolated issue on Wii U.
 
Last edited by cucholix,
My first report got closed once because supposely it wasn't a RA issue but a core issue, I opened a new one but I don't have too much hope for a fix xD. IDK my experience in the Github hasn't been all good :unsure:

https://github.com/libretro/RetroArch/issues/4505

That is weird, very weird, failing that, you can try posting it on a thread on the Libretro forums. I don't know why they have a core or why they ported a core over if it doesn't work.
 
My first report got closed once because supposely it wasn't a RA issue but a core issue, I opened a new one but I don't have too much hope for a fix xD. IDK my experience in the Github hasn't been all good :unsure:
Why not report it at the core git then instead of RA?
 
My first report got closed once because supposely it wasn't a RA issue but a core issue, I opened a new one but I don't have too much hope for a fix xD. IDK my experience in the Github hasn't been all good :unsure:

https://github.com/libretro/RetroArch/issues/4505

EDIT: Can you check if the PC or other platform have the same problem? We could make a case if it's isolated issue on Wii U.
But is it an issue with Retroarch itself, or a problem with the core? Did an older Retroarch work, or was it an older core? You have to determine if the problem is in the core or not, and post the issue accordingly.
 
But is it an issue with Retroarch itself, or a problem with the core? Did an older Retroarch work, or was it an older core? You have to determine if the problem is in the core or not, and post the issue accordingly.

That might explain the report's deletion, if one can narrow down by testing different version builds, well, yeah..
 
Can anyone get me a question to run sega cd do i have to rename the bios to some specific name? Which bios version to use. Thank you very much in advance
 
But is it an issue with Retroarch itself, or a problem with the core? Did an older Retroarch work, or was it an older core? You have to determine if the problem is in the core or not, and post the issue accordingly.
The issue with TyrQuake wasn't present until the recent 1.4.0 updates.
Before it worked out without a problem, but the 1.4.0 refuses to open any .pak file, the core simply goes to a black screen very quickly then goes back to the menu, kind of what happened when you didn't have a BIOS file I think.
 
The issue with TyrQuake wasn't present until the recent 1.4.0 updates.
Before it worked out without a problem, but the 1.4.0 refuses to open any .pak file, the core simply goes to a black screen very quickly then goes back to the menu, kind of what happened when you didn't have a BIOS file I think.

Then that needs to be clarified in the GitHub report, and possibly when the builds stopped working. They'll need more info.
 
The issue with TyrQuake wasn't present until the recent 1.4.0 updates.
Before it worked out without a problem, but the 1.4.0 refuses to open any .pak file, the core simply goes to a black screen very quickly then goes back to the menu, kind of what happened when you didn't have a BIOS file I think.
Yes that's the problem I have as well worked fine on 1.3.6 but black screens on 1.4. it worked on every nightly until the first version of 1.4 came out and has not worked since
 
Last edited by AmandaRose,

Site & Scene News

Popular threads in this forum