It says “Defend the new breach in the defense 0/4” but the defense isn’t even breached yet. I think some kind of mortar destroyed it when I was playing with my buddy on his savegame.
The issue is most likely to appear when You play in Your Friend’s World!
For now, if you play with your friends the DLC, just carry yourselves through fully through the whole questline, it’s not very long anyway and side-quests aren’t that easily buggable because they’re even shorter.
Any update to this?
Having same issue on my single player game after i played on friends game.
This kinda bums out all progress on this questline when i try to continue my solo game.
Description: Stuck in mission, its show as completed on challenges, but in location waves of enemys dont show.
I played this mission with friend in Co Op (his game), then when i wanted to play it solo i get stuck as shown in next images.
Images / Videos:
Tell me if a can give u any more info, and sry for bad english!
I can’t progress il the main scenario of fenix rising, il’m blocked when the “waves” must attack the fort at mullvadsberget.
I wait and nothing happens.
He game say the mission is already finished but it’s not.
Please help, thanks.
Same issue for me as well. 0/4 waves defeated. Can’t seem to fix it by completing other missions or spawning elsewhere, restarting etc. Any advice on how to proceed?
Same issue as MrSteelRat. This is game breaking, I can’t complete the main quest line. I played through this quest on a friend’s account who finished the quest line solo. I am no longer able to complete this with him or solo for my save file. Is there a save game edit that I can cut in or something? Pics from progress below. Starting a new character doesn’t help. Running from another spawn point does not trigger the waves to start. Firing weapons at all static objects, killing enemies in the area, revisiting points from the previous step in the quest, starting new character, playing with friends, and many more user sided troubleshooting steps have been done with no success.
This bug is so serious that I would guess it’s quite high priority on the jira. So we all just have to hold onto our hats and wait the storm out until it’s fixed.
