You’re right – Yesterday I designed a test-case route from EGKK to LGAV using LNM, including SID & STAR, and also the starting point: Gate 21. The plan contained a mixture of usual GPS waypoints and VOR navaids.
I saved that (from LNM) as a .PLN file
I also used LNM’s send to Simbrief function – which transmits it directly to my Simbrief [basic] account.
I switched over to Simbrief in the web browser which told me that the plan it received from LNM was all ok – even the SID, STAR and en-route VORs.
From Simbrief I generated the Operational Flight Plan (OFP) and also exported as a PLN file for FS2020’s ATC (and also to compare with the LNM-generated .PLN file).
Next I headed over to the World Map in FS2020 and loaded the .PLN file that Simbrief had produced. All looked good, Runway, SID & STAR all correct. I then selected Gate 21.
(I also selected the FBW A32NX - Experimental version).
Once inside the cockpit parked at the gate, and even before I activated the FlyPad EFB, I noticed that the route was already correctly loaded into the MCDU & Nav display! (ie from the World Map).
In the MCDU I removed two discontinuities – which is normal for the A320 Family.
So it looks like FBW has fixed the World Map MCDU glitch at last: ie you can now go straight from the World Map & .PLN file import to the cockpit of the FBW in the Experimental version. (no corruptions in the route waypoints & VORs – and no more loop-backs etc.) The arrival runway ILS frequency was also present in the Rad-Nav page.
When I did load up the FlyPad I entered my Simbrief pilot ID and it loaded the OFP. This was useful because I could auto-fuel-up the aircraft directly from the data in the OFP. ‘Data Init Request’ in the MCDU also fills in various fields directly from the Simbrief OFP.
Everything went perfectly after that. The ATC approved the route, the taxi guidance took me to the correct runway; I took off, went into autopilot ‘Managed-climb’ mode to FL390.
I then left my PC for two hours to go out for some dinner – leaving the sim running and the FBW’s autopilot solely in charge of the flight.
When I got back I could see from the recorded track in LNM that the aircraft obeyed all the VNAV constraints along the way up and had followed the route accurately along the way during my absence. Subsequently ATC advised me when to descend, and the aircraft obeyed all constraints on the way back down - to a smooth ILS-guided landing.
~ You can design your flight – any kind of route you like – using LittleNavMap and it works well both with Simbrief and the World Map.
~ A route entered on World Map (or imported from a .PLN file) now works directly with FBW A32NX’s MCDU.
~ LNM can send its flight plan directly to Simbrief; LNM can also retrieve your current flight plan directly from your Simbrief account.
~ For a quick flight in the FBW (Experimental version), you can just use the World Map and go from there straight into the cockpit, ie:
World Map>MCDU (for both ATC and MCDU)
Or to design a more interesting route:
LNM>World Map>MCDU (for both ATC and MCDU)
~ For planning all the fine details, to have a full OFP, you can use:
LNM>Simbrief>World Map (for the ATC)