NavData or FMC bug?

[Graeme_77]

Hi, Brand new X-Plane user here after many years of MSFS. IXEG was one of the key factors in moving to X-Plane. 

I've noticed some oddities with how the planned route is drawn with SIDs and STARs. I'll post them here in the hope I've missed something.

Glasgow (EGPF) 05 NORBO1J departure. Should be fly ahead to XEXUS, left turn C247 to ELBAN then PTH R236. The SID is coded with two intercept points but the picture on the ND is nothing like what the departure should be. Removing the Intercepts leaving XEXUS, ELBAN allows the aircraft to make a better job flying it.

Marseille (LFML) 31R ILS Z with MTL8C arrival and DOLIV transition. On the missed approach the routing should be basically ahead, MTG, CALAN, Hold. At MTG the ND shows a right hand orbit then out to CALAN. Removing and then replacing CALAN gives the correct left turn though the hold at CALAN is then missing.

I'm using 1.0.4 I think - I've done the hot fix but can't see how to verify the version number? Standard Xplane 10.45 with no navdata mods or updates. Are there known issues with the supplied NavData?

I can do some more investigating and provide screenshots if required?

Thanks.

[daemotron]

1 hour ago, Graeme_77 said:

I'm using 1.0.4 I think - I've done the hot fix but can't see how to verify the version number?

The version number is shown on the PREFERENCES menu, I think, or the PREFLIGHT - not 100% sure which one, but one definitely shows it.

1 hour ago, Graeme_77 said:

Are there known issues with the supplied NavData?

Indeed, there are some issues with (INTC) waypoints. Most of them are marked as Fly-by in the navigation data, while they should be Fly-over. You can test this by editing the SID with a text editor; if it displays correctly afterwards, you have the culprit (a known one in this case). NB: IXEG or X-Plane itself (not sure which component's responsible here) seems to cache nav data, so for me it only worked after restarting X-Plane and re-loading the B733.

1 hour ago, Graeme_77 said:

I can do some more investigating and provide screenshots if required?

If what I stated above doesn't help, you could produce a debug log - after completing pre-flight for the FMS, key in four dots ("....") into the FMS scratchpad. This leaves a file called IXEG_debug_xy.txt in the IXEG 737 Classic folder (xy being a two digit index incremented by one for each debug output).

[Graeme_77]

Thanks, I changed the INTC waypoints to fly over but no luck I'm afraid. It looks like the first INTC is the problem as it's quite far out of position. Debug log and screenshots attached for both the Glasgow and Marseille issue.IXEG_debug_01.txt

 

[tkyler]

I'll give this one a look see tomorrow...dig into the nav data and see whats what.

-tkyler