CTD during year change

[unmerged(147948)]

Im really pissed off..i guess it is some kind of a mission bug, that always occurs during the year change, in my case 1612 to 1613. I have 2 missions not accomplished, in first 1 i had to destroz a pirate fleet that should have been destroyed until 1613. The other 1 is to deliver a message in time from mz homeport to an indian port. In that mission i alreadz get a ctd when i simply try to click it in mission overview. In all cases i crash without any message, but with some delay to desktop. Plz add it to your mayor bug-list.

I should have known that, not to buy a game @ release date, the customer always plays the role of a beta tester in that stage.

PS: Im playing the german steam version

 

[unmerged(147948)]

Ok short update.. I re-installed EAC via the English Steam Client and now even my save games are working. So it seems to be only a mayor bug in the localized german version. Even the three XXX in the top right corner in the overview are vanished and the "Pause" Button appears.
So plz fix it. Its lame to play the Holy Roman Empire Company with english voices -.-

 

[Cloudbusting]

I have the same bug except that I m using the English gamersgate version of the game.
And I have no mission left the year where it crashes.
This bug has already happened to me twice in 2 different game and I already tried to reinstall the game after the first time it happened.

 

[unmerged(140091)]

This will be fixed in the next patch.

 

[unmerged(147948)]

This will be fixed in the next patch.

glad to hear that. also i have to admit, since i play with that english version-workaround, i really started to enjoy this game.

 

[unmerged(140091)]

encarnus, actually the problem you're having with the german version is diffrent from the crash related to year change in other language versions.

As we took another look at the german version you're playing, we found an issue that causes a different kind of effect, causing the game to crash at year change. We are corrently fixing this problem also.

Your detailed information led us to finding the bug, so thank you very much.