Quote:

This error message usually indicates a missing 3rd party aircraft. If this happens part-way through a campaign it might be the first mission this aircraft is used in. You should be able to find the culprit by looking in a file named Error.log in the main CFS2 directory folder. This can be opened in Notepad & will give you the Unit number of the culprit. Then open the MIS file in Notepad to track down the culprit which could be missing or incorrectly installed. It takes a little figuring out at first but is not difficult once you get the hang of it.

I reinstalled all the Aircraft that were included in this one, but, it seems the corrupt file is not an Aircraft in fact, I can still try the Europacks all out since they have all the Aircraft from CFS1 but should that fail, it would mean that it's definitely something else.

Problem is I'm starting to reach the Aircraft limit for my CFS2 here.

I have the Fall Weiss and the Polish Campaign already dowloaded in my Computer, I also have all the Aircraft for the Kursk Campaign though it never worked properly in the end I also have the Defence of Australia Campaing and a TA-152H1 that I'm very fond of...Next I also have the FAA Campaign I'm trying to make working.

I also have Operation Victor: The Invasion of the Phillipines
Operation Forager: Battle of the Mariannas
Operation Iceberg: Battle of Okinawa
Operation MI: Battle of Midway

But the latter four are no biggies since they mainly use stock aircraft.

Any suggestions now?

Hi Hagar,

Can the error.log file be deleted from the CFS2 Folder?

Regards,
Stratobat

Androcles. I just found one of my earlier replies to a similar question. This might give you an idea of what to look for. Check out those 3rd party aircraft for Panel & Sound folders. This is a common problem with some AI Only aircraft.

===============================
The  error.log file will tell you the unit number of the one causing the problem. In your example this is unit 3001. Open the mission file in Notepad & use the Search/Find feature to find this number. From this you need to search again for the [unit_type.x] entry that will give you the folder name. I don't have CFS1 installed right now so this is an example from CFS2.

[unit_type.0]
type_id=3800
unit_family=1
name=a6m2_zero

The name= entry is the exact folder name of the aircraft. Make sure you have this aircraft & that it's installed correctly. A common problem with unflyable AI drones is that it won't have Panel and/or Sound folders. If these are missing, copy/paste them from another aircraft you know works. (Empty folders with the correct names will fix it.) Once you've found & fixed the problem try the mission again. There might well be other problems that you will need to check individually in the same way until the mission loads properly.

Quote:

Now you come to mention it I found a ppath.log. Not noticed it before & have no idea what it's for. Just a load of gibberish in Notepad.

I think I've got it guys, I want to thank everyone here for their support, I'm currently at Mission 18 and still no sign of anymore bugs.

I've got to admit I did a very thourough clean up in my files, got rid of everything, re-installed my CFS2 and all the Campaigns I really cared about, now it seems to work like a charm.

I'll soon find out if it really was successfully installed, how many missions are there on FAA anyway? It looks to me like there are indeed a lot of those in there.