[Steam Input] "Old Gods, New Blood" - Controller Does Not Work on Startup *03/06/26 Balance Patch Bug Remains*

[washroomAccessFor.30]

I've just made some observations and small tests related to this bug. Before this bug affected me, my omnidirectional stick could be partially pushed for a slowed movement (a classic controller trick ofc). The last two times I've opened the game and replugged my controller due to this bug I've noticed that it no longer works like this (only 0 or 100% speed).

Out of a random hunch I just (literally 5 minutes ago) replugged my controller for a 2nd time in the game session, & it fixed this observation. Going back to controller my speed with partial pushes of the stick.

Finding this interesting, I decided to restart the game for the sake of replication. My stick worked perfectly without the need to replug it. Then thinking it may make a difference, I restarted steam itself after closing the game. My stick worked perfectly on startup without the need to replug.

Naturally, the next step was to reboot my system, surely that would reset the bug on opening Deadlock, right? NOPE. My stick worked perfectly on startup without the need to replug.

I will ofc post again if/when I experience the need to replug my controller after initial Deadlock startup. To those who also experience this bug: have you at anytime replugged your controller twice after needing to replug it once due to this bug? If not, please test so and share if it made any difference at all.

 

[DeadlockerBenReporting]

Another week without a fix in sight

 

[DeadlockerBenReporting]

Weekend bump

 

[DeadlockerBenReporting]

Monday bump

 

[DeadlockerBenReporting]

Updated post with image bump

 

[DeadlockerBenReporting]

Long time no bump

 

[washroomAccessFor.30]

As my previous post in this thread, I ceased experiencing this bug on the 19th of February. This persisted until last night, 2nd of March, when I opened the game up and had to reconnect my controller to be able to move.

Like before, I cannot slow walk if this is needed: something I didn't think I'd miss in actual matches outside of the hideout but I actually do notice the difference in how my heroes move in PvP modes. Additionally, double reconnecting did nothing unlike before where it somehow 'fixed' the issue for me for weeks.

As always, I will update if anything changes. No update means this current experience continues each time I open the game.

 

[washroomAccessFor.30]

Subsequent starting of game sessions have had the controller working on startup again. An individual flook on the 2nd of March for some reason. While I'm glad I mostly do not experience this bug anymore, clearly there is some sort of inconsistency going on for me to get it once in a blue moon still.

 

[DeadlockerBenReporting]

Great patch tonight but still no fix

 

[DeadlockerBenReporting]

Any chance we will get a fix for this? Haven't got a single developer to even mention this for 3 months

 

[DeadlockerBenReporting]

I will bump to the end of my days

 

[DeadlockerBenReporting]

Saturday bump

 

[kyotanaka442]

Now the usual workarounds are not working anymore. Deadlock will just REFUSE to acknowledge my controller now.

 

[washroomAccessFor.30]

My joystick is still working on startup with only the aforementioned 1 time it didn't since I double reconnected. I guess the inconsistency of this bug is the most annoying thing about it.

 

[kyotanaka442]

My joystick is still working on startup with only the aforementioned 1 time it didn't since I double reconnected. I guess the inconsistency of this bug is the most annoying thing about it.

It was extremely consistent before. Then whatever patch that happened recently made it not work anymore.

 

[DeadlockerBenReporting]

The temporary fix still works for me on the 8BitDo Ultimate 2 Wireless but I'd really like to not have to do it every single time I play

 

[kyotanaka442]

The temporary fix still works for me on the 8BitDo Ultimate 2 Wireless but I'd really like to not have to do it every single time I play

I am using this controller myself and the temporary fix's stopped. At this point I'm just considering forgoing Steam Input and have it be read as Keyboard/Mouse however messy as that is

Edit when I mean Steam Input, I meant the game actions. As far as I can tell: ONLY the game action is messy, the mode changing still works as intended. Haven't tested that myself, but at this point fuck game actions

 

[kyotanaka442]

Back with my testing: Keyboard works just fine. Except the layers are broke too, so have fun with spec controls. Fun times.

I realized I've yet to try this issue on Linux. I'll give that a try and report my findings later.

EDIT: Bazzite has issues getting controller to work as well, so it's not a Windows problem.

I also have the game on steam deck, Everytime I booted it up it appears that the controller works consistently? Only booted it up twice to spectate matches since it slurps batteries, will try test some more later but it appears at the very least Steam Deck (or possibly SteamOS) does not have this issue.

 

[DeadlockerBenReporting]

Monday bump