I had a notification this evening that the G1000 NXi had an update in the content manager. Instead of messing around with an index for each SID/STAR, the flight plan should include the transitions for the SID/STAR. The flight plan only works correctly when the transition waypoint is in the zero slot. If MSFS is sending a “zero” instead of a 1 or a 2, then this is a huge bug that breaks the NXi (and the WT CJ4). (IMHO a very bad design even if it works correctly). This has the aircraft flying each SID and STAR twice.Īn earlier post described how MSFS passes an index to the FMS indicating the transition. The mess is complicated when the SID/STAR transition is corrected manually in the FMS, the FMS adds the correct waypoints for the correct transition but does NOT delete the “original” correct waypoints. This creates a jumbled mess because the FMS adds all the waypoints for the wrong transition AND keeps all the waypoints for the correct transition. The flight plan contains each waypoint for the SID and STAR. Looking at the flight plan itself, the SID and STAR are in the flight plan but without any transitions specified. The NXi creates a flight plan route that fly each transition for the SID and STAR. The Navlog and VFR Map show the flight plan correctly. There is one input which is the flight plan file. Generally there are three “outputs” of the flight plan in the cockpit: 1) GPS/FMS, 2j Navlog, 3) VFR Map. What is baffling is where in the flight plan pipeline the flight plan is breaking. I am going to fly this plan again to see if this particular “flyback” problem has been fixed.Įdit: Update: I tried the same flight and the same errors occurred. The GPS would fly one transition, then turn around to fly another until all the transitions had been flown. The same thing happened with the STAR except in reverse. The GPS then flew the aircraft back to the start of the other departure transition at DOTSS then proceeded to fly the other transition CLEEE. The departure SID DOTSS2 was flown correctly until the CNERY transition exit gate. Several months ago I created and flew IFR from KLAX to KPHX (KLAX/25L DOTSS2 CNERY DCT BLH HYDRR1 KPHX/R07RY). How could one ever hope to test every iteration of flight plan to look for these sorts of mishaps? I just want to route the error to the appropriate place.īTW, I’ve been able to easily reproduce this.Īs an aside, I had an absolute panic attack for the testing process of this whole mechanism. I was able to erase both the ORCUT & GVO waypoints in the flight plan from the NXi, which is great as a workaround, but the question remains: Who’s responsible for adding the superfluous transition – WT or Asobo? This is a ~100NM roundtrip superfluous transition. When I load into the cockpit, however, I can see it has added a Gaviota Transition (AVILA4.GVO), which would have me take off, turn towards AVILA, turn the opposite direction of MQO towards ORCUT then GVO, make a 180º turn back towards ORCUT then AVILA then MQO and I’m on my way. All looks as it should on the World Map – take off, turn towards AVILA, turn towards MQO and you’re on your way. It showed departing KSBP via an AVILA FOUR departure with Morro Bay Transition (AVILA4.MQO). I changed it from VFR-direct to IFR low altitude, keeping the default flight plan as constructed by the World Map. I selected the DA62 and setup a flight plan departing KSBP parking 13, arriving KSLC auto-selected runway arrival in the World Map. Be forgiving of errors in terminology please. I’ve mostly focused on VFR within the sim, however I’ve tried to educate myself. Ok, then I’m thinking this is the correct place for the issue.įirst, I’m pretty new to IFR – specifically GPS-based.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |