|
Post by Dutch Owen on Oct 27, 2012 15:14:59 GMT -5
The Problem:
You want to fly in your favorite airplane but it's not offered as an option in the drop-down list on the Flight Dispatch tab. Why not?
The Solution:
Important note: As of 1.5.0, there is a new feature to pin down why an airplane isn't on the list. If you don't see what you expect click on "<Unlisted Type>" then click on List Flights. A dialog box will appear with all the aircraft types that were seen but rejected for inclusion on the list, with the reason why beside each one.
If that doesn't work, there are two likely possibilities:
1. The airplane doesn't have an FSCaptain configuration file. To create one, install the ACARS (FCOM or FCDU) in the airplane, enter FS in it, and login using the ACARS device. You'll get a message saying a starter configuration is created for you and giving its name. You'll want to go back to Administrator and pull up the new config and fix it up -- the starter config is based on lots of guesstimates. But now it'll appear in the drop-down list in Flight Dispatch.
2. If that's not the problem, it's likely that it's not showing up because none of the paints in the aircraft.cfg have a non-blank atc_id line. The atc_id in the aircraft.cfg is the registration number, and FSCaptain can't log a flight in an airplane that doesn't have one. To solve this, edit the aircraft.cfg and put a number next to the atc_id= line. If there isn't an atc_id add a line in the [fltsim.X] section like: atc_id=N1234P - the number doesn't matter as long as there is one.
Hope this helps, Dutch
|
|
|
Post by tamsini on Oct 30, 2012 18:23:24 GMT -5
Why does this have to be so complicated? I have tried adding entries in ATC_ID then, wonderfully the entry is there. I then modify the airplane config in fscaptain directory and it no longer shows up. Next, after creating a new airline and try to add a new aircraft, ACARS reports that the ATC_ID needs to be the same name as the acronym I gave my new airline. Is there not a simple step-by-step guide for adding aircraft? VERY frustrating.
|
|
|
Post by Dutch Owen on Oct 30, 2012 18:42:26 GMT -5
Sorry you're frustrated...we'll try and help.
It's complicated because the design of FS makes it so. If there's a way to match up these airplanes more simply I'll be glad to implement it...I really hate overly complex things.
There are actually three items in the aircraft.cfg that are relevant:
atc_model (or atc_type): this is vital it's the only way we have of knowing what kind of airplane you are flying. Big difference between a C130 and a C172.
atc_id: This is the registration number. We don't care what it is but every airplane has to have one to be used with the system, otherwise how do we log?
atc_airline: This is really optional and is only looked at if the "Must Match" option is checked for an airline. See below.
The way we have it should work "out of the box" in most situations. Step by step your three problems:
1. Adding an atc_id is necessary, we have to have a registration number. But that's rare for something not to have one, and that should have been all you needed to do to get going...but not, so:
2. I don't know why changing the aircraft configuration would have caused it to disappear unless you changed the aircraft type in the configuration so it no longer matched the type in the aircraft.cfg. How did you get it to appear again?
3. I suspect in the third case your airplane has the "Must Match" option checked, which means the atc_airline must match the airline defined in the the config for FSCaptain. I'd un-check that for simplicity now. It should be unchecked by default. Its purpose is to force pilots to select liveries that match the airline.
Hope this helps, Dutch
|
|
|
Post by Travis on Nov 1, 2012 13:56:02 GMT -5
Tamsini,
Are you seeing your aircraft in the Dispatch tab, or are some still missing? There may be one other thing to try if your efforts are still being frustrated.
|
|
|
Post by tamsini on Nov 1, 2012 16:06:41 GMT -5
Thanks for that quick reply - it's working better now - much appreciated! One other question, of course. What would prohibit the automatic loading (or even manual) of passengers on certain aircraft. ACARS keeps saying "doors opening - power up aircraft". This is using JustFlight's 146-200. Almost seems like fsCaptain does not acknowledge the opening of the doors? Could be a JustFlight problem too I guess.
|
|
|
Post by Dutch Owen on Nov 2, 2012 7:35:38 GMT -5
We do have pilots successfully using the FCDU with the JF 146 so hopefully someone that has the airplane can help here.
"Power up the aircraft" means FSX is reporting that the battery master switch is in the off position.
"Doors are closing" means FSX is reporting that the main exit is positioned somewhere between fully open and fully closed.
That's all the FCDU knows and what it's assuming from that information.
Dutch
|
|
|
Post by Dutch Owen on Nov 2, 2012 7:50:21 GMT -5
I've been thinking about these issues with the aircraft type codes to think of ways we can reduce confusion and frustration.
We can't make the MSFS system simpler but we can assist people in resolving the issue right there in the FCOM/FCDU.
I plan to change the logic so that if no matching flight is found, but another commitment is located within 5 miles of the user aircraft to notify the pilot of that commitment,show the airport and aircraft of type of commitment, and query if that's the one he/she is looking to fly.
If so, then a series of questions based on what matches and what doesn't should be able to resolve the problem:
1. "You are at nearest to airport MFL in a B736 but the commitment you want is a B736 at airport PAFA. Do you want to change your airport to PAFA?
Yes--switch airports the user is considered to be "at". No--Leave other commitment "as is".
2. You are at the same airport but the commitment you want is coded as atc_model 'B736' but the aircraft you are in is coded as model 'B737'. Is 'B737' the correct type?
Yes--validate that the current configuration has enough capacity to handle the current requirements and the fuel burn numbers are not significantly off,then switch configurations. If the current configuration is too different from the booked configuration the pilot must switch airplanes or re-book the commitment.
No--Advise the pilot to switch airplanes to type 'B736'.
Dutch
|
|
|
Post by Travis on Nov 2, 2012 9:10:44 GMT -5
I have seen the "doors are opening / closing" with my F1 PC-12 from time to time over the years. I usually press CRTL-E a time or two to help things move along. I tend to think of it as the door being stuck and whomever is trying to open / close it needs a manly man to throw in some muscle. So we call for one.
|
|
|
Post by Fede on Jan 25, 2013 18:22:15 GMT -5
Hi there, not really "not showing" in my case, but rather showing the wrong one. I have the Duke and Turbine Duke. However, as the piston was configured first, when I try to make the administrator see the turbine, it sees the piston, along with its data (AVGAS, PPH, CRZ speed, etc). How can I make a different one? This is valid also for the BAE146 and its three variations, which have different weights and payloads. Or other planes as well. I really don't care for the livery, as long as the plane is the same, but the version of the plane is important. Is there a way to let these planes be seen by the admin? The only soultion I've found so far would be to delete the conflicting plane, and let it create a new one again, but it's tedious..
Thanks for your help Cheers
|
|
|
Post by Svilen Vassilev on Jan 25, 2013 19:56:25 GMT -5
Hey, Fede!
In both cases it's an issue with the aircraft.cfg files created by the developers. They used the same "atc_model" entries for both varieties of the Duke and for all 3 varieties of the Avro.
For the duke on both models they used: atc_model=Duke For the Avro they used: atc_model=BA46 and bet they'll keep it like this with all 3 146- models that are due for release.
It's just an question of either not understanding or not caring about what the atc_model directive defines. It should be used to designate the aircraft's ICAO code.
So for the piston Beech it should be: atc_model=BE60
For the Turbine Beech there's no separate icao designator, I suggest using atc_model=BE61
For the Avros:
atc_model=RJ70 atc_model=RJ85 atc_model=RJ1H
If you edit your aircraft config files like this, you'll be fine. There's a catch though: FSCaptain uses these model definitions in its aircraft config files and load maps, so if you already have created such files, you'll need to edit them or re-create them. The aircraft config files should also be named according to the atc model.
|
|
|
Post by Fede on Jan 26, 2013 9:22:49 GMT -5
Good to know this workaround, no problem creating new loadmaps, since I'll do it only once then I'm set. After all the atc_id is useless as I use radar contact, no problem changing it Thanks Svilen Cheers Edit: in the posts above Dutch Talkes about ATC_ID, not ATC_MODEL. Id's are all set differently (usually tail numbers), ATC_model don't even exist in any of my cfg's. What should I do then?
|
|
|
Post by Fede on Jan 26, 2013 9:58:12 GMT -5
Tried adding atc_model= but no change at all. Fact is that the Acars detects my atc_id, as it shows the actual tail number in the upper part of the FCDU, so it sees a different livery, but not a different plane. What can I do?
Thanks
Edit: here are the two cfg's
[fltsim.6] title=RealAir Beech Duke Turbine N601TJ Winglets Ventral sim=RealAir_Duke_Turbine model= panel= sound= texture=N601TJ kb_checklists=RASDuke_turbine_check kb_reference=RASDuke_turbine_ref atc_id=N601TJ ui_typerole="Twin Engine TurboProp" ui_createdby="RealAir" ui_manufacturer=Beechcraft ui_type=Duke Turbine ui_variation=N601TJ
[fltsim.5] title=RealAir Beech Duke N2889W sim=RealAir_Duke model= panel= sound= texture=N2889W kb_checklists=RASDuke_check kb_reference=RASDuke_ref atc_id=N2889W ui_typerole="Twin Engine Prop" ui_createdby="RealAir" ui_manufacturer=Beechcraft ui_type=Duke B60 ui_variation=N2889W
|
|
|
Post by Svilen Vassilev on Jan 26, 2013 10:05:35 GMT -5
.... ATC_model don't even exist in any of my cfg's. What should I do then? Just to make sure we're on the same page: the atc_model declaration is part of the aircraft.cfg file in FSX, not in FSCaptain. The aircraft.cfg files are located in the plane's folder, i.e. for the Turbine Duke it's: [FSX root folder]\SimObjects\Airplanes\RealAir Duke Turbine etc The atc_model declaration is part of the [General] section of the cfg, which for example for the Turbine Duke by default looks like this: [General] atc_type=Beech atc_model=Duke editable=0 performance= Category=airplane
|
|
|
Post by Fede on Jan 26, 2013 10:26:14 GMT -5
Yeah, right, sorry. I was looking in the single liveries, not in the "General" section. I'm trying again...
|
|
|
Post by Fede on Jan 26, 2013 11:12:26 GMT -5
I made some progress. While I was able to differentiate between the dukes, the MD11 and Freighter, the RJ don't want to cooperate. Chnaged them to RJ70, 85, 100, detected by the FCDU. Went into admin and set each one, deleted the original one, and the new ones don't want to appear in the drop down. What did I do wrong now?
|
|