CV flying as fighter never returns to base

[oleb]

Japan escorted a ground strike with a CV unit. The unit never returned to base. After conquest the game checks for overstacking. A Chinese/yellow "Overstacked Hex" interface opens up. Clicking "Destroy this unit" crashes, clicking "OK - Done" opens the same interface again. Save game available.

[Shannon V. OKeets]

ORIGINAL: Ktarn

Japan escorted a ground strike with a CV unit. The unit never returned to base. After conquest the game checks for overstacking. A Chinese/yellow "Overstacked Hex" interface opens up. Clicking "Destroy this unit" crashes, clicking "OK - Done" opens the same interface again. Save game available.

Could you please send the saved game to MadExcept@MatrixGames.com?

This bug appeared during beta testing but I had trouble reproducing it.

[AxelNL]

Did you do a game save between the grond strike/support with the CV unit and the combat?

[oleb]

ORIGINAL: AxelNL

Did you do a game save between the grond strike/support with the CV unit and the combat?

It was a ground strike. Only automatic savegames, and they are overwritten by now. The hex is empty apart from the CV unit.

Savegame from conquest phase sent.

[AxelNL]

ORIGINAL: Ktarn

ORIGINAL: AxelNL

Did you do a game save between the grond strike/support with the CV unit and the combat?

It was a ground strike. Only automatic savegames, and they are overwritten by now. The hex is empty apart from the CV unit.

Savegame from conquest phase sent.

No reloading of autosaves done in between? That could be the culpritt.

[oleb]

ORIGINAL: AxelNL


No reloading of autosaves done in between? That could be the culpritt.

I did a couple of reloads.

[AxelNL]

ORIGINAL: Ktarn

ORIGINAL: AxelNL


No reloading of autosaves done in between? That could be the culpritt.

I did a couple of reloads.

I think that until Steve fixes this we should try to limit the reloads (to zero) in between assigning a CV air component to Ground Strike/Support and the end of the combat phase. When you do not do a reload in that window this works as it should be.

That means accepting bad combat results for the moment! [8|]

[oleb]

ORIGINAL: AxelNL

I think that until Steve fixes this we should try to limit the reloads (to zero) in between assigning a CV air component to Ground Strike/Support and the end of the combat phase. When you do not do a reload in that window this works as it should be.

That means accepting bad combat results for the moment! [8|]

I think the problem is the escort mission, not the ground strike, but not 100% sure.

Why do you think reloading is a factor?

[AxelNL]

ORIGINAL: Ktarn

ORIGINAL: AxelNL

I think that until Steve fixes this we should try to limit the reloads (to zero) in between assigning a CV air component to Ground Strike/Support and the end of the combat phase. When you do not do a reload in that window this works as it should be.

That means accepting bad combat results for the moment! [8|]

I think the problem is the escort mission, not the ground strike, but not 100% sure.

Why do you think reloading is a factor?

Because this stuff works if you don't reload a saved game in those phases, and this problem appears in your case and my current game when reloading. Most folks play with the optional rule where the air component is a separate air unit (with or without a pilot). This problem probably doesn't appear in that case.

[oleb]

ORIGINAL: AxelNL


Because this stuff works if you don't reload a saved game in those phases, and this problem appears in your case and my current game when reloading. Most folks play with the optional rule where the air component is a separate air unit (with or without a pilot). This problem probably doesn't appear in that case.

What do you mean by "those phases"? In my current game I flew two ground strikes with CV units. The next impulse I reloaded the dow-step, and the carrier units were still in the hex (displayed as fighters).

[AxelNL]

ORIGINAL: Ktarn

ORIGINAL: AxelNL


Because this stuff works if you don't reload a saved game in those phases, and this problem appears in your case and my current game when reloading. Most folks play with the optional rule where the air component is a separate air unit (with or without a pilot). This problem probably doesn't appear in that case.

What do you mean by "those phases"? In my current game I flew two ground strikes with CV units. The next impulse I reloaded the dow-step, and the carrier units were still in the hex (displayed as fighters).

Wow, you went back to DoW and the CVair units where still "ghost-overed" from a later phase? Are you sure? Could you try to reproduce this with a reboot in between? I have never seen this one.
This problem can only happen if the program was not completely ended, where there are e.g. loose memory chunks influencing prior saves when loading. If you can reproduce this and give clear instructions for Steve how to get this, he will be able to do something about this.

[oleb]

New savegame sent.

Steps to reproduce:
1. load axis ground strike cap imp#1
2. ground strike hex 86,141 with Soryu and Hiryu (both flying as bombers)
3. end phase to arrive at imp#3 axis
4. Choose land action with Japan
5. Proceed to Naval air
6. Reload choose action Japan
7. Behold the carrier units in 86,141

Rebooting, then loading choose action Japan yields the same result.

Note that the title is misleading. The CV flies as a bomber, but is displayed as a fighter before the game crashes. The first time the bug occured I flew one bomber and one escort, and assumed it was the escort that didnt return.