Homebrew Official Retroarch WiiU (wip.)

[ploggy]

Can you take some scrshot of the dsi error ?and is it always the same?

King quest 6 and 7 both share the same DSI Error... The Error happens as soon as you load either game.

 

[the_randomizer]

I erroneously thought all DSI crashes were resolved.

 

[ShadowOne333]

I erroneously thought all DSI crashes were resolved.

This is different, it's for the scummvm core, which hasn't been touched upon as much as the others

 

[ploggy]

I erroneously thought all DSI crashes were resolved.

I think this is ScummVM specific

 

[SG854]

I erroneously thought all DSI crashes were resolved.

O really? That means I can switch any game, any console, and as many times as I want and no crashes?
The crashing issue has finally been resolved?

 

[ShadowOne333]

O really? That means I can switch any game, any console, and as many times as I want and no crashes?
The crashing issue has finally been resolved?

There has not been any notable cases of crashes when changing roms lately that I recall.
I can't speak for myself as I haven't tried the latest nightlies, but I assume no complaints = no crashes.

 

[the_randomizer]

O really? That means I can switch any game, any console, and as many times as I want and no crashes?
The crashing issue has finally been resolved?

I don't know, that's what I'm trying to find out. I haven't used RA in some time.

 

[QuarkTheAwesome]

I erroneously thought all DSI crashes were resolved.

