REALLY annoying...

[Mike Scholl]

There are a lot of problems remaining in various parts of the game. Land Combat, Coastal Artillery Combat, Supplies "wandering off", etc all have several threads going.
But for sheer annoyance (probably because if I remember to set everything just right
it can be avoided, but invariably I forget periodically), nothing drives me crazier than
the bizarre conpulsion of troop-carrying transport TF's to unload troops on every piece
of land thay pass through!

Whether it's a number of sub TF's trying to bring a cadre out of the Philippines, or an
AP bringing some Aussies out of Singapore, it makes no difference what the actual
destination hex is----unless the TF is specifically tabbed to "DO NOT UNLOAD"; I end
up leaving chunks of unit standing around in mangrove swamps of coastal hexes the
TF sailed through. I don't understand why the "default" on a troop transport mission
seems to be "bail out on any rock we pass!". It's not like the TF's have been damaged
(some have, some have not) --- it seems to be in the game primarily just to cause
"hair-tearing aggrivation" for players who forget to fiddle everything "just right".

Anybody else got one of these "REALLY Annoying" little glitches that drive them nuts?

[byron13]

I think I've had that happen even with "do not unload." I regularly sailed LCUs from SF with destination Canton Island, home port Noumea. I always had them set to do not unload with the idea of letting them refuel in Canton. It was not unusual for me to find fragements on Canton Island that I would have to divert APs to go and pick up. As a result, I now send them one hex away from Canton where they can rendezvous with escorts for the run in to Noumea.

I wonder if that has anything to do with replacements. In other words, the unit still has replacements arriving and when the ship briefly visits the island, no troops actually get off, but some replacements arrive at the island that don't make it onboard the troop ship when it weighs anchor. Regardless, I do avoid intermediate stops with troop ships even with the TF set to do not unload.

[Nomad]

I had part of the 27th Division get off at Christmas Island. The TF was set for do not unload and was at Christmas Island to refuel and wait for a second TF that was lagging behind. That was annoying since it took about 6 days to reload them. [&:][:@]

[byron13]

ORIGINAL: Nomad

I had part of the 27th Division get off at Christmas Island. The TF was set for do not unload and was at Christmas Island to refuel and wait for a second TF that was lagging behind. That was annoying since it took about 6 days to reload them. [&:][:@]

Are you really sure they got off? Is it possible that what was left on Christmas were replacements that never merged with the troops on board ship? I think Christmas would have had to have the 20k in supply to do so, but it is another possibility.

But Mike is right: this is annoying.

[freeboy]

But for sheer annoyance (probably because if I remember to set everything just right
it can be avoided, but invariably I forget periodically), nothing drives me crazier than
the bizarre conpulsion of troop-carrying transport TF's to unload troops on every piece
of land thay pass through

Sounds like a bug, I have 1500 turns behind me or so, and have not seen thisparticular one

[Nomad]

ORIGINAL: byron13

ORIGINAL: Nomad

I had part of the 27th Division get off at Christmas Island. The TF was set for do not unload and was at Christmas Island to refuel and wait for a second TF that was lagging behind. That was annoying since it took about 6 days to reload them. [&:][:@]

Are you really sure they got off? Is it possible that what was left on Christmas were replacements that never merged with the troops on board ship? I think Christmas would have had to have the 20k in supply to do so, but it is another possibility.

But Mike is right: this is annoying.

No, the division was complete before leaving Los Angles. Since 246 attack factors got off, I doubt is was some kind of reinforcements.

[byron13]

Fair 'nuff. Same thing might have been happening to me. But, since I don't do it no more, I'm not in a position to test a fully-stocked unit.

[Titanwarrior89]

I played thru the whole game and as far as i could tell that never happened to me. But i had multiple patches applied to the game.[:D]

[Mike Scholl]

I have applied every patch as it became available,,,. but this still occurs.

[mogami]

Hi, I have not seen it yet. I used to see it in UV and it was very annoying.

[herbieh]

I get this all the time
I just treat it as troops on leave, special training, convalesing, even guys who's train was delayed.
Pretty rare to ever have 100% of a unit actually at the same location
(troops unloading - AWOL[:D][:D][:D]- happens a lot in my army, they know what is going to happen to em[8|][8|][8|][:'(])

[eMonticello]

The line to the head was too long and the ship sailed without them?

[ZOOMIE1980]

Not just troops but just about anything. It would seem to me that a commander would be smart enought to realize you don't want to unload 900,000 barrels of fuel on Pago Pago....

[von Murrin]

Interesting.

I've never, ever seen this. My play preferences require I only use "Patrol/Do Not Retire" OR "Do Not Unload", never both. I wonder if that has anything to do with it?

[Halsey]

I learned in UV never to set a destination for a TF that has any bit of land in it. If the TF has troops it starts unloading. SOP from here on out. Got to watch the sub trans missions very closely too.[;)]

[jwilkerson]

As IJN I use both Patrol and Do not unload as a standard ( together ) ... I had this happen to me a lot early on .. but not in either of my current PBEM games ... patch 1.4 fresh install with 1.3 comp patch.

It is a bug - but I seem to have found the magic way to avoid it in the current games ( wish I knew what they were ! ) ... but certainly use Do not unload ... don't rely on "AI" to avoid unloading at non-destination hexes with unload orders !