Fast TR problem

Post bug reports and ask for help with other issues here.

Moderators: wdolson, MOD_War-in-the-Pacific-Admirals-Edition

Post Reply
Chris21wen
Posts: 7861
Joined: Thu Jan 17, 2002 10:00 am
Location: Cottesmore, Rutland

Fast TR problem

Post by Chris21wen »

Latest Patch. DaIronBabes C

A fast TR heading for Bandjermasin will not unload. I'm told it ‘cannot unload here ‘ and it matters not what the destination is. It load as a fast TR but something has screwed up, probably the air attack made on it last turn. I’ve even tried creating a new single ship fast TR but get the same effect. The message goes away if I create a standard TR though.
Attachments
wpae010.zip
(2.61 MiB) Downloaded 4 times
User avatar
Puhis
Posts: 1741
Joined: Sun Nov 30, 2008 6:14 pm
Location: Finland

RE: Fast TR problem

Post by Puhis »

ORIGINAL: Chris H

Latest Patch. DaIronBabes C

A fast TR heading for Bandjermasin will not unload. I'm told it ‘cannot unload here ‘ and it matters not what the destination is. It load as a fast TR but something has screwed up, probably the air attack made on it last turn. I’ve even tried creating a new single ship fast TR but get the same effect. The message goes away if I create a standard TR though.

I believe at the moment your TF is at coastal marsh hex. It cannot load there, but it can unload when the TF arrives base hex.

"Cannot unload here" means TF cannot unload that particular hex.
Chris21wen
Posts: 7861
Joined: Thu Jan 17, 2002 10:00 am
Location: Cottesmore, Rutland

RE: Fast TR problem

Post by Chris21wen »

ORIGINAL: Puhis

ORIGINAL: Chris H

Latest Patch. DaIronBabes C

A fast TR heading for Bandjermasin will not unload. I'm told it ‘cannot unload here ‘ and it matters not what the destination is. It load as a fast TR but something has screwed up, probably the air attack made on it last turn. I’ve even tried creating a new single ship fast TR but get the same effect. The message goes away if I create a standard TR though.

I believe at the moment your TF is at coastal marsh hex. It cannot load there, but it can unload when the TF arrives base hex.

"Cannot unload here" means TF cannot unload that particular hex.

Thanks for the reply. Why would I need a message telling me I cannot unload at a hex the TF is currently in if the hex is not the destination hex of the TF. Who cares about that, it's the destination hex I'm interested in. Now if this is the case then that message should be removed ASAP, it's misleading, pointless and plain stupid.
Post Reply

Return to “Tech Support”