[Bug] Steam Deck input stops working sometimes

[Pixxel124]

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...

• [x] I have made sure I am using the latest version of Controlify for the latest version of Minecraft.
• [x] I have made sure there are no other issues describing the same problem on the issue tracker.

[thinker5555]

I have also been having a similar problem. It started for me when the Steam Deck updated the stable channel of Steam OS to version 3.7.8. I'm experiencing the issue with two configurations. Both of these configurations were working fine before the Steam OS update.

Configuration 1:

• Minecraft Java 1.21.4
• Fabulously Optimized 6.5.0-alpha.5 via Modrinth
• Controlify 2.0.2+1.21.4-fabric

Configuration 2:

• Minecraft Java 1.21.5
• Fabulously Optimized 6.6.0-alpha.7-mr.1 via Modrinth
• Controlify 2.1.2+1.21.5-fabric

I'm experiencing something similar to Pixxel124's video at the 0:25 and 0:38 marks. Sometimes when I push one of the joysticks, the character does nothing for a second or so, and then it will start up and go. Other times when I let go of one of the joysticks, the character may continue moving or turning in the direction for a second or so longer before stopping.

To me, the controls aren't exactly lagged, as in everything I do happens a second or two after I do it. Instead it's almost like the controller inputs are operating on a dashed line. The dashes are where input is accepted and works normally, but in the spaces between the dashes, it's like the input "holds" whatever state the input was in at the end of the dash until the next dash starts.

I'm not sure if that's very clear, so I'll try to muddy it up more with a visual representation. I apologize if the following is completely unhelpful, but I'm trying to describe the feel of what's happening as best as I can.

Let's say this line represents pushing "right" on a joystick and releasing it a few times of varying lengths. The longer the string of "r" or "_", the longer the joystick is held to the right or released, respectively.

___rrrrr_________rr___rr___rrrrrrrrrrr_______

Normally the input flows constantly, and the game reacts to the joystick push and release right away.

But now the input flow feels like it's being filtered by a dashed line, as if input is accepted during the dashes and is held during the gaps.

_____ _____ _____ _____ _____

If this dashed line is overlaid with the inputs of pushing right from the first line, what results is something like this. The lowercase "r" represents where the input would be given or released normally, but the capital "R" represents where the last known input was held through the gap until the next "dash" starts.

___rrRRRRR____________rr___rrrrrrrrRRRRR_____

Not only is joystick input getting held during the gaps, but it also loses the first "rr" input completely, which happens entirely within a gap.

Again, I'm sorry if that not helpful or clear.

[vit-owl]

I am experiencing the same problem. When using Controlify on Steam Deck. Previously the problem was not observed until the Staem OS update.

Launcher: Prism 9.4 Steam OS version: 3.7.8 Decky Loader version: v3.1.5 Minecraft Version: 1.20.1, 1.21.4, 1.21.5 Modloders: NeoForge, Fabric. Controlify version: 2.1.2

Problem description: at random moments the controller seems to turn off. Positions of pressed analog sticks and triggers at that moment are saved and the character continues to move or act. For example, I move the camera to the right, a “disconnect” occurs, I release the stick, but the camera still continues to move at a fixed speed that depends on the last stick position at the time of the disconnect.

I can say for sure that the problem was not observed before, before the Steam OS update I played about 40 hours.

This problem is also experienced by my friend. It also appeared after the Steam OS update.

Video (clearly visible at 0:58): https://drive.google.com/file/d/1XIY6GJrLOXfQ1oJT5GKPK7AZcPonfuYb/view

[SortingFarmer]

Hmm im also experiencing the same problem, however im playing on windows (Neoforge 1.21.1) with a ps5 controller and for me it occasionally happens when entering water/swimming or always when blocking with a shield in my offhand

Edit: I have tried turning on "Mixed control support", this made the hanging significantly worse.

[billw1]

~is there any workaround?~ You can disable the enhanced steam deck driver in the settings and it will be playable again, I guess you lose back buttons and gyro

[Pixxel124]

I switched to Controllable and it works for me with no issues. This bug was so annoying I couldn't keep playing with it.

[crisscrosss]

currently having the same issue on 1.21.4 (fabric) with steamos 3.7.8

[Cheesy358]

I am also experiencing the same issue right now. Others have said that they did not observe this bug before the steamOS update. Is it somehow possible to revert the steam deck to previous OS versions?

[Pixxel124]

I am also experiencing the same issue right now. Others have said that they did not observe this bug before the steamOS update. Is it somehow possible to revert the steam deck to previous OS versions?

I found this post: https://www.reddit.com/r/SteamDeck/comments/zvjc5f/remember_you_can_rollback_to_a_previous_steam_os/

[Rocker824]

Created an account to say that I'm having the same issue lol. Hopefully it gets fixed soon.

And for me disabling "Enhanced steam deck drivers" and restarting the game makes it so that it doesn't detect the controller and defaults to mouse and keyboard. I have to manually select the Steam Deck again in Controller settings.

[loganisme11]

Thought I’d pitch in and say that I had this issue as well.

However, as others are saying, disabling the “Enhanced Steam Deck Drivers” has fixed the issue for me. And as far as I can see, it hasn't effected anything major.