Homebrew RetroArch - A new multi-system emulator

[the_randomizer]

^^+1 on the memory leak issue as well.
Now if only somebody else could confirm my issues with input delay...

And yet, nothing has been done about said issues, input lag or otherwise.

 

[Toad King]

And yet, nothing has been done about said issues, input lag or otherwise.

Our core switching code needs to go through a refactor to fix a lot of these crashes/hangs on switch. It is on my to-do list.

EDIT: What cores do you get this on specifically? (The one you're switching from)

 

[DJPlace]

LibRetroRetroarch a piece of advice don't let troll's or other people ruin you for your work i think dogway is just riding his own rocket somewhere in his own butt or something your doing a great job on this just give us all support i'm 100% precent on this i just wish there was a one for all core you can load. but it's all right. still i just wish you can play all games on this... also how is the android piece of this comming along?

 

[the_randomizer]

Our core switching code needs to go through a refactor to fix a lot of these crashes/hangs on switch. It is on my to-do list.

EDIT: What cores do you get this on specifically? (The one you're switching from)

I switch from Snes9x Next to Fceu Next or Genplus. It happens regardless of which cores I swap back and forth to, it crashes when any core swapping occurs. The first time, it doesn't happen but the second time, however, is when it crashes. Any info about Snes9x Next performance degrading over time?

 

[Toad King]

I switch from Snes9x Next to Fceu Next or Genplus. It happens regardless of which cores I swap back and forth to, it crashes when any core swapping occurs. The first time, it doesn't happen but the second time, however, is when it crashes. Any info about Snes9x Next performance degrading over time?

Do you get it when you switch from any core that's not Snes9x?

I haven't looked at the snes9x degrading speed. It's a difficult thing to debug since it only happens after hours of play. Does restarting the game reset the speed, and what games is it happening with?

 

[the_randomizer]

Do you get it when you switch from any core that's not Snes9x?

I haven't looked at the snes9x degrading speed. It's a difficult thing to debug since it only happens after hours of play. Does restarting the game reset the speed, and what games is it happening with?

happens regardless of which cores I switch, as for degradation, resetting the emulator itself helps reset the speed. The degrading speed happens on any game, depending on how long I've been playing.

Summary

Core crashing happens regardless of core, but usually after the first or second time.
Degradation happens on any game on Snes9x Next, resetting RetroArch resets the speed.

 

[Toad King]

happens regardless of which cores I switch, as for degradation, resetting the emulator itself helps reset the speed. The degrading speed happens on any game, depending on how long I've been playing.

Summary

Core crashing happens regardless of core, but usually after the first or second time.
Degradation happens on any game on Snes9x Next, resetting RetroArch resets the speed.

One last thing: By crash do you mean you get a code dump and everything, or it just hangs when you try to reload?

 

[the_randomizer]

One last thing: By crash do you mean you get a code dump and everything, or it just hangs when you try to reload?

Yep, pretty standard DSI exception code dump. It doesn't reload as far as I can tell so yeah, it just hangs there forcing me to hard reboot.

 

[Toad King]

Yep, pretty standard DSI exception code dump. It doesn't reload as far as I can tell so yeah, it just hangs there forcing me to hard reboot.

It returns to HBC if you hit A on a gamecube controller. The next release will add a timeout to the coredump for those without GC controllers.

 

[the_randomizer]

It returns to HBC if you hit A on a gamecube controller. The next release will add a timeout to the coredump for those without GC controllers.

But is there a reason it dumps as often as it does? And for the degradation in performance, any leads?

 

[Toad King]

But is there a reason it dumps as often as it does? And for the degradation in performance, any leads?

Like I said, the code needs to be refactored. And the degradation in performance you're describing is almost impossible to debug, since it takes so long to happen.

 

[the_randomizer]

Like I said, the code needs to be refactored. And the degradation in performance you're describing is almost impossible to debug, since it takes so long to happen.

To me it sounds like a memory leak issue, but if it can't be fixed, oh well. But as for the code dumps, that's good news.

 

[sideskroll]

Do you get it when you switch from any core that's not Snes9x?

I haven't looked at the snes9x degrading speed. It's a difficult thing to debug since it only happens after hours of play. Does restarting the game reset the speed, and what games is it happening with?

- The "crash" (freeze, black screen whatever you want to call it) happens when the core switch asks for a reboot. It doesn't matter which core you switch to/from.

- "the degrading speed" or memory leak or whatever that is happens after a long period of use (could be hours. Haven't timed it TBH) and it manifests itself as some sort of stuttering... Like, for example, imagine you're playing a game on your PC and suddenly the disk defrag starts in the background. That kind of stuttering/lag.

- Regarding my issues with the input delay, I don't know if you own or able to get your hands on a Classic Controller, but if you do, try this: Play TOP GEAR 2 (just because that's the one game I can attest lags like sh*t) first with your GC controller and then with the CC. You'll notice the difference immediately.

 

[gameBro]

One last thing: By crash do you mean you get a code dump and everything, or it just hangs when you try to reload?

while changing cores and reloading, my wii crashes. The blue light just stays on and freezes. I have to unplug my wii to do a cold restart.

This happens sometimes

 

[Vague Rant]

You don't have to unplug in those situations, just hold down the Power button on the Wii (not the Wii Remote) for five seconds.

 

[sideskroll]

You don't have to unplug in those situations, just hold down the Power button on the Wii (not the Wii Remote) for five seconds.

^+1

 

[Jacobeian]

Let's just say I've never really liked it being the only choice when one of the releases had a buggy libfat module that corrupted several SD cards/hard drive before I found out the reason. It's one thing to release software that doesn't work, but having your software corrupt user's data is not a nice feeling.

EDIT: That combined with a lot of other things over the years I've used it, leading up to this (possible) input lag issue.

And what do you propose then ? The reason why no alternative exist is because 1) what exists is good enough for most people and has been continuously updated/fixed/etc and 2) nobody ever bothered or was able to propose a different solution for homebrew.
About bugs within libfat/libwiiuse (which are btw separated libs from libogc), well that happens when you release stuff, remember this is jot a paid job, people can make mistakes too and not all edge cases can be tested (i personally never had any issues regarding corrupted sd or controller lags). I feel a little bit ironic that you cannot apply to yourself what you are asking to your user base regarding retroarch bugs and i must say that libogc devs always were much more open to criticism and bug report than what we have been seeing in this thread.

I know there is nothing that can be done against homebrew devs bashing because that's what people like to do but i would have expected from devs themselves a little bit more common sense and respect to what other devs do. All i read in this thread was about how libogc or core xxxx sucks or is too slow or bugged or whatever could avoid putting retroarch in a bad light.

 

[quepaso]

The lag problems that a few of you are having are not from retroarch code. Get that through your skulls. Its due to the libgc code that the homebrew is complied in. If you have issues with lag with CC Pro, take it up with those people who wrote that code. There is nothing retroarch team can do to fix it.

 

[Toad King]

Okay, I'm calling for this to stop now. This has gone on for way too many posts and it won't go anywhere productive. If your posts aren't related to RetroArch then please don't post them in this thread.

 

[Dogway]

"libogc code that the homebrew is compiled in"
my homebrew is 1.0.7 so maybe there's a reason. if sideskroll can confirm he has an old version as well that can clear up many of the questions (why some suffer from lag and others don't)