​Hello,

We're aware that some players are having issues with controllers and we're sorry about this!

 These are the reported problems:

1.  Controller disconnecting or becoming unresponsive after varying play lengths (various controller types)
2.  Legion Go controls stop working
3.  Some crashes that seem related

 To help us with investigation if would be great if anyone who is experiencing this bug could send us some info to support@twopointstudios.com or add as a bug in the forum. 

1. Dxdiag https://support.sega.com/hc/en-gb/articles/201556491-Creating-a-DXDIAG-Report
2. Logs If you are using windows, you can find it here; C:\Users\[Username]\AppData\LocalLow\Two Point Studios\ (type %APPDATA% in to file explorer) 
3. Installed software report https://docs.google.com/document/d/1KDaBFMorDxKDYCD5uo9mO6gwaa-MsbUum0co0UPrjR8/edit?tab=t.0

 Let me know if you have any questions,

 Many thanks,

 Jo

Hi all, We have an update for you! This was meant to go out at the same time as the post on the Steam Community back on the 19th - oops... better late than never?

In short, we have a fix, and if things go well, we should be able to get this fix to you next month.

We've managed to reproduce the issue with controllers becoming unresponsive, and with the game then locking up when trying to exit - we bought a Lenovo Legion Go, and it does happen very quickly there. We've dug in, and have found that it's due to a bug in the Unity engine's input handling code. It's very likely to be the same issue that affects both the Legion Go, and other controller types on Windows. We've worked with Unity, and they have fixed the issue in an upcoming release, which we've upgraded to, and we're currently testing now. I've confirmed that the issue is fixed in the new version. We hope to release this in a larger update to Two Point Museum soon. We can't give a firm date yet, since upgrading the engine version does often take extra time to hammer out any new issues that get introduced. I hope that this happens next month though.

For more details, for anyone interested - these are the specific Unity bugs causing this issue, fixed in version 6000.0.37f1, which we're upgrading to (from 6000.0.17f1):

• UUM-85315: https://issuetracker.unity3d.com/issues/input-is-not-received-after-some-time-when-using-a-gamepad
• UUM-91181: https://issuetracker.unity3d.com/issues/player-exe-remains-open-as-a-background-task-after-closing-it-when-active-input-handling-is-set-to-input-system-package-new

There is one caveat, which is that there's one more bug still present in this version, which causes the same issue to happen in very long play sessions. We'll need to take another engine upgrade to get this fix - but I don't believe it will affect you as it should only be unusually long play sessions.

• UUM-98890: https://issuetracker.unity3d.com/issues/the-input-system-will-stop-responding-to-events-when-the-number-of-handled-inputs-reaches-the-max-int32-value-2147-483647

Thank you all for being so patient while we investigate this!

All the best,

Ben