Richard,
Interesting this looks like it has all the packages still even though they’ve been removed.
Content.xml (162.1 KB)
Content.xml (162.1 KB)
Sorry let me add the system info.
I’m running the MSFS Store version, should be 5.1 or 5.2 whichever one they just released. In the marketplace I have all of my add ons disable that are scenery currently as requested to clear the community folder so it’s down to just Navigraph and the aircraft. Aircraft active right now (most are turned off due to add on linker) are the PMDG 737/777s, the Fenix package, and the iFly 737. Mostly cause those install direct to community folder.
All other scenery (both mp and add on linker installed) are turned off right now at the suggestion of Navigraph. This issue persists across all working title aircraft that use Garmin suites, both the G1000 and the G3000, the Longitude, etc.
Interestingly enough because the Content.xml (which weirdly saves one folder down in my xbox user name folder compared to places online expects me to find it) was out of date I deleted it to let it regenerate and use the correct values on startup (seen attached) and the problem persists.
Everything loads in fine but sends me straight to DPK. Trying to direct to another navaid does not actually draw a track to the fix requested.
Weirdly it does still feel contained to stuff around the Northeast. I loaded up at SFO (forgive the darkness) but everything is working fine there?
Interestingly enough I spawn up at KBED and try to go the other direction to KTTN and I get the forever importing issue.
Aha! Interestingly I tried a different simbrief profile (Random like the E175) and DID get KBED to KTTN to import correctly but it deletes the intermittent points of the airway.
KTTN - KBED imported as a different profile
(fast forwarded me halfway down the STAR so thought it might be a proximity issue)
So now with a different profile I load up and everything is fine! So not clear why the same problem deletes have the airway southwest bound but works Northeast bound
I guess it’s in the profile? Which makes no sense to me. That’s an easy fix, but it is woefully inconsistent…because it did not load the Q167 airway for me in the other direction. Was missing the fixes BUZRD-NESTT-GRONC-ALBOW-ORCHA-HOFFI
Hi Sean,
What do you mean by “other profile” in SimBrief? Do you mean you used another airframe/aircraft, or what do you mean by it?
What have you used before? Is it possible for me to reproduce it too when I use your settings?
Cheers
Richard
I was using FSReborn’s custom profile from their discord to create and generate flights, when I tried to import TTN-BED I was having issues. Changed it to the default Simbrief profile or literally ANY random aircraft and it partially worked. The default SB or default FSR profile allowed me to import and fly the route no issues.
HOWEVER I was still having issues with other aircraft on import still in the NE USA, where I shared the photo that the default Phenom 300 profile did not still import the Q167 airway… even on the default or different aircraft profile.
So I fixed TTN-BED temporarily with a different aircraft profile, but still some wonkiness for me with flights into or out of the Northeast.
Hi Sean,
Thanks, will test it, but did I understand you correctly that when you use another aircraft profile, you can import the flightplan?
I will inform the SimBrief team to check the profile.
Cheers
Rich
It’s very intermittent. Like right now on the above example I’m using the default profile and NOTHING works. I have to enter the end of each airway manually.
I’ve tried this on Phenom profile, 737 profile, E175 profile, won’t even import with that Q167 airway. Same problem I was having out of boston.
Sean
Hi Sean,
Thanks for the details. I have spoken with the Simbrief team, and it is very unlikely that this has anything to do with the profile itself, buuut… It looks a little strange that these missing waypoints are in the TOC/TOD. Therefore, we have involved another team to analyze this as well.
I still can’t promise anything, as no one on our team can reproduce it, but I want to let you know we are still working to identify the issue. It’s essential not only for you, but also for us 
Thanks again for your patience and your help in this case
Richard
Thank you Richard! The inconsistency of me to other users is bizzare, so I understand it’s an edge case for you. It has been a frustrating few days of trying to fly after work but I’m sure you’re on it!
Have a great weekend!