Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

RetroLab

Early access to simulations and prototypes in development for RetroFab · By Itizso

Button A inherits other controller buttons behavior (retrofab-windows-player-0.2.1)

A topic by a19xys created 20 hours ago Views: 13 Replies: 2
Viewing posts 1 to 2

Hi, I’d like to report a bug I found with Xbox controllers, and possibly with other types of controllers too.

I’m using RetroFab Windows Player v0.2.1. The issue seems to be that Button A can inherit the behavior of Game A, Game B, Time, Alarm, etc.

More specifically:

  • If I assign Game A to any controller button and press that assigned button at least once, Button A starts triggering Game A as well.

  • The same happens with Game B: if I assign Game B to any controller button and press it at least once, Button A starts triggering Game B.

  • This also seems to happen with Time, Alarm and other mode buttons, although I don’t think it happens with normal gameplay controls.

  • Button A appears to change its behavior depending on the last assigned mode button pressed on the controller.

  • This does not happen when Game A, Game B, Time, Alarm, etc. are triggered with the keyboard or mouse. It only seems to happen with controller buttons.

  • Button A does not need to be assigned to anything for the issue to happen. It can be assigned or unassigned.

So, for example, if I map Game A to Start, pressing Button A (assigned or unassigned) may also trigger Game A after Start has been pressed at least once.

I’m not 100% sure my diagnosis is completely accurate, and there may be other related issues with controller mapping. For example, sometimes the same button appears to be assigned as “1” and other times as “B”, even though they are technically the same button.

Expected behavior: Button A should only trigger the action assigned to Button A, if any, and should not inherit the last mode or action button pressed on the controller.

(2 edits)

Thanks for the detailed feedback! Testing with a single controller plugged in it seems fine. I am aware there is an issue if you have multiple controllers  plugged in. Do you maybe have more than one controller connected?

I honestly have no idea what to answer you, because I only have one Xbox One controller (wired) and the keyboard connected. I don't know if I have drivers that make Retrofab think it's receiving inputs from multiple sources, although this shouldn't be an issue. I imagine it's not very helpful, but I can also replicate this error in the browser. In any case, I can play without problems if I don't assign Mode buttons to the controller. I just wanted to warn that this issue exists, even though it might only happen to a few people.

As a side note, I haven't done exhaustive testing, but this happens with games that have configurable Game, Game A and/or Game B buttons, and that don't have these Game buttons assigned to controller buttons by default. It happens with practically all Game & Watch games and, for example, with Elektronika clones.