Solved? Launcher stops...

[redxfred]

I tried everything posted everywhere. However, the problem would always occur during the Quick Mission: "British Attack - Column", so I focused on fixing that mission with hopes that the solution will transfer to other missions.

My initial solution: Reduce the number of planes in each flight by one. That is, two Spitfires instead of three; three BF-109's instead of four, etc., for each flight in the briefing screen.

I was very surprised that this reduction works consistently since I never had problems with even larger numbers of planes in some other missions, such as the air battle over the channel. I assume it is a combination of planes and land features that causes the Launcher to fail on this particular mission.

After such a long time trying to get this mission to work, I felt obliged to share my preliminary solution with the forum. Now, it may very well be that a reduction in each flight is unnecessary, but an increase in the number of planes, as seems logical, does not seem to stop the CTD's. I don't claim to know precisely why, but the reduction mentioned at the start of this post works for me all the time.

Here is a rundown of my settings and system:

In-Game Video is set for all features at their highest values except for Anti-Epilepsy Filter, SSAO and VSYNC which are unchecked. Resolution: 2560x1600, 60HZ which is native to my Dell U3011 30" monitor. All software is current with Framework 4 newly applied. Removing the cache folder doesn't seem to make any difference. Realism is all checked except for Head Shake, Engine Temperature Effects, Clouds and No Map Icons.

Video Hardware is 2 x AMD HD6970's in CrossfireX, managed by the new "RadeonPro" software, available free from AMD, with all the settings set for maximum quality, not max performance so as to push it to its limits. Clock speeds are overclocked as high as they will go without voltage adjustment, using MSI Afterburner.

Fan Cooling is managed by MSI Afterburner with my stock fans running so that degrees C = percent maximum speed. (i.e., 50% @ 50C, 80% @ 80C, 100% @ 100C, etc. The fans are noisy at that level, but not as noisy as the inside of a real cockpit. I have convinced myself that it adds to the realism. Max graphics card temps are 70C. Frame rates run from 50 fps upwards.

My System Hardware:
ASUS Rampage III Formula in a Coolermaster HAF 932 case (Lots of airflow) running Windows 7 Professional, 64 Bit.
Intel I7-950 overclocked to 4.2GHz max with Hyperthreading OFF to reduce heat. 12 GB Corsair Dominator DDR3-1600 Memory, Corsair 750TX Power Supply, SanDisk 240 GB SSD (Loads CLoD really fast!), Coolermaster Hyper 212 processor cooler (70c Max in CLoD), big hard drives, 2 optical drives, etc.

Bells & Whistles: Saitek X-52, Saitek Pro Pedals, TrackIR 5 Headtracker, Game Commander 2 Voice control, (Oldie but Goodie!), Original Buttkicker Gamer (Works good, lasts a long time!) It all works and NO overheats!

--------------------------------------------------------------------------------

[Stirwenn]

As for me, your are a bit short with your PSU. I may not search something relative about software. A 1100w psu would do it.

[redxfred]

Using the loadmeter on my uninterruptible power supply, I saw as much as 745 Watts demand from CLoD. So I ordered a new 1000 Watt PSU and will report here if it fixes the problem. If it doesn't fix it, Stirwenn is in big trouble when my wife finds out I bought another computer gizmo!

"Honey, it's not my fault, Stirwinn made me do it!"

[redxfred]

new power supply was no help regarding CLoD problems. At least I have eliminated another potential problem...

[Continu0]

Are your Crashes connected to seeing the bomb-explosions on the screen? I had the crashes in this mission as well, but only if I saw the explosions directly on the screen... (distance to the explosion didn´t matter).

And, are you using the beta-patches?

[redxfred]

Thanks to you all for your help. The release candidate has fixed all my problems mentioned in this thread. I highly recommend it.