Pramod,
I use FSX, not P3D, so there is a chance there will be differences in "default" waypoints between the two. I brought up in ADE the default KSGR, Sugarland in Houston and discovered none of the taxiways are labeled, but other than that it's a good rendition of the way the layout exists today in real life. No runway renumbering or new taxiways that I saw.
I looked at your screenshot but the detail is too small for me to make out the waypoint names. I also looked at the current RNAV (GPS) approach to RWY 17. I assume the "right" 90-degree turn leg in your attachment comes from DIZGY to EBOKE. DIZGY is not a default waypoint in FSX, so I assume it is not in P3D either. Did you add it?
That is "technically" not an Approach leg, but rather a transition to the approach leg. Your approach leg can only be a continuous line of connected waypoints from the IF to the runway (or Missed Approach Point) to the Missed Approach Legs. That is why you cannot add the other side of the "T" to the approach. It would no longer be continuous. When you build an Approach in ADE you do that in three steps with three main types of Legs; Approach Legs from the IF to the Runway or MAP, Missed Approach Legs from the Runway (or MAP) to the Holding Point of the MAP, and Transition Legs from the IAFs to the IF. You first build just the Approach Leg, in this case from EBOKE to Runway is the easiest way , although technically on the Jeppesen Charts I use the "Approach" ends at the Missed Approach Point which is 1.8 miles short of the runway. Anyway, After building the Approach you then add the Missed Approach Legs from the Runway (or Missed Point) to the Missed Approach Hold Fix. As you said, you have that displayed correctly. Now you have to add in the Transition Legs and there can be multiple Transitions from multiple points all converging on the IF at EBOKE.
The IF for the RNAV (GPS) Approach to Runway 17 at Sugarland is EBOKE. Note that an IF can also be an IAF, especially in the case of RNAV (GPS) Approaches, however in the case of KSGR it is only an IF, not an IAF also. So, you have to build your approach using EBOKE as the IF, not DIGZY as I suspect you have. There are two transitions listed on my charts to get to EBOKE, one from DIZGY and one from BASGE. To do that, first remove, if it is there, the EBOKE Transition since EBOKE is no longer an IAF, only an IF. Now look on the right side of the Approach Page when you have the RWY 17 GPS approach displayed on the screen. You will see the heading "Current Airport KSGR" displayed and below that right click where it says "R17:GPS". Four choices should come up; Add Approach Leg, Add Missed Approach Leg, add Transition (note the absence of the word "Leg"), and Show XML.
First make sure you have added the two Transition Waypoints of DIZGY and BASGE. Now select "Add Transition" and in the box that appears select "FULL", "TERMINAL WAYPOINT", and then press the down arrow key next to "Fix Ident" and scroll to BASGE and click "ADD". Next do the same thing for DIGZY. Now at the bottom of the text description of the Approach you should see "Transition BASGE" and "Transition DIGZY" listed.
Remember when I said to note that the word "Leg" was missing from the "ADD TRANSITION" option when you right click "R17:GPS"? That's because transition legs are not added to the runway, but rather to the transition. To add a Transition Leg right click either the words "Transition DIGZY" or "Transition BASGE" and the option to add a Transition Leg will appear. Add an IF Leg at BASGE and also when you move to the other Transition an IF Leg at DIGZY. The Approach has an initial fix at EBOKE, but each transition has an initial fix also (IF...really an Initial Approach Fix (IAF), but that type "leg" is not available in ADE because it was never coded by the ACES Team). Now for both Transitions add a TF (Track to Fix) leg to EBOKE (which, remember, is a waypoint, not a terminal waypoint).
After doing this you still will not see both "sides" of the "T" you are expecting to see at the same time, but they are both there, trust me. Clicking on "Transition BASGE" will show you the left side of the "T" and clicking on "Transition DIGZY" will show you the right side.
Clear as mud, right? Here is mine in two separate screenshots...one for the left side and one for the right....
Randy
. However, when I looked at your file, you had BASGE, EBOKE and DIZGY all nicely lined up in a straight line (top of T), but when I looked at my P3D installation, the coordinates for EBOKE do not match with the coordinates in your file!!! I don't know what is going on here. And in both cases the coordinates do not match with the real-life coordinates (from my ForeFlight). I can understand not matching with real-life data but at least two installations of P3D should not have any discrepancy.
