Is there any way I can fix this?

[witp1951]

A fragment of the 144th IJA RGMT did not recombine after units assembled when transports were attacked and some lost. Now its recognized as a Brit. PBEM Scenario 1. The troops are uneasy following Major Hicks. And there is the language barrier.

[Crackaces]

You are assuming that Maj Hicks might not have graduated with a degree in Japaneese [8D]

Wow .. what a corrupton of reality ...[X(]

[Capt Cliff]

Wow!! That is nuts!! What you need is a saved file editor.

[michaelm75au]

ORIGINAL: witp1951

A fragment of the 144th IJA RGMT did not recombine after units assembled when transports were attacked and some lost. Now its recognized as a Brit. PBEM Scenario 1. The troops are uneasy following Major Hicks. And there is the language barrier.

What game version are you playing?
If current patch, do you have a save of the turn when this happened so I can replay it?

[witp1951]

Saved game prior to Rabaul invasion attached with file extension changed to zip. We were using r6 at the time fragments were unloaded in two different locations. We changed to r9 when patch 6 was final. Transports from two locations with 144th were combined and invaded Rabaul and the fragment originally located elsewhere went over to the enemy.

[witp1951]

Here is the following game turn with the fragment identified as a Brit.

[michaelm75au]

Bad fragment still shows if run turn on latest build.
Will investigate where this happens.

[michaelm75au]

The problem seems to that one of 144th fragments is pointing to another fragment as its parent. Something that shouldn't happen. This fragment is the 224 RAF unit. Can see this if you look in TF 93. There are 3 fragments to 144th, but only 2 actually show up if the click on the Unit Org for 144th.
This data mishandling occurred presumably during the TF 93 load process. Do suppose you have that save?

[witp1951]

OK. Here is turn with 144th on its way to Truk

[witp1951]

Here is next turn after Allied carriers had their way with the transports. 144th split into different escort TF. I think the fragment in question is in TF109

[witp1951]

Here is the following turn after TF109 transport sinks and troops rescued by PB. No wonder they changed sides!

I have more turns if needed.

[witp1951]

Here is the turn where TF93 loads for Rabaul.

[michaelm75au]

There is a big gap between the latest saves (early Dec 41 - turn 10) and the ones with the problem (late Jan 42 - turn 52)
The fragments are fine in the last saves.
Any chance for the saves from turn say turn 48 to turn 51 - use my email (michaelm75 @ hotmail.com) to save time.

I'll backtrack till the fragment comes good and then see why it goes bad.

[witp1951]

Backtracking through the saves here are the turns where the 144th fails to combine at Truk. In this turn a fragment is at Truk and the rest of the Rgmt about to dock.

[witp1951]

Now we have two separate fragments at Truk.

[michaelm75au]

ORIGINAL: witp1951

Backtracking through the saves here are the turns where the 144th fails to combine at Truk. In this turn a fragment is at Truk and the rest of the Rgmt about to dock.

Can I have the one before this. The rest of 144 has already unloaded. And no TF seems to be there.

[witp1951]

ORIGINAL: michaelm

ORIGINAL: witp1951

Backtracking through the saves here are the turns where the 144th fails to combine at Truk. In this turn a fragment is at Truk and the rest of the Rgmt about to dock.

Can I have the one before this. The rest of 144 has already unloaded. And no TF seems to be there.

I think this is the one you've requested.

[michaelm75au]

I tried loading the 2 parts of  the 144th at Truk with the other save, and I can see that when the orphaned fragment loads on ship is treats the old fragment as its parent. But then that fragment goes away and is used by something else (in your game the 224 RAF). Thus the chain back is ending at the wrong unit.
I have added logic to cause a fragment to drop its parent if it is another fragment. This would fix problems where this has already happened and allow the fragment to be disbanded (add devices back to pool).
In the meantime, I'll look at the saves to see WHY this happens in the first place.

[michaelm75au]

Sorry, could I have one before. Looks like the bad fragment is the one already unloaded.

[witp1951]

ORIGINAL: michaelm

Sorry, could I have one before. Looks like the bad fragment is the one already unloaded.

Is this the turn you need?