After creating an LBS flight plan for the FsLabs A320, I download it and notice that the downloaded PDFs are indeed in LBS, except for the one saved in C:\Users\Public\Documents\FSLabs Data\Routes, which is still in KG!
In fact, when I check the OFP in the EFB, it’s in KG even though the selected option is LBS in SimBrief and the aircraft.
Would it be possible for you to provide the file corresponding to the requested option (LBS or KG)?
But…
I just noticed that if I initialize the flight plan via MCDU>>>ATSU>>>AOC Menu>>>INIT with the flight number, not only is the flight plan in LBS, but it is complete with all its pages.
On the other hand, if I initialize the FP via MCDU>>>Init, the FP will still be in KG and will only have 2 pages.
For me, the problem is solved as long as I have the choice. As for why, I haven’t quite figured it out…
The file that gets saved in C:\Users\Public\Documents\FSLabs Data\Routes is intentionally forced to KG, so this is normal.
For some background, FSLabs used to read this file when it uplinked the route and payload (at least in the Prepar3D versions from a few years ago). For this to work properly, the file needed to always be in KG, and the FSLabs would take care of converting the units into LBS as required after importing.
We can’t update this file to LBS as this would break compatibility with older P3D versions of the FSLabs, which many users still rely on. The file was never meant to be viewed by the user, only used in the back-end.
Today’s add-ons (including current versions of the FSLabs) can instead download your OFP data directly from our servers (provided you have entered your SimBrief username). It seems that downloading the file into C:\Users\Public\Documents\FSLabs Data\Routes might still work, perhaps as a workaround for users who don’t want to enter their SimBrief username, but this is an outdated method that results in the issues you’ve described.
My guess is when you initialize through the MCDU>>>Init page, you are simply reading the raw file, which is why it always shows in KG and only shows an abbreviated flight plan in the EFB. However, when you initialize through MCDU>>>ATSU>>>AOC Menu>>>INIT, FSLabs is contacting our servers directly and downloading the full version of your flight plan with the correct units.
So basically, to summarize:
The file saved in C:\Users\Public\Documents\FSLabs Data\Routes is intentionally always in KG.
We can’t change that unfortunately, in order to maintain compatibility with older P3D versions.
While it is still possible to import using this file, this method is outdated and results in some issues.
The recommended way to import in the latest FSLabs aircraft is to always import through the ATSU, which will download your full OFP directly from our servers.
Thank you very much for your explanation. I understand why, and you’re right—there’s no need to change anything since there’s a solution.
Thank you again for your support.
