Hotfix didn’t do ■■■■. Same boat as you on XBOX.
This thread merits some screenshots to show the defect.
Also - rather than asking for a show of hands to the majority - let’s reverse this - is anyone here who can recreate the Topic Author’s defect NOT on XBox? I’m going to assume everyone who chimed in is on console? I need to tag the thread accordingly.
1 Like
Here’s one illustrating the “holes” in the flight plan. You can clearly see there are blank waypoints on the Legs page. This screenshot is post-SU9 pre-SU9 Patch (SU9.1? SU9a?).
I’ll try to replicate my issue with the GNS 530, by redoing that FP and see what it does.
1 Like
Ok, here’s the replicated flight from PASI to PAJN. Oddly, today, the flight planner didn’t automatically choose the SSR waypoint. It just generated a direct flight sans waypoint.
I did a search for SSR, and you can see the waypoint (VOR) exists, but the search results show only airports and no VOR.
I inserted SSR into the flight plan manually and loaded the flight.
I could see immediately that the GNS’ flight path was a direct airport-to-airport without the SSR waypoint. However, the SSR waypoint is the current objective as indicated on the GNS’ display. This is sitting on the ground parked on the apron.
I took off, flew a short distance and you can see the aircraft symbol is on a trajectory to SSR, and the “Magenta Line” remains white. Note: SSR is located roughly where the cursor is.
Here’s a bit further on towards SSR.
Once I reached where SSR should be and the FP updated to the SSR-to-PAJN leg, the GNS’ display froze and its controls (other than zoom) became inoperable. See how the flight plan is a mess now, the white line is not leading to PAJN and its stopped updating.
1 Like
I am not on console. On PC. Thanks. Happened loading my first flight after update yesterday. Did not occur on second but only because I didn’t have to change any waypoints (complete coincidence). I will try again this afternoon after I’m home (in about 4 hours).
EDIT: To be clear, my A/C has all the waypoints (because I’m flying PMDG and entering them into the FMS as per SOP). My issue is exclusively the World Map missing info on dropdowns/no zoom-to once entered in search. I have to find them all and manually select them to add them to route.
If you turn filters on, are the navpoints visible?
I have the filters on (man, do I wish they would stay on!!) and that is the only way I could get SSR to appear. I knew it was there and zooming in is how I could see it.
Having the filters on did nothing for the search results, however.
I’m starting to suspect the missing waypoints are VORs.
I believe that may have been the case with the 787 flight plan I posted the screenshot of and it was definitely the case with this GNS 530 flight.
Yes, in the map itself (not the drop-down). Then you have to zoom in enough to see them show up as a white dot at first and then the symbol appears as I get close. The more difficult ones to locate (not right on my P2P line of travel) I use my Navigraph map (which shows my complete route) to determine the location so I can add them. It’s cumbersome, particularly on trips with many waypoints, but it does work.
Ok, I used the Logbook to re-fly my 787 flight that the FMS screenshot was from in a previous post.
Here’s the flight plan in the map. Note the highlighted waypoint KUDME, note it appears in my FMS screenshot in the previous post and is followed by a missing one. That missing one is MTU — a VOR.
Further note the vast majority of the flight plan’s waypoints are all missing across the central part of the USA along the route. However, those waypoints do show up above in the area just below FROM & TO. If you zoom way in on the map you can see them. I thought I recall all the waypoints used to appear at the default zoom level. I don’t recall having to hunt for them in this fashion.
Your recollection is the same as mine. Prior to this last patch, I could see all my waypoints in the default zoom level as well (without applying any filters). I then could search for additional specific points of any kind, and they would appear in the dropdown (unless there were so many airports that matched the search criteria - it would cut off the list in that case) without applying filters. If I had a VOR waypoint that was cutoff in this way, I could enter it, but would have to go physically search for it to locate it on the map, and filters would have to be applied to see it.
Following the patch, no waypoints of any kind except airports populate the drop-down search list, AND filters must be applied to see any of them, and you have to zoom way in to see them. Typing in a waypoint no longer populates the list and you can no longer thus select it to zoom in to it.
1 Like
Hey everyone, I had a bit of time tonight so did some research on this to see if I could help narrow this down. Just wanted to add some findings.
Note: I’m on XBSX.
World Map and Initial Wait Period
It actually seems to matter how long you sit on the home screen before starting to create a flight plan in the world map. I don’t know if it’s related to the phantom “download completed” notification we are seeing, but if I wait in the main menu until I get the notification there is more data available in the world map waypoint wise.
As an example of what I see here:
In both cases, the scenario starts out with selecting:
- KFAR as a departure airport
- CYWG as an arrival airport
- Selecting the drop down to choose IFR (low altitude airways)
If I immediately go into the World Map and create a Flight Plan
The fight plan is more direct. Some waypoints aren’t present. If I choose the approach/runway drop downs, I just get “automatic” as an option and I cannot choose a specific runway.
If I wait a 5 minutes at the main menu, and then enter the World Map
More waypoints are generated in the flight plan created the exact same way. The drop downs to select approach and runway are populated and I can choose an ILS approach.
This seems to purely have to do with how long I sit at the home screen, and I feel like it has to do with entering the world map after that phantom download notification but I am not sure. There is a variable here though that didn’t exist before.
Waypoints missing in MCDU
Sometimes if I go with scenario 1 above and go in early, the RNAV waypoint that would normally be used in the default generated flight plan is visible if I turn the NAV info filter on (they aren’t always visible though). If I manually add these waypoints to my flight plan (e.g., LITNA, PEPNO) they show up in the world map flight plan.
However, when I enter the aircraft (A320) the MCDU doesn’t include them in the list of waypoints. Basically there is just a gap between the waypoint before, and the airport.
Missing ILS frequency
If I wait and choose scenario 2 from the first section, once I am in the airplane viewing the MCDU configuration it will show the runway for the ILS approach but the frequency is just blank. This doesn’t seem to be the case for all airports, some of them work but CYWG 36Z is a good example of one that does not.
Fin
Hopefully this helps, at the end of the day there are always a few things that end up happening:
- The ILS frequency is never present in the MCDU configuration, even if it’s selected in the flight planner as part of the IFR flight plan
- The navigation display locks up once you cross a waypoint to one that was entered in the flight plan but didn’t show up in the legs in the MCDU
- The aircraft doesn’t seem to follow the flight plan displayed and will go off in some strange directions even though the direction displayed in the 320 navigational display is correct, it’s not followed.
This totally feels like corrupt AIRAC data or something to me, there is something wrong here with respect to the NAV data being used. I don’t know why it matters how long you wait to create a flight plan and how that changes how much information you get in the world map but it’s worth noting.
Thanks everyone
4 Likes
Interesting findings.
I tend to leave my sim running just sitting on the Home Screen or World Map when I’m not currently flying and am up to other life activities.
Therefore, I’m definitely “waiting”, yet I get the misbehavior regardless. Perhaps it would be worse if my waiting wasn’t happening.
Yes it definitely doesn’t fix things to wait but I just find it really interesting that it does change the amount of data I can see in the world map if I do wait. It almost feels like something asynchronously happening in the background. In both cases I can’t get an ILS approach, but if I wait I actually can select an ILS runway in the world map (vs. just a single “automatic” option in the menu).
1 Like
I’m flying a long flight in the Skymaster and got to thinking.
I looked up SSR in the GNS 530.
Take a look a the position data, the screenshot says it all:
Furhermore, that isn’t SSR’s frequency. It’s 114.00.
1 Like
I did a bit more digging as well, here are some more illustrations of this problem.
KGFK → PEPNO (broken)
I created a flight plan in the world map, from KGFK (airport) to PEPNO (RNAV waypoint):
Everything looks as you would expect in the NAV log:
After starting the flight, this is the craziness you get in the MCDU on the runway for the flight plan:
This is after takeoff, with the autopilot engaged. Full zoom in the navigational display to zoom out, you can see there is no flight path indicated (also you can’t tell from the image, but the map itself is frozen and not changing):
KSEA → VPBRI (seems to work?)
Now lets do the exact same thing from KSEA to VPBRI, another RNAV waypoint:
The MCDU looks like you would expect it to in this case now:
Both of these plans were generated the exact same way, but the first one causes the displays to freeze and seems to screw up the flight plan. As I’ve mentioned in previous posts too, this ONLY started happening after SU9 on XBSX.
Thanks all
2 Likes
In the interest of trying to confirm we are corrupted “the same way” I tried the same thing I described earlier, from PAOH → SSR. I see the same thing happen in the A320 I see with other broken markers (the MCDU just shows the flight plan as the airport being repeated over and over again).
If I use that flight plan with the King Air, the NAV display will not list SSR as a waypoint and no flight plan is shown on the display.
1 Like
I’ve suspected AIRAC data being the cause all along. This adds evidence to that theory. Thanks for this…very well done.
1 Like
Hey CasualClick; as a moderator I was just wondering if you might have any suggestions on what we can do to get these issues actioned. We have some other details in here including screenshots like you suggested that are repeatable. Is there a good path we have besides just trying to vote on bugs to get somebody on the development team to have a look at this? This one is a game breaker for us IFR/airline pilots so I’m trying to do whatever I can so we can get this problem resolved.
Thanks
2 Likes
We don’t normally do this, because our role is to facilitate Board conversations, but I escalated this to the CM who talks to the Dev Team earlier this week. This is NOT a guarantee it will get ingested, it’s simply a head’s up to the Dev Team to give this a look.
If it gets moved upwards it will get at the minimum a “Feedback-Logged” tag
5 Likes
Thanks so much, massively appreciated! If I can do anything to help troubleshoot as well I’d be happy to.