Ttools Flugpläne interpretieren

[Oliver H.]

Hallo Wolfgang
------------------------------
@Oliver
Ich find da keine HTML-Datei. Hab die Version 2.02
Gibt es da was Neueres ?
Oder was meinst Du ?
------------------------------

Ja ich meine auch die 2.02. Bei mir ist je eine PIC/ TTool/ Collect Airports/ und die HTM Readme (90kb) Datei im Download mit bei.


(Der Gesamttext würde zu lang)
Auszug daraus:



21. FlightPlans...txt File

This is the main file of the three source files that the compiler needs to create a traffic file. It is a list of all the AI traffic flight plans, or at least the plans that will be grouped in the compiled traffic file.

Each flight plan specifies a complete circuit. A circuit consists of at least two legs, an outbound and a return leg. Most stock flight plans have two legs but a circuit can have multiple legs so you can lay out a multi-hop ‘milk run’ with a single flight plan if you want. TTools allows up to 200 legs in a single flight plan. The circuit must terminate back at the start point.

Note that each leg must actually end at an airport in order to work properly.

Although most flight plans go between two or more different airports, you can create flight plans that generate practice circuits at a single airport. See Touch and Go's.

IMPORTANT NOTE: Each flight plan creates one ‘virtual’ aircraft in the FS2002 world and programmes its operation in perpetuity. Unlike in real-world aviation where a single aircraft could have several flight plans for a day’s or a week’s operation, an AI aircraft must have only one flight plan. If you convert airline timetables into flight plans by creating a flight plan for each entry in the schedule you could end up with too many aircraft, which will sit around most of the time taking up parking space. If an aircraft shuttles back and forth between two airports several times a day then you must create a single flight plan with a leg for each trip to each airport, or specify a repeat period if the aircraft flies at regular intervals all day and night.

Each flight plan specifies a repeat period. The repeat period can cause the complete flight plan circuit to be repeated several times a day or once a week. The repeat period is one of : 1, 2, 4, 6, 8, 12 or 24 hour intervals, or WEEK to repeat every seven days. Most of the stock flight plans repeat several times a day unless the circuit is so long it can only be done once a day. Unless a flight plan specifies a WEEK repeat period, it will re-occur at the same time every day of the week.

All AI flights fly direct point-to-point great circle routes from the departure airport fix to the destination airport fix. There is no provision in FS flight plans to designate segmented routes using nav-aids, airways, or other en-route fixes. You cannot use flight plan legs to simulate flight waypoints.

All flight plans have a base component and a component for each leg. The base component has parameters that apply to the whole flight plan such as the aircraft type and registration. The leg component specifies parameters that vary from leg to leg, such as the departure time, cruising altitude, and destination.

Here are a few typical lines from a FlightPlans...txt file. Each line is a complete flight plan:

AC#4,N29696,56%,12Hr,IFR,01:46:21,06:29:27,320,F,2 953,KLAX,07:46:16,12:29:22,310,F,2954,KMCO
AC#27,N68008,95%,8Hr,IFR,00:11:37,03:15:36,190,F,4 365,KGEU,04:11:33,07:15:32,180,F,4366,KSFO
AC#1,N60168,51%,24Hr,IFR,03:45:43,09:28:50,050,F,1 782,CYYZ,15:45:32,21:28:40,060,F,1783,CYQR

Here is the first flight plan line above broken into the base and leg components:

Base: AC#4,N29696,56%,12Hr,IFR,
Leg1: 01:46:21,06:29:27,320,F,2953,KLAX,
Leg2: 07:46:16,12:29:22,310,F,2954,KMCO

Each leg ends with the destination airport for that leg. The last leg always connects back up to the first leg. An unfortunate quirk of this flight plan layout is that the initial airport, the departure point for the first leg, is always found at the end of the flight plan. So the above flight plan begins in KMCO, the first leg is a trip to KLAX departing at 01:46:21, and the last leg is a return to KMCO departing at 07:46:16 .



BASE COMPONENT:

Here is a flight plan base component spread out, with a description of each field. These parameters will remain constant for all legs of the flight plan:
.....
.....schnipp und weiter.....
.....
Aircraft tag:
This is used strictly by the compiler. It specifies which aircraft in the Aircraft...txt source file to use with this flight plan. You can use any aircraft from the associated Aircraft...txt file, but the flight plan parameters, especially the altitude, trip distance, and flying time should be realistic for the type of aircraft used.

Aircraft registration:
This is the so-called ‘Tail number’ for the aircraft. This will be used as the ATC call sign for the aircraft if the aircraft model is not associated with an airline. The registration can be changed to any text sequence up to seven characters, so you could replace it with country-specific aircraft registrations. Microsoft randomly assigned ‘N’ numbers for this field.

Traffic Percent:
This specifies at what level of the FS ‘Traffic Percent’ setting (on the ATC/Traffic settings window) this flight will appear. If this is 56% then this AI flight will only appear if the traffic percent control is 56% or greater. This must be between 1 and 100%. If you run with 100% traffic all the time then this value is not important.

....... usw.