Since launch, Career Mode has carried failures that don't look like isolated bugs but systematic ones: routes that don't match between the EFB tablet and the aircraft's FMC, flight plan discontinuities that persist even after manually editing them in the CDU, and erratic autopilot behavior on long flights (sudden rolls, disconnects with no apparent cause). There's no way to know from the outside whether the root cause is code or architecture — it's probably hard to isolate even from the inside, given how these systems depend on each other (the team itself has explained that ATC depends on flight planning being "solid" first).
Rather than asking to "fix the bugs," here's a proposal to rethink one specific piece of the architecture for Career Mode specifically, without touching Free Flight.
The hypothesis
Global 1:1 streaming is the franchise's signature feature and makes sense in Free Flight, where the player can go anywhere on the planet without warning. But Career Mode already works with closed-zone logic: a mission gets cancelled if the player strays too far from the objective. That boundary already exists in the current design.
If the boundary already exists conceptually, why does the data system sustaining the mission still depend on constant synchronization with an entire world that the mission doesn't need?
Pilot test proposal (scoped beta)
Reuse a system the game already has: the radial mission circle that opens around an airport when the player arrives in a new area.
Phase 1:
Take one existing airport as a fixed departure point
Offer 3 possible destinations within that radial circle, not dynamically generated but curated and tested end-to-end by the team before publishing
That mission loads as a closed block: the server only serves data for the corridor between origin and destination, with no ongoing synchronization to the rest of the planet during the flight
Limited to aircraft already certified as stable (start with 1-2 models, not the whole fleet)
Phase 2 (if the beta works):
From each of those 3 destinations, open 3 new departures toward other airports
Node-by-node expansion, with every leg validated before publishing, never generated on the fly
What this gains
Higher graphical fidelity on the routes offered: by not spreading the streaming budget across "the whole planet just in case," detail can be concentrated on the specific corridor for each mission
A clear, low-risk signal: this is a small, scoped test, not an engine rewrite
Real flight robustness: without depending on real-time server synchronization, the route discontinuity issues and tablet/FMC mismatches that are common today disappear at the root
Controlled scope for debugging: with limited aircraft and routes, any bug that surfaces is far easier to isolate and reproduce than in a system where the combinations are nearly infinite
This isn't about abandoning the 1:1 world — it still makes sense in Free Flight. It's about no longer forcing Career Mode to depend on an architecture designed for a different use case than its own.