I set up a plan in the SB Dispatch plugin for MSFS2024. It shows up in the EFB and seems to work okay. However, when I click on Import route it only loads the Dep and Arr into my G3000. None of the waypoints are loaded. Bug?
I am having a similar problem in default 2024 A321 aircraft (I have not tried others but presume all affected). After generating a flightplan, it says flightplan imported and loaded into sim, but when trying to import the plan into the flightdeck EFB it doesnt load, as continually says ‘SimBrief Plan Requested’.
In MSFS 2024 A321-251N, I just edited and generated a flight in EFB SimBrief.
In the MCDU, I used INIT REQUEST to enter the plan. The Inibuilds A321-251N doesn’t support IMPORT PLAN directly into MCDU.
In Navigraph Hub, please try installing SimBrief EFB App v1.0.0-beta.1, restart machine, and try again. If still an issue please post SimBrief Route.
Please post a picture of your plan in the default planner after importing from SimBrief.
Cheers
Ian
@tuptup61 Are you still having this issue?
Here is what the import looks like for me using the latest SimBrief EFB application and the Vision jet:
What other addons do you have installed? Are you using our beta AIRAC package?
Kind Regards,
Malte
Sorry for reviving this, but I am also encountering this issue with the 737 MAX and the EFB plugin.
Here’s the route: VVNB/11R K0863F360 NAH3A NAH Q1 DOVIN DALA2J VVTS/25L
The entirely of the waypoints from NAH to DOVIN are all removed, which is very weird. Any ideas what’s going on? My guess is that it has something to do with this bug: [Facilities] SEARCH_BY_IDENT Behaviour Change/Compatibility Break - HTML/JS - MSFS DevSupport since I encountered it too in FlyByWire aircraft.
Hello!
Your issue is different. This is the expected output, based on what WT has asked us to do in order for their EFB to work correctly.
References:
-
WASM fsPlannedRouteGetEfbRoute returns VIA field not to spec - WASM - MSFS DevSupport
-
Follow-up discussion in the WT Discord server - happy scrolling!
In essence:
All waypoints following NAH are on the same airway. Only the first (LAH) and last (DOVIN) are included. Additionally, since DOVIN is the transition for the procedure, the waypoint is not added to the route. As far as I understand, this is what WT has asked us to do.
This also seems to be working correctly, based on what is seen in the EFB:
I have asked WT about this particular situation. If we can make changes to improve the situation, we will. But it is not related to the original question in this topic.
Hello again @tuptup61 !
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 problems mentioned in your first post?
Kind Regards,
Malte