Bug after " SUB UNITS MERGE COMPLETE" message - game freezes
Posted: Fri Jan 11, 2008 5:38 pm
Hi all,
I discovered this game two months ago, and purchased it shortly thereafter. After trying a couple of times the Coral Sea scenario, I launched myself in the Guadalcanal campaign as the Allies.
Things were going well (it's AI, and difficulty is on easy), and the date was January the 31st, 1943. Rabaul, Kavieng and the coast up to Wewak are already mine, and I've been pounding Truk under my four-carrier armada and 250 heavy bombers... with the result of bringing the IJN down to two badly damaged ships.
Land combat was going on in Dagua and two hex on the New Guinea trail (SE of Wewak, and SW of Madang).
The game freezed during resolution, after the "SUB UNITS MERGE COMPLETE" message. Seeing this, after a couple of times and trials-and-errors I suspected a problem with sub-units, and loaded as the Japanese side. Effectively, 15th Base force was split between Dagua (parent) and on the tracks (sub-unit). So, I stopped the attack, and the game moved on to February 1st.
So, I thought I had found the problem. But the game froze on the next day too.
After another long evening (night) of brainstorming and trials, I noticed that japanese ships were severly hurt, and that Truk's anchor was nowhere to be seen when the game froze. So, I wondered if the lack of any ship might be a problem.
After another head-to-head reload, I built a couple of AGs and played on... successfully. I went back, loading as Allies (after having commissioned several TFs of AG)... and the game froze again.
So, I'm stuck now. My last backup save dates from the early January, so I don't want to replay a full month of the game - especially as I've only a couple of days left in the campaign. But I'd wish to be sure what exactly goes wrong, so I just don't want to quit.
Any idea ?
I can send a save if needed (the 02/01/43 autosave, "saved" to another slot so as to be able to load as either side).
Version of the game : 1.806. Stock game, no mods, no edits of the database/scenario.
And brand new computer with Vista (I hope it's not the source of the problem).
I discovered this game two months ago, and purchased it shortly thereafter. After trying a couple of times the Coral Sea scenario, I launched myself in the Guadalcanal campaign as the Allies.
Things were going well (it's AI, and difficulty is on easy), and the date was January the 31st, 1943. Rabaul, Kavieng and the coast up to Wewak are already mine, and I've been pounding Truk under my four-carrier armada and 250 heavy bombers... with the result of bringing the IJN down to two badly damaged ships.
Land combat was going on in Dagua and two hex on the New Guinea trail (SE of Wewak, and SW of Madang).
The game freezed during resolution, after the "SUB UNITS MERGE COMPLETE" message. Seeing this, after a couple of times and trials-and-errors I suspected a problem with sub-units, and loaded as the Japanese side. Effectively, 15th Base force was split between Dagua (parent) and on the tracks (sub-unit). So, I stopped the attack, and the game moved on to February 1st.
So, I thought I had found the problem. But the game froze on the next day too.
After another long evening (night) of brainstorming and trials, I noticed that japanese ships were severly hurt, and that Truk's anchor was nowhere to be seen when the game froze. So, I wondered if the lack of any ship might be a problem.
After another head-to-head reload, I built a couple of AGs and played on... successfully. I went back, loading as Allies (after having commissioned several TFs of AG)... and the game froze again.
So, I'm stuck now. My last backup save dates from the early January, so I don't want to replay a full month of the game - especially as I've only a couple of days left in the campaign. But I'd wish to be sure what exactly goes wrong, so I just don't want to quit.
Any idea ?
I can send a save if needed (the 02/01/43 autosave, "saved" to another slot so as to be able to load as either side).
Version of the game : 1.806. Stock game, no mods, no edits of the database/scenario.
And brand new computer with Vista (I hope it's not the source of the problem).