Repository navigation
FAQ and Troubleshooting
Stuck on something? Find it below. Jump to a section:
📻 Radio & Widget · 📡 Map Downloader · 🛫 Flight Path Viewer · 📺 On the stream · 🔒 General
The widget writes the reason right on the tiles:
- 🟥 Red, "No Tiles Found" → there's no map on the SD card for this spot at this zoom. Either you never downloaded this area, or you've zoomed in past what you grabbed. Fix: get the area with the Map Downloader, or zoom back to a level you have.
- 🟦 Blue, "Loading" → the tiles are on the card and being read in. It clears in a second.
Double-check the folders actually landed as MAPS/<type>/<zoom>/<x>/<y>.png on the card, and that you rebooted after copying main.lua.
If a tile sticks on Loading and never turns into imagery, that PNG is probably corrupt (a half-finished copy to the SD card is the usual culprit). Re-download the area and copy it over again. A slow SD card can also make it linger a moment longer than usual — no drama unless it never resolves.
Update to the latest main.lua — the newer build keeps retrying to read the name for the first few seconds instead of giving up. If it still shows "MODEL" after that, your EdgeTX build just doesn't hand the model name to widgets, and there's nothing the script can do about it. Everything else works regardless.
Your flight controller is almost certainly sending attitude in radians. Open the menu → Attitude: DEG/RAD and flip it. Still flat afterwards? Then the pitch/roll sensors aren't coming through over telemetry at all — check your sensor discovery on the EdgeTX telemetry screen.
Yep 👍. Menu → Zoom knob → pick a pot, slider or channel (S1, S2, LS, RS, or a CH). That knob now sets the zoom across the map's range. OFF puts it back to rotary-only. The rotary keeps working in between knob moves either way.
After updating the Map Downloader, you have to regenerate main.lua, copy it into WIDGETS/SatMap/ on the card, and reboot the radio. Tiles you can swap without a reboot; the script you can't.
Yes. 🎉 Everything you set in the menu — page, map type, zoom, zoom knob, graph channels, HUD, attitude DEG/RAD and the rest — is saved to MAPS/satmap.cfg on the SD card and comes back on the next boot. Set it up once and forget it. The only way it won't stick is if there's no SD card or the card is write-protected.
EdgeTX 2.10.x on colour radios — TX16S and similar. It's laid out for the colour screen; the smaller mono-screen radios aren't supported.
↩︎ back to the SatMap Widget page
You've almost certainly picked too big a radius at too high a zoom — tile count explodes as you zoom in. 🧮 Drop the top zoom level by one, or shrink the radius, and it'll fly. For everyday flying, 13–16 over a modest radius is plenty. Also: OpenTopoMap and OpenAIP throttle harder than satellite, so a big topo pull is just slower by nature.
That's CORS — some tile servers (OpenTopoMap, OpenAIP) block browser requests unless you're on the real site. Esri satellite works anywhere. If a type comes up empty in a local test, try it from the live site, and make sure you've entered your OpenAIP key for the Airspace layer.
Writing straight to the card only works on Chrome or Edge (it uses the File System Access API), and you have to click through the folder-permission prompt. On any other browser, or if you'd rather not grant that, just take the ZIP and unzip it onto the card yourself — same result.
↩︎ back to the Map Downloader page
You need logging turned on before you fly:
- 📄 EdgeTX CSV → set up a Logical Switch (or SD logging) that writes telemetry to the card while armed. The files land in the
LOGS/folder on the radio's SD card, named per model and date. - 🪵 Blackbox → INAV/Betaflight logging has to be enabled in the FC (Blackbox tab), logging to onboard flash or an SD card, and then you pull the
.bbl/.bfl/.txtoff it.
No GPS in the log = no map, so make sure GPS is actually being logged too. 🛰️
Totally normal, two usual causes:
- The log started before GPS altitude settled, so the first points sit at a weird height until it locks in.
- GPS altitude is MSL (height above sea level), not height above the ground — so a field that's 300 m above sea level shows the whole flight "floating" at +300 m.
Nothing's broken — it's just where the numbers start. Scrub past the first few seconds and it sorts itself out.
Most BF logs work fine. One rare encoding (a variable-length variant) isn't decoded, and those logs will stop with a clear message rather than failing silently. INAV logs are the better-supported path if you have the choice.
No. 🙅 The viewer decodes everything in your browser — there's no server to send it to. Close the tab and it's gone.
A 30-minute-plus log can take 10–15 seconds to decode, because your browser is doing the whole thing locally. There's a spinner — just give it a moment. ⏳
↩︎ back to the Flight Path Viewer page
The overlay only has something to show while I'm actually flying.
Those are Twitch features that only switch on once a channel hits Affiliate. When the channel qualifies they show up on their own — nothing you need to do. The chatbot and the drop game run either way. 🎮
Type !drop in chat and a little parachutist comes down toward a target — land on the bullseye for the most points, dodge the odd hazard, and climb the leaderboard. !drophelp lists the commands, !leaderboard shows the standings. There's a bit more about it on the Behind the Stream page. 🎯
Oh. Oh no. You actually asked. 😬
Nobody who's learned the real meaning has made it to the next stream. The regulars go quiet in chat, one by one. My drones have started arming themselves at 3:47 AM and flying the exact same heading — out past the treeline, toward something I've stopped trying to name. That cold draft on the back of your neck right now? Normal. Do not scroll down to the gallery. Whatever you do, do not count the aircraft in the gallery. 🩸
…
…okay, okay 😄 — it's aviation phonetics, it just sounds cool over a crackly radio, and you are 100% safe. Mostly. Welcome to Tango Kilo. 📻
The live overlay is wired into my streaming setup, so it's not a plug-and-play thing to point at your own plane. The tools, though, are here for any EdgeTX pilot: the Flight Path Viewer, the Map Downloader and the SatMap Widget all work on their own with nothing but your radio and an SD card. 🛠️
Easiest is to just say it in the Twitch chat while I'm live — that's where most of the good ideas come from anyway. 💬 If you're the GitHub type, opening an issue on the repo works too. No promises on everything, but I do read them. 🙂