|
Post by scottw on May 23, 2015 16:09:18 GMT -5
So I followed option 1 and eliminated the line atc_model=DHC-6. I still don't see the plane in the Dispatch file. The Twin Otter is in the Overrides file, but I don't know what to do with it. I imported it, altered an entry, and applied it, and I still don't see the plane.
I have no idea what I'm doing wrong. The one thing I do see is that there is no reference to the overrides folder on page 82 of my manual. Is there a new version?
Scott
|
|
|
Post by scottw on May 23, 2015 16:37:36 GMT -5
I've just tried something else. I selected a new plane, imported the config file for the Twin Otter from Overrides, and called it Twin Otter. Nothing in dispatch. But the plane is identified by FCOMM.
Thanks, Scott
|
|
|
Post by peter on May 23, 2015 16:59:10 GMT -5
Hi Scott,
I think I referred to the user guide of 1.6.3 (which is not published yet), sorry. In 1.6.2 it should be on p. 81. If it is not there, just search for "Overrides" in the pdf file. Which version of FSCaptain are you using?
There is an easy way to find out more about why the plane is not listed: - Open the Administrator and go to Flight Dispatch - Under Aircraft Type, select <Unlisted Type> - Click on List FLights You should then see a list of the planes that are not listed, along with the reason for their exclusion.
If you are using the economic model I would suggest to switch to another airline that does not use it (I always use Alitalia for that purpose) and see if the plane is listed there. And you could send us (see below) a zip file with your FSCaptain\Aircraft folder and the Your_Airline_name_Aircraft.cfg file of your airline. I can then have a closer look at this problem.
Cheers, Peter
|
|
|
Post by scottw on May 23, 2015 20:36:39 GMT -5
I have checked that. There are seven entries for the DHC6 that all say "DHC6: ATC_ID not defined or blank in aircraft.cfg" I have four variations of the plane in the cfg file. Each has a separate ATC_ID. Only one seems to show up in the FCOMM. Could the multiple variations be causing the problem?
|
|
|
Post by scottw on May 23, 2015 20:42:18 GMT -5
And, as I discovered in another post, when I say FCOM I mean FCDU.
|
|
|
Post by Travis on May 23, 2015 23:04:13 GMT -5
Scott, Please ZIP and email us your recent FCDU & ADMIN log files. Version 1.6.3 (which I hope will go into Public Beta within 24 hours) has better logging of such things, so if we can't suss out what's happening now, then perhaps in a few days we'll have a better glimpse.
|
|
|
Post by pauldm on Aug 19, 2015 22:11:26 GMT -5
I'm having the problem with my airplane not in the dispatch list. I'm trying to use the PMDG MD11F. this is my aircraft config. [fltsim.0] title=PMDG MD-11F GE CF6-80C2D1F Engines sim=MD-11F model=GEF panel= sound=GE texture=GEF kb_checklists= kb_reference= atc_id_color=0xffffffff atc_id=N11PM atc_airline=PMDG atc_flight_number=11 atc_heavy=1 ui_manufacturer=McDonnell Douglas ui_type=MD-11F GE ui_variation=PMDG House Livery ui_typerole=MD-11F ui_createdby="PMDG" description=McDonnell Douglas MD-11F\nPrecision Manuals Development Group\nwww.precisionmanuals.com \nProduced under license from Boeing Management Company.\nBoeing MD-11, McDonnell Douglas MD-11, MD-11, McDonnell Douglas & Boeing are among the trademarks owned by Boeing.\n visual_damage=0
[fltsim.1] title=PMDG MD-11F PW4460 Engines sim=MD-11F model=PWF panel= sound=PW texture=PWF kb_checklists= kb_reference= atc_id_color=0xffffffff atc_id=N11PM atc_airline=PMDG atc_flight_number=11 atc_heavy=1 ui_manufacturer=McDonnell Douglas ui_type=MD-11F PW ui_variation=PMDG House Livery ui_typerole=MD-11F ui_createdby="PMDG" description=McDonnell Douglas MD-11F\nPrecision Manuals Development Group\nwww.precisionmanuals.com \nProduced under license from Boeing Management Company.\nBoeing MD-11, McDonnell Douglas MD-11, MD-11, McDonnell Douglas & Boeing are among the trademarks owned by Boeing.\n visual_damage=0
[fltsim.2] title=PMDG MD-11F Fedex sim=MD-11F model=PWFb panel= sound=PW texture=FXF kb_checklists= atc_id_color=0xffffffff atc_id=N608FE atc_airline=Fed Ex atc_flight_number=73 ui_manufacturer=McDonnell Douglas ui_type=MD-11F PW ui_variation=FedEx ui_typerole=MD-11F PW ui_createdby=PMDG description=McDonnell Douglas MD-11\nPMDG\nwww.precisionmanuals.com \nProduced under license from Boeing Management Company.\nBoeing MD-11, McDonnell Douglas MD-11, MD-11, McDonnell Douglas & Boeing are among the trademarks owned by Boeing. PMDG Developer and Customer Forum available at our website. \nSounds Developed by PMDG \nThank you for supporting PMDG!\n visual_damage=0 atc_heavy=1 atc_parking_types=CARGO, RAMP, MIL_CARGO
[General] atc_type=MCDONNELDOUGLAS atc_model=MD11 performance="" editable=0 Category=airplane
I shows the atc ID but not in the dispatch list.
Paul
|
|
|
Post by peter on Aug 20, 2015 4:14:08 GMT -5
Hi Paul,
please create a zip file of your FSCaptain\Aircraft directory and send it (see below) to us. I am sure we can resolve this.
Cheers, Peter
|
|
|
Post by jimos on Aug 30, 2015 4:55:27 GMT -5
I'm having a problem with getting my planes to show as well I've checked some of them they have atc Ids and I have installed the acars but they still wont show up.
E300: ATC_ID not defined or blank in aircraft.cfg
AT425: ATC_ID not defined or blank in aircraft.cfg
ATR72: ATC_ID not defined or blank in aircraft.cfg
BN2AMKIII: ATC_ID not defined or blank in aircraft.cfg
B717: ATC_ID not defined or blank in aircraft.cfg
: ATC_ID not defined or blank in aircraft.cfg
744: ATC_ID not defined or blank in aircraft.cfg
: ATC_ID not defined or blank in aircraft.cfg
BE58: ATC_ID not defined or blank in aircraft.cfg
B773: ATC_ID not defined or blank in aircraft.cfg
B741: ATC_ID not defined or blank in aircraft.cfg
B741: ATC_ID not defined or blank in aircraft.cfg
B741: ATC_ID not defined or blank in aircraft.cfg
B744: ATC_ID not defined or blank in aircraft.cfg
CRJ700: ATC_ID not defined or blank in aircraft.cfg
1011: ATC_ID not defined or blank in aircraft.cfg
C130: ATC_ID not defined or blank in aircraft.cfg
A36: ATC_ID not defined or blank in aircraft.cfg
A321: ATC_ID not defined or blank in aircraft.cfg
DHC2: ATC_ID not defined or blank in aircraft.cfg
DHC7: ATC_ID not defined or blank in aircraft.cfg
DH8B: ATC_ID not defined or blank in aircraft.cfg
DH8A: ATC_ID not defined or blank in aircraft.cfg
E120: ATC_ID not defined or blank in aircraft.cfg
F14: ATC_ID not defined or blank in aircraft.cfg
F15: ATC_ID not defined or blank in aircraft.cfg
F16: ATC_ID not defined or blank in aircraft.cfg
F35: ATC_ID not defined or blank in aircraft.cfg
MD83: ATC_ID not defined or blank in aircraft.cfg
G21: ATC_ID not defined or blank in aircraft.cfg
F22: ATC_ID not defined or blank in aircraft.cfg
T6: ATC_ID not defined or blank in aircraft.cfg
T6: ATC_ID not defined or blank in aircraft.cfg
A320: ATC_ID not defined or blank in aircraft.cfg
P38: ATC_ID not defined or blank in aircraft.cfg
P38: ATC_ID not defined or blank in aircraft.cfg
P38: ATC_ID not defined or blank in aircraft.cfg
P38: ATC_ID not defined or blank in aircraft.cfg
CONI: ATC_ID not defined or blank in aircraft.cfg
CONI: ATC_ID not defined or blank in aircraft.cfg
T50: ATC_ID not defined or blank in aircraft.cfg
M7: ATC_ID not defined or blank in aircraft.cfg
M7: ATC_ID not defined or blank in aircraft.cfg
M20TS: ATC_ID not defined or blank in aircraft.cfg
M20T: ATC_ID not defined or blank in aircraft.cfg
MV22: ATC_ID not defined or blank in aircraft.cfg
ARCHER: ATC_ID not defined or blank in aircraft.cfg
A318: ATC_ID not defined or blank in aircraft.cfg
J3: ATC_ID not defined or blank in aircraft.cfg
B738: ATC_ID not defined or blank in aircraft.cfg
CARJ: ATC_ID not defined or blank in aircraft.cfg
RQ170: ATC_ID not defined or blank in aircraft.cfg
DC10: ATC_ID not defined or blank in aircraft.cfg
DC10: ATC_ID not defined or blank in aircraft.cfg
DC10: ATC_ID not defined or blank in aircraft.cfg
DC10: ATC_ID not defined or blank in aircraft.cfg
DC10: ATC_ID not defined or blank in aircraft.cfg
tornado: ATC_ID not defined or blank in aircraft.cfg
TU_95: ATC_ID not defined or blank in aircraft.cfg
I'm just trying to add the BN2AMKIII for now but the folder name looks like this B-N2A_3-x
and this is theconfig file fltsim.0]
title=BN-2A - Trislander Aurigny G-BDTO
sim=BN2
model=3prop
panel=trisx
sound=0
texture=aurignynew
atc_airline=regional
atc_id=G-BDTO
kb_checklists=trislander_check
kb_reference=trislander_ref
atc_flight_number=AU120
prop_anim_ratio=1.015
ui_manufacturer=Britten Norman
ui_type=Trislander
ui_variation=Aurigny G-BDTO
ui_createdby="Premier Aircraft Design"
ui_typerole="Commuter-Utility"
atc_heavy=0
description= Britten-Norman BN2A Mk111 Trislander. 16/17 passenger short range, STOL commuter aircraft. Max Speed 150 kts IAS (170mph), Normal Cruise Speed 130 kts IAS, Service ceiling 10,000 ft, Max ceiling 13,000 ft, 3 x Avco Lycoming 6 cylinder O-540-E4C5 engines 260hp each.
|
|
|
Post by peter on Aug 30, 2015 6:21:08 GMT -5
Hi Jimos,
can you send us (see below) a zip file with your FSCaptain\Aircraft folder and the aircraft.cfg file of your BN2 Islander model?
Cheers, Peter
|
|
|
Post by Travis on Aug 30, 2015 14:43:01 GMT -5
Paul & Jimos, Also please include your most recent ADMIN log files, especially if you're running version 1.6.3 or newer. These log files contain lots of data detailing why & why not an aircraft isn't listed. AAMOF, Peter reported his Metroliner wasn't appearing in the latest test builds, and a quick look at the ADMIN logs showed me why. Fixed in less than 30 minutes.
|
|
|
Post by lumpi86 on Dec 5, 2016 14:36:56 GMT -5
Hopefully I'm not asking a question that has already been answered, and if so hopefully someone else needs this....
I have FSX SE and I have recently purchased and downloaded a DLC aircraft (Boeing C-17A Globemaster III) through steam and it installs into a secondary folder (C:\Program Files (x86)\Steam\SteamApps\common\FSX\DLC) and any plane that I purchase through Steam will not show up in the dispatch screen, I can however use the FCDU to manually enter flight information while in the aircraft... is there anything I can do to fix this issue or is anyone else having this issue with Steam purchased aircraft...
Note however that I have downloaded aircraft from other freeware sites and the planes integrate perfectly without any issues.
If it comes to moving the aircraft folders can someone please inform me on how to move folders safely without damaging the integrity of the aircraft files.
|
|
|
Post by Travis on Dec 5, 2016 19:52:15 GMT -5
Hi Lumpi, Could you please zip and email us your fsx.cfg file along with your most recent ADMIN log file from FSCaptain? I'd like to play a hunch but I'd need to see that data first. And no moving aircraft folders... we want to play 'nice.' Regards,
|
|
|
Post by lumpi86 on Dec 7, 2016 19:27:39 GMT -5
I emailed you, I wanted to touch base to see if you had recieved it.
|
|
|
Post by Travis on Dec 8, 2016 2:01:17 GMT -5
Hi Lumpi, Sorry, I was called into my job today and I'll be there tomorrow -- it's crazy hours because of the holiday season, shoppers, and crewmates who call in sick.... I might not be back here full time until the weekend. Yes, but that was the incorrect Admin log - we need one that's generated by the Admin.exe program. Just run it and exit, then pick the newest Admin log and that should be it. As for your fsx.cfg file - for FSX box Captains, it's located in your \AppData\Roaming\Microsoft\FSX\ folder. There's something that tells FSX Steam to look for your aircraft in another location. We need a sample of what that is... and my (first) guess is it's in your fsx.cfg file. Regards,
|
|