Fix issue with DJI O3 showing miles instead of kFt

[MrD-RC]

Fixes #9005

Tested on other systems via HITL. All fine. Should be tested by someone with the O3 system for final confirmation.

[prelator]

Looks like this corrects it to give altitude in thousands of feet. While better, would it be possible to just always give altitude in feet without decimals, like INAV 6.0 does?

[MrD-RC]

Looks like this corrects it to give altitude in thousands of feet. While better, would it be possible to just always give altitude in feet without decimals, like INAV 6.0 does?

INAV 6 doesn't do that. Altitude has always been kFt. If 6.0 showed something different, it was because of this bug. The altitude has space only for 3 digits. Which is why kFt is used.

[mmosca]

@MrD-RC I will try to test this later this week, but it is possible to verify BF*COMPAT behavior with Walksnail in case you ever want to verify behavior with your hardware.

Just pick BFHDCOMPAT as OSD type and manually set the FC type to Betaflight in the goggles menu. This will tell the goggles to use the BF font, which is exactly what DJI does.

[MrD-RC]

@MrD-RC I will try to test this later this week, but it is possible to verify BF*COMPAT behavior with Walksnail in case you ever want to verify behavior with your hardware.

Just pick BFHDCOMPAT as OSD type and manually set the FC type to Betaflight in the goggles menu. This will tell the goggles to use the BF font, which is exactly what DJI does.

I don't really want to infect the Walksnail stuff with anything DJI. They may stop working in disgust 😉

Great tip though 👍🏻

[mmosca]

I can confirm it will show 1.XX above 1000ft. Tested on o3 + v2 w/hitl

[MrD-RC]

Thanks @mmosca

ready to merge in that case.