Page 1 of 1
Fast TR problem
Posted: Tue Nov 26, 2013 8:39 pm
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.
RE: Fast TR problem
Posted: Thu Nov 28, 2013 7:10 am
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.
RE: Fast TR problem
Posted: Fri Nov 29, 2013 6:12 am
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.