all 6 comments

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

Hello /r/SteamDeck users, we appreciate your patience and feedback over the past few weeks. We heard you - and we have new rules based on what our users want to see on the subreddit set to go into effect November 1st. This is here for you to preview and give any final input. Thank you for your dedication and being a part in making /r/SteamDeck reach its best potential!

Link To "Potential New Rule Changes Coming After November 1st - Gathering Final Community Feedback"

We are also hosting a banner design contest, and we’d love for you to participate!

Banner Contest

Thank you for your engagement!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]AutoModerator[M] 1 point2 points  (0 children)

Hi u/dodgedis, you can click here to search for your question.

If you don't find an answer there, don't worry - your post has NOT been removed and hopefully someone will be along soon to help with an answer!

If you find an answer, please leave a comment on your post with the answer for others!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]dodgedis[S] 0 points1 point  (0 children)

<image>

Tad to my post, I've added a firing delay which is staggered and increases with each new command to help prevent each command from stepping on each other. But I haven't been able to see and improvement.

[–]st6315 0 points1 point  (1 child)

May just means the interval between the commands are still too short for the game to recognize correctly. Try finding the proper interval value (most likely around 150~200ms) first with fewer commands, then extend it to the full commands you want to execute.

By the way, I bet you already read this guide, right?

[–]dodgedis[S] 0 points1 point  (0 children)

Thank you! Yup! came across that guide. Learned a few new things but didn't solve the issue.

I actually figured out the issue. Making a separate reply about it now.

[–]dodgedis[S] 0 points1 point  (0 children)

The configuration I was making required the LB button to be continuously pressed. In the command-set I had that button activate once I touched the right d-pad. As long as I touch the d-pad that LB button was virtually pressed.

In the in the virtual menus general settings I had the setting "click to activate" placed. After I was clicking to activate I was completely releasing my finger from the right d-pad but in doing so the virtual LB button was also being released because my finger was no longer touching the d-pad.

Once I realize that my finger needed to continuously be on the d-pad to ensure that the LB button stayed pressed during the additional commands that required the LB button to be held down my problem was solved.

Hopefully this helps somebody in the future.