Jump to content


  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Cruise altitude FL360. Upcoming waypoint with restriction of above FL167 and below FL177. LEGS FMC page shows the climb indicator arrow. LEGS DATA page shows it as a CRZ phase. No VNAV guidance provided.   DUM9ZA STAR ZBAA

      Please login to display this image.

      Please login to display this image.

      Please login to display this image.

    • Ok. Thank you. Sorry it doesn't make sense. That's not what its doing. In the KALT-KMGM the KMGM is picking up another waypoint with the same designation (KMGM) Thousands of miles away. Same with KCLT, instead of Charlotte it's loading some waypoint with the same designation (KCLT) A thousand miles away. Next time I fly this weekend I'll upload pictures. Thanks for taking time to reply. 
    • Danke für den Hinweis! Das Problem ist, dass in OSM Straßen, sogar auch Bahnlinien, innerhalb von Flughafen-Arealen erfasst sind, die keinerlei Zugangsbeschränkungen, z.B. access=no", "access=private", bekommen haben. Das betrifft vor allem "highway=service". Ich selektiere alle "highway=service", die mit Einschränkungen versehen sind, vorab für die weitere Bearbeitung aus. Es bleiben dann natürlich die unerwünschten "Rest-Konstellationen" wie hier übrig. Ich habe nur die Wahl, die Klasse "highway=service" komplett außen vor zu lassen, oder mit Fehlkonstellationen auf dem ein, oder anderen Airport zu leben. Vielleicht können wir ja ein Projekt starten, um betroffene Airports zu lokalisieren und dann in OSM die betreffenden Ways zusätzlich z.B. mit dem Tag "access=private" ausstatten. So würde sich diese Auffälligkeiten im Laufe der Zeit, sprich mit jedem network-Update, reduzieren.   Edit: Wobei EDWS erledigt ist
    • You are not making any sense.  Are you saying that you planned a flight KATL-KMGM and the FMC loaded KATL-KCLT?  Take pictures of your simbrief plan and then what the EFB and FMC say.  I just planned KATL-KMGM and loaded it into the CRJ with no problem.  Ditto KATL-KCLT.  The only reason this could happen is if you last flew KATL-KCLT and then somehow the EFB is not loading the KATL-KMGM flightplan, most probably do to some issue with your simbrief username.     Whatever is causing this is not something that can be fixed by Aerosoft.  It is an issue on your system. 
    • Da ist jetzt wohl der / die Entwickler am Zug. Bin gespannt.
    • I'm having some trouble with the FMC when adding STARs and APPs in flight.   I'm using a few of the AI ATCs instead of the MSFS2024 ATC, one of the "immersion" options there is that, if the destination weather changes from the time the flightplan was filed, the STAR and APP that get assigned also can change.   While enroute, I'm given a STAR. At this point, my typical workflow is: Check the charts to see which runways are potential destinations. Select the STAR from the FMC menu. Since the FMC won't add the waypoints unless I pick an APP, if my original runway isn't one of those serviced by the STAR, pick an APP from those that are serviced. ATC hasn't told me which approach I'll be using yet, so I don't know for sure.     Later, usually while flying the STAR, ATC will assign an APP. At this point, all hell breaks loose. Going to the FMC menu to add or change the APP or transition causes, seemingly at random, some or all of these effects: The STAR and APP are added again at the end of the existing STAR, with no knowledge of my current progress along the STAR. The old APP isn't always completely cleared, leading to waypoints in the LEGS display that aren't even part of the (final) STAR or APP. Advisory VNAV completely breaks, because it doesn't read your current altitude and (as near as I can tell) thinks the Cruise Altitude is now 0, meaning the first waypoint becomes a "CLIMB" waypoint.   I can't imagine this is how real life pilots juggle this? If it is, I'd love to know their workflow to prevent them from wildly swinging the plane back and forth in a desperate attempt to recapture STAR and APP legs and glideslopes.
    • The flight plan is originated in sim brief. I sent it from the EFB to the FMC. It always does it KATL-KMGM and now it's doing it KATL-KCLT
    • Thank you for the feedback. Have fun flights.
    • wird gemacht...ich sehe du hast schon bei meinem Thread auf x-Plane.org Fotos geposted. Kannst du noch die Linux Distri dazu schreiben?
  • Popular Contributors

  • Forum Statistics

    • Total Topics
      121.5k
    • Total Posts
      839.9k
  • Files

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use