Close Combat: The Longest Day - v5.50.33 Update

[AlbertoC]

We're releasing a new update for a few games of the Close Combat franchise. It contains a few fixes for The Longest Day, Wacht am Rhein and Last Stand Arnhem.

You can find the full changelog down below:

Changelog:
• Fixed potential crash caused by duplicate weapons firing during airstrikes in multiplayer games.
• Armored fighting vehicles with light damage (damaged, immobilized, or main gun out) are now tallied as ‘Damaged’ on the debrief screen.
• Armored fighting vehicles with light damage must pass a repair check to be recovered and repaired between battles.
• Halftracks, armored cars, and towed guns with light damage are automatically repaired between battles.

[Tejszd]

Thank you!

[WilliSaenger]

I had a multiplayer game yesterday and both of us had the .33 patched version of the game. Unfortunately the game crashed during an airstrike. Did you notice that the counter in game is still .32 while in the launcher is .33? This causes some confusion amongst players who think their version of the game is not even patched!
Try to fix the game or release the source code!so that we can do it! Thank you.

[WilliSaenger]

The message above was intended for you Alberto.

[SteveMcClaire]

Hi WilliSaenger -- which game crashed, the host or the client? Where did you update your game? From Matrix, Steam, or GOG? If possible, it would be helpful to know where your opponent updated from as well. Thanks.

[WilliSaenger]

Hello Steve,

I don't know if the client or the host crashed unfortunately.We both have the Matrix version of the game and the update from the Matrix website.

Thanks for reaching back.

[SteveMcClaire]

Thank you for the information. I will take a look at the build to make certain it has the correct files.

[WilliSaenger]

[UPDATE]
After playing dozens more multiplayer battles, I did not encounter any crashes during an airstrike.
What I did encounter though were multiple crashes exactly at the end of the battle after a morale breakdown.
It may well be, that the game did not crash because of the airstrike in the first place the first time I reported it here, but because of morale breakdown and consequentrly end of battle AFTER the airstrike hit the enemy troops.
So the cause may lie in some routines that are called at the end of the battle.
Hope this helps you out guys.

Any update from your side?

Thank you!

[SteveMcClaire]

I've confirmed that the version number shown on the game main screen is incorrect -- there is a resource file that the Matrix update doesn't replace. The executable in the update is correct, it's just the string for the version number that is not. This is being corrected.

I haven't been able to reproduce the crash on battle-end but will investigate that further when time allows.