mupen64plus-libretro-nx icon indicating copy to clipboard operation
mupen64plus-libretro-nx copied to clipboard

[Android] mupen64plus-next GLES3 blackscreen

Open Rando-T opened this issue 3 years ago • 15 comments

Hi there.

I've experienced this issue using both SuperMario64(USA) and SuperMarioKart64(USA) roms. Whenever I'm playing(on a Huawei p10) and I minimize Retroarch, if I go back to it the screen will become black(you can still play; you just cannot see). Restarting the game won't solve the issue. Only closing it does.

I'm using the latest version of the Play Store application, but this was an issue even in older versions(at least 4 iterations if I'm not mistaken).

This is my first post here, so I apologise if I haven't provided enough information. Please do tell me if more is needed. Thank you.

Rando-T avatar Jul 26 '21 11:07 Rando-T

What is the behaviour on other GL cores? I never heard of that, if its phone specific i fear I might not be able to help you. Good chance this is frontend too

m4xw avatar Jul 26 '21 11:07 m4xw

On GLES2 it crashes as soon as I start a rom. A friend on Discord, on GLES3 experiences the same thing(crash), while I, only a black screen. What other info can I provide to help with reporting the issue?

On Mon, 26 Jul 2021, 13:34 m4xw, @.***> wrote:

What is the behaviour on other GL cores? I never heard of that, if its phone specific i fear I might not be able to help you. Good chance this is frontend too

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/libretro/mupen64plus-libretro-nx/issues/364#issuecomment-886623406, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANPGG7ZGH2Y27CT5IJGRCADTZVB45ANCNFSM5A74YPXA .

Rando-T avatar Jul 26 '21 13:07 Rando-T

Description

While using Mupen64Plus-Next, switching apps and then returning to RetroArch results in a black screen or (rarely) a force close. Using default settings, shaders disabled.

Steps to reproduce the bug

  1. Open RetroArch, load and run N64 rom.
  2. Switch to another app (e.g. phone dialer or web browser).
  3. Switch back to RetroArch.

Expected behavior

The game should be able to continue where it left off, like the rest of the cores do.

Actual behavior

Display is black when resuming a game. Audio continues to play as it should and controllers still work. Sometimes RetroArch will crash as soon as it opens.

Version/Commit

RetroArch Plus (1.9.8) from Play Store Mupen64Plus-Next GLES3 (2.3-Vulkan ecfc77e)

Environment information

OxygenOS 11.2.7.7 (Android 11) battery optimization disabled

kp8888 avatar Aug 19 '21 04:08 kp8888

On Odin Pro (Snapdragon 845, Adreno 630, 8GB RAM) a get a similar issue when using the Parallel core, but on Mupen64Plus-Next GLES3 it crashes on minimize, sleep etc. retroarch__2022_05_18__12_27_35.log

Debug level log attached, there's no indicator of what could be wrong. I'll try to set up ADB debugging and check why the application is crashing.

doctor-amaton avatar May 19 '22 13:05 doctor-amaton

Did anyone get to the bottom on this? Facing this on my Retroid Pocket 3+ too using glcore

alondero avatar Jan 11 '23 23:01 alondero

Did anyone get to the bottom on this? Facing this on my Retroid Pocket 3+ too using glcore

I haven't had a chance to jump into it. Might be able to do so next week... I think the rice and angrylion RDP plug-ins don't show that behavior, so you can probably try them for now (rice is visually buggy and I don't think the RP3+ has enough cpu for angrylion though)

doctor-amaton avatar Jan 12 '23 01:01 doctor-amaton

Did anyone get to the bottom on this? Facing this on my Retroid Pocket 3+ too using glcore

I haven't had a chance to jump into it. Might be able to do so next week... I think the rice and angrylion RDP plug-ins don't show that behavior, so you can probably try them for now (rice is visually buggy and I don't think the RP3+ has enough cpu for angrylion though)

Forgot to reply back to this. Like you thought this issue doesn't happen with angrylion (though not usable on a Retroid Pocket 3+).

alondero avatar Jan 23 '23 22:01 alondero

Experiencing this issue as well on a Pixel 7. Exact same behaviour as @Rando-T: Crash when attempting to use GLES2. Issue not present with Angrylion.

ericjessee avatar Apr 25 '23 15:04 ericjessee

I experienced the same issue

Device : Samsung Galaxy s21 Ultra 5G Android Version : 13

Retroarch Version : 1.16.0 Git Version : 14cb373 Build Date: October 2 2023

Using Mupen64Plus-Next GLES2, the games crash on startup.

Games : Tested on OOT (U) V1.2 and Starfox64 (U) V1.1. The issue doesn't seams to be game-specific.

Core : Mupen64Plus-Next GLES3 Core Version : 2.5-Vulkan 26fd1ed

On GLES3 : On RPD Plugin GlideN64 Minimizing any game and coming back to it cause the screen to be completely black, sounds and input continue to perform as expected. Nothing short of a full Retroarch restart fix the issue.

The issue is not present on RPD Plugin Angrylion or ParaLLEI-RDP, but the performance and render quality difference is very steep, making these options unattractive (parameter problem ? I used default).

RedYggdrasil avatar Nov 18 '23 09:11 RedYggdrasil

I have the same issue, webOS (v22) configured with GLES2, game crashes on startup.

It creates a core dump however.

Log: https://pastebin.com/cPNZ8dPC

Use angrylion works, but its slow.

Edit: Just tried GLES v3 and it works awesome :+1:

csdougliss avatar Feb 24 '24 21:02 csdougliss

Experiencing same issue. Android 11, Retroid Pocket 2S Retroarch 1.17.0 Mupen64Plus-Next GLES3

Launch a game then either switch apps or put the device to sleep and when you return you get a black screen with the audio/gameplay still continuing. All default settings on core. Battery optimization turned off for RA.

This issue does not occur when changing RDP to Angrylion or Parallel. But instead a different issue occurs where RA stops responding to my controller.

yotengodormir avatar Mar 22 '24 01:03 yotengodormir