by Cody_Coyote » Mon Apr 17, 2006 11:59 pm
Assuming you have all of the aircraft, ships, and infrastructure that a mission calls for you can fly any mission in the game even if you don't have the airfield scenery installed. When flying the mission your position is determined by the longitude and latitude written into the mission file, not by the airbase.dat entries. However, just because you can fly the mission doesn't mean it will work right.
If you're flying the mission out of Adak, Alaska but don't have that scenery installed you'll find yourself sitting on the tundra when you should be sitting on a runway. Additionally, when you warp back to the base to land you may see nothing but bare ground. Another possible glitch is caused when you have one version of an airbase entered in your game but the mission author used a different version of the same base. In that case you may find yourself sitting inside of a building or in a vacant field a quarter mile from where your base is located. Again, this is caused by the mission using longitude and latitude to determine your position and his starting position lining up with his scenery, not yours.
As you mentioned, this becomes a management issue with downloaded missions as you may have to tweak the takeoff and landing positions to get them to fly right for your setup.
The big problem comes when you try to look at the map or go to Advanced Information. If the runway ID's shown in the mission file don't match the ones in your airbases.dat file you can get a crash. None of these problems are insurmountable, but you may find that in some cases it is more bother than it's worth to tweak the missions, particularly if it is a very large campaign.