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?

Recentering the MFD display to anything other than the aircraft position is non-functional.   Hitting LSK4 to center on a waypoint always causes a NOT FOUND caution message.  

Please login to display this image.

Thanks for the Help. Everthing works perfectly. And the Link is verry good.  

Hallo Ron, dein Thema hat mich jetzt auch neugierig gemacht. Ich denke, die NavigraphData ist richtig installiert.

Please login to display this image.

  Ich konnte bei einem Anflug einer aeroflot auf EDDL auch keine STAR erkennen.   Vielleicht kannst mal Screenshots bei einem Windows vom Anflug machen. Incl. NavigraphDATA Screenshot und einmal von Linux und das dann im Forum von WorldTraffic veröffentlichen.   Ich denke, der Vergleich macht das Problem offensichtlicher.    

Please login to display this image.

 

Please login to display this image.

 

Please login to display this image.

 

Importing from what?  How are you importing?  I have not seen this problem and if you did a search and came up with nothing, that tells me that few, if any others are seeing this.  Logically, this would probably be a local problem with a local fix.    99% of all sim problems are local problems.