Homebrew Official Retroarch WiiU (wip.)

[the_randomizer]

It seems to be random though, at least what I've experienced, we better wait until @ShadowOne333 upload his cfg and hopefully Quark find a solution.

Indeed, but something has to trigger it, possibly some kind of memory leak, if anyone can find out what the issue is, it's Quark. I know before I could trigger the error when loading it a second time from a fresh install every time, but the message was the same.

 

[ShadowOne333]

It seems to be random though, at least what I've experienced, we better wait until @ShadowOne333 upload his cfg and hopefuly Quark find a solution.

Two more hours until I get out of work
Then it's debugging time!

 

[Opoth]

Good? news, I just got the same memory error in the MAME 2003 core. I've mostly been using Nestopia which has been fine.

 

[QuarkTheAwesome]

Quick bit of background - 160-2203 means that the loader doesn't like an RPX it's been fed, nothing to do with actual RAM (whenever Nintendo says "system memory", they're referring to NAND). I'll do a full writeup on my hunch when I see Shadow's config, but I think I know the specific thing that triggers the error, though I don't know the root cause.

 

[ShadowOne333]

Quick bit of background - 160-2203 means that the loader doesn't like an RPX it's been fed, nothing to do with actual RAM (whenever Nintendo says "system memory", they're referring to NAND). I'll do a full writeup on my hunch when I see Shadow's config, but I think I know the specific thing that triggers the error, though I don't know the root cause.

Finally out of work, and as promised, here are my config files for RetroArch.
Hope this helps.
I upload both my normal config (config.rar) and a clean config with no modifications made to any settings (configclean.rar).
One thing that might be interesting...
With the clean config, I got a DSI exception instead of the System memory error.
Don't know why the change, but might be worth noticing.

 

[the_randomizer]

Quick bit of background - 160-2203 means that the loader doesn't like an RPX it's been fed, nothing to do with actual RAM (whenever Nintendo says "system memory", they're referring to NAND). I'll do a full writeup on my hunch when I see Shadow's config, but I think I know the specific thing that triggers the error, though I don't know the root cause.

That sounds pretty serious if it doesn't like the RPX being read, should we let the developers know though so they can look into it as well?

 

[Giamon]

I'd like to go back to a 22 May nightly build where I hadn't been receiving dsi errors when running Retroarch for a second time. As opposed to deleting my cfg file on every instance where I want to run the application, can someone please point me in the direction of where I can find a 22 May build. The oldest nightly build on buildbot is now 26 May.

In the event that I still receive no dsi errors with an older nightly build, then logic - which doesn't always prevail - tells me that the difference would be with a certain change that had been implemented between 22 May - 25 May.

 

[the_randomizer]

I'd like to go back to a 22 May nightly build where I hadn't been receiving dsi errors when running Retroarch for a second time. As opposed to deleting my cfg file on every instance where I want to run the application, can someone please point me in the direction of where I can find a 22 May build. The oldest nightly build on buildbot is now 26 May.

In the event that I still receive no dsi errors with an older nightly build, then logic - which doesn't always prevail - tells me that the difference would be with a certain change that had been implemented between 22 May - 25 May.

Let me know if this works

https://drive.google.com/file/d/0B1i3usEfPbYrOUlqSWVtRGMyTVE/view?usp=sharing

 

[Giamon]

Thanks mate - the download link worked. Unfortunately, I'm still receiving a dsi error on the second boot of retroarch, but only when launching a rom.

As discussed previously, deleting the .cfg file rectifies this, but only 'til I attempt to launch a rom. Irrespective of the core / rom, a dsi error is present. Looks like I may need to go back to a stable build :/

 

[A Plus Ric]

Finally out of work, and as promised, here are my config files for RetroArch.
Hope this helps.
I upload both my normal config (config.rar) and a clean config with no modifications made to any settings (configclean.rar).
One thing that might be interesting...
With the clean config, I got a DSI exception instead of the System memory error.
Don't know why the change, but might be worth noticing.

Did you ever try loading a separate core rpx instead of the main retroarch one after u exit retroarch and see if it crashes or not? Never saw a response to it.

 

[ShadowOne333]

Did you ever try loading a separate core rpx instead of the main retroarch one after u exit retroarch and see if it crashes or not? Never saw a response to it.

Haven't tried that yet.
That was my setup before the XMB update, if this issue continues I will try the individual cores next.

 

[A Plus Ric]

Haven't tried that yet.
That was my setup before the XMB update, if this issue continues I will try the individual cores next.

Point being, even with other cores you can still use playlists and load other cores from them. I just wanted to see if it was ONLY the main retroarch Rpx having the system memory....like mine does.

Because then it might not be a configuration issue. Unless it's way the retroarch rpx handles it.

 

[ShadowOne333]

Point being, even with other cores you can still use playlists and load other cores from them. I just wanted to see if it was ONLY the main retroarch Rpx having the system memory....like mine does.

Because then it might not be a configuration issue. Unless it's way the retroarch rpx handles it.

Wait so you are saying you can use any other core like FCEUMM for example, and then load a game from another playlist/core in it, and then the proper core is selected automatically?
I thought onlythe main RetroArch app could do that.

 

[A Plus Ric]

Wait so you are saying you can use any other core like FCEUMM for example, and then load a game from another playlist/core in it, and then the proper core is selected automatically?
I thought onlythe main RetroArch app could do that.

I open mgba usually and load right to other cores from it and use playlists. It's why the retroarch main rpx not working isn't bothering me lol

 

[ShadowOne333]

I open mgba usually and load right to other cores from it and use playlists. It's why the retroarch main rpx not working isn't bothering me lol

My whole life has been a lie

 

[Giamon]

Bingo! A Plus Ric was on the money.

As opposed to using 'Retroarch' from HBL to launch the emulator, instead, I used Snes9x and loaded multiple games / other cores without any hiccups. I've been trying to break it in order to replicate the dsi error but to no avail. It seems to only occur when launching 'Retroarch.'

 

[Opoth]

Manually switching between cores should be a thing of the past. The RA forwarder channel just loads the most recently used RPX at the start of the session and loading a ROM or ISO from a playlist automatically loads the correct core of whichever ROM you decided to load (since you are specifying the exact core for each ROM when you generated the playlist) - picking a core at random from the HBL and then relying on the playlists to handle your core switching (described above) is the next best option.

If you played your cards right, you should have a seamless multisystem emulator on your Wii U, launchable right from your official channels. Everything is working for me on the 5/25 builds aside from a memory error in MAME 2003 (need to test that again to see if it was a one off) - but Nestopia, PCE Fast, Final Burn Alpha and the Sega emulator have all been consistent performers so far over the past few days.

 

[wicksand420]

Manually switching between cores should be a thing of the past. The RA forwarder channel just loads the most recently used RPX at the start of the session and loading a ROM or ISO from a playlist automatically loads the correct core of whichever ROM you decided to load (since you are specifying the exact core for each ROM when you generated the playlist) - picking a core at random from the HBL and then relying on the playlists to handle your core switching (described above) is the next best option.

If you played your cards right, you should have a seamless multisystem emulator on your Wii U, launchable right from your official channels. Everything is working for me on the 5/25 builds aside from a memory error in MAME 2003 (need to test that again to see if it was a one off) - but Nestopia, PCE Fast, Final Burn Alpha and the Sega emulator have all been consistent performers so far over the past few days.

I recommended using the wup retroarch channel before, as i said, i haven't had this problem at all, but the channel only is really plausible if you have CBHC.

 

[ShadowOne333]

I recommended using the wup retroarch channel before, as i said, i haven't had this problem at all, but the channel only is really plausible if you have CBHC.

The thing is that the official RetroArch builds are either RPX/ELF formats, there is no official installable channel for it afaik.
So when it comes to debugging the issue, using the channel version is not suitable.

 

[wicksand420]

The channel doesn't use anything located inside the apps folder, it only loads the rpx cores found in retroarch/cores. i think the problem stems from the apps folder.
Also it autoloads the last core you used.