HiSorry, if this question was answered before ;-).Sometimes, I have in FP message "discontinuity inserted after waypoint" and this discontinuity cannot be deleted.ThanksEdin

HiSorry, if this question was answered before ;-).Sometimes, I have in FP message "discontinuity inserted after waypoint" and this discontinuity cannot be deleted.ThanksEdin

Yes, I

Hi,Maybe Dan will answer this better but this could also be due to minor mistakes in the SID/STAR txt file. There are certain cases which will cause a DISCO.You can eliminate it by entering custom waypoints and clearing it or by getting a new file from the Navdata database.My personal advice would be to get Terry Yingling's tutorial and edit/build them yourself, it's fairly easy once you understand the logic. It's very fun, too. :(

Thanks guys.I will try it :-)Edin

Hey Edin, in case you're interested you can get the tutorial herehttp://planepath.com/html/pmdg_utilities.html

Maybe Dan will answer this better but this could also be due to minor mistakes in the SID/STAR txt file. There are certain cases which will cause a DISCO.

There are some odd issues in FS9, for example, that will cause disco errors in perfectly written script. Case in point is when the track is 180-deg True then there is a disco on entry to holding patterns (example KMCO) or discos after the initial climb on runway track to minimum safe altitude before turning to first fix on RNAV SIDs (example KDFW). I see other examples as well, and new ones are provided to me as recently as this weekend.Most of the time, if you cannot delete the disco error, it is because the logic cannot solve for the track between two points. I wasn't aware of the end-of-page issue... learn something every day. Thanks for that.

I have noticed this with doubled up waypoints in SIDs and STARs... removing the second of the duplicate waypoints and then clearing the discontinuity seems to solve it...It is always handy to have the relevant chart to review the procedure when doing this of course...Andrew