libretro / parallel-n64

Optimized/rewritten Nintendo 64 emulator made specifically for Libretro. Originally based on Mupen64 Plus.
309 stars 128 forks source link

No physical button input when launching from other frontends on android #485 #758

Open unbelievableflavour opened 1 year ago

unbelievableflavour commented 1 year ago

I hope this is the right repo. Sorry if it aint.. I'm having an issue with Parallel-n64. Whenever I launch this particular core from a frontend different from retroarch. I sometimes don't have have input.

Expected behavior core launched from command runs the game with buttons working

Actual behavior core launched from command core runs the game without buttons working. Not even retroarch overlay's and such can be opened.

Steps to reproduce: Launch an instance of parallel using the following config::

-n com.retroarch.aarch64/com.retroarch.browser.retroactivity.RetroActivityFuture
-e ROM {file.path}
-e LIBRETRO /data/data/com.retroarch.aarch64/cores/parallel_n64_libretro_android.so
-e CONFIGFILE /storage/emulated/0/Android/data/com.retroarch.aarch64/files/retroarch.cfg
-e IME com.android.inputmethod.latin/.LatinIME\n  -e DATADIR /data/data/com.retroarch.aarch64
-e APK /data/app/com.retroarch.aarch64-1/base.apk
-e SDCARD /storage/emulated/0
-e EXTERNAL /storage/emulated/0/Android/data/com.retroarch.aarch64/files
--activity-clear-task
--activity-clear-top

Issue has been confirmed on the following devices:

Important This issue does not happen with every game.

Try one of the following

Mentions This issue has been mentioned multiple times before in other locations:

Frontends where this happens

CANNOT reproduce this on the following device OS: Google Pixel 3A with Xbox controller. works perfectly there..

unbelievableflavour commented 1 year ago

Workaround The issue doesn't occur when you hold down a button when retroarch starts opening until the game has started. (for instance, the A button).

hizzlekizzle commented 1 year ago

Same issue here: https://github.com/libretro/RetroArch/issues/15109

AFAICT, it only affects the N64 cores, which have a lot of the same DNA, so fixing it in one will likely apply to the other, as well.

This does not appear to be an issue with Launchbox frontend, so it may not be entirely a problem with RetroArch/cores.

unbelievableflavour commented 1 year ago

Not true actually. I was able to reproduce the issue on Launchbox.

@hizzlekizzle what device do you use?

unbelievableflavour commented 10 months ago

Better Workaround

Change this setting like so:

  1. Go to Retroarch > Settings > Input > Polling Behaviour
  2. Change to "Early"
  3. Save configuration.
  4. Restart retroarch.