- Home
- Games
- Company
- Community
- Roadmap
- Media
- Store
- Store Support
- Feedback
- Contact Us
- Warhammer 40K
- Home
- Community
- Hub
- Void crusade missions become unselectable after connection failure
Hi:
Sometimes when we play in group, a window would pop up saying things like "in-game progress lost, returning to bridge".
And after that, the mission will become unselectable (see the picture below, 2 missions unselectable), and cannot be played anymore.
Restart the game doesn't seem to help.
This bug has been a while. It prevents people from completing a perfect crusade. Please fix this, thanks!
Your Thoughts? Please login to place your opinion. Not a member yet? Register here and now!
Hi Marco
No, I have no disconnection during mission since my last reply. (Though I only tested in last week, had to be away from computer this week, which is also the reason I didn't reply earlier :( )
As of now I cannot say for sure if this is issue is gone.... I'll let you know if that happens again in Feburary.
======================================================================================
Some players still say similar issues happened this week, but I think it is slightly different from mine (all people got kicked out during void crusade):
THEIR issue: (Maybe @mixol9 is saying this as well)
When playing void crusade in groups, sometimes the team leader didn't load into mission at all (But others in the team succeeded)
The (former) team leader then found the void crusade mission icon became dark and unselectable, like the picture I showed above. (While the "survivors" were playing that mission )
Later he found this mission became "failed". He didn't ask if the other people actually won or lost the battle, guess they just lost it.
Hope this helps
No point in writing here at this stage
I suggest cutting your loss and Finnish it
Do a perfect crusade solo most connection loss is in co-op
this new season is complete disaster with problem, last season was stable enough to be played co-op in campaign
Now i had this problem in campaign missions co-op sabotage(fairly early), then 3rd mission on martyr. Its do to the bosses.
I have a support ticket opened
December 17
got reply
December 19
Marcopolocs
Hey there,
we would like to inquire whether the problem you reported is still being experienced to this day. If yes, please let me know your partner's in-game account name as well as we can see yours on the screenshot and our developer team will check on the issue.
Looking forward to your reply,
Marco
NeocoreGames
I named the accounts on that day
December 22
my messages :
still experiencing
what are you doing there!?
great so i am locked out of game story progress till this is fixed
December 30
dude WTF ? 1 week ago!? are you serious
I rage quite will wait for a new season or will later redownload the game to play on normal server this season is BS.
They should have launched Battle Sister 1st then new season at a later date
this game is fun playing with friends and having this season be played do to these server loss glitches(co-op exclusive problem) is just was the straw this month.
Sinking in other games
Regrettably, I just confirmed the issue is still there :(
I'll describe this issue again in more details:
During team play, 2 people got kicked out simultaneously.
Message say: "You have been disconnected from the server. In-game progress has been lost and you will be returned to the Command Bridge. Reason: Server closed. "
Then the game would try to re-login but fail. We had to restart the game and login——then found that void crusade mission became unselectable. (If we move mouse onto the icon, the texts say "Mission Available" but we cannot select it)
======================================
Other details :
one of the players crashed several times during same mission , and each time he restarted the game to resume the battle.
I don't really think this is related to the issue but I think I should say it here.
We can't track it down unless a player implements a verbose_log command on PC and plays until they receive a disconnection. The error written into the log file can give us some clues.
The devs sometimes read and reply here, so I leave this message in vague hope that it could be solved in the future.
Other communication channels like discord are not always convenient to me so I have to write here : (
"Server closed" issue still happens. After that, wait for ~10 minutes, then the affected mission will return to normal and can be selected again.
Set this current order state as My default.