Hotkeys not working when using lr-fbneo. I'm confused as to why they're not?- HK work in mame-libretro

wtstreetglow1

Hello,

Could I get some guidance on fixing the subject from someone here?

And secondly, I'm hoping someone could help me understand if this is normal or abnormal. I was under the impression that any retroarch core should have the hotkeys working right "out of the box".

In my case lr-mame2003 (mame-libretro), it is but with the lr-fbneo, it is not.

Thank you all again for some guidance/ understanding on this subject.

I would very much appreciate it!

mitu

Please be more specific on what exactly is not working - describing the game/what input you've tried and it's not working.

Also, please add some info about your setup - at least minimally - so we know what's your general setup and platform.

barbudreadmon

@wtstreetglow1 what do you mean by "hotkeys" ?

wtstreetglow1

@barbudreadmon https://retropie.org.uk/docs/RetroArch-Configuration/#hotkeys

wtstreetglow1

@mitu, @barbudreadmon

I apologize for this post. When I started messing with this more, everything is working perfectly fine with the hotkeys.

I must have been mistaken earlier today when I was working on this. (Pushing the wrong buttons more probably)

barbudreadmon

@wtstreetglow1 said in Hotkeys not working when using lr-fbneo. I'm confused as to why they're not?- HK work in mame-libretro:

@barbudreadmon https://retropie.org.uk/docs/RetroArch-Configuration/#hotkeys

Hmmm ok, i was wondering if you were talking about the MAME specific hotkey for opening MAME OSD.

Cores have no control over the retroarch hotkeys you were talking about, meaning if they ever stop working randomly or for one specific core, you are most likely in one of the following scenarios :

you messed up with configuration and/or overrides
you have some kind of hardware issue
you are pressing the wrong buttons

wtstreetglow1

@barbudreadmon oh I follow you now. And that's nice to know about the mame keys. That will be useful to me shortly.

Thank you again for helping me understand all of this.

Luckily in this instance, it was user error.