Page 1 of 1

Netplay Surprise Port Attack

Posted: Tue Feb 04, 2014 6:15 pm
by Sabre21
Are the surprise port attack bugs for Netplay on the bug list to be worked on or are more Netplay saved games needed?

Bloodybill and I updated to 1.1.2 and just tried a fresh Global game and ran into several surprise port attack bugs again. Bill played the Axis and ran into a problem when he used his Nav unit to surprise attack the Polish Ca unit. He had 8 surprise points and put them all into the attack. His screen indicated the Allied unit would be destroyed but the final pop-up indicated "No Effect" as did a pop-up on my screen. Is this possible to have a no effect?

As the Brits during the 2nd impulse I attacked Kiel with 2 British bomber units. I only had 4 surprise points and put 2 into reducing German AA. The AA fire caused 5 points of damage forcing one of my bombers to abort. The moment I selected a bomber to return to base, Bill received a crash pop-up.

We terminated the game at this point and figured we will try again next week or whenever this gets fixed.

RE: Netplay Surprise Port Attack

Posted: Wed Feb 05, 2014 7:37 pm
by HeroFromBavaria
Solitaire play doesn't look clean either... It's easily reproduced by starting a fresh Barbarossa scenario with the "Fast Start" saved game and performing a Port Attack with the trustworthy Condor. After spending a couple of Surprise Points for column shifts (and not choosing to select a specific target), in the next screen Germany(?) is supposed to annonce targets without being offered any resuts (X, D or A). No screen for Soviet selections pops up afterwards and the plane returns to base without any results. I uninstalled MWiF as the update.exe wasn't working anymore too, installed from scratch and updated to 1.1.2 again. Same behaviour. And this is reproducable in solitaire Global War also wih a german unit performing a Port Attack on Polish Ships.

RE: Netplay Surprise Port Attack

Posted: Thu Feb 06, 2014 5:18 am
by warspite1
Port Attack in solitaire mode is pretty screwed up at present. This has been reported so its a known problem. Hopefully will soon be fixed.