Homebrew Official Retroarch WiiU (wip.)

[AmandaRose]

I just need a working Neogeo Pocket emu than I have everything I need lol.

 

[the_randomizer]

I just need a working Neogeo Pocket emu than I have everything I need lol.

Right, but one thing at a time I suppose, I should know better XD

 

[AmandaRose]

Right, but one thing at a time I suppose, I should know better XD

i know I just thing it's strange the Neogeo Pocket emu is still included when it has not worked from day one but then again when I was being a dick a while ago I had a go at someone for saying the same thing about the psx emu lol. And since I first got my wiiu Neogeo Pocket was the one emulator I really wanted.

 

[ShadowOne333]

I think this might be a factor in the 160-2203 issues people are getting. This is all just guesswork (haven't been able to run the newer builds, let alone replicate the issue!) but I'd say that this standalone RetroArch you guys keep mentioning has an incorrect method of loading a core on startup; which leads to the loader getting fed a bad RPX thus triggering the 2203. My best guess for the trigger at this point is the "libretro_path" section of the config files. Shadow's one looks like the following:

I would think that RA sees that path in the config and attempts to load the core, then (mumble mumble mumble mumble mumble) and the loader throws the 2203. For a quick acid test, can someone remove/clear/fiddle with that line in their config and see how RetroArch reacts? If it will work without loading a core on startup, then that narrows the bug right down.

Yep that seems to have worked.
Basically, I redownloaded the config.rar I posted in the previous page just to be sure, then deleted ONLY the libretro_path setting inside retroarch.cfg (very first line I believe), then loaded up RetroArch, tried loading a ROM normally through the playlists, and it loaded just fine.

Btw Quark, in case you haven't read the other replies, it seems other users are able to avoid the issue by using an individual emulator core to load the playlist, and as long as you have the proper RPX files in /retroarch/cores, switching cores automatically with the playlists seems to work just fine, so it's definitely just the retroarch.rpx which has the issue.
They even took another core like mGBA, renamed it to retroarch.rpx and that seems to be working okay.

 

[worm28]

Yes so following the advice of others here I have deleted the standalone retroarch launcher thingy and replaced it with a renamed mGBA.rpx and no more system memory errors and now the game and watch core I could never get to work now works perfectly. Happy days lol

This also fixes my exception dsi errors when loading roms from the playlist

 

[A Plus Ric]

Btw Quark, in case you haven't read the other replies, it seems other users are able to avoid the issue by using an individual emulator core to load the playlist, and as long as you have the proper RPX files in /retroarch/cores, switching cores automatically with the playlists seems to work just fine, so it's definitely just the retroarch.rpx which has the issue.
They even took another core like mGBA, renamed it to retroarch.rpx and that seems to be working okay.

It fits with his theory though. Retroarch rpx errors trying to load the core. Mgba or core specific rpx doesn't use the configuration to say the default core to use as its preprogrammed to use its own implemented in its rpx.

 

[cucholix]

@Marko76 Atari Lynx no longer hangs when loading a second rom when using a core as the main rpx.

 

[AmandaRose]

@Marko76 Atari Lynx no longer hangs when loading a second rom when using a core as the main rpx.

Ah that's good to know thanks.

 

[Maxbeta]

Any chance somebody talented in coding here that could turn this version of Nestopia into a retroarch core?

http://www.romhacking.net/forum/index.php?topic=24125

 

[A Plus Ric]

Any chance somebody talented in coding here that could turn this version of Nestopia into a retroarch core?

http://www.romhacking.net/forum/index.php?topic=24125

Doubt it.

 

[SleeplessKnight]

Nice to see the progress that's been made. Thanks for all the hard work.

 

[Antonio Soler]

Retroarch 1.6 is out!

 

[Osakasan]

Hey, my photo of the Wii U version is featured on the article :v

https://rompiendomandos.wordpress.com/2017/05/23/xmbc-llega-a-retroarch-en-wii-u/

Not that i care xd

 

[lordelan]

Retroarch 1.6 is out!

Finally the "nice UI"!
I also read that there's native HID support now? That should make the GameCube USB adapter workable?

Has anyone tested if 1.6 is stable? I hope that it is as 1.5 was not and we had to stay on 1.4.1 for weeks... :/

 

[LibretroRetroArc]

It fits with his theory though. Retroarch rpx errors trying to load the core. Mgba or core specific rpx doesn't use the configuration to say the default core to use as its preprogrammed to use its own implemented in its rpx.

Sad to hear this. Is there anybody able to resolve this issue? I am not much familiar with WiiU development.

 

[AmandaRose]

Finally the "nice UI"!
I also read that there's native HID support now? That should make the GameCube USB adapter workable?

Has anyone tested if 1.6 is stable? I hope that it is as 1.5 was not and we had to stay on 1.4.1 for weeks... :/

Tested multiple cores all working great so far.

 

[lordelan]

Tested multiple cores all working great so far.

Woohoo! Sounds promising!
I can't test it before monday but I going to test GameCube controllers right away.

 

[Osakasan]

Woohoo! Sounds promising!
I can't test it before monday but I going to test GameCube controllers right away.

Fucking agreeing here. Quake all day erry day (Because that core works... right?)

Anyway, i'm happy to see the Wii U version as the non PC version with the longest release notes.

 

[ploggy]

Sad to hear this. Is there anybody able to resolve this issue? I am not much familiar with WiiU development.

I think the only people who could is probably @aliaspider and maybe @QuarkTheAwesome.

Also congrats on getting 1.6.0 out the door mate But what happened to the 360 port?
have you stopped supporting it?

 

[LibretroRetroArc]

I think the only people who could is probably @aliaspider and maybe @QuarkTheAwesome.

Also congrats on getting 1.6.0 out the door mate But what happened to the 360 port?
have you stopped supporting it?

I don't have a development 360 anymore.

A guy from Cyprus might be sending one over, until then, the port is dead.