You'll never get them all, since DSIs are just how bugs manifest. Think of it like the check engine light in a particularly badly-made car - any number of problems can cause it to come on. Sometimes a specific problem will cause it to turn on constantly; but if you fix it the light can still come on for a different, unrelated problem. So yes, some of the root causes may have been fixed, but others will still show up.
(Programmers: they're segfaults.)

 

[ShadowOne333]

You'll never get them all,

That's not how a true Pokemon master thinks.

 

[the_randomizer]

You'll never get them all, since DSIs are just how bugs manifest. Think of it like the check engine light in a particularly badly-made car - any number of problems can cause it to come on. Sometimes a specific problem will cause it to turn on constantly; but if you fix it the light can still come on for a different, unrelated problem. So yes, some of the root causes may have been fixed, but others will still show up.
(Programmers: they're segfaults.)

Well, maybe I just won't use RA nearly as much if it's going to be so unstable *sigh* It's incredibly frustrating to wait for the Wii U to load up, enable sigpatches/CFW, then loading RA. If only the DSI errors would time out. Never gonna happen though.

 

[AmandaRose]

Well, maybe I just won't use RA nearly as much if it's going to be so unstable *sigh* It's incredibly frustrating to wait for the Wii U to load up, enable sigpatches/CFW, then loading RA. If only the DSI errors would time out. Never gonna happen though.

Its not so unstable as you are claiming i have been using retroarch for several hours a day the last few weeks and had one dsi error the whole time.

 

[the_randomizer]

Its not so unstable as you are claiming i have been using retroarch for several hours a day the last few weeks and had one dsi error the whole time.

I'm talking loading ROMs back to back, changing the cores back to back; there was a time doing even one or two changes made RA very unstable to use.

 

[AmandaRose]

I'm talking loading ROMs back to back, changing the cores back to back; there was a time doing even one or two changes made RA very unstable to use.

Yes and that is what i have been doing and only had 1 dsi error.

 

[the_randomizer]

Yes and that is what i have been doing and only had 1 dsi error.

But how frequently? Loading from the directory or from playlists? Auto-detecting core or manually choosing it? See, any combination of these can make it crash, and that concerns me.

 

[AmandaRose]

But how frequently? Loading from the directory or from playlists? Auto-detecting core or manually choosing it? See, any combination of these can make it crash, and that concerns me.

I use a combination of all of the above. Plus change game regularly as have about 20000 roms on my sd card for various systems and i am trying to see which ones are worth keeping or are not working ect

 

[QuarkTheAwesome]

Well, maybe I just won't use RA nearly as much if it's going to be so unstable *sigh* It's incredibly frustrating to wait for the Wii U to load up, enable sigpatches/CFW, then loading RA. If only the DSI errors would time out. Never gonna happen though.

I think you misunderstood me.

Have you ever had this happen?

How about this one?

It's a royal pain when these happen, but something you have to understand is that these are only indicators of an error; not the actual errors themselves. They tell you what happened and stop whatever bad thing is happening to prevent untold horrors. Microsoft can fix whatever specific error happened that specific time; but the laws of programming state that there is always another bug and these error messages will eventually show up again, caused by some completely unrelated problem in a completely different program. As programmers, we have a responsibility to fix as many bugs as we can; but expecting perfection is crazy. Despite having millions of man-hours and billions of dollars poured into it, Windows still crashes. Linux still has privilege escalation bugs.
One may look at that and say that the crashes will never be fixed, but that's the wrong way of looking at it. A bug causes a crash, and a bug can be fixed. Once a bug is fixed, it (hopefully) won't cause any more crashes. Do crashes still happen? Yes, but you've plugged one hole, patched one flaw. There's one less problem causing crashes, and they become slightly less frequent. You move onto the next bug, and you'll soon get to the point where bugs start to be rare, and crashes infrequent. They still happen. Crashes still come, but you try your damnedest to stomp the causes of many of them as you can; and catch new ones on the way in.
So, when I say "you can't patch every bug" I don't mean that the crashes will still come at the same rate they did when core switching was broken. I mean that there will always be some weird, obscure thing which sets off the chain of events leading to a crash. The goal is never to eradicate every bug; it's to deal with every known bug. As things are brought to attention, they are dealt with. Two days ago, we didn't know there was a problem with ScummVM - and thus couldn't have dealt with it - but now that we know, the process of fixing the root bug can begin.
Think of it this way - Core switching issues could have been described as "I open and close the program a few times and it crashes", right? IIRC GenPlusGX was a particularly bad offender. This current, unrelated bug? "I use the program on this specific core, with this specific game, and it crashes". That's going to happen less frequently than people simply opening GenPlusGX; and is going to have less of an impact on people. Crashes are getting rarer, we're making progress. The particular bug that was causing problems on a GenPlusGX core switch has been patched, so fewer people are encountering crashes.

So yeah. Fixing every bug is an unattainable goal, but making them as rare as possible is definitely worth working towards.

(P.S. When trying to judge program stability, keep in mind the reverse survivorship bias you get in these threads. Happy customers don't post error screens.)

 

[the_randomizer]

@QuarkTheAwesome My apologies, I'm know next to nothing regarding the nature of programming, and I have been following the thread, at least, somewhat recently and have found that many major bugs have been neutralized. I know that not all of them can be eliminated; the problem with the DSI error codes, is that to the average user, the error messages are Greek to them, and aren't indicative of what kind of error had occurred, if that makes sense. I know in Windows 7 and 10, BSOD error messages will display, but have a countdown to where it will automatically reboot the system. I wish the Wii U homebrew scene would somehow implement such a feature, so restarting would be a little less of a hassle, you know? I doubt such a thing is feasible on Wii U.

 

[ploggy]

It would be good if it were possible to reset on DSI Error like the original Wii. Save's me getting up, walking to the WiiU to hard reset over and over

 

[the_randomizer]

It would be good if it were possible to reset on DSI Error like the original Wii. Save's me getting up, walking to the WiiU to hard reset over and over

Right, it would be nice to have a similar feature, but I don't know if the Wii U is capable given that there's not nearly as much people involved in the scene. BSODs have it, Wii U should as well.

 

[ploggy]

Right, it would be nice to have a similar feature, but I don't know if the Wii U is capable given that there's not nearly as much people involved in the scene. BSODs have it, Wii U should as well.

I dunno, just throwing it out there again