All mouse movement (dead)locked. The bug spreads virus-like 🫣

[d4]

Hey! This is about the bug that got posted before

1.5 months in, the problem is still VERY relevant and could spoil the experience for many players if not addressed

Original post here

___________
TLDR:

Mouse movement for the crosshair does not get registered. (After pressing some button / console command combination ??) any crosshair movement stopped getting registered, heroes' guns are just frozen in place. Everything else works fine, all the button input gets through. You can move the mouse while pressing TAB or after pressing J, but nothing seems to fix the crosshair lockout.

The bug gets linked to the player's account. Even after switching PCs (and disabling steam cloud sync), you can't move the crosshair.

The bug "spreads" to a new account after you play on an "infected" PC. After one player experiences the bug on their PC, any new player on the same PC will get their account "broken" in the same way, mouse movement will stop working for them (with no fix on the horizon ).

____________

This virus-like behavior makes the problem very annoying and potentially dangerous (we already got 2 steam accounts and 5 PCs "infected", there could be more casualties )


As always, any advice/help is very welcome in the comments! Also ready to collaborate with devs for any investigations necessary.

 

[andrewdesire.business]

same problem

 

[fskinspam]

I am having this same issue. New player first time playing today, I can't move my crosshair at all. Mouse input works for for menus and clicking...

 

[fskinspam]

I am having this same issue. New player first time playing today, I can't move my crosshair at all. Mouse input works for for menus and clicking...

Validating files fixed it for me just now.

 

[d4]

Validating files fixed it for me just now.

Thank you might try that!

 

[d4]

UPD: while the underlying problem did not get fixed, we found 2 workarounds to "cure" your account from the issue

1)
try validating the game's files (click on the gear icon on the game's page in your library –> Properties –> Installed files –> Verify integrity of game's files)

2) if that didn't help:
- delete all game files (the most fool-proof way we found is to re-install Steam entirely with all its directories, maybe even use a brand new drive for the installation)
- turn off Steam Cloud sync for Deadlock (you can do that in the Properties menu after clicking on the gear icon on the game's page)
- re-install Deadlock with Steam Cloud sync turned off
After that, If done correctly, the crosshair becomes responsive again!

You may also re-enable Steam Cloud sync for the game after the first launch – just don't forget to prioritize the local version over the cloud save.

 

[zgamer4]

This happened during the tutorial for me as well, hasn't happened in game.

 

[Altimor]

Fix with

exec user_keys_default

in the console (press F7)