Matrix Games Forums

what goes wrong if this happens? I just unloaded a brigade at an enemy atoll and during the combat replay I see two "brigades". One is the 56th brigade and one the 56/1 brigade. I unloaded them from the same TF at the same time. Now the bad thing about it: the "parent" unit was very small and was wiped out immediately, while the much bigger fragment only had some disablements. BUT the fragment didn´t become the parent unit so IN FACT I now lost a whole brigade due to sh*t happening!

Any suggestions why the game makes a tiny parent unit and a BIG fragment of a unit when I unload them from the same TF?? [8|]

It is normal while unloading to have several 'fragments' of the same unit in same hex.
There is a phase later during the turn that does sub-unit merging that collects the fragments.
Do you have any ships still unloading the 56 Brigade? It is possible that one of the fragments still on the ship has become the 'parent'.
The choice of which is parent is based on what it determines the 'size' of the fragment is. Size does not necessarily mean more devices.

ORIGINAL: michaelm

It is normal while unloading to have several 'fragments' of the same unit in same hex.
There is a phase later during the turn that does sub-unit merging that collects the fragments.
Do you have any ships still unloading the 56 Brigade? It is possible that one of the fragments still on the ship has become the 'parent'.
The choice of which is parent is based on what it determines the 'size' of the fragment is. Size does not necessarily mean more devices.

no, all fragments were unloaded during the turn, BEFORE the combat happened. After the combat, the parent unit was wiped out. The fragment stayed on the island without becoming the parent unit and there wasn´t a single man left on the ships. Then I loaded up the fragment (56/1 brigade) on the ships again and left. On the ships there are now 56/1, 56/2, 56/3... fragments but no parent 56 brigade. [&:]

Since the parent unit was destroyed in combat, one of the fragments should become the parent.  If it doesn't happen on the ship, hopefully it'll happen after they are unloaded.  Keep your fingers crossed.

ORIGINAL: Mike Solli

Since the parent unit was destroyed in combat, one of the fragments should become the parent.  If it doesn't happen on the ship, hopefully it'll happen after they are unloaded.  Keep your fingers crossed.

I will for sure... [:D]

ORIGINAL: Mike Solli

Since the parent unit was destroyed in combat, one of the fragments should become the parent.  If it doesn't happen on the ship, hopefully it'll happen after they are unloaded.  Keep your fingers crossed.

In previous versions, if the parent "fragment" was destroyed, then all the other fragments vanished, but i think (hope and pray) this is fixed... this was a real pain when the ship with the parent (say, of the 2nd Marine Div) was torpedoed, and then the whole division (spread out on 10 ships) disappeared!! [X(]

Normally the fragment with the most support squads becomes the parent.

It isnt fixed, actually it isnt "a bug" (I believe it is also). I had a simular situation a few weeks ago and was told "working as intended".

I landed the South Seas on Midway, had 440 losses, and the remaining 5400 troops of the South Seas went poof.

ORIGINAL: Yamato hugger

It isnt fixed, actually it isnt "a bug" (I believe it is also). I had a simular situation a few weeks ago and was told "working as intended".

I landed the South Seas on Midway, had 440 losses, and the remaining 5400 troops of the South Seas went poof.

Yes - it was supposed to say "unit destroyed by attrition" - but it didn't show that in your replay for some reason...

Well, if it is working as intended then I wonder why now, as the rest of my brigade is unloaded at a safe place, it now shows 56/4 brigade and when I click on it I get into the 4th naval HQ screen... [8|]

Means I lost the unit (as expected) due to the parent unit wiped out (even if the parent unit only was tiny compared to the fragment!!) and now the fragment has turned into a GHOST unit... It won´t rebuild, it won´t fight, it is no longer accessable to me...

working as intended... [8|] must be seldom happening though as I have seen this the first time, but it is still annoying if you see a whole brigade being destroyed (in my case vanishing or becoming a ghost) because some kind of unload routine decides to make two parts of a unit with the parent being very small, that it gets immediately wiped out....

I have had that happen as well when the parent dies of attrition and there are fragments, but not in 1.806. Are you still using 1.804? I KNOW it used to happen there, but as I said, I have yet to see it in 1.806.

ORIGINAL: Yamato hugger

I have had that happen as well when the parent dies of attrition and there are fragments, but not in 1.806. Are you still using 1.804? I KNOW it used to happen there, but as I said, I have yet to see it in 1.806.

no using 1.806. While it is certainly always not nice to lose a unit because a fragment doesn´t rebuild in this case it is still different as the only reason I lost the unit is the fact that the unit unloaded and there was the parent (very small) and the fragment (nearly the complete unit). Then the parent decides to die because of attrition . No way the whole brigade could have died, only the "parent fragment".

And to make it perfectly worse, the fragment (which is nearly as big as the whole unit) is now a ghost unit... [8|]

so the problem actually started because the ONE unit was unloaded and split into a tiny parent and a huge fragment. And I can´t see a reason why this is happening.

Well I have been trying to set up a situation in a game where the parent and fragment switch places and reverse the movement orders and this may be related. I THINK I should have it on my next turn. Turn after next at the latest. Depends on how many troops my air transports move. Im using the low capacity Dutch ones so I can watch it.

Was this a new game started under 1.806 or one begun under an earlier version and then upgraded?

ORIGINAL: michaelm

Was this a new game started under 1.806 or one begun under an earlier version and then upgraded?

mmm, I think we started under 1.804 just shortly before 1.806 came out.