• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS20 Title line

Messages
695
Country
us-northcarolina
What is the correct procedure for the title line because with the new formatting in MSFS...aifp can't find the plane or whatever. It finds some and not other so is there a trick to MSFS for the proper formating of aircraft cfg's?

Thanks for any help concerning these and what is right..

BobM.
 

Attachments

Last edited:
Bob, you are going to have to be more explicit than this for me to understand what you are asking?
 
i guess what I am really asking is: For MSFS, in the aircraft cfg in order for AIFP to ( find the aircraft) substitute or add an aircraft.....for the flight plan to be properly configured, what is the ideal way for the info in the fltsim section to be formated. These all have variations in the title line and maybe due to Asobos....there may be a bug but lots of times these planes don't show up. They are in black in the aircraft lines. So I don't know if these variations are ok or what. Sorry to be a pain in the ass but Asobo isn't making this sim any more enjoyable by making it hard to have some old timer ai's to show up...lol... The planes are mounted but I sit there and look at an empty airport..at least here in KINT..

Obviously AIFP can find these but is there a better way for me to do these aircraft cfg's?

.

Here's one:
[FLTSIM.0]
title=A1A B737-300 PIEDMONT
sim=aia_737_CL
model=Piedmont Airlines
texture=Piedmont Airlines
atc_airline=PDT
atc_heavy=""
atc_parking_codes=PDT
atc_parking_types=GATE,RAMP
description=""
ui_manufacturer=BOEING
ui_type=B733
ui_variation=Piedmont Airlines
isAirTraffic=1
isUserSelectable=0
atc_id_enable=1
icao_type_designator=B733
icao_airline=PDT
sound=soundAI

Here's another:

[FLTSIM.0]

; LEGACY
title = Douglas DC3 Piedmont Airlines N105CA ; Variation name
sim = Douglas_DC3_v1.5 ;
model = C47_2 ; model folder
panel = OFF ; panel folder
sound = ; sound folder
texture = piedmont ; texture folder
kb_checklists = C47_check ; Procedures/Checklist sibling file name
kb_reference = C47_ref ; Reference information sibling file name
atc_id = N105CA ; tail number
atc_flight_number = N105CA ; flight number
atc_airline = "Piedmont" ; airline name
ui_manufacturer = "Douglas" ; e.g. Boeing, Cessna
ui_type = "C-47 Skytrain" ; e.g. 747-400, 172
ui_variation = "Piedmont Airlines" ; e.g. World Air, IFR Panel
ui_typerole = "Twin Engine Prop" ; e.g. Single Engine Prop, Twin Engine Prop, Rotorcraft, etc
ui_createdby = ; e.g. Asobo Studio, Microsoft, FSAddonCompany, etc
description = DC-3/C-47 Piedmont Airlines with Modern Cockpit ; Variation description.
atc_parking_types = RAMP,GATE ; "ANY" / "RAMP" / "CARGO" / "MIL_CARGO" / "MIL_COMBAT" / "GATE" / "DOCK"
atc_parking_codes = PDT ; Comma separated and may be as small as one character each
isairtraffic = 1 ; airtraffic flag for variations
isuserselectable = 0 ; flag off for non selectable planes
; MODERN
;-wip_indicator = 0 ; know if the variation is good to go or still WIP : -1=Disabled, 0=Rough, 1=1st Pass, 2=Finished
;-ui_thumbnailfile = "" ; app relative path to ThumbNail image file
;-ui_certified_ceiling = -1 ; service ceiling / max certified operating altitude (ft)
;-ui_max_range = -1 ; max distance the aircraft can fly between take-off and landing in (NM)
;-ui_autonomy = -1 ; max duration the aircraft can fly between take-off and landing in (Hrs)
;-ui_fuel_burn_rate = -1 ; average fuel consumption per hour (lbs/hr) - reminder: fuel density is ~6.7lbs per US gallon
;-atc_id_enable = 1 ; enable tail number
;-atc_heavy = 0 ; heavy?
;-atc_id_color = "" ; color for the tail number : i.e. "#ffff00ff"
;-atc_id_font = "" ; font for the tail number

[FLTSIM.0]

title = YS11A AI ;
sim = YS11A AI ;
model = ;
panel = ;
sound = ;
texture = Piedmont_old ;
kb_checklists = ;
prop_anim_ratio = -1.76 ;
description = YS11A for AI traffic.\nFSDS2 model by Dee Waldron. ;
ui_manufacturer = Nippon ;
ui_type = YS11A ;
ui_variation = Basic ATC model ;
cruise_speed = 315.0 ;
ui_typerole = "Aircraft" ;
isAirTraffic = 1
isUserSelectable = 0
icao_airline = "PDT"

[FLTSIM.0]
title = "AIA B727-200 PIEDMONT" ;
sim = "aia_727_200" ;
model = "PDT" ; model folder
panel = "" ; panel folder
sound = "" ; sound folder
texture = "Piedmont Airlines"
kb_checklists = "Boeing747-400_check" ; Procedures/Checklist sibling file name
kb_reference = "Boeing747-400_ref" ; Reference information sibling file name
description = AI Aircraft ; Variation description.
wip_indicator = 0 ;
ui_manufacturer = BOEING ; e.g. Boeing, Cessna
ui_type = B722 ; e.g. 747-400, 172
ui_variation = "AIA B727-200 PIEDMONT" ; e.g. World Air, IFR Panel
ui_typerole = "Commercial Airliner" ;
ui_createdby = AIA ;
ui_thumbnailfile = "" ;
ui_certified_ceiling = 39800 ; service ceiling / max certified operating altitude (ft)
ui_max_range = 3500 ; max distance the aircraft can fly between take-off and landing in (NM)
ui_autonomy = 7 ; max duration the aircraft can fly between take-off and landing in (Hrs)
ui_fuel_burn_rate = 5300 ; average fuel consumption per hour (lbs/hr) - reminder: fuel density is ~6.7lbs per US gallon
atc_id = "AZU321" ; tail number
atc_id_enable = 0 ; enable tail number
atc_airline = "Piedmont" ; airline name
atc_flight_number = "1123" ; flight number
atc_heavy = 0 ; heavy?
atc_parking_types = "GATE,RAMP" ; "ANY" / "RAMP" / "CARGO" / "MIL_CARGO" / "MIL_COMBAT" / "GATE" / "DOCK"
atc_parking_codes = "" ; Comma separated and may be as small as one character each
atc_id_color = "" ; color for the tail number : i.e. "#ffff00ff"
atc_id_font = "" ; font for the tail number
isAirTraffic = 1 ; Is the plane usable for air traffic
isUserSelectable = 0 ; Is the plane selectable by the user
icao_airline = "PDT" ;

Thanks Don for all your hard work..just trying to understand...

Best Regards,
BobM.
 
Last edited:
AIFP should process any aircraft.cfg files that comply with MS/LM SDKs. If the aircraft shows up "black", it's been found. If "red', AIFP hasn't found it. I see nothing in any of the samples that should confuse AIFP. Simplest is best.

What is it you find confusing in confusing.jpg?
 
Last edited:
Back
Top