GBirkn
Posts: 249
Joined: 5/6/2004 From: the briny deep Status: offline
|
Thinking about this a little more, I have a theory as to why this happened, and a test seems to confirm it. Here's the theory: the problem began when I created three separate TFs to load these units and then merged them together. Here's what I did to test this theory. I started up the Marianas scenario, vs. Japanese computer. On turn 1, I took all of the existing TFs and set their destination to be the Eniwetok base where they start (just to avoid distraction). On turn 2, I created a TF with 2xAP of 4000 capacity, and told it to load the 73d Base Force (AP load cost: 7,148). I created another TF with a 6000 cap AP and a 4000 cap AP, and told it to load the 71st Aviation Rgt (AP load cost: 8,080). I created a third TF with a single 6000 cap AP, and told it to load the 100th SeaBees (AP load cost: 3,480). I then selected the 1st TF, the one loading the 73d Base Force, and clicked on "transfer ships to/from tf". I transferred all of the APs from the other two TFs into this one. The combined TF took a few days to load, but when it finally sailed, it included the 100th SeaBees/1, which left no parent unit behind on the base. (The 73d BF loaded completely with one of the fragments chosen to be the parent, the 71st Aviation left a parent unit behind at the base.) I then sent the TF back to the base, and unloaded it, and the 100th SeaBees disappeared. So, the obvious workaround is: don't merge TF's while they're loading troops. You can merge them (like the tutorial tells you to), just make sure that they're completely loaded, or better yet a hex out to sea before you do it.
_____________________________
"War is the remedy our enemies have chosen, and I say let's give them all they want." -- Gen. W. T. Sherman
|