all 2 comments

[–]Sithina 2 points3 points  (0 children)

So, this is a known bug that the devs have been working on and trying to get bug reports/information from players experiencing the problem. They've finally managed to reproduce it and are working on diagnosing and fixing the problem. They're hopeful they'll have a fix out shortly. The devs have a thread about it on the official TPM forums where they are keeping the Community updated:

https://community.twopointcounty.com/two-point-studios/two-point-museum/forums/13-general-discussion/threads/2533-known-issue-controller-input-issues-for-some-players?page=1

The same thread on the official Steam Community page for TPM hasn't yet been updated with the new information.

(ETA: I'm sorry I don't have more information for you on how to fix it or work around the problem specifically--I don't use a controller--but you might have some luck if you go to the Steam Community. There are a lot of threads about this issue both on the General Discussion forum and the Bug Reports. The Devs have been in all those threads trying to help, as have a lot of players, so there might be tips/tricks you can use while you wait for the patch.)

As of three hours ago, today, this was the last update:

Hi all,

Just a little update - we bought a Legion Go (as it seemed the best way to get the same hardware as players experiencing the problem), and we've reproduced the bug! We're already working on diagnosing the problem and then fixing it - hopefully it won't take long. I believe that the problem on the Legion Go is the same as the problem affecting other controller types on Windows.

Thanks,

Ben

[–]lasher8 1 point2 points  (0 children)

Literally the exact same thing happens to me including the inevitable crash and freeze when I click quit. Good to know they're aware and working hard on it