After much experimentation I figured out the problem.
When an Amphib TF is made the default values are “Retirement Allowed” and “Unload Cargo”.
When the TF is sailing to the pickup island it is empty, so these are fine.
Turn 1 the TF arrives at the pickup island, empty, you must have selected “Remain on Station” to get it to stick there. Because you can't pre-select the units to be removed and must do it after arrival.
Turn 2 you can select which units the TF will pickup.
Turn 3 the TF loads the units you selected. BUT, if you left the TF set on “Unload Cargo” it will then immediately unload them, that same turn.
Once the “load these” orders have been given you CAN change the order “Remain on Station” to “Retirement Allowed” as you prefer. But you MUST change the “Unload Cargo” to “Do Not Unload” if you have not already done so.
Note: When the TF was loading/unloading on the same turn defenders shot at the Amphib TF, a lot. When the Amphib TF just loads and leaves it did not get shot at. So if you Amphib TF is being shot at a lot it is because you are unloading stuff. Scrolling notes in lower left also contained messages about elements of the units on the island “merging”. Thus showing they were in fact divided, loaded, then immediately unloaded and merged. All in one turn.
I might have assumed that the Retirement/No Retirement command would be triggered as soon as the loading was completed. Nope, after loading it then checks that Unload/No Unload flag and only after executing that does it finally check the Retirement Allowed versus Remain on Station flag. Sequences of events do have consequences.
There was no need to "figure" this out, particularly as you haven't done it correctly for a naval evacuation anyway.
The correct technique to effect a naval evacuation is detailed in s.220.127.116.11 of the manual. Who da thunk the answer would be contained in a section titled "Naval Evacuations". Tricky those devs who wrote the manual, hiding the answer in plain sight.
Dude, many of us have politely asked you to chill-out with your patronizing responses.
What is your malfunction? Mock was sharing with us how he figured it out so there was no pressing need for you to open your dirty, filthy mouth.
God knows you wouldn't mouth off to me like you did to him if we we're in the same room.
Oh look, the troll Rusty1961 is back.
The troll who in a decade plus of being on this forum, has failed to provide any correct game advice. Whose own game posts have always demonstrated a complete and utter lack of game skill and knowledge.
A troll who never misses an opportunity to jump in to make an ad hominem post, which is totally unrelated to the threads subject matter, against anyone who has ever forensically demonstrated the inaccuracies of his souffle "contributions".
A troll who has claimed to be an engineer but whose lack of logic in addressing AE problems raises serious questions as to how he ever qualified and worked as one.
Yes, a troll whose every single AE post were to be deleted, not a single piece of AE knowledge would be lost.
A troll whose every OT thread demonstrates the validity of the old saying, "misery loves misery". Never constructive, but like a pig in mud, always relishing an opportunity to disparage, on a fact free basis, public officials and programs.
Yes, the troll is back. Soon to make another ad hominem attack because let's face it, he is the scorpion of the famous fable.