Homebrew Official Retroarch WiiU (wip.)

  • Thread starter Thread starter aliaspider
  • Start date Start date
  • Views Views 2,689,560
  • Replies Replies 15,197
  • Likes Likes 93
After a restart each core that failed worked fine?

It seems to fail a few cores in and it never fails directly after a restart, maybe a memory leak? I dunno.
Yeah perhaps a leak.
One more thing, are the failing cores giving you DSI errors or Memory errors (160-2260 I think)?
 
  • Like
Reactions: ShadowOne333
Strange. I've been loading rom after rom, changing cores and geerally being a dick with my poor Wii U on Retroarch and got a measly DSI error wich i didn't reported because wasn't able to reproduce it. In fact, i found the 1.6.3 version to be extremely stable.
 
Strange. I've been loading rom after rom, changing cores and geerally being a dick with my poor Wii U on Retroarch and got a measly DSI error wich i didn't reported because wasn't able to reproduce it. In fact, i found the 1.6.3 version to be extremely stable.
Yep exactly the same for me since 1.6 I have never had one memory issue or dsi issue and I play retroarch daily for a few hours each day and I. Constantly switching games and cores. If it helps I load it with mocha
 
  • Like
Reactions: Osakasan
I use CBHC with the retroarch forwarder and have not gotten errors in so long, i don't even remember the last time it happened.
 
I use CBHC and boot retroarch through the Homebrew Launcher

I would say load a Core then two roms, then switch to another Core and load another two roms and keep doing that until you have gone through all the Cores you have and see if you get any errors?

Sent from my GT-I9505 using Tapatalk
 
I use CBHC and boot retroarch through the Homebrew Launcher

I would say load a Core then two roms, then switch to another Core and load another two roms and keep doing that until you have gone through all the Cores you have and see if you get any errors?

Sent from my GT-I9505 using Tapatalk

I remember there was a theory for causing these was a conflict with CFW and RetroArch, but I remember being able to reproduce the same error even without CFW enabled (for libfat), so yeah, this is quite baffling. I mean, if it were the case, I'd gladly give up CFW, but then again, read speeds.
 
I remember there was a theory for causing these was a conflict with CFW and RetroArch, but I remember being able to reproduce the same error even without CFW enabled (for libfat), so yeah, this is quite baffling. I mean, if it were the case, I'd gladly give up CFW, but then again, read speeds.
I have massive romlists so cfw is a must for me. Theres no way I could go back to the slow read speeds.

Sent from my GT-I9505 using Tapatalk
 
  • Like
Reactions: the_randomizer

Site & Scene News

Popular threads in this forum