Can't progress in Black Day co-op [solved]

[bunnytrain]

Hey guys, I did some searching and couldn't find anything like this problem, so I figured I would ask here. My friend and I have run into this problem twice in a row, so maybe it's something we're doing?

We are playing FA mission 1 in co-op, two of us. Both times we've played, we cleared the artillery positions, cleared the two bases, and destroyed the bases attacking the town to the north. Once that's done, the map is supposed to expand for the third time to reveal the enemy Aeon commander, plus some scripted hordes of units.

This part never happens for us. Once we've destroyed everything in the visible part of the map, the map never expands to show the Aeon commander, and there's no cutscene where the transports carrying enemy forces spawn in. However, there's a rush of ground units including a single enemy colossus.

We played once with him as UEF player 1, me as Aeon player 2, and then played again with him as Cybran player 1, and myself as Aeon player 2. The map never expanded for the third time in both attempts.

Has anybody seen this problem before or have an idea why this might be happening?

EDIT: The answer is that you should not put both players on the same team - leave teams unassigned and the bug goes away.

[Paul Kauphart]

Hi,

Yes, I have seen it, it happened to me and I think there is a topic on the subject in the support forum, can't be bothered to search for it though.

And no, I have no idea why it happen, it's far beyond my skills to try and find out.

[Deering]

Well i just played it through successfully with no problems. Also this is a problem for the tech forum so I am going to move the topic there. What you need to do is firstly, read the red text at the top of the tech forum and then use that knowledge to post game logs. Only way that people can see whats wrong

[bunnytrain]

Ok, thanks. I will do that.

[bunnytrain]

Found the answer. We had set ourselves on the same team in the lobby when we set up the game. By switching both of us to unassigned teams ("-" instead of 1, 2, 3, etc.) the bug went away.