Back to Blog

Refreshing Cinematic Mode: Our Oldest EVE Frontier Feature, Rebuilt

Cinematic Mode is the oldest thing in EF-Map that nobody had touched in nine months. It shipped back in October 2025 as the map's "look how pretty space is" mode — smooth camera glides between systems, a hazy nebula, a handful of ambient effects — and we wrote it up at the time with some pride. People liked it. But it was held together with faked decoration, its settings panel was a wall of sliders nobody understood, and it was wired so deep into the app that we'd quietly been afraid to touch it. This week it got the same treatment as the HDR starfield and the 19,846-line monolith before it: handed to a frontier model on a feature branch, rebuilt against real hardware, and shipped. Here's the honest tour.

The map started as white dots on black

EF-Map went live in August 2025. The very first version — built by its operator, one prompt at a time, with the best knowledge and the best models available at the time — was a black background with white single-pixel dots for stars. It did the job: you could see the shape of the cluster and plan a route. It was not, by any measure, nice to look at. Nearly a year later, almost everything about how those 24,000 EVE Frontier systems get drawn has been rebuilt at least once. Cinematic Mode was the last holdout.

The old Cinematic Mode looked good — and faked most of it

The October 2025 version was genuinely a step up for its day, and it was fun. But it earned its "cinematic" look with a stack of decoration that had nothing to do with the actual universe:

And then there was the panel. Cinematic Mode's settings were a long column of sliders — chromatic aberration, haze colour, haze radius, background intensity, aurora intensity — most of which no player ever moved. They were never really controls. They were the operator's own tuning surface, left exposed because there was never a pass to clean them up. The mode shipped, worked, and then sat untouched for nine months while everything around it moved on.

Buried at the root

Part of why it sat untouched: Cinematic Mode is one of the very first features EF-Map ever had, and it's wired into the core of the app — the same enormous App.tsx we wrote about refactoring. Its enable/disable logic threads through the render loop, the shared star material, the camera controls and the label pipeline. You cannot cleanly lift it out; pull one thread and something unrelated unravels. So the refresh had to work around that reality — carefully, in place — rather than extract and rewrite. Some code genuinely is load-bearing, and the honest engineering move is to respect that instead of pretending otherwise.

Don't reinvent the look — pump up the real starfield

The key decision made everything else simpler. A week earlier, the normal-view starfield got its HDR rebuild — real bloom ranked by stellar temperature, a themeable nebula, spectral star colours. The old Cinematic Mode had been a separate, faked pipeline sitting alongside it. The insight was to stop maintaining two starscapes: make Cinematic Mode a slightly pumped-up version of the real HDR starfield, not a parallel illusion.

So the faked layers were cut — the haze, the aurora, the gradient dome, the ripple rings, the lens blinks, the single-pixel dots — and in their place cinematic now renders the same spectral, temperature-graded stars as the normal map, through the same real bloom, in front of the same accent-themed nebula, just turned up. On top of that sit the genuinely cinematic pieces: a directed auto-tour that finds the densest star clusters and glides a smooth camera path through them, a soft depth of field, a little lens dirt, and a filmic colour grade tinted to your interface theme. Every point of light is still a real system you can fly to. Nothing on screen is invented.

Why this fits EVE Frontier

EVE Frontier sells itself on hard-science grounding — real stellar classes, real distances. A cinematic mode that glides you through actual clusters of actual stars, colour-graded by real surface temperature, is more in keeping with that than a haze filter and a lens flare. Set it fullscreen, hide the UI, and it's the map as a planetarium.

The part that fought back: leaving Cinematic Mode

Here's the confession section, because this is where the week went. Building the look was the easy half. The hard, genuinely frustrating half was that exiting Cinematic Mode didn't cleanly restore the normal map. Turn it off and the stars came back flat and colourless; the stargate lines rendered noticeably brighter than a fresh page load; and the camera was left wherever the auto-tour had wandered off to, "side on" to the galaxy.

The breakthrough came from the operator, not the tooling. He noticed that the only thing that snapped the gates back to normal — short of reloading the page — was opening the Display Settings panel. That was the clue. Toggling Cinematic Mode tears down and rebuilds a big chunk of the render pipeline, and the rebuild was leaving it half-synced; opening Display Settings happened to fire the exact event that re-synced it. So now we fire that same re-sync automatically on exit, repaint the stars the instant the mode turns off, and return the camera to the default overview. It took several rounds, a fistful of diagnostics, and an operator who flew around the map after every single preview deploy to catch what a headless browser simply cannot.

The other stubborn one was flicker. A fair question came up mid-debug: the normal starfield has bloom too, so why do its stars never twinkle while cinematic's halos flickered on camera motion? The answer turned out to be the whole fix. Normal mode blooms only the bright, stable star cores; cinematic had been blooming every pixel, which dragged each star's dim, jittering halo edge into the glow. Mirror the normal recipe — bloom only what's genuinely bright, through a soft threshold — and the halos hold steady. Some bugs are like that: you can't measure them in a screenshot, only see them in motion, and the person watching the real thing is the instrument.

Locked in, then stripped back

Tuning the look followed the same pattern as the starfield refresh: where a choice was purely a matter of taste — how much lens dirt, how strong the depth of field, how warm the grade — we temporarily exposed it as a slider, dialled it in on real hardware, and then locked the tuned values in as the defaults and deleted the sliders. Cinematic Mode's panel is now back to what it always should have been: pick your Star Colours, drag Bloom to taste, toggle the Auto Tour, and a Pause button for when you want to stop and look. Four controls. The wall of tuning knobs — chromatic aberration and all — is gone, along with a pile of genuinely dead code that had been dragging along for the ride.

Cinematic ModeBefore (Oct 2025)After
StarsSingle-pixel points, preset tintsSpectral HDR stars, graded by real temperature
BackdropColoured haze + aurora veil + gradient domeThe accent-themed nebula from the real starfield
Ambient effectsTimer-fired lens blinks, ripple rings, bloom pulseA directed auto-tour + depth of field + filmic grade
Exiting the modeLeft the map half-rendered until you poked itRestores the fresh-load view automatically
Settings panelA column of tuning sliders nobody usedStar Colours, Bloom, Auto Tour, Pause

What's next

It ships to production alongside this post. If you play EVE Frontier, open the map, switch on Cinematic Mode, turn on Auto Tour, hide the interface, and just let it fly you through the cluster for a minute. It's the same real stars you route through every day — turned up, and finally allowed to look the part. As always, if there's a knob you wish we'd left you, tell us; every default started as somebody's slider.

Related Posts

cinematic mode hdr bloom eve frontier three.js auto tour depth of field starfield ef-map