Homebrew Official Retroarch WiiU (wip.)

[willianholtz]

This was fixed a version or two back. You're gonna have to find a more current download.

Above I said I already downloaded the most current 1.9, but it doesn't work!

 

[ChiefReginod]

Above I said I already downloaded the most current 1.9, but it doesn't work!

Confirm that it says "1.9.0" in the bottom left corner like in the attached image. If that checks ok, try deleting retroarch.cfg. If that doesn't work, backup the retroarch folder and try it with a fresh install.

 

[the_randomizer]

How stable is 1.9.0 on Wii U? I haven't used RA on Wii U in at least a couple of years or so.

 

[ChiefReginod]

How stable is 1.9.0 on Wii U? I haven't used RA on Wii U in at least a couple of years or so.

I haven't encountered any crashes on 1.9.0 outside of certain arcade games. It feels pretty "stable" overall. Ozone works now as well.

However, it feels like it got a little slower to load ROMs within the past one or two versions. Even with the mitigations discussed several pages back (ie, remove the "info" and "assets" folders, don't use playlists or history, manually load cores and ROMs), it still seems to take a few seconds longer than it did around 1.8.5 or so. I think there were some recent changes to the way ROMs are loaded that might account for this.

Also, turning Achievements on slows most cores down to the point of being unplayable now. I don't know what changed, and maybe it's just my own setup, but at one point it was usable and now it's not.

I'm thinking of going back a few versions myself.

 

[the_randomizer]

I haven't encountered any crashes on 1.9.0 outside of certain arcade games. It feels pretty "stable" overall. Ozone works now as well.

However, it feels like it got a little slower to load ROMs within the past one or two versions. Even with the mitigations discussed several pages back (ie, remove the "info" and "assets" folders, don't use playlists or history, manually load cores and ROMs), it still seems to take a few seconds longer than it did around 1.8.5 or so. I think there were some recent changes to the way ROMs are loaded that might account for this.

Also, turning Achievements on slows most cores down to the point of being unplayable now. I don't know what changed, and maybe it's just my own setup, but at one point it was usable and now it's not.

I'm thinking of going back a few versions myself.

I haven't used RA on Wii U since 1.6.0 (yes, it's been that long) and I got a lot of DSI exception errors forcing a hard reboot *shrug*. Will probably use Wii U mostly for DS, N64 and GBA injections, but I can try RA later maybe.

 

[willianholtz]

Confirm that it says "1.9.0" in the bottom left corner like in the attached image. If that checks ok, try deleting retroarch.cfg. If that doesn't work, backup the retroarch folder and try it with a fresh install.View attachment 222042

No way, even updating by downloading version 1.9, it doesn't change! And the ozone drive doesn't work!

 

[ChiefReginod]

Here's a download link for 1.9.0 stable (RPX version).

link

Downloaded from libretro.com shortly after the official release.

EDIT: See post #9174079 below.

 

[willianholtz]

Here's a download link for 1.9.0 stable (RPX version).

https://mega.nz/file/KNVAVKob#UncE_6TBpQVuwNS1avzL6-2H4S3EWOZ4pHjPhGlKLVA

Downloaded from libretro.com shortly after the official release.

Gosh, I even managed to update now, but I had to delete everything. Even your upload was the same as I already had here. But the pro control doesn't work!

EDIT:

Well I found the error, I should update all the cores I had, but I had to "update" to version 1.8.9 because version 1.9 did not work my control, even remapping the buttons.

 

[the_randomizer]

Gosh, I even managed to update now, but I had to delete everything. Even your upload was the same as I already had here. But the pro control doesn't work!

EDIT:

Well I found the error, I should update all the cores I had, but I had to "update" to version 1.8.9 because version 1.9 did not work my control, even remapping the buttons.

You're supposed to delete the config file when upgrading to a new version

 

[cugel]

I'm pretty sure Stellaview games load up just like any other SNES game. I've loaded them up but haven't really played any.

 

[SnakeEater]

try mame_2003 or fb_alpha2012

Already tried this.

 

[ChiefReginod]

Can someone help getting "Machbreakers" to running? I tried every Mame Core but black Screen or Bad Code Dump.
Would be really cool to play this game again on the wii u

I just gave it a try with proper ROM sets.

MAME 2003: Works, but no sound.
MAME 2009: Crashes RetroArch.
FBA Alpha/Neo/2012: The game isn't even listed in their ROM set DATs, so not an option.

To get it to boot with MAME 2003 you'll need the MAME v0.78 version of the ROM. If you're using a different version of the ROM it probably won't work.

 

[ZiRoN321]

Well I found the error, I should update all the cores I had, but I had to "update" to version 1.8.9 because version 1.9 did not work my control, even remapping the buttons.

Had the same issue with the Pro Controller yesterday after update, it wouldn't work as primary. Plus, on v1.8.9 they removed the "all users control menu" setting, which on top of the former, effectively disables all input as soon as you remove the Gamepad from the slot 1 config (having to force shut down the console and edit config file manually).

So I am staying on v1.8.8 for now.

Also, most versions are indexed by the Wayback Machine (just feed the direct link to the version you want).

 

[ChiefReginod]

Also, most versions are indexed by the Wayback Machine (just feed the direct link to the version you want).

Oh, cool! Thanks for the tip.

Here's the archive link to 1.9.0:
https://web.archive.org/web/2020081...m/stable/1.9.0/nintendo/wiiu/RetroArch_rpx.7z

If you need a different version you only need to edit the version number in the URL and it should default to the latest date that the file was archived.

 

[cugel]

Already tried this.

Try Finalburn Neo, and if that doesn't work all the other MAME cores.

If that doesn't work, you need to download a rom set that matches one of the cores available to you. MAME isn't like other emulators, when better dumps of arcade machines are created, MAME stops supporting the old dumps. This means that if your rom is too old or too new for the version of MAME you're using, it will not run.

edit: oops I see ChiefReginod already covered this.

edit edit: I just loaded up the 0.78 romset of Machbreakers with MAME_2003 on Windows 10 and it says upfront there is no sound emulation. I think you are probably sol.

 

[ShadowOne333]

I haven't encountered any crashes on 1.9.0 outside of certain arcade games. It feels pretty "stable" overall. Ozone works now as well.

However, it feels like it got a little slower to load ROMs within the past one or two versions. Even with the mitigations discussed several pages back (ie, remove the "info" and "assets" folders, don't use playlists or history, manually load cores and ROMs), it still seems to take a few seconds longer than it did around 1.8.5 or so. I think there were some recent changes to the way ROMs are loaded that might account for this.

Also, turning Achievements on slows most cores down to the point of being unplayable now. I don't know what changed, and maybe it's just my own setup, but at one point it was usable and now it's not.

I'm thinking of going back a few versions myself.

The ROMs taking longer to boot (iirc) was because of some cap that WiiU homebrew still hasn't addressed in terms of memory management.
Try changing the menu driver to something simple like RGUI, and then try booting a ROM that way.
It should load way faster with that.

 

[cugel]

The inclusion of MAME_2009 as a core is really weird, as I can barely find evidence that the core exists, much less a romset for it. I tried a copy of Machbreakers from the commonly shared 2010 romset here:

-snip-

But it also crashes.

 

[ChiefReginod]

The inclusion of MAME_2009 as a core is really weird, as I can barely find evidence that the core exists, much less a romset for it. I tried a copy of Machbreakers from the commonly shared 2010 romset here:

(link)

But it also crashes.

MAME 2009 uses the v0.135u4 ROM set. You can usually find the corresponding version numbers in the info files for each core.

Also, wasn't 2010 on the Wii U at some point?

 

[Sonic Angel Knight]

So, someone wants to explain this?

For the record, using 1.9.0 snes9x (1.6.0) and this only happens when Hi-res mode and Blargg NTSC Filter both active. Having one or the other won't make this happen.

Which means I either have to turn off the Blargg ntsc filter, or turn off high res mode.

 

[the_randomizer]

So, someone wants to explain this?

View attachment 222260


For the record, using 1.9.0 snes9x (1.6.0) and this only happens when Hi-res mode and Blargg NTSC Filter both active. Having one or the other won't make this happen.

Which means I either have to turn off the Blargg ntsc filter, or turn off high res mode.

The game is weird in that it uses the rarely used 512 x 256 (I think?) or 512 x 224, etc mode, why it does that in this case is anyone's guess. Weird.