Page 1 of 1

Strange Message: Task force unable to unload at this location.

Posted: Sat May 17, 2003 4:21 am
by Deathtreader
Has anybody seen this message before?? I just pounded the wazoo out of Port Moresby for the 3rd consecutive day prior to launching an invasion. My task force starts to offload (aggressive commander, patrol/do not retire) the warrior sons of heaven & then this message streaks across the screen. The next turn has the task force slinking home with about 12 squads left ashore to face the inevitable. Is this a bug?? If not, any ideas as to what I'm doing wrong??
Scen. 17 as Japanese started under ver. 2.30. Task force ships suffer no damage (other than normal at sea sys. damage), adequately fuelled at start of invasion turn (no refuelling to eat up points etc), unopposed landing, air superiority, etc
I can't figure this one out. Any suggestions gladly accepted. :confused:

Posted: Sat May 17, 2003 8:58 am
by Mike_B20
I believe this message sometimes appears if there are enemy naval forces detected in the hex.

Maybe there's another explanation.

Posted: Sun May 18, 2003 7:44 pm
by Chris21wen
I've had it happen on a number of occasions, and as Mike_B20 said it occurs when an ememy TF is in the same hex. Makes sense though.

Posted: Sun May 18, 2003 8:47 pm
by brent_2
yeah - i get the "cannot unload here and now" either just before or after some BBs have just waxed the convoy :mad:

Posted: Mon May 19, 2003 4:40 am
by Mike_B20
Originally posted by brent_2
yeah - i get the "cannot unload here and now" either just before or after some BBs have just waxed the convoy :mad:


:D

...even in the middle of the Pacific, nearest land 500 kilometres away.

Sigh of relief..........

Posted: Mon May 19, 2003 4:50 am
by Deathtreader
Thanks guys!
Good to know. I'm feeling much less frustrated about it now. (I guess misery really does love company ;)

Rob.

same problem

Posted: Tue Jul 27, 2004 2:43 am
by Gladius
Hi!

I got the same message, but as far as I know their was no enemy
TF near and I sent it back again and it worked.

is there an official statement, what causes this message?
(after all the message System is very weird in my opinion)