Bugs in the sequel are always useful !

:confused:

launcher ever crash after some minutes of fly.........Tired and sad.

Updated, still getting Launcher exe crash, pity because it seems aa lot better.

Win7 32 bit
4gb ram
Q6600
AMD 6800 1gb

Salute

On the ATAG server last night, during their Dunkirk setup, some of the bombed ships appeared after being destroyed, hanging in the air 200 ft over the beaches.

All the Spitfire I's/IA's and Hurricane I's have engine cutout bug, which appears at different altitudes and gets worse the higher the aircraft flys. Spit IIA not affected, so obviously Merlin III bug.

I also have had my first launcher crash today, I have not had that for months.....

just did a full reinstall... the game still doesn-t launch....

bah, back to 1946...


... and its working.

uninstall the thing, and for osme reason A LOT of stuff is not removed from the game folder on steam. delete it all, reinstall and voila.

@Black Six
 

It would still be a good Idea to collate any further information on game bugs etc if the same engine is being used in the sequel as this would be handy to sort the problems out pre-production rather than the New release being published with them .Fixes would then be included in the New release .
The Sequel may well have other bug conciderations that would be harder to rectify if old bugs are still present .If any lesson has been learnt since the release of Cliffs of Dover till now it should be not to repeat the mistakes of the past.

If you arent going to collect bugs to fix for the sequel you should atleast collect them to put on the box as "features" :)

Launcher crash here, too.

Note to self:
Delete CloD again and check Website in December 2013 for a possible new patch.