|
|
Post by Moostafa on Dec 28, 2010 17:21:01 GMT -5
I have quite a few add-on airports and I would like to see a higher priority given to those airports when building an airline schedule.
|
|
|
|
Post by Dutch Owen on Dec 28, 2010 18:06:38 GMT -5
The final release of 1.2 will contain a feature where you can give the hub builder a list of airports to include in the schedule it builds.
Hope this is something close to what you want...
Dutch
|
|
|
|
Post by Moostafa on Dec 28, 2010 19:12:26 GMT -5
Yup that sounds great.
Thanks
|
|
|
|
Post by Moostafa on Jan 25, 2011 20:52:18 GMT -5
Hey Dutch,
Is this still scheduled to make the 1.2 release?
Molders
|
|
|
|
Post by Dutch Owen on Jan 25, 2011 21:40:55 GMT -5
Yes. In fact it is in Beta 6, but not documented yet. I'll be updating the documentation starting tomorrow I suspect. Major updates to the FCOM Reference...sigh.
To make a node list for the hub generator, make a file with the airline's name plus _nodes.txt. For example, Landmark_nodes.txt. Put this file in the FSCaptain\airlines folder along with the airline's .cfg file and (possibly) its schedule file.
Inside that file list every airport you want to be included, here's an example:
Node=KATL
Node=KMEM
Node=KCVG
Node=KTYS
Node=KBNA
Node=KSDF
Node=KLEX
Node=KLOZ
Node=KHTS
The more you put in here the richer your schedule will be.
If this file is present when you run the hub generator for an airline only these airports will be destinations from your hub.
Dutch
|
|
|
|
Post by Travis on Jan 26, 2011 0:54:47 GMT -5
Thx Dutch... already poking at the envelope....
|
|
|
|
Post by Moostafa on Jan 28, 2011 19:13:19 GMT -5
I have been doing some testing and this works really well Dutch...thanks.
Molders
|
|
|
|
Post by Dutch Owen on Jan 29, 2011 15:05:17 GMT -5
There are two bugs that will be fixed in 1.2 non-beta.
Dutch
|
|
|
|
Post by Travis on Jan 29, 2011 18:42:41 GMT -5
I have a node list of 1673 airports (extracted from 3rd party sceneries) so it's fairly robust.  |
|
