search

libretro / gambatte-libretro

Hard fork of Gambatte to the libretro API.
http://sourceforge.net/projects/gambatte/
GNU General Public License v2.0
102 stars 78 forks source link

make "double pression" of a buttons when Loadstate or Savestate maded from RetroarchGUI #226

Closed DjDiabolik closed 2 years ago

DjDiabolik commented 2 years ago

Currently i have a Pi4....... whit current retropie full updated to 4.8 and lr-gamebatte upgraded to current binary. It's a strange issue and i noticed from about two or three days until now.

Step to Reproduce: Start a random .GB roms......... like a platform or somethings similar. Put your personage like near a chasm...... open the RetroarchGUI and go to make a "SaveState"

If the button to "Confirm" the retroarch operation it's the same of Jump you can see the Retroarch GUI closed immediatelly... it's appears the notification say correctly "Savestate saved on Slot #" but at same time you can see clearly your personage do an action in game. By Default the confirmation buttons on retroarch it's mapped at button A of Gameboy and if A equal to jump after you see the notification about savestate you can obtain your personage jump.

I don't know if i can explain good...................... but i have tested this things also for other system and core (like nes... megadrive... lynx roms) and apparently it's only appen when i use lr-gamebatte.

I also confirm there's caused by my gamepad it's like damaged because this "Double Pression" it's append only when LoadState or Savestate.......... i never see a similar things for example whit normal navigation thru retroarch gui.

EDIT Open a help request also on official Retropie forum: https://retropie.org.uk/forum/topic/32426/retroarchgui-double-pression-of-action-button-when-i-load-or-save-states-using-current-lr-gamebatte

You can also found a VERBOSE LOGGING during running a GB games......... apparently there's no revelant info about this issue: Can post the developer log also here: https://justpaste.it/57dvw

DjDiabolik commented 2 years ago

After recently news on retropie forum i have to close the issue because apparently it's not a core related issue.

If someone want to report or partecipate about this little issue please follow the retropie thread posted upper here.

Thanks in advance.