PlanG3 Approach Display - Waypoints and Transitions

[ronzie]

Using Airport Design Editor I added an ILS navaid and approach using current named waypoints added to FS9's scenery list and also showing in Plan-G to feeder airport KANE. There was no default ILS navaid. Plan-G though is showing different waypoints than I designed into it.

First, here's the IAP plate I worked on:

https://www.dropbox.com/s/gyrsvp8i69onruf/KANE_IAP_ILS%20OR%20LOC-DME%20RWY%2027.PDF?dl=0

Here's a screenshot of Plan-G with ILS 27 Approach selected:

https://www.dropbox.com/s/yfnr7bzs630jg65/PlanG-3%20KANE%20ILS%2027%20Approach.jpg?dl=0

Note also the transitions are not offered. Here's an extract in xml format of the approache in the af type .bgl file:

https://www.dropbox.com/s/ovfql824c0aatur/KANE%20ILS%2027%20Appr%20extract.txt?dl=0

What is showing are waypoints used by default other approaches.

Now in the intersection database there is some duplication of intersections including T-Waypoints and unnamed custom intersections from the intersection update downloaded database with slightly shifted positions. Some of these are used in the other imported default approaches yet were used for my designed approach although not designated. I also noted in order for this approach to show I had to designate the leg waypoints as not fly-over so there would be a two mile radius or else the approach would not load into Plan-G at all.

In the screenshot plan section you can see the added waypoints are not what I used as shown in the xml extract. That and no transitions are offered.

The XML approach section appears to follow the FS9 bgl SDK standards plus tutorials from the ADE folks.

The Plan-G log on a data build shows this .bgl file was listed near the beginning of the scan list and the line shows the five transitions and eleven waypoints.

Do you have any ideas as to these discrepancies?

Here from the Plan-G log is the Approach read when I selected it:

23:34:35.2 APPROACH: ILS 27
23:34:35.2  TERMINAL_WAYPOINT JUDAL IF
23:34:35.2  TERMINAL_WAYPOINT BOKYA CF
23:34:35.2  8 IANE CF
23:34:35.2 MISSED:
23:34:35.3  CF fix: GEP VOR Crs: 268 7.409895 (Rec: rho: 0 theta: 0) Flyover: False
23:34:35.3  HM fix: GEP VOR Crs: 084 0.001 turn: Right (Rec: rho: 0 theta: 0) Flyover: False
23:34:35.3 TRANSITION STILS
23:34:55.9 APPROACH: VORDME 27
23:34:55.9  TERMINAL_WAYPOINT CF27 IF
23:34:55.9  TERMINAL_WAYPOINT TOURI CF
23:34:56.0  RUNWAY RW27 CF
23:34:56.0 09 27
23:34:56.0 MISSED:
23:34:56.0  CF fix: GEP VOR Crs: 264 13.33781 (Rec:GEP rho: 0 theta: 0) Flyover: False
23:34:56.1  HM fix: GEP VOR Crs: 084 0.001 turn: Right (Rec: rho: 0 theta: 0) Flyover: False
23:34:56.1 TRANSITION D050R GEP
23:34:56.1  IF fix: D050R TERMINAL_WAYPOINT Crs: 000 0 (Rec:GEP rho: 33344.53 theta: 50) Flyover: False
23:34:56.2  AF fix: CF27 TERMINAL_WAYPOINT Crs: 050 0 turn: Right (Rec:GEP rho: 33344.53 theta: 84.4) Flyover: False
23:34:56.2 TRANSITION D103R GEP
23:34:56.2  IF fix: D103R TERMINAL_WAYPOINT Crs: 000 0 (Rec:GEP rho: 33344.53 theta: 103) Flyover: False
23:34:56.3  AF fix: CF27 TERMINAL_WAYPOINT Crs: 103 0 turn: Left (Rec:GEP rho: 33344.53 theta: 84.4) Flyover: False
23:34:56.3 TRANSITION GEP
23:34:56.3  IF fix: GEP VOR Crs: 000 0 (Rec: rho: 0 theta: 0) Flyover: False
23:34:56.4  TF fix: TOURI TERMINAL_WAYPOINT Crs: 000 0 (Rec: rho: 0 theta: 0) Flyover: False
23:34:56.4  HF fix: TOURI TERMINAL_WAYPOINT Crs: 264 0.001 turn: Right (Rec: rho: 0 theta: 0) Flyover: False
23:34:56.4 TRANSITION TOURI
23:34:56.5  HF fix: TOURI TERMINAL_WAYPOINT Crs: 264 0.001 turn: Right (Rec: rho: 0 theta: 0) Flyover: False
23:34:56.5 Finished reading transitions


