KuntaKinte 210 Posted August 29, 2021 Share Posted August 29, 2021 Example: After manually entering a basic flightplan, you decide to remove a waypoint from within the route. IRL, this can easily be done either on the LEGS page or on the FPLN page - the FMS simply connects the previous with the following waypoint. AS CRJ: On the FPLN page, deleting a waypoint as mentioned above does not work correctly. The FMS fails to connect the waypoints adjacent to the deleted waypoint and creates a DISCONTINUITY instead. Trying to get rid of this DISCONTINUITY causes more problems. The behaviour should be reproducible with the procedure below. It has been tested several times, so if you stick to it exactly, you should get the same results. My setup: Startup airport: EDDM Aircraft state: after inital loading or after restart FMS 2 (Copilot)): LEGS page (for comparison) FMS 1 (Captain): FPLN page On FMS 1 ⦁ As ORIGIN enter EDDM and EXEcute ⦁ As DEST enter EDDH and EXEcute ⦁ Select NEXT PAGE ⦁ Enter waypoint WLD and EXEcute ⦁ Enter waypoint BURAM and EXEcute => Known bug: BURAM does not show up in the list until you put DELETE on LSK2L. This has been reported already. ⦁ Enter waypoint BOMBI and EXEcute ⦁ DELETE waypoint BURAM Result: FMS fails to connect WLD with BOMBI and creates a DISCONTINUITY. To close the gap between WLD and BOMBI: ⦁ Select LEGS page ⦁ Put BOMBI in the scratch pad, insert it below WLD on LSK2L and EXEcute Result: The last action causes WLD to be unintentionally deleted. Link to comment Share on other sites More sharing options...
SinusJayCee 38 Posted September 4, 2021 Share Posted September 4, 2021 I don't know how it works exactly in the real plane. But I usually don't delete waypoints but just move the following waypoint one up. In your example, instead of deleting BURAM, I would copy BOMBI to the scratchpad and hit the LSK next to BURAM. However, in particular in the second part of your example, WLD should stay in the flight plan of course. Link to comment Share on other sites More sharing options...
KuntaKinte 210 Posted September 4, 2021 Author Share Posted September 4, 2021 That was only to force the occurance of this error and make it reproducible, because that is what the AS guys require. Link to comment Share on other sites More sharing options...
SinusJayCee 38 Posted September 4, 2021 Share Posted September 4, 2021 Sure, and you did a pretty good job there with describing it step by step. I was trying to help with an alternative method to work around this Link to comment Share on other sites More sharing options...
KuntaKinte 210 Posted December 16, 2021 Author Share Posted December 16, 2021 Dear AS Reps/Devs, since you never responded to this report, I would like to know: Can you confirm that you are able to reproduce this bug? this is is on your bug tracking list? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.