Discontinuities are inserted pretty much every time a procedure is added because the FMC doesn’t know if you want to connect that procedure with the existing plan or add more waypoints. In order to clear a discontinuity, you can simply delete it, or you can click on the first waypoint after the discontinuity and then press the line select key next to the discontinuity and the FMC will move that waypoint up.
This becomes only slightly more challenging when a discontinuity is preceded by a (vect) vector leg. This happens when a procedure ends with a vector - which occurs often at the beginning of a departure procedure or at the end of an arrival procedure. In these cases, if you want to connect the waypoints and not fly the vector, you need to pick up the waypoint after the discontinuity, like described above, but instead of inserting it on the discontinuity, insert it on the (vect) leg.
Hope that helps - there are some good youtube videos showing people removing disco legs also.
Ah gotcha! I thought that I was entering my flight plan wrong, but from your responses I gather that discontinuities are an acceptable thing to have. So far I’ve fixed them by going directly to the waypoint after the discontinuity, but I want to see if I can delete it, too. Thanks guys!
Thanks for sharing the pic, would you mind creating a github issue for that - does look like a bug specific to visual approaches. You can get around it for now by using the DIR (direct to) page and choosing the RX027 fix as your direct to.
@CutthroatPath73, have you heard of any issues following the glideslope on the latest 0.8.3 version? Just did 3 ILS approaches. First one was fine, then on the next 2 the autopilot captures the glideslope, but the descent rate is excessive and it immediately goes to full scale deflection too low.
Here is a video on the 2nd flight. (left the autopilot on to see what it would do). Glideslope intercept is around the 11min 15sec mark.
Not specifically anything new. For now we still use the default AP for ILS, and it’s always flown it a bit low despite our attempts to resolve. We’re considering our options…
ok, thanks for the info. Wasn’t sure if anything was tweaked, but sounds like that isn’t the case if it is the default AP. It definitely went full scale deflection about 10 seconds after capture. And repeated it exactly on the next identical scenario.
I’ve been flying more RNAVs lately for this reason, and because I find so many ILS beacons missing with Navigraph + third party airports. It can be pretty frustrating at times. I’m going to try to track down the RNAV lateral deviations tomorrow since that is in our control.
It does feel like GS following has been degraded, so when I do fly an ILS I tend to take the opportunity to practice hand flying
We’ll get it nailed down eventually though, of that I’m certain.
Never had a CTD before, now I have installed this mod and I’ve had 3 in the space of 3 flights - no error messages. Reverting back to the default CJ4. Will report back what happens.
Some people are definitely having CTDs and many are not. Our best advice right now is to only enter the starting position on the world map and use the FMC to import the flight plan from simbrief or add it manually. That solves it for many people. We are working with Asobo to track it down by sharing full crash dumps with them.
Have now done 2 flights successfully in the default CJ4 with no CTD, and 3 with a CTD using the MOD. Such a shame, as it’s so useful to have the extra features it gives. Fingers crossed for an update soon!
Yep, 3 CTDs in a row trying to plan a flight with the MSFS world map flight planner. Using Simbrief and/or manually entering the flight plan in the MDCU have so far been so good.
