search

hd-zero / hdzero-osd-font-library

Share the osd font library you made or get your favorite.
26 stars 18 forks source link

INAV OSD file doesn't work #15

Closed DanO83 closed 1 year ago

DanO83 commented 1 year ago

the INAV OSD file doesn't work, I have made a Resource directory on my sdcard and copied the file to this directory. Then renamed it to FC_VARIANT.bmp.

The OSD was the same as without the bmp file.

Did anyone tested these files ?

lesharodin commented 1 year ago

You need rename it to INAV6.bmp or INAV5.bmp

DanO83 commented 1 year ago

I have just tried that, but still no change. Also if this is the the way files should be named maybe someone can change the instructions to make it better understandable.

DanO83 commented 1 year ago

I also noticed that the layout of the bmp image files are very different then the betaflight files. Shouldn't they be more alike ?

ligenxxxx commented 1 year ago

It should be renamed "INAV.bmp".

ondrascz commented 1 year ago

There are two options of the glyph spacing in the bmp. 0px and 6px. You can chose any of them for any fc variant.

DanO83 commented 1 year ago

I have changed the file name to "INAV.bmp", now it's working fine.

There is another issue, I have to go to the menu first to make the new OSD fonts active. But that's probably a firmware issue with the VRX4. This is already reported

ondrascz commented 1 year ago

VRX4 doesn't have this issue (at least mine doesn't). It's reported for ShaBy VRX

DanO83 commented 1 year ago

I have a VRX4 on firmware 40.2A.4C, and it has this issue. I have to go to the menu and back first see the new fonts

ondrascz commented 1 year ago

That is weird. I have the same. The custom font is always loaded during a boot. No need to enter the menu. A few thing come to my mind:

DanO83 commented 1 year ago

I tried to boot it with a selected channel and I tried booting with auto scan.

Also I tried powering the vtx first (then wait a few seconds) then the vrx and the other way around.

Also tried reformatting the sd card in the vtx

nothing helps, I still need to go into the menu to activate the fonts.

ondrascz commented 1 year ago

I assume you have only INAV.bmp file in the resource folder. Did you try to copy BTFL.bmp there also?

DanO83 commented 1 year ago

I tried to also copy a BTFL.bmp file to the sdcard. This is clearing up things.

Now it looks like the BTFL.bmp is loaded when powering up the vrx. It shows a different osd then stock, but it's a bit messed up with parts of the betaflight logo showing. When I go to the menu and back the INAV.bmp is showing.

so to work around having to go to the menu to get the right osd fonts I have copied the INAV.bmp to the BTFL.bmp file so there both contains the inav font file.

There must be something wrong with the vrx firmware, it probably looks for a BTFL.bmp file at boot

ondrascz commented 1 year ago

The messed up BF logo is probably caused by the fact you are not using BF 4.4.0 and HD OSD

DanO83 commented 1 year ago

Yes i know that the osd is messed up because i'm not using betaflight at all, i'm only using inav. but it shows how the vrx firmware always wanting to use the BTFL.bmp at startup, no matter if there is an INAV.bmp present in de Resource directory