Gateway to Caen Official Update v1.01 Now Available

[Gerry Edwards]

Hello Everyone,


The Close Combat: Gateway to Caen v1.01 update has been officially released. You can update via your update client or with the direct link Here. Please let us know of any issues you may have updating and enjoy.

v1.01 – June 8, 2014

Bug Fixes
- Fixed ‘Invalid Call’ error when using multi-player chat with minimum screen resolution window and Windows task bar present.
- Fixed an end of battle crash bug.
- User names are now removed from the lobby list as soon as a user connects to an opponent.
- Direct connect mechanism has been updated and enabled.
- Multi-player ‘help’ dialog now shows 1 of 3 tips, rotating each time you come into the screen.
- Failed connection attempts time out after 30-40 seconds in all cases.

Cheers,
Gerry

[Jonathan Pollard]

Do we need to delete the multiplayer hotfix before installing the patch?

[SteveMcClaire]

The patch will overwrite the necessary files, so no you do not need to delete anything.

Steve

[Jonathan Pollard]

I was unable to host a patched game using my Matrix version when my opponent had the Steam version. However, there was no problem connecting to a Steam opponent when I used my steam version. Also, the airstrike crash bug is still present in the patch. It happened both times I used an airstrike against a tank. I'm seriously considering doing a mod of the grand campaign that does not have any airstrikes available.

[Cathartes]

If anyone sees an airstrike bug, can you please provide detailed information? We were only able to reproduce this when a successful airstrike led to a force morale collapse at end of game, otherwise we have not been able to reproduce this in testing h2h. Any information you can provide related to the type of aircraft, the type of vehicle hit, time of game, and general circumstances of battle would help. Screenshot is always helpful as well.

[Tejszd]

Thanks for the patch!

Glad to hear an end of battle crash was found. Given that this game is still using the original CC engine then the odds are that the same crash bug is in previous CC games so when will they get this fix?

[SteveMcClaire]

ORIGINAL: Tejszd
Glad to hear an end of battle crash was found. Given that this game is still using the original CC engine then the odds are that the same crash bug is in previous CC games so when will they get this fix?

The same issue might exist in Panthers in the Fog, but not any earlier versions. This is in code new as of Panthers. If / when there is an update to Panthers in the Fog, I will check all code changes between the two games and fix it if so.

Steve

[Troger]

ORIGINAL: Steve McClaire

ORIGINAL: Tejszd
Glad to hear an end of battle crash was found. Given that this game is still using the original CC engine then the odds are that the same crash bug is in previous CC games so when will they get this fix?

The same issue might exist in Panthers in the Fog, but not any earlier versions. This is in code new as of Panthers. If / when there is an update to Panthers in the Fog, I will check all code changes between the two games and fix it if so.

Steve

Not sure which end of battle crash you and Tejszd are referring to, but if it's the 00:00 timer crash, it's been around since CC3 I believe.

ORIGINAL: Jonathan Pollard

Also, the airstrike crash bug is still present in the patch. It happened both times I used an airstrike against a tank. I'm seriously considering doing a mod of the grand campaign that does not have any airstrikes available.

[:(]

[SteveMcClaire]

ORIGINAL: Troger
Not sure which end of battle crash you and Tejszd are referring to, but if it's the 00:00 timer crash, it's been around since CC3 I believe.

The way the old CC engine is designed, there is a LOT of code that executes at the end of every battle. All the post-battle clean-up and tallying, all the 'prep for next battle/turn/day' campaign and operation code, all this information is exchanged between host and client, and then the debrief screen is executed. 'End of battle' crashes can be anywhere in this, and are likely different causes for any given version of the game.

Steve

[PztCrackwise]

An in-game (tactical screen) save option would nullify all the annoying things with the crash. Why can't you guys put a save-option there, is it not possible?

Turning auto-save on for instance to something like to save each 5 minutes would prevent many of the frustrations we have here with the random crashes.

(Of course, ideally there should not be any crashes at the first place. But assuming current engine does not allow you to fix these crashes, then you should at least try implementing such a feature.)

[SteveMcClaire]

ORIGINAL: PztCrackwise
An in-game (tactical screen) save option ... Why can't you guys put a save-option there, is it not possible?

It is possible but it's not something that has ever been in the game, and thus it's not something simple to do. It would be a significant work item in terms of coding and testing, and for all that not something very many people would ever be likely to use. That said, we do discuss it from time to time and I'll keep it in mind.

Steve

[Keston]

Installed, clicked "Check for Update" in the initial screen, get
"Download Error
Click Back to retry or Cancel to quit.

Error:

Unable to download file.
An error occurred while trying to open an FTP file."

-------- Zip download installs without complaint. Got my fingers crossed (tough to type).

Thanks.