I recently was flying from GCLP to GMML trying to use waypoint D119W and COSTI. I had the latest AIRAC in MSFS 2024. On using Simbrief in the EFB to import the flight plan D119W came up as a GPS coordinate not a waypoint and did not load correctly at all in the G1000, either for the C182T or the C172. I have attached images of both. I tried a similar thing with the GOPIM waypoint and that did not load correctly either, though I could get it to work when I unloaded the Navigraph AIRAC. COSTI worked consistently. Is this a bug, as I would think loading the AIRAC should allow all waypoints shown and selectable in Simbrief or Charts to make it into flight plans imported into MSFS2024, and hence the G1000. Currently I have unloaded the AIRAC as it just seem easier to use the MSFS default and keep Charts for flight tracking and the Jeppesen plates.
Hello!
This sounds related to the known issue we’re currently dealing with: the simulator’s inability to handle an explicit order of the navigation data packages we provide. You can read more about the situation in this topic (among many others):
While Asobo is figuring this out, feel free to try our workaround to see if that helps your case!
Kind Regards,
Malte
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
Hello again!
The release of SU2 included improvements to how the simulator handles packages that do not follow the specification. In addition, our AIRAC is now considered stable, and we do not expect any issues while using it.
Are you still experiencing the same problem?
Kind Regards,
Malte
Hi,
I gave this a quick test just now. I repeated this flight plan in Simbrief with both the GOPIM and D119W waypoints. Neither loaded correctly on import into either the in game MSFS 2024 flight planner or the G1000 in the CT182T. On the flight planner they both showed as geo coordinate waypoints, in the G1000 they came up as a strange description. Interestingly I could delete the incorrect entries for both intended waypoints in the MSFS 2024 in game flight planner and the G1000, then add the intended waypoints (GOPIM and D119W) manually in both correctly. I could also correct them in the in game MSFS 2024 flight panner and load correctly to the G1000.
Thank you for testing again!
I can reproduce. Upon initial investigation, this seems to be caused by us providing insufficient data when trying to find these terminal waypoints. To load them correctly, MSFS requires us to specify the related airport.
We will investigate how to make this happen. I’ll let you know when we have an update!
Thanks happy to test again once you have something.
Hello again!
Please try this build to see if it works for you. It is important that you generate a new flight before trying this out, as SimBrief has been updated and the changes will only apply to new flightplans!
navigraph-efb-simbriefapp.zip (175.3 KB)
These are the results that I got:
Thanks, just tested this and found the following. The flight plan is as below and as shown in the image Simbrief GOPIM COSTI. This was generated for this test:
GCLP/03L N0137F050 DCT GOPIM DCT COSTI DCT GMML/02
-
With the new Simbrief installation the GOPIM waypoint now showed correctly in the MSFS2024 planner as well as the G1000 when sent to avionics. The COSTI waypoint however now shows as a geo coordinate in the planner and a strange value in the G1000. This is the reverse of the prior behavior.
-
I loaded back the original Simbrief EFB component and the behavior reverted to its prior state, that is GOPIM showed as a geo coordinate and COSTI was correct in the planner and the G1000 when sending to avionics.
I have uploaded images of all of the above. Please let me know if I can clarify anything else.
Apologies, this is another mistake on our side. Please try this version instead:
navigraph-efb-simbriefapp.zip (175.3 KB)
Hi,
I tested with the GOPIM and COSTI waypoints, plus the D119W and COSTI waypoints, see attached Simbrief screen captures. In both situations the newly generated flight loaded into the MSFS2024 in game flight planner correctly. On sending to ATC and sending to avionics, they also loaded into the G1000 correctly on launching the flight. Thanks for the fix.
Cool, thank you for the confirmation! We’ll have this released in an update soon.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.