Page 1 of 1
Netplay Cannot proceed During Port Strike
Posted: Sat Dec 07, 2013 2:42 pm
by Zorachus99
Yep, my buddy had placed his fleet in Riga to tempt me into wasting two air missions on it. I suckered on the bait and I got 6 surprise points. [:@] I was hoping for more [8|]
Anyway, I got 1X, 2D, and 2A. [8D]
The first hit was against the Kirov, which bottomed it. Pretty exciting result!
I asked my buddy if he was ready to choose the next damage.
Sadly, he could select a unit, but could not get the ok button to light up.

We went back to the port-strike phase to see if we could continue.
Our auto-save would not start, saying 'waiting for player' in MWIF.
We tried to go back to a previous earlier auto-save, but it also said 'waiting for player' after the game loaded for both of us.
Can you point me to a safe phase or time we can both save the game at the same time, where it should restore?
Thanks!
Edit: It was the Barbarossa campaign.
RE: Netplay Cannot proceed During Port Strike
Posted: Sat Dec 07, 2013 2:58 pm
by Centuur
If the entry numbers of the saved games are the same for both players, both players should be able to restore the saved game.
RE: Netplay Cannot proceed During Port Strike
Posted: Sat Dec 07, 2013 3:02 pm
by paulderynck
ORIGINAL: Zorachus99
Yep, my buddy had placed his fleet in Riga to tempt me into wasting two air missions on it. I suckered on the bait and I got 6 surprise points. [:@] I was hoping for more [8|]
Anyway, I got 1X, 2D, and 2A. [8D]
The first hit was against the Kirov, which bottomed it. Pretty exciting result!
I asked my buddy if he was ready to choose the next damage.
Sadly, he could select a unit, but could not get the ok button to light up.

We went back to the port-strike phase to see if we could continue.
Our auto-save would not start, saying 'waiting for player' in MWIF.
We tried to go back to a previous earlier auto-save, but it also said 'waiting for player' after the game loaded for both of us.
Can you point me to a safe phase or time we can both save the game at the same time, where it should restore?
Thanks!
Edit: It was the Barbarossa campaign.
You didn't happen to try doing the second damage based on his instruction as to which ship? Not saying this is the issue, but I've seen times where on NetPlay, only one player can do all the deciding in an open Form.
Maybe Shannon can comment on this or maybe it's in the manuals.
RE: Netplay Cannot proceed During Port Strike
Posted: Sat Dec 07, 2013 3:05 pm
by Zorachus99
how do you check the entry numbers?
is the save game safe to open?
RE: Netplay Cannot proceed During Port Strike
Posted: Sat Dec 07, 2013 3:12 pm
by Centuur
If you select any saved game before restoring it, a form pops up on the right. Check the next entry # there.
RE: Netplay Cannot proceed During Port Strike
Posted: Sat Dec 07, 2013 3:22 pm
by Zorachus99
ORIGINAL: Centuur
If you select any saved game before restoring it, a form pops up on the right. Check the next entry # there.
Muchos Gracias! [&o]
RE: Netplay Cannot proceed During Port Strike
Posted: Sun Dec 08, 2013 1:54 am
by Zorachus99
Reproduced the issue. Port attack on Leningrad causes a bug where opponent cannot choose air loss. This time Kirov was damaged in first round.
Still cannot restore save game during setup.
Found a third error also. You cannot spend 3 surprise points to choose a target - which I very much wanted to. See attached photo. Save in next post.
RE: Netplay Cannot proceed During Port Strike
Posted: Sun Dec 08, 2013 1:57 am
by Zorachus99
Manual savegame that won't restore in port strike phase attached.
RE: Netplay Cannot proceed During Port Strike
Posted: Sun Dec 08, 2013 2:12 am
by paulderynck
Sorry, I can't test this without your playing partner's matching file.
RE: Netplay Cannot proceed During Port Strike
Posted: Sun Dec 08, 2013 3:21 pm
by Zorachus99
Here is the other players save file.
RE: Netplay Cannot proceed During Port Strike
Posted: Sun Dec 08, 2013 7:34 pm
by paulderynck
Thanks - I was able to load the game files and link up - although only if player 1 got to the forum first. I found the same problem with the Port Strike.
I'll report all my findings back to Shannon. Until he can fix this, port striking (at least in this scenario in turn 1) will have to be avoided.