Devirex wrote:Hi,
i have found an error, you don't have to resolv it but maybe it helps you for further improvement:
When starting a flight from LOWG (Graz) [http://www.x-plane.at/drupal/LOWG-Graz-Thalerhof] i get an Segmentation Error if i use a valid SID endpoint as first waypoint for ATC flightplan.
LOWG SID MILGO DCT VATET DCT REDBU Q112 NAPSA STAR EDDM -> Seg fault
LOWG SID REDBU Q112 NAPSA NAPS2A EDDM -> No Problem , but no SID used.
My suggestion is that there is a problem by resolving the airport SIDs because tehre are two other runways which are used by small planes and have no SIDs.
Tried out on Xplane 11 with Boeing 737 (ZIBO mod 2.79)
Is it MILGO you are referring to?
MILGO is not a SID, it's a NAV point. The SID's are MILGO5G, MILGO2H for RWY 17 and MILGO4U for RWY 35. And according to your flight plan that works you have changed STAR to the actual NAPS2A which is for RWY 08 and 26 ARR.
I'm not really following you along here, are you referring to the SID or STAR?
The first one is the most correct, but I can only make it work as follows:
LOWG SID REDBU Q112 NAPSA STAR EDDM.
REDBU is the the START segment on Q112 and pass TITIG then out on NAPSA. There seems to be a problem with SEGMENTS (airways) and Segment Errors with X-Life.
But a route like:
LOWG SID MILGO VATET REDBU TITIG NAPSA STAR EDDM won't work. X-Life seems to not be able to connect NAV points, DCT doesn't help either. DCT shouldn't be needed anyway so.
It's wierd though, becuse:
MILGO VATET REDBU Q112 NAPSA is even valid in CFMU so... Well I guess JAR have an answer to this maybe?
NOTE:
It doesn't matter if you just file LOWG SID REDBU Q112 NAPSA STAR EDDM to ATC, then program your FMS with correct RWY's, SID and STAR. They might tell you some vector info, but just ignore it. Attached my FML from the 737, you can put that in your Output\FMS plans and load it to check.
Post's attachments LOWGEDDM.fml 244.18 kb, 430 downloads since 2017-06-22