Homebrew Official Retroarch WiiU (wip.)

[A Plus Ric]

This should be fixed as of the next build (at least as far as the crashing is concerned).

That should be all of them swapping right? When trying to set the File Browser it was crashing as well.

 

[Radius4]

build just finished

 

[A Plus Ric]

build just finished

Directory stuff is fixed. Thanks! Retroarch.rpx standalone still just blackscreen though. (I know he wasn't fixing that part on that but just stating the main .rpx does not work need to use others)

 

[ploggy]

As @A Plus Ric says Launching Retroarch.rpx still freezes, but so far I havent had a single DSi Error Loaded roms from different cores constantly.
I'm going to try changing a load of settings to see if I can trigger one


EDIT: Spoke too soon
Got this error messing with the XMB apperance settings @LibretroRetroArc

 

[A Plus Ric]

Have swapped games from multiple cores changing around. Not a single crash. So all the probs possibly are fixed for that stuff. Now to get that darn Retroarch.rpx to load instead of black screen lol.

 

[A Plus Ric]

Hey @ShadowOne333 was it you that told me before? Whats the rewind thing need to be set at for the granularity? If not no big deal. I thought it was 5. but that code dumps when you try to load a gb or gbc game with mGBA. (only at set to 5, back to 2 no dump)

Edit having rewind on code dumps when trying to load a gc game in mGBA.

 

[the_randomizer]

I'm so behind and lost and all what happened as I stepped out for a while.

@A Plus Ric
@ploggy

Can you bring me up to speed? Main RPX still black screening? Crashes? What's going on.

 

[lordelan]

@LibretroRetroArc :
I've got this error after directly loading Chrono Trigger (SNES) while Street Fighter 3 (FB Alpha) was still running:

 

[the_randomizer]

@LibretroRetroArc :
I've got this error after directly loading Chrono Trigger (SNES) while Street Fighter 3 (FB Alpha) was still running:
View attachment 100707

Hmm, most odd indeed Methinks a close-content-when-changing-cores feature is in order.

Edit: Snes9x, 2005, 2002, 2010?

 

[A Plus Ric]

Where

@LibretroRetroArc :
I've got this error after directly loading Chrono Trigger (SNES) while Street Fighter 3 (FB Alpha) was still running:
View attachment 100707

which fbalpha were u using and which snes did you try to load to?

 

[Tarpii]

Hi guys,

Don't want to derail the thread, but can anyone tell me if Retroacrch Wii U supports overlays / shaders at the moment? Any recommendations, I love a good scanline!

 

[QuarkTheAwesome]

I guess I'm officially part of cool club - got a 2203 for the first time today. Deleting snes9x (the last core I loaded) along with retroarch.cfg fixed it for me. I think it was some kind of corruption in the s9x RPX; though what it is is beyond me. The RPX loading code is bad, but it's probably not destructive...

 

[lordelan]

Where

which fbalpha were u using and which snes did you try to load to?

I was using the main FBA (without 2***) and Snes9x.
The games were "Street Fighter 3: Third Strike" on FBA and "Chrono Trigger" on SNES.
I should add that both are running with any issues normally but never tried to open a SNES rom while an Arcade rom is still opened before.

 

[the_randomizer]

I guess I'm officially part of cool club - got a 2203 for the first time today. Deleting snes9x (the last core I loaded) along with retroarch.cfg fixed it for me. I think it was some kind of corruption in the s9x RPX; though what it is is beyond me. The RPX loading code is bad, but it's probably not destructive...

I assume there's no way around that or to fix it up somehow? I was hoping for the crashing to be, you know..

 

[ShadowOne333]

Hey @ShadowOne333 was it you that told me before? Whats the rewind thing need to be set at for the granularity? If not no big deal. I thought it was 5. but that code dumps when you try to load a gb or gbc game with mGBA. (only at set to 5, back to 2 no dump)

Edit having rewind on code dumps when trying to load a gc game in mGBA.

View attachment 100696

Well the thing with the Rewind feature is that it is not compatible with all cores apparently.
For example, I remember I had it on for Mednafen PCE Fast, I used it in Rondo of Blood just for testing purposes, but I got a LOT of DSI Exception errors when I tried even booting other cores, as GBA I believe.

I don't know what's the problem in detail, all I know is that having Rewind enabled crashes some cores on boot, so it is better to just have it off all the time or enable it on a particular play session and disable it after you finished.

 

[the_randomizer]

Well the thing with the Rewind feature is that it is not compatible with all cores apparently.
For example, I remember I had it on for Mednafen PCE Fast, I used it in Rondo of Blood just for testing purposes, but I got a LOT of DSI Exception errors when I tried even booting other cores, as GBA I believe.

I don't know what's the problem in detail, all I know is that having Rewind enabled crashes some cores on boot, so it is better to just have it off all the time or enable it on a particular play session and disable it after you finished.

Have you have a chance to test the latest nightly build?

 

[ShadowOne333]

Have you have a chance to test the latest nightly build?

Not yet, sadly :/
I haven't had time to do any testing, otherwise I'd be all over the place

 

[the_randomizer]

Not yet, sadly :/
I haven't had time to do any testing, otherwise I'd be all over the place

I'm hearing that the main RPX is still wonky (black screen), and loading another works, but also that the crashes are reduced significantly

 

[ShadowOne333]

I'm hearing that the main RPX is still wonky (black screen), and loading another works, but also that the crashes are reduced significantly

That's neat.
Last I remember is that I switched from the main RPX to using individual cores again, I don't remember having issues with that setup so I stuck with it, that was like 2 weeks ago I believe or more.

 

[LibretroRetroArc]

OK, I've split up the xmb_draw_items function into two: xmb_draw_items, and xmb_draw_item. When you guys download the next build, the stack trace should give us a clearer understanding of exactly where the crash happens. I've also tried reducing some more on stack size usage in the case the DSI errors come from there.