Schedule file (Plans*.txt)
Each line of the file specifiy a different boat. Lines starting with '//' are comments and not read by the program.
The line is split using the comma as a field separator. A plan starts by 4 fields then is followed by the list of plan orders (at least two)
AC#14,B60264,60%,2Hr
- AC#14 define the boat model identifier. Use the same identifiers as specified in Boats.txt
- B60264 is the boat name. It is not displayed or used by the traffic, but could help to distinguish plans. Only characters valid for an aircraft registration could be used here. Avoid punctuation marks and use no more than 10 leters.
- 60% is the minimum traffic percent that must be configured to see this boat in the simulator
- 2Hr is the repeat frequency. You can specifiy it as a number of hours or weeks, e.g. 1344Hr or 8WEEK
In each order, a departure time is given. The departure is relative from the start of the period. If a plan has a 4 hours periods, then an order that starts at 1:45 will be repeated at 5:45, 9:45, 13:45, 17:45, and 21:45 each day. Although all these times could be used to define a plan, the first one (between 0:00 and 4:00 the end of the period) should be used.
For periods that span multiple days, a day number is also used, followed by a '/' before the time. Day numbers starts at 0. For 1WEEK periods, 0 means Monday, so for instance 4/15:20:40 means 15:20:40 on friday.
For periods that span multiple weeks, the day number 0 is (apparently) the first monday of the year, though it remains unsure.
An order consists in 5 comma separated fields:
00:18:19,00:24:06,1754,reverse,ferry
- The first field is the departure time or day/time if period is more than 24 hours. The time is always GMT.
- The second field the arrival time. It is not used by the program since the arrival time is recalculated based on the route length and the boat speed. When a file is compiled, calculated arrival times are inserted back in the file. It's generally a good idea to check the calculated arrival time to see if the next leg does not starts before the arrival of the current leg. Otherwise the boat may conflict and not appear at correct times.
- 1754 is the route number, as defined by the Boats.KML or Boats.CSV file. Only numerical identifiers are supported
- The fourth field is a boolean indicating the travel direction on the route. If it is marked reverse, then the route is followed from the last point to its first point. Any other word in this position means normal direction
- The last flag concern terminal parking type. As said before, a boat marked FERRY will stop at the endpoint of the route. The default behaviour is not FERRY, so any other word in the leg definition will cause the boat to find a parking spot on a circle around the endpoint.
When designing flight plans, users should be very careful to the order and directions of the legs. Like aircrafts schedules, a boat schedule must loop back to its first point before the end of its period. However improper route definitions and direction may cause the circuit to break. AIBTC check circuit continuity and errors.
A complete plan definition looks like this:
AC#14,B60264,60%,2Hr,00:18:19,00:24:06,1754,reverse,ferry,01:18:19,01:24:06,1754,normal,ferry
Note that the plan use only one route with one leg marked as "normal" and the other as "reverse". This is the safest way of creating a boat plan. Due to some limitations in the AI subsystem, no more than two different routes (not including direction) could be used in one plan. The contrary may cause FSX to crash.
You can fortunately have more than two orders provided they use only two routes and makes a correct closed circuit