Skip to main content

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

Just Keep Running

Run, leap, and uncover the truth in an adrenaline-fueled parkour odyssey. 路 By I.M.I.Self

Bug with controller binding settings

A topic by Pylast created Aug 23, 2023 Views: 172 Replies: 3
Viewing posts 1 to 2
(1 edit) (+1)

The game is pretty great but when i pick up an uplink with my controller or interact with the keypad i jump and press the button at the same time i tried changing it in the controller binding setting still needed to press a  to interact with something


(sorry for my bad grammar english is my second language)

Developer

That seems odd, the default binding key for interacting with items should be the B button, not the A button. 馃
Everything appears to be working fine on my end, so this might be some weird anomaly with the Input System, but I don't really know XD

Quick question, Are you using an XBOX controller or another type of controller? I've only playtested controller bindings on an XBOX controller, so there might be inconsistencies between different controller types.

Thanks for playing the game though! If I find out what the issue might be, we'll get around to fixing it. And I hope you stick around for Chapter 2! 馃榿

(+1)

ive used a switch pro controller the info card keeps switching between a and b

Developer

From a quick Google search, it seems that the Unity Input System (which is the system the game uses to handle player input) tends to struggle with Switch Pro controllers on Windows and Mac, sometimes reading a single press from A / B / X / Y as a continuous press on all of them, and sometimes just registering random inputs.

This is most likely something we can't solve ourselves, this is most likely an issue for Unity and their team to solve since they know the system inside and out, and any changes we might try to make to the system could cause issues.

What I might suggest is trying to connect the controller via Bluetooth rather than using USB, if you haven't already tried to do so. That seemingly works better sometimes, but not guaranteed.

Thanks again for pointing this out to us! This will now be listed as a known issue in our changelogs and we'll keep track of this issue and let everyone know once it has seemingly been solved. 馃榿