Homebrew Official Retroarch WiiU (wip.)

[the_randomizer]

Yes that's the problem I have as well worked fine on 1.3.6 but black screens on 1.4.

Please try to name the build or builds where it stopped working, the team will need to know if possible.

 

[AmandaRose]

Please try to name the build or builds where it stopped working, the team will need to know if possible.

I just edited my previous post with the info just as you posted lol.

 

[brienj]

Yes that's the problem I have as well worked fine on 1.3.6 but black screens on 1.4. it worked on every nightly until 1.4 came out.

But are we sure that the core wasn't updated in that same time-frame? I'll go take a look right now.

 

[the_randomizer]

I just edited my previous post with the info just as you posted lol.

Sorry about that

 

[brienj]

I just checked and the core was updated on Dec. 20th. Are you sure you had tried a build after Dec 20th that worked?

I know the appstore had Dec. 17th, until they were all updated to include the multi-controller support.

 

[Columbo2811]

Can anyone get me a question to run sega cd do i have to rename the bios to some specific name? Which bios version to use. Thank you very much in advance

https://wiki.libretro.com/index.php?title=Genesis_Plus_GX

All core info is here
https://wiki.libretro.com/index.php?title=Main_Page

 

[brienj]

I think the best thing to do to try to solve the quake problem, is to build a core version prior to Dec. 20th, and link it to the new Retroarch version, and see if the problem persists or not. I have no way to test these builds though at the moment. I guess I could locate everything needed to use it and test, unless someone else can compile all of this and test it out, before I can. If we can prove the problem is not in the core, then they can fix the issue in the main repo. If the problem is in the core, then we can post the issue there.

BTW, to all people that compile Retroarch, you now need DevKitPPC r29 in order to compile the newest build. DevKitPPC r29 will however break some other things you may already have. Just a warning to you.

 

[the_randomizer]

Do we know if there are any changes to 1.4.0 or a change log? Mostly curious about it.

 

[iannoah440]

NXEngine doesn't save but crashes on mine, are others still having this problem?

 

[cucholix]

I think the best thing to do to try to solve the quake problem, is to build a core version prior to Dec. 20th, and link it to the new Retroarch version, and see if the problem persists or not. I have no way to test these builds though at the moment. I guess I could locate everything needed to use it and test, unless someone else can compile all of this and test it out, before I can. If we can prove the problem is not in the core, then they can fix the issue in the main repo. If the problem is in the core, then we can post the issue there.

BTW, to all people that compile Retroarch, you now need DevKitPPC r29 in order to compile the newest build. DevKitPPC r29 will however break some other things you may already have. Just a warning to you.

I have a working copy of Tyrquake, but I'm not sure what date it's from, not sure if that would help. User roflcopter777 from github needs to narrow the version where it stopped working.

Testing 1.3.6 - TyrQuake v0.62, according the file it was modified las time november 23 ‏‎7:24:24 it's working on my end. I attached it

 

[AmandaRose]

NXEngine doesn't save but crashes on mine, are others still having this problem?

in game saves have been working for a few weeks now but save states still don't work.

 

[brienj]

I have a working copy of Tyrquake, but I'm not sure what date it's from, not sure if that would help. User roflcopter777 from github needs to narrow the version where it stopped working.

Testing 1.3.6 - TyrQuake v0.62, according the file it was modified las time november 23 ‏‎7:24:24 it's working on my end. I attached it

Well if it was working on a build from November 23, then the problem could just as easily be from the core itself, because the core has been updated several times since then. I think the best place to report the issue would be on the core itself, then they can determine where the problem is coming from.

 

[cucholix]

Well if it was working on a build from November 23, then the problem could just as easily be from the core itself, because the core has been updated several times since then. I think the best place to report the issue would be on the core itself, then they can determine where the problem is coming from.

The one ploggy posted is from ‎december 3rd ‏‎19:00:40, is also working on my end too.

I suck at navigating github lol, can you point me out the link where the core issues go?

 

[brienj]

The one ploggy posted is from ‎december 3rd ‏‎19:00:40, is also working on my end too.

I suck at navigating github lol, can you point me out the link where the core issues go?

https://github.com/libretro/tyrquake/issues

 

[depaul]

Dear Retroarch team: It would be great if you could please fix the DSI EXCEPTION error. I get it every time I try to launch a game for the second time.

Thank you very much!

 

[brienj]

Dear Retroarch team: It would be great if you could please fix the DSI EXCEPTION error. I get it every time I try to launch a game for the second time.

Thank you very much!

It was fixed in the newer builds, update your cores.

 

[the_randomizer]

Dear Retroarch team: It would be great if you could please fix the DSI EXCEPTION error. I get it every time I try to launch a game for the second time.

Thank you very much!

The cores on 1/18 were fixed, update them

 

[iannoah440]

in game saves have been working for a few weeks now but save states still don't work.

Just tried the nightly build again and it's still hanging, idk what I am doing wrong.

 

[cucholix]

https://github.com/libretro/tyrquake/issues

Done hopefully we got an answer, I feel like this issue has been dragging too long lol

 

[the_randomizer]

Just tried the nightly build again and it's still hanging, idk what I am doing wrong.

Delete all config files and make new ones, save states are working fine for me.