To make most of FPV Combat system, it is recommended to use combat OSD (Pins: MSP for digital and OSD for analog).
With OSD you can see your lives, ammo, score, easily configure different settings via menu.

Note: There two other ways to configure FPV Combat board settings: Desktop companion and Gadget.

Font (character map) in analog case is flashed to onboard OSD chip and can't be changed.

In digital case, OSD is implemented via MSP DisplayPort extension.
As of now, FPV Combat system supports: WTFOS, Walksnail and HDZero.
Support for DJI Goggles 2 and Integra may come later.

You need FPV Combat board V2.6 (HW2.6) for Digital OSD to work (only this board has dedicated MSP pins).

Basic Digital OSD works out-of-the-box. We are limited to letters and numbers in this case, no nice icons are displayed.
Nicer OSD with colourful icons, shooting traces, etc can be enabled in INTERFACE submenu.

Fonts are handled differently on different digital FPV video systems.

• WTFOS (rooted DJI V1/V2 goggles) uses set of .bin files;
• Walksnail uses "tall" 36x27648 .png files;
• HDZero uses 576x1728 .bmp files for 1080px "FHD" camera resolution and 486x1350 for other camera "HD" resolutions.

We created digital-fonts-tools to help with digital fonts handling and conversion. The tools can be used to inject FPV Combat icons into any digital font, please see FPVCombat example in linked repository.

We opted to have two sets of combat icons: Short and Full.
Consequently, two versions of fonts can be generated.

FPV Combat firmware expects our icons are situated in the end of the font address space, to minimise impact on existing characters. Short version of the combat font overwrites last three rows of original font. Full version occupies more space.

In FPV Combat OSD menu you can then choose which icons combat firmware shall try to use: Short or Full.

Short version of FPV Combat font does not overwrite any characters, even in INAV case! So you can use the same combat font with non-combat models what use BetaFlight, INAV, etc OSD w/o need to switch font in your goggles! Full font does overwrites some minor INAV characters.

Since digital fonts are basically images, feel free to edit our example font for your taste. Make nicer icons, bundle them in your font version and share with the community!

Download example fonts for your system from digital-fonts-tools repository (link above) or make your own!

Copy four .bin files to the root of SD card that you insert into goggles later.
If you use flight controller together with combat board (msp pass through), you need to add respective designators to the file names.

Example: font_inav_hd.bin would be one of 4 files renamed from original font_hd.bin

Custom fonts must be placed in "userfont" directory on the SD card.
Do not forget to sync font_update.ini file with eventual changes you made.
In goggles, you must load/update custom fonts via goggles menu and then choose one of installed custom fonts.

Steps below assume you use MSP pass-through with INAV flight controller

First you decide about whether to use the Short or Full combat font set, as explained further up on this wiki page.
Then, depending on your FPV camera resolution mode, you will need either a HD (720px) or FHD ("Full HD" 1080px) version of the desired combat font set. If you will alter between HD and FHD camera resolution then you will need both sets.

On the goggles SD card, using a computer, copy the desired combat font file to your goggle SD card.
The path is resource/OSD/FC/

If the path does not exist, please create it.

Note: As per today we lack a ready to download HD combat font for HDZero, but the FHD font is available and works well.

Now rename the file on the SD card:

• HD font file: INAV_000.bmp
• FHD font file: INAV_FHD_000.bmp

Insert the SD card into the goggles and restart.

Note 1: As far as we know, only two HDZero camera models are able to produce FHD (1080p) today: Micro 2 and Micro 3 (produced by Runcam). All other cameras are non FHD.

Note 2: What fonts you select in INAV Configurator OSD tab has no effect on which font you will see in the goggles. But you can still modify the INAV OSD layouts in order to avoid conflicts with the combat OSD fields.

Note 3: In order for the Combat board to know what combat font set you decided on, you need to enter the combat configuration menu / display / and select Full or Short combat font – corresponding to what file you put on the goggles SD card.

Using HDZero combat fonts without INAV will be different and how to do this is still work in progress. Wiki will be updated when there is such an instruction established.

Short FPV Combat font, limited set of icons overlayed on SneakyFPV font	Full FPV Combat font, full set of icons overlayed on SneakyFPV font