Launching Mupen64plus GLES3 or Parallel64 Retroarch cores through Daijisho causes inputs to not register

[AncientCarthage]

I encountered this glitch two days ago, if you launch a game through Daijisho when M64P GLES3 or Parallel64 is selected, the controls on your device will no lomger register, or if they do, they will register in an extremely delayed manner. This effect persists even when not launching a game through Daijisho, as long as you do it once the effect will persist. The only fix I've found is to completely uninstall retroarch and all of its installation folders, then reinstalling it.

[Jetup13]

This is a known issue when launching into the N64 corrs from a front-end. Here's the issue being mentioned back in 2016

Launching the Retroarch Quick Menu restores the controls. I'll recommend creating an touch screen overlay

[stuffu]

I also encountered this, I guess the issue is in RA rather than the frontend or emulator itself?

[TapiocaFox]

I also encountered this, I guess the issue is in RA rather than the frontend or emulator itself?

Seems like it.

[stuffu]

@AncientCarthage Trying to narrow it down with the help from RA, which device are you using when you experience the issues with inputs not registering? I have a Retroid Pocket 3+ myself.

[stuffu]

@magneticchen It could be device specific or a Daijishou issue, do you have any possibility to test this on a different device than Retroid Pocket? libretro/RetroArch#15109 (comment)

[TapiocaFox]

Hello. I've tried it myself seems like the core has several issues with several games.

[stuffu]

Hi, RA thinks it's the device mistself. Can you specify the bugs in the core, that might help out finding the issue.

[delta62]

I'm seeing similar problems on an Odin Lite, Android 11. I posted detailed testing information in the linked thread. From what I can tell this is not a Daijishou issue since I can repro the exact same problem with LaunchBox. I'm wondering for others experiencing this problem - do other front ends have the same issue with RA?

[Jetup13]

The issue is most likely how RetroArch starts to recognize a controller connected. It's inconsistent between games & controllers on the N64 cores when launched from a front-end.

Here's the apparent fix:

Open RetroArch by itself > Settings > Input > Polling Behavior > Early > Save Configuration

Or if you want to save it per core

RetroArch Quick Menu > RetroArch Main Menu > Settings > Input > Polling Behavior > Early > RetroArch Quick Menu > Overrides > Save Core Override

I tested it on my end with Rogue Squadron (since that's the only game I can get to always reproduce the issue) and it seems to work.

If your still following this issue try the setting mentioned above and see if it works.

[Jetup13]

Closing this issue as the above message fixes the issue when launched from a frontend