danhenri Posted January 13, 2017 Report Posted January 13, 2017 (edited) Hello, I have an issue with the new version of the CRJ. When entering a star with a transition, the approach procedure displayed on the FMS is incomplete. See below, e. g., for star AMVAR, GOMET transition, on approach to LFLL. I have the last update of Navigraph data (no problem with the same flight plan with the IXEG B733). Thanks for your assistance, Daniel. Edited January 13, 2017 by danhenri Quote
danhenri Posted January 25, 2017 Author Report Posted January 25, 2017 Hello, May I have some support to solve this issue ? Thanks, Daniel. Quote
philipp Posted January 27, 2017 Report Posted January 27, 2017 (edited) I see what you mean. LFLL has a very strange encoding for the STAR, where it lists the same trunk route twice for the L and R runways instead of listing the trunk once with a "B" for both runways, as is the standard. Unfortunately, this is due to how ARINC424 data is converted to the various file formats for the different FMSs, and these converters are done by Aerosoft and Navigraph. This is one of the many reasons why for X-Plane 11 I have changed that whole process and now support 424 directly and wrote the converter myself, instead of leaving that to Aerosoft and Navigraph, which eliminates the possibility to have different encodings of the same data. If you try the X-Plane 11 FMC, which uses my new data flow, it of course works correctly: For a future pure X-Plane 11 version of the CRJ, I will obviously use this new infrastructure. For the current CRJ, which still supports X-Plane 10, I cannot do this. Edited February 6, 2017 by philipp Quote
danhenri Posted January 27, 2017 Author Report Posted January 27, 2017 Thanks Philipp for your answer. But, as you may notice above, I don't have this issue with the IXEG 737. So, I will wait till XP 11 is ready ! Cheers, Daniel. Quote
danhenri Posted April 21, 2017 Author Report Posted April 21, 2017 (edited) Hello Philipp, I am now flying the CRJ with XP 11 (last update of course) and the issue I mentioned above is still there. I tested on the same airport (LFLL) and on another one, LFBO, which has 2 L and R runways too (as many airports actually...). And you may see that the STAR entered in the FMC is still incomplete. The STAR was SECHE 6S for the 14R (SURAS transition). All the waypoints between SECHE and SURAS are missing, and the altitude restrictions too. I hope you'll find a solution. Thanks for your work, Daniel. Edited April 21, 2017 by danhenri Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.