Campaign soft lock on act three, some Assembly required

I really haven’t heard anything of it, but WeeEdengarden said he got an email from TC support saying they were looking into the issue, the typical response from support. From all the other issues ive been seeing on the forums its probably not high on their priority list for fixes i would assume.

1 Like

Holy baloney. I’ve been bug-free with the game up to this, but yeah, just ran into this issue. Not fixed after two months? Jeez. I like the game but I’m not really inclined to replay the entire damn chapter.

What’s really strange is that the dialogue at the start of the Cosmonaut facility took into account that you were going there instead of the rocket facility. Your team talks about how they found such and such place and then Padek says his people were gonna get the beacons from there but now that you wandered there anyway you might as well do it, etc. So clearly it was meant to be possible to do it that way, only then to not have the game recognize you did that once you lower the bridge. Seems strange indeed that this bug was not caught early on.

2 Likes

I cant believe this is still broken…

1 Like

They made the money, now they can focus on the MP, R.I.P. single player.

1 Like

Hi all -

Apologies for not providing updates on this here, we’ve been engaged with some folks around this on other platforms.

This issue is slated for a fix in TU3, pending any surprises. Once TU3 deploys, this issue will be prevented - unfortunately, the fix will not be able to resolve those of you already in a bad state. Once TU3 is out, we recommend you restart the Chapter in order to unblock the issue.

Sincere apologies for the reset to your progress and the time it’s taken to address this - but the team worked hard on resolving it as soon as we could. Thanks for your understanding.

:face_with_head_bandage::face_with_head_bandage::face_with_head_bandage:Still it really sucks to restart the chapter for this. This is more of a game design failure that’s causing the bug instead of a technical issue. How did you guys not foreseeing this? T_T

1 Like