Crash after paradrop

[Mitotyn]

After paradropping a US para corps into an italian hex already being invaded by two other US units,
the game reports an error and i am unable to continue.
Tried without any air combat but still get a crash.

I noticed that the invading units after the paradrop mission are marked as paradropping instead of invading,
and the IT notional strength has mysteriously dropped from 3 to 2[&:]

I mailed the bug report file earlier today, but i post a savegame from the paradrop phase here too.
To replicate, load the US para in sicily on the CW atr and drop on the invasion hex.

Mitotyn

[Centuur]

I can't recreate this bug using the latest beta test version. I dropped the PARA with no problems and got the correct odds calculation at the start of the land combat declaration phase.

[paulderynck]

There could be another issue. If one of the invading units was not a Div, then this move is illegal. You cannot overstack by invading with two corps and dropping a para corps.

I would have thought MWiF would have caught this, though, had it been tried.

[Shannon V. OKeets]

ORIGINAL: paulderynck

There could be another issue. If one of the invading units was not a Div, then this move is illegal. You cannot overstack by invading with two corps and dropping a para corps.

I would have thought MWiF would have caught this, though, had it been tried.

The para may or may not get through - so checking for overstacking doesn't occur until after that result has occurred. But you're right, the para should probably be destroyed (before adding to the attack)) if it does get through the air-to-air combat and the anti-aircraft fire.

[paulderynck]

I don't even think you can fly the mission under the rules. "You may not voluntarily overstack..."

[Mitotyn]

No, one of the units invading is an INF division, the other a MOT corps, so there is no overstacking issue.
I am using the version 2.5.5 that was hot-patched earlier this week.

Any chance of you posting a save game after successfully completing the paratroop Peter? [&o]


Mitotyn

[Centuur]

Of course.

[Mitotyn]

Thank you! [:)]
You have greatly aided the struggle against tyranny!...
(Playing solo, i will of course be the tyrants next impulse...[8D])

Mitotyn

ORIGINAL: Centuur

Of course.

[Mitotyn]

I have experienced two more of these Para-problems in 2.5.5 [:(]

They occur when i paradrop into a hex that is also being invaded, in all instances there have been a corps & a div invading so there is no overstack.
When the paradrop phase begins, the invading units are flagged as paradropping, and when the drop is cleared through any air combat,
there is an error message before returning the atr to base, and i can't continue the game.

Paradropping into non-invasion hexes works fine.

Mitotyn

[Centuur]

That's strange behaviour. If you reload the Paradrop autosave, can you proceed normally? If so, than reloading that gamesave will somehow get rid of the problem for you.

Can you post a gamesave from before the invasion takes place with instructions what hex to invade and where the PARA needs to come from? I think we need to investigate this further.

[Mitotyn]

Hi!

No, reloading didn't work.
In order to continue the game I made a work around by calculating the odds as if the paradrop was done, and then adjusting the die roll...
So the autosaves are overwritten, i did however zip the para cap phase so here it is attached.
The para and atr are in Sicily, and the invasion hex is the coastal forest hex in Yugoslavia.

Note also that the invading units including a US mar div invading next to Truk are flagged as paradropping!
After the crash, you'll see that the notional defense strength in Yugo has dropped by one...

The original savegame from my original post might also give some clues.

Thank you for your interest!

Mitotyn

ORIGINAL: Centuur

That's strange behaviour. If you reload the Paradrop autosave, can you proceed normally? If so, than reloading that gamesave will somehow get rid of the problem for you.

Can you post a gamesave from before the invasion takes place with instructions what hex to invade and where the PARA needs to come from? I think we need to investigate this further.

[Centuur]

I don't get that crash if I load this gamesave and land the PARA. The game continues correctly. I don't know what's wrong at your end.

[paulderynck]

Maybe this is one of those "I always click this or that in this order, and you don't" things.

Perhaps Mitotyn needs to describe the steps followed in detail.

[Mitotyn]

Well, the three times i have tried to paradrop a hex that is also being invaded, the game crashes.

Dropping the Para alone, or to attack with other non-invading adjacent units works fine.
The crash occurs when the atr should be returning to base.
The invading units, that until the paradrop are flagged as invading, are in the paradrop phase flagged as paradropping instead?
After the crash, hovering the mouse over the target hex shows the notional defense strength reduced by one.
The drops in the two previously attached files were against notionals only, the third was against two defending units.

I hope the bug report and the savegames contains enough material to solve this, operation Overlord is getting closer... [:)]

Mitotyn

[Centuur]

Which buttons are you using from the moment you are loading the PARA until the moment the crash happens?

I can't reproduce this bug with you gamesaves.

So: how do you load the Para (which buttons are you using)?
and:
how do you return the ART to base?

This is important, since you are probably using a different way to drop the PARA than I do. That might cause the crash...

[Shannon V. OKeets]

ORIGINAL: Centuur

Which buttons are you using from the moment you are loading the PARA until the moment the crash happens?

I can't reproduce this bug with you gamesaves.

So: how do you load the Para (which buttons are you using)?
and:
how do you return the ART to base?

This is important, since you are probably using a different way to drop the PARA than I do. That might cause the crash...

I agree. It works correctly for me too. No Mad Except and the Notional value is correct.

The label that the units invading by sea are paradropping is cosmetic - it has to do with the phase of the game being Paradrop. Once you get to the Land Combat phase(s), all the invading units (by air or by sea) are shown as Invading.

EDIT: I ran both saved games and both behaved correctly.

[Mitotyn]

Ok, it seems i'm alone with this problem.
I'll see if it disappears in the next patch/update.

Keep up the good work! [:)]

Mitotyn

[Sabre21]

I'm having the same exact problem as Mitotyn described above when dropping an airborne unit along with an invasion using 2.5.5 patch. The airborne drop works without an invading corps, but crashes if a single ground unit is added in. I will try and upload a save game and include exact steps.

[Sabre21]

Ok..here are step by step instructions on how to recreate the airborne/invasion crash.

I am playing a Global War scenario in solitaire mode on my desktop using windows 10 and am in the German invasion phase of the game.

1. Move the cursor over the German fleet located in the Baltic Sea 3 box. Using the Flyout box, advance the box until the German 9-4 infantry corps is displayed and then drag/drop it onto the Swedish IV infantry corps located at the Malmo port.

2. Left click the green advance button to the German Paradrop phase;

3. Using the Flyout box again, move the cursor over the German Ju-52 unit on the northern tip of Denmark.

4. From the flyout box, right click on the Ju-52 and load the para unit.

5. Again from flyout box, left click Ju-52 and drag it over the Swedish corps at the Malmo port where you invaded and drop the para unit.

6. Left click the green advance button and the game will crash. So far with 5 attempts it has crashed 5 times.

Attached is the Invasion game file.

[Sabre21]

Here is a copy of the crash screen.

I hope all this helps correct this problem.