Update on this thread?

Hi all, my previous thread was closed while waiting for a reply — can I get an update?

Hi,
No, sorry, we can´t reproduce your issue. We have discussed this internally with SimBrief and our Sim-Dev team, but neither has a clear idea. Have you tried that with our G1000/3000 plugins too? Because the plugins can also handle the TOD/TOC waypoints.

The TOD/TOC waypoints are the main thing because it changes when you change the aircraft/profile. But anyway, as I wrote, we don´t see any issues with the plugins or the SimBrief profiles, and no one on the team can reproduce this. I´m also at the end of my knowledge here, sorry.

Cheers,
Richard

Richard,

Surely the solution can’t be, we can’t reproduce it so good luck.

I use all of your plug ins and keep the navdata up to date. It seriously is only in and around the Northeast area as I experienced again last night. Other parts of the country or other routes have been fine. I don’t know what that could be but please do not leave me as a customer for over 10 years with:

“I’ve reached the end of my knowledge, good luck”

Sean

Sean,
I know this is not what you expect to hear, and I know it’s frustrating (for us, too, because we would help when we know where). Possibly someone on our team still has other ideas…

Personally (and honestly, you confirm my assumption with your last posting), I guess this has something to do with a 3rd-party package on your system (in the community folder). Are you able to do this test? Please follow these steps exactly!

  1. Rename your community folder
  2. Start the sim → close the sim
  3. Open the Navigraph Hub and install the AIRAC and all plugins you need
  4. Start the sim again and try the flightplan in the stock Cessna Citation Longitude with the G3000

What is the result?

Cheers,
Richard

Richard,

We did this previously if you look at the other thread. I had my entire community folder empty except for airplanes and navdata and could still produce the same issue.

It does not seem like a scenery issue but rather maybe something with the file that handles NAVAIDS in that area especially where it’s not just BED or BOS but even MHT or other airports in the Northeast.

Sean

Ok, Sean, then I hope someone else on our team has a better idea. I have removed the auto-close feature from this thread… sorry.

Cheers,
Richard

PS: The strange thing in your previous test was that there were still a few 3rd-party packages (I don´t really talk only from sceneries) in the content file. Therefore, my idea is to rename the complete community folder, but anyway - thanks that you have tried it in the past.

Hi All,

Even after a clean install of MSFS2024 and only the navigraph nav data in the folder this issue persists with any G1000/3000/5x aircraft. Please advise of a solution. I have lost a month of flying and as a subscription customer I’m starting to become very frustrated.

Sean

Is there a way that we can look at your system via remote connection?

I can´t reproduce your issue, and we don´t see any other reports here in the forum or in our ticket system about this issue. It seems we have the same initial point now; it works on my system but not on yours.

You have reinstalled your MSFS2024, use our packages only (no other 3rd-party packages installed), and the MSFS stock G1000/3000 (no 3rd-party add-on used) is working here, not on your system. I guess, we have no other possibility but to look directly at your system.

Cheers,
Richard