Post by Dutch Owen on Oct 15, 2012 10:38:09 GMT -5
The Problem:
You go into the Administrator, pick an airport and an aircraft type, book a flight, and then get into that aircraft type at that airport and the ACARS device doesn't recognize the flight. Instead it comes up with "Dispatch Online" (called "Preflight Menu" in the new FCDU) and tells us we have another commitment at or near this same airport!
The Solution:
In order for the ACARS to see and start a flight you've booked in the Administrator three things have to match up:
* The current airport must be the same as the one booked, and,
* The current aircraft type must match to that booked, and, potentially,
* The current aircraft registration must match to the one booked.
Two displays available on the FCOM/FCDU will allow you to figure out this problem. Follow this guide for the solution.
In most cases you will not have to worry about the aircraft registration number. Normally when you book a flight it's for a type, not a specific airplane. Unless you pick an aircraft configuration for a specific registration number, or you have previously started a flight in a specific airplane at an airport and are trying to re-start it, you can forget about the registration number.
The next least likely possibility is that you are at an airport that has another airport so nearby that FSCaptain considers you to be "at" the wrong airport. In FSCaptain versions at or above 1.3.2 if this might be a problem you'll see a new option appear on the pre-login page (the SELF-TEST page) which will refer to F3=Select Airport (or on the FCDU SELECT AIRPORT>). If you don't see this there is no airport conflict. If you do see it, you can see all the airports within a 5 NM radius and choose the one you want to be "at". This will resolve the "wrong airport" issue if you have it. It's rare. If you want to see this in action, try flying out of PANC.
The most likely problem is that the aircraft type doesn't match. You will know this is the problem by looking carefully at the information available to you. After you log in you'll be at the Dispatch Online (or Preflight Menu) page, number 10. What you expected was to be at the Start Flight page, number 54. At the top of the page right under the white colored title you will see the current aircraft type and registration number. Write them down or remember them. The flight you want to start is probably that "other commitment" it's telling you about. Press F7 (or REVIEW OTHERS>) to go to a page that will show you your other flight commitments. If there's more than one, look for the one at this airport. Under the column "Aircraft" will be listed the aircraft type (and possibly registration) that was booked, separated by a dash or slash. If you don't see a registration that's good - one less thing to worry about, just check the aircraft type. Unless there's a true bug, these won't match up with what was shown on the other page, the current ones for the airplane you are in at the moment.
How can this happen? And how do I fix it?
First, if there's a registration involved, you probably picked the wrong livery. That's easy to fix - switch airplanes.
If as is more likely there is only an aircraft type to match, why don't they match?
The 'aircraft type' that FSCaptain uses is defined in the aircraft.cfg file for each airplane on a line that starts with the term atc_model= (or, rarely, atc_type= either means the same thing.) Some add-ons have multiple variations that are installed with them, and some of those variations may go in different folders, although they are from the point of view of the pilot all the same type. The problem is that some designers have put different atc_model= lines in their different folders! Or, they have put different atc_model= lines in the same aircraft.cfg! Either way, the door is opened to confusion.
Imagine we are flying a new add-on for a Boeing 737-200. This add-on installed two folders for two different configurations of the 737, one for PAX and one for cargo. In the cargo, the atc-model is B732, but in the PAX version it's B737 - perhaps coded by a different team member. Now, you go book a flight in the Administrator for PAX (B737 model code) then select the cargo one (B732) when you start your sim up. The FCOM/FCDU thinks you are in a 'B732' because that's what FS tells it...but your booked flight is in a 'B737'. In the FCOM/FCDU the codes must match exactly so be sure to look for subtle differences in coding.
How to fix this? Two options:
1. Be very careful to be sure you select the same variation in FS that you booked in the Administrator. The aircraft type code is shown in the aircraft type selection drop-down. That's what's going to be expected by FCOM/FCDU in the airplane.
-or-
2. Go into the aircraft.cfg files for all the variations and change them to all match up. If there are multiple atc_model (or atc_type) lines in one aircraft.cfg, change them to all match up. This should not affect the airplane or its flying characteristics in any way. It may or may not affect the way FS (or external) ATC pronounces your type, but this is minor and unlikely in any event. It's your choice which of the multiple codes to use, just be sure they are all the same. If you do this, watch out for newer versions of the airplane that you may install resetting them back wrong again. Also, be sure to change to the type code that has an FSCaptain configuration file not any other ones that might be floating around in there.
Now, your numbers and codes should match up and you're all set to do the preflight and take off on an on-time and error-free flight.
Thanks for flying with FSCaptain!
Dutch
You go into the Administrator, pick an airport and an aircraft type, book a flight, and then get into that aircraft type at that airport and the ACARS device doesn't recognize the flight. Instead it comes up with "Dispatch Online" (called "Preflight Menu" in the new FCDU) and tells us we have another commitment at or near this same airport!
The Solution:
In order for the ACARS to see and start a flight you've booked in the Administrator three things have to match up:
* The current airport must be the same as the one booked, and,
* The current aircraft type must match to that booked, and, potentially,
* The current aircraft registration must match to the one booked.
Two displays available on the FCOM/FCDU will allow you to figure out this problem. Follow this guide for the solution.
In most cases you will not have to worry about the aircraft registration number. Normally when you book a flight it's for a type, not a specific airplane. Unless you pick an aircraft configuration for a specific registration number, or you have previously started a flight in a specific airplane at an airport and are trying to re-start it, you can forget about the registration number.
The next least likely possibility is that you are at an airport that has another airport so nearby that FSCaptain considers you to be "at" the wrong airport. In FSCaptain versions at or above 1.3.2 if this might be a problem you'll see a new option appear on the pre-login page (the SELF-TEST page) which will refer to F3=Select Airport (or on the FCDU SELECT AIRPORT>). If you don't see this there is no airport conflict. If you do see it, you can see all the airports within a 5 NM radius and choose the one you want to be "at". This will resolve the "wrong airport" issue if you have it. It's rare. If you want to see this in action, try flying out of PANC.
The most likely problem is that the aircraft type doesn't match. You will know this is the problem by looking carefully at the information available to you. After you log in you'll be at the Dispatch Online (or Preflight Menu) page, number 10. What you expected was to be at the Start Flight page, number 54. At the top of the page right under the white colored title you will see the current aircraft type and registration number. Write them down or remember them. The flight you want to start is probably that "other commitment" it's telling you about. Press F7 (or REVIEW OTHERS>) to go to a page that will show you your other flight commitments. If there's more than one, look for the one at this airport. Under the column "Aircraft" will be listed the aircraft type (and possibly registration) that was booked, separated by a dash or slash. If you don't see a registration that's good - one less thing to worry about, just check the aircraft type. Unless there's a true bug, these won't match up with what was shown on the other page, the current ones for the airplane you are in at the moment.
How can this happen? And how do I fix it?
First, if there's a registration involved, you probably picked the wrong livery. That's easy to fix - switch airplanes.
If as is more likely there is only an aircraft type to match, why don't they match?
The 'aircraft type' that FSCaptain uses is defined in the aircraft.cfg file for each airplane on a line that starts with the term atc_model= (or, rarely, atc_type= either means the same thing.) Some add-ons have multiple variations that are installed with them, and some of those variations may go in different folders, although they are from the point of view of the pilot all the same type. The problem is that some designers have put different atc_model= lines in their different folders! Or, they have put different atc_model= lines in the same aircraft.cfg! Either way, the door is opened to confusion.
Imagine we are flying a new add-on for a Boeing 737-200. This add-on installed two folders for two different configurations of the 737, one for PAX and one for cargo. In the cargo, the atc-model is B732, but in the PAX version it's B737 - perhaps coded by a different team member. Now, you go book a flight in the Administrator for PAX (B737 model code) then select the cargo one (B732) when you start your sim up. The FCOM/FCDU thinks you are in a 'B732' because that's what FS tells it...but your booked flight is in a 'B737'. In the FCOM/FCDU the codes must match exactly so be sure to look for subtle differences in coding.
How to fix this? Two options:
1. Be very careful to be sure you select the same variation in FS that you booked in the Administrator. The aircraft type code is shown in the aircraft type selection drop-down. That's what's going to be expected by FCOM/FCDU in the airplane.
-or-
2. Go into the aircraft.cfg files for all the variations and change them to all match up. If there are multiple atc_model (or atc_type) lines in one aircraft.cfg, change them to all match up. This should not affect the airplane or its flying characteristics in any way. It may or may not affect the way FS (or external) ATC pronounces your type, but this is minor and unlikely in any event. It's your choice which of the multiple codes to use, just be sure they are all the same. If you do this, watch out for newer versions of the airplane that you may install resetting them back wrong again. Also, be sure to change to the type code that has an FSCaptain configuration file not any other ones that might be floating around in there.
Now, your numbers and codes should match up and you're all set to do the preflight and take off on an on-time and error-free flight.
Thanks for flying with FSCaptain!
Dutch