and these are not what I designed.

Now the full XML file has the usual delete_all_approaches=TRUE. I did import the default approaches which are RNAV and GPS. So it does see the ILS I added but not the legs as I designed them and shown in the extracted xml from decoding that bgl file.

Any ideas?

[tim arnot]

Can you send me your bbl, and I'll try and take a look.

[ronzie]

Here is the airport bgl file link:

https://www.dropbox.com/s/7mlfyafzz6s2xar/KANE_ADE9_REG.BGL?dl=0

Here is the (renamed) updated intersection file I installed in FS9:

https://www.dropbox.com/s/2rd5o8f2zg6ekxc/NVWorldINT.zip?dl=0

It other than minor location changes it is stated to be used for FS9 and/or FSX.

Here is the ADE 9 display for KANE ILS 27 Transition STILS:

https://www.dropbox.com/s/6t0f13kpj5zy4le/ADE%209%20DISPLAY%20KANE%20ILS%2027%20TRANSITION%20STILS.jpg?dl=0

Do you want the ADE 160 FS9 project file?

I also wonder if this is a bounds issue on the waypoints if you acquire the nearest waypoint on a slight displacement.

[ronzie]

Did you find anything wrong with the KANE ILS27 transitions in the .bgl file? The Plan-G log seemd to see them but does not list them in the approach selection dialog for ILS27. The main part seems to display OK including the missed legs.

[tim arnot]

Sorry, haven't had the chance - I'm working both ends of the clock at the moment, and nothing else gets a look in (some days I don't even manage to log on to the forum!) But I haven't forgotten about it.

[tim arnot]

I don't have FS9 installed, so I'm looking at your data in the context of FSX, and so some aspects may be different.

I presume that the NVWorldINT file is to reposition some of the existing intersections? It would help to know what you changed in this file, since I don't have a default one for comparison. (I'm assuming that duplicated waypoints I see here are the result of the differing file layouts between FSX and FS9?)

* There are two JUDAL waypoints, at 17DME and 23DME from GEP. The JUDAL at 23DME appears to correspond to the PDF plate. It must be defined as a TERMINAL WAYPOINT (it isn't) if it is to be used for the IAF (this will colour it blue and include the ID of the airport in its tag).

* The waypoint at STILS is set to region K5, yet the transition requires it to be in K3. Thus it will not appear.

* If your system only shows the 23DME JUDAL, the BLAYN transition will not have a correctly defined termination (since it must end at a TERMINAL_WAYPOINT), so it will not appear.

Hope that helps :)

[ronzie]

The updated waypoint file link is covered in this thread. Renaming solved the problem. Yes, there are are some slight discrepancies with FS9 placement as forewarned by the author. He determined the region but I can correct those errors. He also defined named and unnamed as enroute and other. I'll change the IAF to a terminal waypoint.

The default VOR/DME FS9 approaches I imported and used as an example had both K3 and K5 regions which did not make sense but I used those mixed for these new transitions. I'll modify those.

Thank you for looking at this.

I am using Plan-G to proof my updated approaches of airports of interest. I also recommended it to an FS9 enthusiast who appears to be cash strapped to use as a moving map to show these new waypoints. I also pointed out it helps with terrain situational awareness.

Very nice application. Thank you for it.