Homebrew Official Retroarch WiiU (wip.)

  • Thread starter Thread starter aliaspider
  • Start date Start date
  • Views Views 2,702,777
  • Replies Replies 15,205
  • Likes Likes 93
IMPORTANT NOTE FOR HID USERS:

We've just decided to make controller_patcher an optional extra. If the proposed changes are merged as-is; it'll be disabled on the nightly builds. If you rely on a HID controller - such as a GameCube controller adapter, set of Joy-Cons, DualShock or other non-Nintendo controller - you may want to hold off on updating to the latest nightly until we finish writing a replacement (it shouldn't take long). Alternatively, you can compile your own RetroArch to re-enable controller_patcher - simply append ENABLE_CONTROLLER_PATCHER=1 to your normal make command.

On the plus side; I think this might fix retroarch.rpx; and should eliminate an awful lot of the more esoteric DSI errors. I'll update this post as more information becomes available.

I've been checking on the progress on GitHub, and all I can say is, thank you and the others fixing this so very much ^_^ :P

@ploggy and @A Plus Ric
 
IMPORTANT NOTE FOR HID USERS:

We've just decided to make controller_patcher an optional extra. If the proposed changes are merged as-is; it'll be disabled on the nightly builds. If you rely on a HID controller - such as a GameCube controller adapter, set of Joy-Cons, DualShock or other non-Nintendo controller - you may want to hold off on updating to the latest nightly until we finish writing a replacement (it shouldn't take long). Alternatively, you can compile your own RetroArch to re-enable controller_patcher - simply append ENABLE_CONTROLLER_PATCHER=1 to your normal make command.

On the plus side; I think this might fix retroarch.rpx; and should eliminate an awful lot of the more esoteric DSI errors. I'll update this post as more information becomes available.

Yes finally. So this means Wii U will be stable'ish?
 
We think it'll make it better, at least. There's always more work to be done on this sort of thing.
Ya, I did noticed the black frame insertion on the ps3 port works but not Wii U. Although Im having trouble with that ps3 online updater not working. Wii U updater works fine though. Both consoles have their negatives.
 
Controllers are broken in the latest nightly, whatever input get registered as "up" except for the analog sticks.
The only way press the button A for example and that doesn't go up; is tap B then quicky press A

EDIT: Don't tell me that I need reconfigure all my customs core button mappings :/
 
Last edited by cucholix,
Hi everyone, I might sound a little bit late with this, but are racing games supposed to stutter both in terms of gameplay and sound during Mame 2009 or 2003? So far I have tested Powerdrift, Cycle Warriors and Outrun and all three run awful.

Also just to mention that all other genres that I have tried so far seem to work fine (side scrollers and beat em ups) so no issues there

I just wanted to know if this sounds normal, or do I need to adjust some settings within retroarch or something?

Thanks guys

Did anyone find a workaround the stuttering sound and gameplay issues on racing games whilst using MAME 2003/9? Or is it supposed to stutter?
 
Did anyone find a workaround the stuttering sound and gameplay issues on racing games whilst using MAME 2003/9? Or is it supposed to stutter?
probably are playing a game that the wiiu can keep up with speed, you know wiiu cpu is preety slow so any demanding game will be slow or have issues, stutering means it cant keep up.
 
probably are playing a game that the wiiu can keep up with speed, you know wiiu cpu is preety slow so any demanding game will be slow or have issues, stutering means it cant keep up.

I thought so...

But should it happen on 80s games like Outrun or Powerdrift?
 
Well...um...yeah I'm here again and I have problem with Retroarch :shy:

I think my playlist is making Retroarch freeze If thats possible. I get problem with system memory error.
I followed this settings with playlist buddy : https://gbatemp.net/attachments/tuto_ra_thumb_pl-png.96632/
I manage files on WiiU(upload and everything) with FTP so Im not sure if I did something wrong
 
Can you get me a stack trace? Just take a photo. There shouldn't be any HID code left at all; so that's confusing.
I tried again and same thing happened. I was loading up f-zero snes. So it didn't say HID, but it mentions controls. Don't know what this is.
 

Attachments

  • HNI_0035.jpg
    HNI_0035.jpg
    74.1 KB · Views: 263
Last edited by SG854,
  • Like
Reactions: cucholix
  • Like
Reactions: Radius4
Controllers are broken in the latest nightly, whatever input get registered as "up" except for the analog sticks.
The only way press the button A for example and that doesn't go up; is tap B then quicky press A

EDIT: Don't tell me that I need reconfigure all my customs core button mappings :/
There shouldn't be anything different... does it work if you rename the config files and test the stock ones?
I tried again and same thing happened. I was loading up f-zero snes. So it didn't say HID, but it mentions controls. Don't know what this is.
I have an idea regarding this one, let me try and reproduce the issue and I'll get back to you. I'll use the 2017-12-02 nightlies.
 
There shouldn't be anything different... does it work if you rename the config files and test the stock ones?
Ok, I know what produce the issue, it's when a HID controller is connected on the Wii U, I have a wireless keyboard and GCN adapter in the console front ports, when I remove them RA works correctly again.
 

Site & Scene News

Popular threads in this forum