Change to departure airport creates discontinuity I can't get rid of

Ok, I am such a newbie at this. Trying to learn how to program and fly the Fenix A320 (or any 320 for that matter) and it seems like my Simbrief flight plan always picks the wrong runway from what either BATC or sim ATC picks and I need to change it. Once I do of course I’m always going in exactly the opposite direction and after changing departure information in the MCDU flight plan, there is this discontinuity I can’t get rid of even if I go and create a new Simbrief flight plan with the new airport and start over. What is a MANUAL waypoint which is created before the discontinuity and how do I get past it? I can find tons of videos explaining how to deal with a change to the destination but nothing about the departure. This seems to happen 90% of the time to me. Is Simbrief just that bad at creating flight plans that it can never match the sim or BATC? I have the most recent AIRAC cycle always.

Maybe this can help you:

1 Like

Oh that is a great explanation. Thank you. A shame you have to go to FBW to get this documentation but real credit to them for being so thorough. I’m surprised I could find no Youtube videos explaining it and I think Fenix should do a better job of explaining all the ins and outs of flying their aircraft. I think they assume that people that buy their product already have all the basic knowledge. That’s probably the case most of the time.

So, with my newfound knowledge I took a flight from Denver to Las Vegas in the Fenix A320. It was strange when I set up the flight plan in Simbrief that the approaches were really odd and disconnected. Turns out that when choosing the arrival airport, I inadvertently chose North Las Vegas instead of the main airport which apparently is now called Reid. (I was looking for McClarren). I wanted an ILS approach so forced it to runway 12L which I found out at the end was really short and just rolled off the end of the runway but it was recoverable. I learned a great deal about flying the 320 though. VR was stunning with the flight going over Monument Valley and the Grand Canyon but it is tough to push and pull the buttons like altitude using VR because pressing the mouse center button also is the control for zoom. I need to see if I can get more sane bindings for the mouse and VR controllers. BATC had no clue about the approach to North Las Vegas and I was on my own.