Hi JayS,
It's a common problem with imported missions & campaigns and aircraft, the AC file name may be slightly different to the player aircraft the mission is trying to load, you should see the dialog ' player aircraft blah blah brP40k cannot be found' check the spelling & wording against the actual file in the aircraft section & you'll need to rename usually cures it.
Dont be frightened of 'Mission builder' you can change 90% of missions in here player aircraft-weapon loads- enemy aircraft/strength etc etc, get a mission you dont like & get in there and alter it, it's the only way to learn.
Another annoying thing that happens when you have a 'failure to load' is all your settings  disappear ) radio coms, ac tags etc.. is'nt it fun !!!!!
Happ 8)

Hi JayS. Look for a file in the CFS2 root folder named Error.log & open it in Notepad. This will give you the name of the problem mission & the unit number of the offending aircraft in that mission. You can use this information to find the type_id number & the name of the aircraft in that particular mission. This is an example from a default mission. Let's say my Error.log tells me this.
[Mission file error]
error=Unable to init unit 9138

First you need to find the type_id= number corresponding to unit 9138 (or id=9138 )

[unit.0]
id=9138
type_id=3814
name=%name_string.0%
allegiance=3
skill=3
aggression=2
payload=0

The type_id is 3814. Further down the mission file you should see something like this. (The Notepad Find feature is very useful when searching for these numbers.)

[unit_type.1]
type_id=3814
unit_family=1
name=f4f4_wildcat

The name= entry is usually (not always) the exact folder name of the offending aircraft. If yours has any other name it will work fine in Free Flight & QC but not missions. This is one of the most common causes of those error messages in missions/campaigns using 3rd party aircraft. The first thing I would check is the folder name of the Br P40K. Make sure it matches the name= entry in the missions. (In your example this is BR_P-40K.) I suspect this will fix your problem. If not, check the title= name in Aircraft.cfg. A few 3rd party missions use this instead of the folder name.

Quote:

The CFS2 "100 plane" limit will vary depending on the aircraft you have installed. If you have over 80 aircraft (including defaults) & get unexplained error messages I would try removing a few 3rd party aircraft.

Hi Happ.

Quote:

Just to point out that folder names are not usually case-sensitive. Despite what many people seem to think this applies to any CFG-style text entries in the M$ sims. In my example the name= f4f4_wildcat entry in the mission file refers to the default F4F4_WILDCAT in my CFS2\Aircraft folder. It works just fine.

PS. To avoid silly typos when renaming folders copy/paste the appropriate entry from the mission. Then it can't possibly be wrong. Most of this stuff is logical once you understand the basic principles & know what to look for.

Quote:

It's better to change the folder name of the aircraft rather than edit the missions. Using your method you would need to edit every mission in the campaign.

Error.log will record errors as they occur. If more than one 3rd party aircraft is involved in the campaign you might need to check it several times. This is time-consuming but the best way I know.

I don't know which method you use to install aircraft but if they come with the campaign they should extract with their correct folder names. Always extract zipfiles to a Temp folder first. To install aircraft paste the appropriate folders into CFS2\Aircraft.

PS. Quote:

As I mentioned earlier, unexplained error messages are usually caused by having too many aircraft installed. Try removing a few addons.

Ask as many questions as you wish. I don't claim to know all the answers but I'll do my best to help.

Right. Let's start again & see if we can figure this out. The problem with aircraft not displaying on the Player Aircraft menu in campaigns is probably the entered_service= date in the DP files. This must be be earlier than the date of the first mission in the campaign. This is easy enough to fix if the aircraft have their own DP files. Either change the date or if the entry is missing copy one from a suitable default aircraft & paste it in. This is the entry for the CFS2 default Wildcat which should be selectable in all US campaigns.

[MISC_DATA]
unit_family=1
category=1
allegiance=3
max_group_size=8
min_speed=240
cruise_speed=405
max_speed=607
min_alt=50
cruise_alt=5893
max_alt=8839
entered_service=11/1/40
crew=1

The CFS2 limit is usually somewhere between 80 to 100 aircraft. 56 is well below that so this is not causing the problem with the MB. I seem to recall that the MB won't run below 1024 x 768 display resolution so this would be the first thing to check.

Hope this is some help. Please don't be afraid to ask again. If I don't know the answer it's quite likely someone else will.

PS. DP files can be edited in Notepad. Each time you edit a DP file delete the corresponding CDP.

Glad you figured out the MB problem. Please tell me if you fix the other one.

Quote:

Glad my suggestion worked. I haven't been involved with CFS2 for a while so I've lost touch with a lot of this stuff. Lots of people around here know much more than me these days.

Quote:

You might like to try Cody Coyote's MB tute. http://www.simviation.com/cfs2misc2.htm

I'm in the process of reformatting it in HTML format so you can read it online. Must get my finger out & finish it. Here's Part 1. http://www.simviation.com/lair/ccmbintro1.htm