Spent way too long messing with capture cards and adapters before landing on a Pi 4 setup, so here's what I wish someone had told me on day one. Flash the image to a decent microSD card, not some old no-name one you found in a drawer. That alone caused me two failed boots and alot of pointless re-flashing before I figured out the card was the problem. Power matters more than people think. If the goggles are hanging off the Pi's USB-C port, that port is busy, so feed the Pi through the GPIO pins or PoE instead. I tried sharing power through a hub at first and got random dropouts that made me think the software was broken. It wasn't, it was just hungry. Do your first run wired over Ethernet, then play with the Wi-Fi hotspot once you know the basics work. Configure everything from the browser, no terminal needed, wich honestly surprised me. Once the feed shows up, HDMI out to a monitor for spectators and pull the same stream into OBS on the laptop for recording or YouTube. Test the whole chain at home before you take it to a field, saves you from debugging in the wind with an impatient pilot waiting.
How I finally got my goggle feed onto a big screen and into OBS, steps that actually worked
Oct 12, 2026
Last reply: 7 hours ago
4 Replies
First reply
I run a similar setup on an older Pi I had in a drawer, mostly for showing local flights at our club meetups. The card thing bit me too, a cheap three pack of no-name cards started throwing read errors after a couple of sessions and I nearly gave up before swapping in a…
Read the full replyI run a similar setup on an older Pi I had in a drawer, mostly for showing local flights at our club meetups. The card thing bit me too, a cheap three pack of no-name cards started throwing read errors after a couple of sessions and I nearly gave up before swapping in a SanDisk. Been solid for over a year now. On power I went a slightly diffrent way. I feed mine from a small power bank rated for the Pi and keep the USB ports free for data only. When I tried sharing a hub between the Pi and my capture stick the feed stuttered every time the goggles pulled a burst of current. Separating them fixed it in one go. Wi-Fi hotspot works for me now but only after I turned off power saving on the wireless interface. The stream would freeze for a second whenever the radio dozed off, and it took me about a week of blaming the software before I found the setting. I record straight on the Pi instead of pulling it into a laptop, one less thing to carry to the field. Storage fills up fast at that bitrate so I offload clips after every session, otherwise I end up deleting stuff I wanted to keep.
Latency is the thing I'd check before trusting it with a fast pilot. I run the AV for our club's demo days and anything past about a tenth of a second of delay makes proximity flying feel sketchy on the spectator screen even when the pilot is fine. Easy test is hover over a fixed spot and compare the feed against what you actually see, you can eyeball the lag in a minute. For people just watching at a picnic table it hardly matters though.
Mine lives in a little case zip-tied to the leg of my folding table and heat caught me out at a summer fly-in. Ran fine on the bench, then an hour in direct sun it started dropping frames and I spent ages checking cables before realizing the thing was just cooking. A bit of shade over it and it behaved again. Also keep a second card with the same image flashed on it in my bag now, took me ten minutes to be back up after one went bad mid-session instead of rebuilding from scratch.
Been running mine off a LiPo through a cheap buck converter at the field, way less faff than a power bank dying halfway through a session. Curious how the hotspot holds up with multiple viewers though. At our last meet half the club tried pulling the feed on their phones at once and everything got choppy. Does it cope with more than a couple of clients, or is it really a one screen at a time thing?
Join the Discussion
Have something to add? Share your thoughts — no account required.
Didn't find your answer?
Ask the community — no account required