Retroarch: WiiU RGUI broken

[fr500]

First and foremost consider this:

• Only RetroArch bugs should be filed here. Not core bugs or game bugs
• This is not a forum or a help section, this is strictly developer oriented

Description

RGUI is completely broken on WiiU (black screen)

Expected behavior

For it to work, it's the only driver that can look fine in both the gamepad and the TV at the same time

Actual behavior

When you change to RGUI and reset you are greeted by a black screen, you can press UP->A to quit so it's not hanging, just not rendering

Steps to reproduce the bug

1. [First step]
2. [Second step]
3. [and so on...]

Bisect Results

[Try to bisect and tell us when this started happening]

Version/Commit

You can find this information under Information/System Information

• RetroArch: 1.7.7 20aff2a05aabfe1423b89682f44859e957080a77

Environment information

• OS: [The operating system you're running]
• Compiler: [In case you are running local builds]

[orbea]

@jdgleaver Do you know the current status of this?

[fr500]

According to
https://gbatemp.net/threads/retroarch-wiiu-wip.447670/page-562#post-8662864
it should be fixed

On Tue, Jun 4, 2019 at 9:55 AM orbea [e-mail] wrote:

@jdgleaver https://github.com/jdgleaver Do you know the current status
of this?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/libretro/RetroArch/issues/8852?email_source=notifications&email_token=AANEFUFGHUGSDVRANRWB5YLPYZ663A5CNFSM4HPXOMKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW42Z2Y#issuecomment-498707691,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANEFUEQOJNHHSCVRMARPXDPYZ663ANCNFSM4HPXOMKA
.

[jdgleaver]

Yeah - QuarkTheAwesome fixed it with this: https://github.com/libretro/RetroArch/pull/8908

There are still some transparency issues to resolve, however.

(I don't have a WiiU, so can't test this myself!)

[orbea]

Thanks for the info! @QuarkTheAwesome Do you want to track the transparency issues here or should this issue be closed now?

[QuarkTheAwesome]

nah, I'll probably file a seperate issue for that. It doesn't quite deserve bug:major ;D

[orbea]

Good point, I'll close this one then, thanks for the fix!