Homebrew Official Retroarch WiiU (wip.)

[tmnr1992]

I just did some testing and ran into the same issue. I thought I remembered it working at some point but maybe not. It seems it's been an issue for a while.

Oh that sucks, thanks for testing and sharing the info, I guess CHD is the way to go for now.

 

[ber71]

Retroarch 1.9.1 finally released

https://www.libretro.com/index.php/retroarch-1-9-1-released/

In another news, mgba 0.9.0 standalone (for Wii) has been released too, with many new features.

 

[marchrius]

Hello there, I'm trying to get Taito F3 games to work on retroarch. I really don't know why since it shouldn't be a difficult system to emulate, but I'm getting DSI error on mame2003 with any rom, and huge performance issues on final burn neo (I'm talking like 2fps on puzzle bobble 2 game). I tried other games on final burn neo and they work fine (puzzle bobble 1, metal slug ecc.). Is anyone able to play Taito F3 smoothly on RA Wii U?

 

[ChiefReginod]

Retroarch 1.9.1 finally released

https://www.libretro.com/index.php/retroarch-1-9-1-released/

In another news, mgba 0.9.0 standalone (for Wii) has been released too, with many new features.

Nice! Here are the Wii U-specific changes:

• WIIU/FILEIO/PERFORMANCE: Faster startup times – remove the path_is_valid() call when loading textures
• WIIU: Fix touchscreen mouse emulation

Hello there, I'm trying to get Taito F3 games to work on retroarch. I really don't know why since it shouldn't be a difficult system to emulate, but I'm getting DSI error on mame2003 with any rom, and huge performance issues on final burn neo (I'm talking like 2fps on puzzle bobble 2 game). I tried other games on final burn neo and they work fine (puzzle bobble 1, metal slug ecc.). Is anyone able to play Taito F3 smoothly on RA Wii U?

I just tried a handful of them on MAME 2003 and they mostly worked fine. Riding Fight didn't have audio but seemed to play alright. Puzzle Bobble 2 didn't have any issues as far as I could tell and had no slowdown.

I'm assuming you're using the same ROMs for both cores? Some ROMs might work that way but it's really hit or miss since each MAME version looks for different files. The MAME 2003 core is based on MAME 0.78, so you'll need to rebuild your ROMs with a MAME 0.78 DAT if you want to play them on that core. I recommend using ROMVault if you're new to ROM auditing.

I did see the slowdown on the FB Neo core. FB Neo is more accurate but much more resource-intensive, so it's just going to be slower with some games. I usually just stick to MAME 2003 unless I find a game that doesn't work.

 

[MikaDubbz]

Yes! Touch screen mouse fix is something I've been waiting for, can finally play Scumm games as I've desired on the Wii U.

 

[Palindox]

Retroarch 1.9.1 finally released

Still not seeing a fix for allowing all controllers to control menu or allowing any other controller except gamepad to be port 1. If I try to change port 1 in settings to any other controller it disables the gamepad and I have to hard reset.

 

[azy77]

Still not seeing a fix for allowing all controllers to control menu or allowing any other controller except gamepad to be port 1. If I try to change port 1 in settings to any other controller it disables the gamepad and I have to hard reset.

Damn, will give this a miss then.

 

[Gabberhead]

Still not seeing a fix for allowing all controllers to control menu or allowing any other controller except gamepad to be port 1. If I try to change port 1 in settings to any other controller it disables the gamepad and I have to hard reset.

i dont know why it take s so long to fix it. last working version was 1.89 from ca 1 year ago. i will staý on 1.89 as long there is no fix for it. i would like to have 1.91, because they fixed the sound problems on pc cd engine .chd files. but without the working controller support, like i said, i will stay on 1.89.

 

[marchrius]

Nice! Here are the Wii U-specific changes:

• WIIU/FILEIO/PERFORMANCE: Faster startup times – remove the path_is_valid() call when loading textures
• WIIU: Fix touchscreen mouse emulation

I just tried a handful of them on MAME 2003 and they mostly worked fine. Riding Fight didn't have audio but seemed to play alright. Puzzle Bobble 2 didn't have any issues as far as I could tell and had no slowdown.

I'm assuming you're using the same ROMs for both cores? Some ROMs might work that way but it's really hit or miss since each MAME version looks for different files. The MAME 2003 core is based on MAME 0.78, so you'll need to rebuild your ROMs with a MAME 0.78 DAT if you want to play them on that core. I recommend using ROMVault if you're new to ROM auditing.

I did see the slowdown on the FB Neo core. FB Neo is more accurate but much more resource-intensive, so it's just going to be slower with some games. I usually just stick to MAME 2003 unless I find a game that doesn't work.

Thank you! I swapped my roms with roms from mame 0.78 romset and now I got F3 working. Since I know very well the originals, I noticed that some sounds are missing from some games (Puzzle Bobble 2, 2X, Elevator Action Returns). I guess this is the best I can get, unless I am missing something (does mame 2003 pick files from a samples folder maybe?)

edit: just tried on pc on the same ancient mame version (0.78) and those specific sounds are missing there as well. So it's probably just due to the fact that mame2003/0.78 is too old and emulation was simply inaccurate back then.

 

[ChiefReginod]

Thank you! I swapped my roms with roms from mame 0.78 romset and now I got F3 working. Since I know very well the originals, I noticed that some sounds are missing from some games (Puzzle Bobble 2, 2X, Elevator Action Returns). I guess this is the best I can get, unless I am missing something (does mame 2003 pick files from a samples folder maybe?)

edit: just tried on pc on the same ancient mame version (0.78) and those specific sounds are missing there as well. So it's probably just due to the fact that mame2003/0.78 is too old and emulation was simply inaccurate back then.

It does use samples but it's mostly for the really ancient games with weird audio hardware.

There are two other cores you could try in older versions:

MAME 2009 (based on MAME 0.135u4) - Was available in 1.9.0.
MAME 2010 (based on MAME 0.139) - It was removed at some point between 1.7.8 and 1.8.1 but it's hard to find those versions. 1.7.7 is archived here.

There's probably some good reason they were removed but it's nice to have options.

 

[Maxbeta]

Why can’t the devs just revert the controller code to the way it was before it broke? Do it at least for the Wii U version and call it a day. What a fucking disappointment.

 

[willianholtz]

I also think so, I was wanting this update for a long time to solve the control problem, but they didn't fix it! Sad.

 

[ploggy]

Why can’t the devs just revert the controller code to the way it was before it broke? Do it at least for the Wii U version and call it a day. What a fucking disappointment.

Perhaps its possible to revert the changes just for WiiU? Someone will have to mention it on the Retroarch Discord.

 

[Maxbeta]

Perhaps its possible to revert the changes just for WiiU? Someone will have to mention it on the Retroarch Discord.

I mean I’m not sure why they changed it in the first place. I’m sure it benefited other systems but it broke the Wii U controller response disabling Wii U pro and Wiimote controllers entirely.

It would definitely be great to let them know how a simple old code replacement just for the Wii U builds could fix this headache. Not sure if it’s been brought up but it’s been present for quite a few revisions so I at least thought they’d knew by now.

 

[ploggy]

I mean I’m not sure why they changed it in the first place. I’m sure it benefited other systems but it broke the Wii U controller response disabling Wii U pro and Wiimote controllers entirely.

It would definitely be great to let them know how a simple old code replacement just for the Wii U builds could fix this headache. Not sure if it’s been brought up but it’s been present for quite a few revisions so I at least thought they’d knew by now.

Is this the commit that's causing the issues?

https://github.com/libretro/RetroArch/commit/1597a6893dae1cb2beaf6d0131aaa9f9a7f0685f

EDIT: better if I post the link huh?

 

[ChiefReginod]

Maybe they just didn't see a reason to mess with the Wii U build if the planned input overhaul would fix it anyway. But did this overhaul ever end up happening? Maybe it got lost in the shuffle after the hack.

I wish it wasn't such an arcane science setting up a proper build environment for the Wii U port.

 

[ploggy]

Maybe they just didn't see a reason to mess with the Wii U build if the planned input overhaul would fix it anyway. But did this overhaul ever end up happening? Maybe it got lost in the shuffle after the hack.

I wish it wasn't such an arcane science setting up a proper build environment for the Wii U port.

I think like you say it was planned but the hack messed the everything up and has been put on the backburner.
I think if the overhaul is still months away we may as well have it reverted for the WiiU port (if possible) until they do the overhaul?

 

[Maxbeta]

Man it would be a godsend if they just provided the old coded before it changed as a temporary fix while they actually finalize the new updated code planned in the first place.

But then again I think all cores after that are very dependent of the new code since I tried updating Genesis Plus GX while on retroarch 1.89 and the core would behave the same way.

What I’m trying to say is I don’t think it’s dependent on just the main frontend controllers code. Each new core since 1.9.1 (I think it was) disregards the native controllers outside the gamepad the same way.

 

[ploggy]

Man it would be a godsend if they just provided the old coded before it changed as a temporary fix while they actually finalize the new updated code planned in the first place.

But then again I think all cores after that are very dependent of the new code since I tried updating Genesis Plus GX while on retroarch 1.89 and the core would behave the same way.

What I’m trying to say is I don’t think it’s dependent on just the main frontend controllers code. Each new core since 1.9.1 (I think it was) disregards the native controllers outside the gamepad the same way.

Yes, once its reverted you'd have to use the news cores that get updated on the build bot

 

[xxThe_Dice_manxx]

Hello.

Is there a way to delete games from the sd card from inside the retroarch menu system?

If not that would be a most handy tool.

Also, getting some micro freeze in the mgba game boy advance can this be fixed or just an expected thing? or is there a better core option?

Thanks