Controller Support for EF-Map: Flight Mode and Recorded Camera Flights

EVE Frontier added WASD flight controls I think around the tail end of 2025, and people immediately started mapping keybinds onto controllers and joysticks to get around the game with them. Since then proper Xbox controller support has been added to the game, and at Fanfest every EVE Frontier demo stand was running on controllers and joysticks, using the demo mode that I believe is the precursor to the Cycle 6 HUD. It works. It's not perfect, I've written before about the flight model and I stand by that, but it works. And having now added controller support to EF-Map, I can see why it took a while to come to the game, because I assumed it would be an easy add and it absolutely was not.

Blame the SuiPlay

At Fanfest, Sui were very generous to those of us there for EVE Frontier. There were about 50 attendees with founder access but only about 10 of us active on Discord and actually playing, and Sui handed out SuiPlays to a number of us, I'm not sure how many. Mine is the SuiPlay0X1 I think, their Linux-based handheld, and it's a genuinely capable wee machine. I believe it's a Zen 4 processor, 16 gigabytes of fast unified memory and a decent graphics chip, and it runs Steam happily. I've played a few games on it. But I'm never mobile enough to say I couldn't live without it, which sounds a bit naff about something I got for nothing, but there it is.

So I had a conversation with ChatGPT about what else it could do. Could it be a little dev machine, could I run a local LLM on it, would that actually be worth anything? That got ruled out fairly quickly. EF-Map's AI features run on Cloudflare and cost two to four hundredths of a cent per question, so a local model saves no money, it would just be tinkering for the sake of it. But somewhere in that conversation it suggested the obvious thing I hadn't considered, use the SuiPlay as the excuse to build controller support into EF-Map. Which is actually a decent idea. So naturally I did nothing with it for two or three weeks.

One feature became three

When I came back to it, the idea had grown legs. EVE Frontier has controller support now, and people play it on Steam Deck even though that's not officially a thing. So somebody could genuinely be sitting playing the game with a pad, glance at EF-Map on a second monitor, and not want to put the controller down. That's the basic case, and on its own it's a bit thin. But I'd recently added Alcubierre warp optics to the flythrough mode, and remembering that got me thinking, if you've got analogue sticks and triggers anyway, why not a proper manual flight mode? And then there's Director mode, which scripts camera movements for making videos. What if you could fly a shot by hand, record it, replay it with the interface hidden, and paste it into a Director sequence?

So it became three connected features. Controller-native control of the normal map, sticks to pan and orbit, analogue zoom on the triggers, and a centre-screen reticle for picking stars so you're not driving a pretend mouse cursor around 24,000 stars. An explicit flight mode modelled on how the game itself flies, left stick for pitch and yaw, no manual roll, the ship banks into turns by itself and levels back out when you straighten up, right trigger accelerates, left trigger brakes and eventually reverses. And a recorder, so a flight you like can be saved, smoothed, replayed cleanly for capturing footage, and handed to the Director.

The overnight build

I scoped the whole thing as one long-running job and let it run while I slept. The orchestrator started by sending five investigation agents through the existing code in parallel before anything was written, because the camera in EF-Map already has half a dozen systems fighting over it, flythrough, the Director, the cinematic auto-tour, the normal mouse controls, and a controller was about to become another one. Then it staged the build, and finished by setting three adversarial review agents on the diff whose only job was to attack it. They found 21 real problems before I ever saw it, 8 of them serious, things like flight mode being enterable inside embedded maps, and a held button firing again when you alt-tab back to the window.

The bits only a human finds

Then I woke up, plugged in an Xbox pad, and found the things no automated review catches. The first time I actually flew it, left was right. An inverted yaw, one sign error, invisible to every automated check because the maths was internally consistent, the ship just turned the wrong way. The status indicator used yellow for mouse mode, which reads like an error state. The bindings card closed itself when you pressed B, which is exactly the button you press all the time to back out of things, so you'd dismiss it before you'd read it. The panel was too narrow so its buttons wrapped onto two rows. There was no way to bring up the extended hover card for a star, so Y got remapped to that and the reframe action it displaced moved across to the View button. None of these are things a test suite tells you. They're things a thumb tells you.

The flight model needed the most feel work. The first version was technically correct and completely weightless, slam the stick and you were instantly at full turn rate and full bank. So angular inertia went in, and the ship now leans into a turn over about a second. That led to its own thought, someone recording a cinematic pass might want a much heavier ship than the default, because a heavy ship draws smoother lines. So there's a ship mass slider now, and a top speed limiter, and the bindings and settings fold away into collapsible sections once you know them.

This is the shape of every big agent build I've done. You hand over a huge scope, and you get back something that compiles, passes nearly 4,000 tests and demos correctly in a headless browser, and it still isn't finished, because nobody has felt it yet. My workflow through the polish stage is iterative rather than babysitting, a quick check with the pad, dictate what's wrong, leave it to run for an hour while I get on with other things. Three rounds of that through the day. And even now it's had exactly one person's hands on it, so I can't call it done, I can only call it released.

Who this is actually for

Honestly, going by the usage numbers, not hundreds of people. Game activity is modest at the moment and controller users on a map website are a subset of a subset. That's fine. I like building, and while the game's world contracts are static there's time to build. Every feature seems to find a way to link into the others anyway, the controller found the flythrough, the flythrough found the recorder, the recorder found the Director. I'd rather have a full-featured product sitting ready if EVE Frontier's numbers ramp up than start building the day they do. And every page like this one adds a bit more surface for search engines and AI assistants to find.

So it's live. Plug in a pad and move a stick, and a card comes up showing the bindings. Flight mode is on the Start button or in the Controller and Flight panel, recording is X while you fly, and if you make something good the Director will take it. I've only been able to test with the Xbox controller I own, PlayStation and Nintendo pads should show their own button glyphs but I can't promise the feel, so let me know what breaks and I'll get it sorted.

Related Posts

• My EVE Frontier Review After 18 Months of Founder Access - includes my standing complaints about the game's flight model, which this feature borrows from anyway
• What travelling in an Alcubierre warp bubble might actually look like - the warp visuals flight mode can switch on
• Custom Intelligence Panels: Build Your Own EVE Frontier Dashboard - the previous long-running agent build
• Half a Million Light-Years Saved: Eleven Months of EF-Map Usage Data - the usage data mentioned above