> For the complete documentation index, see [llms.txt](https://sneaky-fpv.gitbook.io/hd-osd-and-tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sneaky-fpv.gitbook.io/hd-osd-and-tools/fonts/walksnail.md).

# Walksnail

Walksnail custom fonts are stored on the ground side (goggles/VRX) SD card within a folder called `/userfont`.

The Walksnail Avatar system can transmit 3 resolutions.  1080p, 720p and 540p. As 540p transmission actually uses the 720p font file for the OSD display, we only need to be concerned with 2 resolution possibilities.  1080p and 720p.

The userfont folder should contain at least 3 files:

1. font\_update.ini
2. a font file for 720p display resolution
3. a font file for 1080p display resolution

This is a minimum requirement to be able to activate a custom font for display.

## Font\_update.ini

The font\_update.ini contains parameters that tell the Walksnail goggles/VRX information about the font files to assist in how and when to use the custom font.

Below is an example of a userfont folder that contains 2 fonts:

<div align="left"><figure><img src="/files/dUUTZnkoYNxEMup8ahCE" alt=""><figcaption></figcaption></figure></div>

### \[config]

The config section states the name of all fonts as you wish it to be shown in the goggle/VRX menu selection and the order of which they are shown in. 16 unique entries (font names) are possible.

\[config]&#x20;

1=*fontname1*&#x20;

2=*fontname2*

count=2

### \[*font\_name*]

<mark style="background-color:yellow;">Each font name must match with a font name listed in the config section above.</mark>

<mark style="background-color:yellow;">Each section that begins with a \[font\_name] contains parameters pertinent to that font.</mark>

**fcid** is intended for future use and currently ignored.  Its intended use is to allow automatic selection of custom font dependent on the flight control FW of the flight controller the VTX is connected to.

**font\_width\_720** is the width in pixels of a single glyph in the 720p font.

**font\_height\_720** is the height in pixels of a single glyph in the 720p font.

**font\_width\_1080** is the width in pixels of a single glyph in the 1080p font.

**font\_height\_1080** is the height in pixels of a single glyph in the 1080p font.

**imgname\_720** is the font file png of the 720p font.

**imgname\_1080** is the font file png of the 1080p font.

**x\_offset** is the amount of offset in pixels from the left edge of the display the OSD will begin from.

**y\_offset** is the amount of offset in pixels from the top edge of the display the OSD will begin from.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sneaky-fpv.gitbook.io/hd-osd-and-tools/fonts/walksnail.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.