Critical Navigation Display Issue: Waypoint Name Stuck on PFD Across All Aircraft

  • Dear IPACS Development Team,

    I would like to bring to your attention a significant and persistent navigation issue I have encountered in AeroFly FS 4. This problem has now been observed across multiple flights, aircraft types, and routes, and I believe it warrants urgent attention as it affects basic flight navigation functionality.

    Description of the Issue:

    Over the course of my last five flights, using five different routes and five different aircraft, I have consistently experienced the same problem. The affected routes and aircraft are as follows:

    RouteAircraftOrigin-Destination
    AFR344B773LFPG - CYUL
    AAL973B789KJFK - SBGL
    GLO7602B738SBBR - KMCO
    EWG9868A320neoEDDL - LIEE
    KLM895B744EHAM - ZSPD

    The issue occurs when planning a route in the AeroFly FS 4 flight planner, and when a SID is assigned towards the first waypoint. Once airborne, the Navigation Display (ND) top-right corner continues to display the first waypoint for the entirety of the flight, without updating to subsequent waypoints.

    To clarify the behavior:

    1. The distance counter on the ND updates correctly, showing the distance remaining to the next waypoint.
    2. However, the waypoint name itself does not update and remains stuck on the first waypoint of the flight plan.
    3. This is inconsistent with real-world operations, where the ND should reflect the active waypoint accurately.
    4. The problem occurs across the entire fleet of aircraft in AeroFly FS 4 and does not appear to be aircraft-specific.

    Example Observation:

    During my most recent flight, KLM895 (B744) from EHAM to ZSPD, the waypoint ANDIK remained displayed on the ND, even though I had already passed it. As shown on the FMC/MCDU, the active waypoint was PABCO, located 26.6 NM away, but the ND still indicated ANDIK.

    This discrepancy is not only misleading for navigation but also frustrating, as it affects situational awareness and basic flight management tasks.

    Concerns:

    • This bug has persisted across multiple flights and aircraft types without resolution.
    • AeroFly FS 4 is a high-level simulator, and accurate waypoint tracking is a fundamental navigation feature, which makes this issue particularly serious.
    • The problem appears to be a basic development oversight in waypoint display logic, which is surprising given the version 4 release maturity.

    Additionally, on certain aircraft such as the B744 and B773/B777F, there are instances where the route displays circles around seemingly random waypoints, as illustrated in the screenshot below. This can be confusing, so addressing this issue at the earliest convenience would be greatly appreciated. Please see the screenshots below:





    I respectfully urge the development team to investigate these issues and implement fixes that ensures:

    1. The ND correctly updates the displayed waypoint as per the active flight plan.
    2. The displayed waypoint matches the FMC/MCDU active waypoint.
    3. This functionality is consistent across all aircraft in the simulator.
    4. Route displays do not show extraneous circles or markers around unrelated waypoints, preventing potential confusion.
    5. Visual indications on the navigation display accurately reflect the intended route and waypoints for all supported aircraft types.

    Thank you very much for your attention to this matter. I appreciate your continued work on AeroFly FS 4, and I hope this report helps improve navigation accuracy and the overall simulator experience.

  • Sure, here you go.

    This is the entire route from EHAM to ZSPD:



    This is the SID from EHAM:



    This is the STAR into ZSPD:



    Again, as noted before: This problem has now been observed across multiple flights, aircraft types, and routes, and I believe it warrants urgent attention as it affects basic flight navigation functionality.

    Thank you very much for your attention to this matter.

  • This is the SID from EHAM:

    Did you manually enter all those waypoints that are shown on the left hand side or were they added automatically? So, is this error occurring on the first manually added waypoint, or is that part of the SID that sou selected and it's not flying it correctly?

  • No, I added the waypoints via the Missionsgerät inside the main.mcf, as manually creating flight routes of 14–18 hours in the flight planner by clicking through hundreds of waypoints would be very impractical and cause me instant RSI at any flight planning session.

    The error occurs with the first waypoint, ANDIK, as previously reported. This waypoint is indeed part of the SID I selected, which then leads to the issue described earlier. The route itself does fly correctly, but the waypoint name on the PFD (upper right corner) does not update and remains stuck on the first waypoint of the flight plan.

  • No, I added the waypoints via the Missionsgerät inside the main.mcf, ...

    The error occurs with the first waypoint, ANDIK, as previously reported. This waypoint is indeed part of the SID I selected, which then leads to the issue described earlier. The route itself does fly correctly, but the waypoint name on the PFD (upper right corner) does not update and remains stuck on the first waypoint of the flight plan.

    I suggest that we focus on the facts of the error and solve them, because then the problem is solved.

    I would now try to narrow down the error in order to arrive at a reliable reproducible error description. For this I would test:

    • Does the error only exist with this flight route?
    • How far can this flight route be shortened so that the error still occurs?

    When the shortest variant is determined, I would continue experimenting:

    • Is the error related to the fact that the first waypoint from the mission device is part of the SID?

    At the end of this troubleshooting process, there would then have to be the realization at which points something needs to be changed? Is there an error in the third-party software or is there an error in the FS 4 or even both.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • I suggest that we focus on the facts of the error and solve them, because then the problem is solved.

    I would now try to narrow down the error in order to arrive at a reliable reproducible error description. For this I would test:

    • Does the error only exist with this flight route?
    • How far can this flight route be shortened so that the error still occurs?

    When the shortest variant is determined, I would continue experimenting:

    • Is the error related to the fact that the first waypoint from the mission device is part of the SID?

    At the end of this troubleshooting process, there would then have to be the realization at which points something needs to be changed? Is there an error in the third-party software or is there an error in the FS 4 or even both.

    Thanks for your input, I agree that narrowing things down is important, but I believe the key points you’re asking about have already been covered in my initial report. Let me clarify again to avoid any ambiguity:

    • This is not route-specific. I have reproduced the issue across five completely different long-haul routes, different continents, and five different aircraft types, which rules out a single route being the cause.
    • The issue is also not dependent on route length. All tested flights were between medium-haul to long-haul (3–14 hours), but the problem appears immediately after departure and persists throughout the flight. It’s not something that develops later due to route complexity.
    • The common factor in every case is this:
      • A SID is assigned in the AeroFly FS 4 planner.
      • The first waypoint after or within that SID becomes “stuck” on the ND (top-right corner).
      • The distance updates correctly, and the aircraft follows the route correctly.
      • However, the waypoint name does not update, even though the FMC/MCDU shows the correct active waypoint.
    • So to your question: yes, there does appear to be a relationship between the first waypoint and the SID, but importantly, this behavior is consistent across all tested scenarios, not tied to a specific route or setup.
    • Regarding reproducibility: the issue is already reproducible under these conditions:
      1. Create a route.
      2. Assign a SID.
      3. Depart and engage managed navigation.
      4. Observe that the ND waypoint label remains stuck on the first waypoint, while the FMC advances normally.

    Given the consistency across aircraft and routes, this strongly suggests a systemic issue with waypoint display logic on the ND, rather than a problem with a specific route or third-party tool.

    I’m open to further testing if needed, but at this stage the behavior is already reproducible and clearly defined.

  • Unfortunately, it is difficult for me to work out the key messages in just a few words from the texts that are too extensive for me.

    Maybe I'll find the time to do it according to the motto:

    (1) Shortest flight route where the error occurs.

    (2) If the error occurs under (1) regardless of whether the input of all (!) identical (!) Waypoints either (2a) takes place directly in FS 4 or (2b) is recorded via the Missionsgerät?

    If in both cases only identical entries are made, the responsibility can be clearly limited and described in very few words in my opinion.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • Since I was too interested, I simulated the flight with an A320neo EHAM-ZSPD with the internal data available in the FS 4. My result: It works correctly from my point of view. One preliminary remark: You write from the upper right corner in the PFD, but in my opinion it is not the PFD but the ND.

    In my FS 4 Version (4.08.01.20 (2026024) - STEAM alpha-channel - Mac) I can't find the waypoints PABCO, COFCA and SUQUEF, so I left them out and routed them directly from ANDIK to REVLA - and the display in the ND changes correctly.
    => I suspect that in the ND the waypoints are only changed correctly if they are also known in the internal system. If this is the case, the FS 4 also works without errors in this regard to this point.

    I suggest that you try to enter only the waypoints that also exist in FS 4 via the Missins device. I strongly suspect that the display will then work in the ND.


    And if your attempt works, the result is this desire for the future:
    The internal database of the FS 4 should be extended by the missing waypoints.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • Anyway, the internal database of FS4 is so incredibly ancient and so heavily outdated, that issues like the one i reported will occur unless something is done to update it to nowadays standards. In this day and age it is just unforgiveable that a modern sim is still using data from 13 years ago, this is simply unacceptable.

  • I would say that it's apparently time for you to switch sims, but MSFS24 is using data wich are (at least) 20 years old.

    So that's not an option for you either.

    I’ll decide for myself what i do or don’t do, thanks.

  • Sorry, I am late to the party, but here are my two cents: the main.mcf export generated by the Missionsgerät lacks one fundamental property for each waypoint: its internal ID.

    This essentially breaks some functionality the simulation relies on. So possibly the errors reported in this thread are a result of the somewhat incorrect method of injecting a flight plan into Aerofly FS.

  • Sorry, I am late to the party, but here are my two cents: the main.mcf export generated by the Missionsgerät lacks one fundamental property for each waypoint: its internal ID.

    This essentially breaks some functionality the simulation relies on. So possibly the errors reported in this thread are a result of the somewhat incorrect method of injecting a flight plan into Aerofly FS.

    The flightplan tool I created imports flightplans safely with the ID's (since the original is created using the MCDU or Flightplanner)

    Mine is PC only, the Op uses a MAC. From your experience, do you think it would be hard to make a MAC version? All my software does is backs up any created route, then safely copies it back into the main.mcf if needed at a later date.

    Its just a powershell script with a GUI, nothing complicated or fancy. I have zero MAC experience


  • The flightplan tool I created imports flightplans safely with the ID's (since the original is created using the MCDU or Flightplanner)

    Mine is PC only, the Op uses a MAC. From your experience, do you think it would be hard to make a MAC version? All my software does is backs up any created route, then safely copies it back into the main.mcf if needed at a later date.

    Its just a powershell script with a GUI, nothing complicated or fancy. I have zero MAC experience


    Although I've followed the specific forum thread for your route tool 777Driver , I might have missed its internal working.

    You say it "backs up any created route", do you mean created by an external website like http://onlineflightplanner.org/ which has the .route-format that is also shown inside your tool, or how do you mean "any created route"?

  • 777Driver Actually the new tool keeps hold of any UIDs it gets, until it is forced to create brand new waypoints. So depending on how your route files are structured, it is just another import file format the Missionsgerät and its successor (currently called "Startgerät") could read and/or export.

    Do you have an example of a route file I could take a look at?

  • To clarify, my mod only extracts the route from the main.mcf after the user has created the route. It will never try to build a route, the purpose of the tool was so I only needed to create a longhaul route once, then I can save it for later.

    So the route below is created inside the aircraft or FS4 Flight planner - Zurich to Tokyo, I built the route using SimBrief


    <[tmnavigation_config][navigation][]
    <[tmnav_route][Route][]
    <[float64][CruiseAltitude][10058.4]>
    <[pointer_list_tmnav_route_way][Ways][]
    <[tmnav_route_origin][LSGG][0]
    <[string8u][Identifier][LSGG]>
    <[vector3_float64][Position][4394126.04082601 470329.203605148 4583610.47783742]>
    <[uint64][Uid][9536426797715761152]>
    <[float64][Elevation][430.0728]>
    >
    <[tmnav_route_departure_runway][05][1]
    <[string8u][Identifier][05]>
    <[vector3_float64][Position][4395090.45650414 469230.71929561 4582803.77952218]>
    <[uint64][Uid][9535632950273585152]>
    <[vector3_float64][Direction][-0.57882184105663 0.655765431806018 0.484702975815169]>
    <[float64][Elevation][430.0728]>
    <[float64][RunwayLength][3899.916]>
    >
    <[tmnav_route_departure][MEDA4N][2]
    <[string8u][Identifier][MEDA4N]>
    <[vector3_float64][Position][0 0 0]>
    <[uint64][Uid][9536426797716885504]>
    <[string8u][Airport][LSGG]>
    <[vector3_float64][Direction][0 0 0]>
    <[float64][Elevation][0]>
    <[string8u][Transition][]>
    <[uint64][TransitionUid][0]>
    >
    <[tmnav_route_waypoint][NITAM][3]
    <[string8u][Identifier][NITAM]>
    <[vector3_float64][Position][4474103.17637454 561861.324940924 4495679.1873455]>
    <[uint64][Uid][9590144532783892480]>
    <[float64][NavaidFrequency][0]>
    <[uint64][NavaidUid][0]>
    <[vector2_float64][Altitude][-1001 100001]>
    <[bool][FlyOver][false]>
    >
    <[tmnav_route_waypoint][LABIN][4]
    <[string8u][Identifier][LABIN]>
    <[vector3_float64][Position][4401262.96005059 1023508.70207539 4486235.02716301]>
    <[uint64][Uid][9894188084638910464]>
    <[float64][NavaidFrequency][0]>
    <[uint64][NavaidUid][0]>
    <[vector2_float64][Altitude][-1001 100001]>
    <[bool][FlyOver][false]>
    >
    <[tmnav_route_waypoint][NISVA][5]
    <[string8u][Identifier][NISVA]>
    <[vector3_float64][Position][4308881.47678109 1811065.76085736 4325289.52120455]>
    <[uint64][Uid][10391538966653372416]>
    <[float64][NavaidFrequency][0]>
    <[uint64][NavaidUid][0]>
    <[vector2_float64][Altitude][-1001 100001]>
    <[bool][FlyOver][false]>
    >
    <[tmnav_route_waypoint][UDROS][6]
    <[string8u][Identifier][UDROS]>
    <[vector3_float64][Position][4038494.74301824 2387989.16957455 4306242.4640073]>
    <[uint64][Uid][10791146571174971392]>
    <[float64][NavaidFrequency][0]>
    <[uint64][NavaidUid][0]>
    <[vector2_float64][Altitude][-1001 100001]>
    <[bool][FlyOver][false]>
    >
    <[tmnav_route_waypoint][KARDE][7]
    <[string8u][Identifier][KARDE]>
    <[vector3_float64][Position][3794559.24080116 2864109.67976596 4237664.56435877]>
    <[uint64][Uid][11121608085937129472]>
    <[float64][NavaidFrequency][0]>
    <[uint64][NavaidUid][0]>
    <[vector2_float64][Altitude][-1001 100001]>
    <[bool][FlyOver][false]>
    >
    <[tmnav_route_waypoint][ROLIN][8]
    <[string8u][Identifier][ROLIN]>
    <[vector3_float64][Position][3612519.43127935 3102476.02593042 4229000.50805244]>
    <[uint64][Uid][11306644897339738112]>
    <[float64][NavaidFrequency][0]>
    <[uint64][NavaidUid][0]>
    <[vector2_float64][Altitude][-1001 100001]>
    <[bool][FlyOver][false]>
    >
    <[tmnav_route_waypoint][LAGAS][9]
    <[string8u][Identifier][LAGAS]>
    <[vector3_float64][Position][3424060.49367486 3333405.04368572 4210153.43188985]>
    <[uint64][Uid][11489831230165485568]>
    <[float64][NavaidFrequency][0]>
    <[uint64][NavaidUid][0]>
    <[vector2_float64][Altitude][-1001 100001]>
    <[bool][FlyOver][false]>
    >
    <[tmnav_route_waypoint][SARIN][10]
    <[string8u][Identifier][SARIN]>
    <[vector3_float64][Position][540854.52333631 4335042.58122788 4631516.51393746]>
    <[uint64][Uid][13470649829021517824]>
    <[float64][NavaidFrequency][0]>
    <[uint64][NavaidUid][0]>
    <[vector2_float64][Altitude][-1001 100001]>
    <[bool][FlyOver][false]>
    >
    <[tmnav_route_waypoint][LADIX][11]
    <[string8u][Identifier][LADIX]>
    <[vector3_float64][Position][-2248614.15699139 4414582.23900711 4003474.7712288]>
    <[uint64][Uid][15218180592017541120]>
    <[float64][NavaidFrequency][0]>
    <[uint64][NavaidUid][0]>
    <[vector2_float64][Altitude][-1001 100001]>
    <[bool][FlyOver][false]>
    >
    <[tmnav_route_waypoint][DONVO][12]
    <[string8u][Identifier][DONVO]>
    <[vector3_float64][Position][-2781557.84918413 4229153.24858237 3867431.63926798]>
    <[uint64][Uid][15543090669896599552]>
    <[float64][NavaidFrequency][0]>
    <[uint64][NavaidUid][0]>
    <[vector2_float64][Altitude][-1001 100001]>
    <[bool][FlyOver][false]>
    >
    <[tmnav_route_waypoint][AGAVO][13]
    <[string8u][Identifier][AGAVO]>
    <[vector3_float64][Position][-2845395.98204562 4218781.8491667 3832394.59645131]>
    <[uint64][Uid][15577151339553425408]>
    <[float64][NavaidFrequency][0]>
    <[uint64][NavaidUid][0]>
    <[vector2_float64][Altitude][-1001 100001]>
    <[bool][FlyOver][false]>
    >
    <[tmnav_route_arrival][ARLON][14]
    <[string8u][Identifier][ARLON]>
    <[vector3_float64][Position][0 0 0]>
    <[uint64][Uid][16385890514078685184]>
    <[string8u][Airport][RJTT]>
    <[vector3_float64][Direction][0 0 0]>
    <[float64][Elevation][0]>
    >
    <[tmnav_route_approach][I34LZ][15]
    <[string8u][Identifier][I34LZ]>
    <[vector3_float64][Position][0 0 0]>
    <[uint64][Uid][16385890514079211520]>
    <[string8u][Airport][RJTT]>
    <[vector3_float64][Direction][0 0 0]>
    <[float64][Elevation][5.4864]>
    <[string8u][Transition][]>
    <[uint64][TransitionUid][0]>
    >
    <[tmnav_route_destination_runway][34L][16]
    <[string8u][Identifier][34L]>
    <[vector3_float64][Position][-3967884.94890994 3354824.27339573 3686473.16390022]>
    <[uint64][Uid][16386123610480062464]>
    <[vector3_float64][Direction][0.707921954132143 0.0586421996158067 0.703851972563797]>
    <[float64][Elevation][5.4864]>
    <[float64][RunwayLength][3000.1464]>
    >
    <[tmnav_route_destination][RJTT][17]
    <[string8u][Identifier][RJTT]>
    <[vector3_float64][Position][-3966793.89554154 3354443.02305006 3687983.78233723]>
    <[uint64][Uid][16385890514078672896]>
    <[float64][Elevation][6.4008]>
    >