libretro / libretro/fbalpha2012

Core Input Remapping not available in Retroarch GUI

Open
#48 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
31
Forks
55
PR merge metrics
No merged PRs in 30d

Description

Hi! This is a copy of an issue I logged with Retroarch - https://github.com/libretro/RetroArch/issues/2000 - apparently it is an issue with the core itself.

I'm trying to resolve this issue I have with the way that the FBA-lr core handles mapping neogeo buttons on a snes pad: http://blog.petrockblock.com/forums/topic/different-controller-configs-for-retroarch-menugames/

Essentially I can get a configuration that works right in games, but then it makes the buttons do different things in the RGUI - I want it to be correct in both, ideally! :) I'm told that the 'Quick Menu > Core Input Remapping', would solve this issue, but it doesn't appear in the quick menu of this core - why? It DOES appear in other cores, although I don't have issues with those :)

I'm running v1.2.2, with the latest version of fba-libretro


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Quick Menu > Core Input Remapping entry point and compare its availability for FBA-lr with the other cores mentioned in the report. Read the linked RetroArch issue and verify the expected behavior against the reported FBA-lr and RGUI controller mappings; done means the remapping option is available and both game and RGUI mappings work as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.