isXander / isXander/Controlify

[Bug] Steam Deck input stops working sometimes

Open
#593 10 comments 4 reactions 1 assignee View on GitHub

@isXander is already working on this.

Since May 24, 2025.

bug
Dominant language
Java
Stars
341
Forks
97
Avg merge
1h
Merged PRs (30d)
1

Description

Current Behaviour

When I play minecraft with this mod on my Steam Deck sometimes a left stick or right stick input gets stuck for a moment and I can't do anything until it stops. I get stuck moving my character in one direction or moving my cursor in one direction. Other times all my controller inputs stop working and I can only use mouse and keyboard inputs.

Expected Behaviour

Controller inputs should work normally

Screenshots

video made with steam background recording: https://drive.google.com/file/d/1zaEmIMCevZebRoYY9oPVelEIGyFPACmt/view?usp=sharing
Examples of the left stick and right stick problem are at 0:25 and 0:38.
The controller input stops working completely at 3:01
I use the right track pad as a mouse and the L4 button as escape when the controller input stops working (track pad mouse also while using controller input e.g. for the quest book and menus).

Reproduction Steps
  1. Open the game
  2. Enter a world
  3. Do anything while using controller input
  4. The controller input stops working at random times
Logs

Mod Version

2.1.2+1.21.1-neoforge

Controller

Steam Deck

Bluetooth
  • Yes
Operating System

Linux/SteamOS

ARM
  • Yes
Additional Information
  • I was playing Craftoria 1.20.3 on minecraft version 1.21.1 with NeoForge 21.1.169
  • I'm playing on Steam Deck using the Prism Launcher
  • I had the same problems while playing the mod pack Homestead 1.0.3, minecraft 1.20.1, Fabric 0.16.14
  • I have the mixed input option turned on
Just to make sure...
  • I have made sure I am using the latest version of Controlify for the latest version of Minecraft.
  • I have made sure there are no other issues describing the same problem on the issue tracker.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.