fix(mfd): add leading zeros to track display and altitude on F-PLN page

[bulenteroglu]

Fixes #9723

Summary of Changes

• Fixed track display formatting on MFD F-PLN page to show leading zeros for tracks between 000-099 degrees

  • Example: "45°" now displays as "045°"

• Fixed track display formatting on MFD F-PLN page to show leading zeros for an altitude below FL99

  • Example: "FL32" now displays as "FL032"

Screenshots (if necessary)

References

Additional context

Discord username (if different from GitHub):

Testing instructions

1. Create a new flight plan with:

   • Any departure/arrival airport pair
   • Cost Index: Any value
   • Cruise FL: Any value
   • Transition Altitude: Set to a low value (e.g., 3000ft or 5000ft)

2. On the MFD F-PLN page, verify:

   • Track values below 100° are displayed with leading zeros (e.g., "045°" instead of "45°")
   • Track values 100° and above display normally (e.g., "120°")

3. Verify altitude predictions:

   • Below FL100 should show leading zero (e.g., "FL089")
   • FL100 and above should display normally (e.g., "FL330")

How to download the PR for QA

Every new commit to this PR will cause new A32NX and A380X artifacts to be created, built, and uploaded.

1. Make sure you are signed in to GitHub
2. Click on the Checks tab on the PR
3. On the left side, find and click on the PR Build tab
4. Click on either flybywire-aircraft-a320-neo, flybywire-aircraft-a380-842 (4K) or flybywire-aircraft-a380-842 (8K) download link at the bottom of the page

[G-DRAW]

Is it possible to model the diagonal line going through all of the 0's, or is that a limitation?

[bulenteroglu]

Is it possible to model the diagonal line going through all of the 0's, or is that a limitation?

I have 0 clue I am afraid. Wouldn't be done in this PR anyway but I am not sure if its a limitation, or needs some sort of custom font to be done (Is there a open issue for that?)

[BravoMike99]

We already have the slashthrough font but it might not be in use on this page (@flogross89 might know) I believe. In any case, a github issue would be the way to go 👍

[flogross89]

We already have the slashthrough font but it might not be in use on this page (@flogross89 might know) I believe. In any case, a github issue would be the way to go 👍

Yep, we already have a font for it, it’s already used for InputFields for example. It should be as simple as replacing the Ecam font-face with the FBW-Display-EIS-A380-SlashedZero font-face, maybe you could give it a try for the F-PLN page fields.

[bulenteroglu]

We already have the slashthrough font but it might not be in use on this page (@flogross89 might know) I believe. In any case, a github issue would be the way to go 👍

Yep, we already have a font for it, it’s already used for InputFields for example. It should be as simple as replacing the Ecam font-face with the FBW-Display-EIS-A380-SlashedZero font-face, maybe you could give it a try for the F-PLN page fields.

Found it - @G-DRAW

I'll get an issue up if not already, then also get a PR for it

[BravoMike99]

Quality Assurance Tester Report

Discord Username : bruno_pt99
Object of testing : #9724
Aircraft : A380X
Tier of Testing : 1
Date : 17/01/2025

Testing Process:
Programmed a flight plan into the FMS.
Verified FL < 100 on the MFD page appear with leading zeros, FL >= 100 appear with 3 digits.
Verified TRK indications <100 appear with leading zero. Track values >= 100 appear with 3 digits.

Testing Results:
Passed

Media: