Steam Input (or specific controller?) m1/fire bug

[washroomAccessFor.30]

match 1 ID: 57526765 | match 2 ID:57567374
Potential related/same bug report (or maybe not): https://forums.playdeadlock.com/thr...od-controller-does-not-work-on-startup.98353/

Skip to 3 paragraphs down for the direct problem, but everything before should be relevant to understand.

So this is a weird bug imo. I've came back to playing Deadlock in the last week and have had no problems with keyboard & mouse (K&B) but today I set up my Azeron Cyborg II, used through steam input. However, the bug I am experiencing shouldn't even have anything to do with the controller inputs.

This controller is not officially supported in steam input (which isn't good I know, but hear me out). It's essentially recognised as 2 devices: the keypad with keyboard inputs (& I only use keyboard inputs on the keypad) and an xbox controller for the omnidirectional movement stick (used with xpad drivers on Linux). One thing that is very relevant here is I do use this controller in Team Fortress 2 with no problem. Now, TF2 does have built-in xbox controller support, while Deadlock currently has none. But even using it through steam input in TF2 bared no problem at all. This is the reason I am reporting this rather than shrugging that the azeron just doesn't work with steam input/deadlock.

The actual problem description here: I have attempted two street brawl matches today after setting up the aazeron for Deadlock. During the 2nd round of the first match around 1 minute in, my hero started constantly shooting non-stop. Nothing was wrong with my mouse (I thought so at first). I spent time in the hideout to see if it happens again and felt comfortable to try a 2nd game as there was no hideout problem. This time, it also took until the 2nd round for me to not be able to fire.

We therefore have a consistency (first street brawl rounds fine) and and inconsistencypposite problems... but both to do with firing weapon. The consistent detail is why I think it is a Deadlock bug.

I abandoned the first match (apologising to my team), but stuck out the 2nd match. I would randomly start and stop firing, sometimes only a single digit of bullets (I happened to be McGinnis, so automatic weapon helped to notice this). LMB is and still is my fire button, even checked during the 2nd match.

I plan to attempt to play at some point with the azeron unplugged back with K&B to report back here (hopefully with no problems to not ruin a 3rd match with other players in). Note that the azeron has been plugged in all this time since I started playing again about a week ago just not being used in Deadlock. Only after I set it up for Deadlock and used it in game has this occurred in my 2 attempted matches but not 20+ minutes in the hideout between the matches. Maybe I should do a regular mode bot match to see if it is only a street brawl round 2+ problem? As if something to do with switching to the 2nd round triggers something somehow?

One last thing: there doesn't seem to be that many bug reports to do with steam input & Deadlock. Probably not many of us players using non-K&B to test steam input with deadlock. Might be more steam input Deadlock bugs out there to find.

 

[washroomAccessFor.30]

I have played a standard bot match that went on for just under 30 minutes deliberately.There was no issue.
I then played a bot street brawl match. In it I deliberately won 2 rounds in a row then let the bots win 2 rounds. After the bot first win, my space key no longer worked. That is, ofc, jump/mantling in deadlock. This was true for both the key set to space on the azeron and space on the keyboard itself which I tried too for testing purposes. I could no longer jump/mantle that match. I believe this is enough proof that it is a deadlock bug. Or at least a steam input bug in relation to Deadlock. Emphasis: My regular keyboard space did not work in-game at that point.

I then unplugged the azeron and restarted the game, playing a 2nd bot street brawl only with K&M. There was no known issue. However, if it isn't necessarily M1 that bugs but can be any input as now witnessed with space then... it's possible an input did bug out but I literally could not/did not use it with my loadout in street brawl.

Honestly, the fact that space bugged out is really bad as it makes testing this harder. I at least predict that no issue did occur with the azeron unplugged 3rd bot match. I'm sure I'm not expected to keep playing with the azeron unplugged just incase it does occur with only K&B during the 2nd round where the enemy wins (as that seems to be the trigger somehow? Only consistent observation thus far.)

There is 1 more thing I can think of to test: when I leave a match early I exit the game rather than return to the hideout. It should be good to know if an input is bugged in another bot street brawl, does it stay bugged if I abandon match back to the hideout instead? If it isn't bugged, then loading out of a match fixes it (temporarily?) If it stays bugged than that would be very interesting. I'll test that out at some point. I did just play 3 bot matches for testing this bug after trying to play actual human street brawl twice + this thread write up.

Um... let me know if the bot match ID are desired. I reckon they wouldn't be.

 

[washroomAccessFor.30]

I'm going to share the following tests I'll do at some point for this bug. In no particular order:

• (Already mentioned in earlier post) leave a bugged match back to the hideout to see if loading fixes or persists the bug.
• Play 2 bot standard matches instead of 1. If it's always the 2nd round of street brawl that it occurs then maybe a 2nd match of standard mode triggers it too. If not, then it really is only street brawl affected.
• When bugged and identified, switch keybind in settings for whatever is bugged. This will show whether it is the input itself or the action. This one may be the most valuable out of these ideas for identifying the cause.

 

[washroomAccessFor.30]

I started off testing with bot street brawl before planning to try 2 bot standard matches however despite keeping the rounds going long for the sake of identifying any bugged inputs the 2 street brawls I played did not have any bugged input as far as I know (i.e. due to the random nature of items I'm not guaranteed to be able to test every item input).

The next time I open the game to play I'll attempt a human street brawl match to see what happens.

Certainly the worse thing about testing to help with a bug is when it fails to trigger from the observed patterns. That, or, it has miraculously stopped being a problem as if it existed to make me sound crazy on this topic for one day only.

 

[washroomAccessFor.30]

I just played 1 human street brawl where after 2 round wins the enemy won twice, meaning this bug should have occurred during round 4 if not 5. As far as I am aware, no inputs bugged out. I did only get 2 active items, it is possible one of the other 2 item binds bugged without knowing. But just like the previous session bot games, nothing observable bugged.

I'm not going to post again unless it does occur. If and when it does, I will post occurrence updates, then only post once if it 'stops' akin to this post here. I do think reporting how consistent it is can help, thus if it happens to not occur for 7 whole days from now then starts again, then 7 days will be when I post again... hopefully with those tests executed as well for further understanding.

Here's hoping it is fixed though, stealth patched or phantom fixed (making me look like a crazed loon posting to myself).

 

[washroomAccessFor.30]

I have experienced this bug in an earlier play session today after weeks not noticing it. Actually, I experienced it twice in a row! Not only that, but I managed to do some further testing to the point where IDK what more I can test about it.

During the first session, my M3/MMB stopped bringing up the ping wheel. I could still quick ping however. It was yet again during a street brawl and this time I recognised on returning to the hideout that it still remained, thus loading into new matches/the hideout does not fix the issue. Even played a further street brawl match without ping wheel.

Restarting the game does fix/reset the bug. The second session on restarting had my parry bugged... like space & M1 previously from weeks ago; parry bugged is sorta game breaking due to how important it is. In the hideout, I've finally tested redefining keybinds to find out if it is the reading of input that is bugged or the action corresponding to the input.

I can confirm with 100% certainty that it is the action that is bugged each time. Rebinding the ping wheel to anything else did not fix it, rebinding the parry key to anything else did not fix it. An important point is that I deleted the keybind and added a new first bind each time, then I set it back to the original during the same bugged sessions. This shows that the game was reading MMB & the F key pressing despite the actions not working. The game 100% succeeded in setting the ping wheel back to M3 despite the ping wheel not working.

2 additional last things: while I continue to play with my azeron controller through steam input, these tests were done with both the azeron and my proper keyboard (& my trackball for the M3 bugged session). No difference. It really seems to be the game despite the inital idea & title of this thread pointing to steam input/controller as the cause; a pure red herring. Further, I happened to watch Deadlock streams and several days ago while having one on in the background I did actually hear players using their mics saying their jump and/or dash keys 'sometimes feel laggy' or 'not work at all this match'. I know this point is hardly useful in actually figuring out this big, but I genuinely think this is a bug experienced by more than just me & it does exist as a Deadlock bug.

So yeah... I hope these tests I've done can help.