Economic mode not recognising aircraft

[steffeff]

Hi Dutch/Travis,

New update looks great but one or two problems encountered;

I cannot seem to get it to recognise my aircraft in economic mode.
I have created the requisite files and placed them where they should go  (FSCaptain\Airlines\[my airline]_Aircraft.cfg)  but dispatch does not recognise the aircraft.

e.g.
Aircraft=A318CFM,G-EUNA,7050,1000,0,680

i had thought perhaps the airbus was being a bit tricky however the same applies to all other aircraft i have tried.

any assistance would be greatly appreciated.

Also noted that in P3D 2.4 at least bringing up dispatch on the ACARS does not show the dispatch form (a minor annoyance).

Steff

[steffeff]

Scratch that...i seem to have it working now.

[Travis]

Steff,

If you're having issues with the Dispatch Release not being visible via the kneeboard, please zip and email some of the FCDU logs of these flights to me. I've added logging details that I hope I can use to better isolate these issues. (It did for me, and I was able to finally view my Dispatch Release in my P3D kneeboard a few weeks ago.

[crouchair]

Hi I cant seem to get Economy mode to reconise my aircraft have added the file with Aircraft=B733,ZK-NGD,4200,800,0,400 but in the dispatch I get an error that states

The following aircraft types were not included in
the Dispatch list for the reasons indicated:

: ATC_ID not defined or blank in aircraft.cfg
: ATC_ID not defined or blank in aircraft.cfg
B733: Not defined in JetBlue_Aircraft.cfg
E-170: ATC_ID not defined or blank in aircraft.cfg
E-190: ATC_ID not defined or blank in aircraft.cfg
B738: Not defined in JetBlue_Aircraft.cfg
B738: Not defined in JetBlue_Aircraft.cfg
B739: Not defined in JetBlue_Aircraft.cfg
B739: Not defined in JetBlue_Aircraft.cfg
I Have checked the Aircraft file and it includes the ATC ID so if you could help me out that would be great

Cheers

Luke

[peter]

Hi Luke,

for some planes it can be a bit tricky to get recognized by in economic mode. I also had problems with the E170/E190. Here is how I solved it:

- Make sure that your FSCaptain file "airline name_Aircraft.cfg" has an empty line at the end, otherwise the last entry may be ignored.

- For each of the affected airplanes you need to have a look at the aircraft.cfg file of the plane (the one in SimObjects\Airplanes\.. , not the FSCaptain file)

- In this file, atc_id and atc_model should be defined for each livery ([fltsim.X] blocks). Normally that's the case, but some developers do not do this for whatever reason.

- The variable atc_model should have the value <name>, where <name> is the name of the respective file in the FSCaptain\Aircraft directory. For instance, if you have a file FSCaptain\Aircraft\E190.cfg, then atc_model should be E190. Usually FSCaptain creates the file E190.cfg automatically and it should fit. However, for some of my planes the variable atc_model had different values for different [fltsim.X] blocks, and also had a different value in the [General] block. There is simply no way that FSCaptain could recognize the plane if the liveries are so messed up.

Hope that helps,
Peter

[crouchair]

Hi Peter thanks for the response will give it a go but what do you mean by leave a empty line in the Aircraft.cfg? In the title or in the list of Aircraft?

Much appreciated

Luke

[peter]

Hi Luke,

When you edit the file "airline name_aircraft.cfg" with a text editor, go to the very last character of the file. If _ is your cursor, then it should look like this:

Aircraft=A315CFM,G-EUNA,7050,1000,0,680
Aircraft=A316CFM,G-EUNA,7050,1000,0,680
Aircraft=A318CFM,G-EUNA,7050,1000,0,680
_


If it looks like

Aircraft=A315CFM,G-EUNA,7050,1000,0,680
Aircraft=A316CFM,G-EUNA,7050,1000,0,680
Aircraft=A318CFM,G-EUNA,7050,1000,0,680_

then hit enter one time, then you should be OK.

Cheers,
Peter