I rewatched the Squadron 42 gameplay reveal recently and came away both excited and frustrated. Excited, because SQ42 still shows the Star Citizen many of us originally backed: a believable military universe, disciplined fleet operations, purpose-built ships, coherent loadouts, and combat grounded in doctrine, logistics, and immersion. Frustrated, because the current direction of the Persistent Universe feels increasingly disconnected from that same vision. The Reveal Still Shows the Original Promise In the SQ42 reveal, the F7A-style fighters appear to run standardized Panther-style loadouts. That makes sense in context. Military units standardize equipment for reliability, logistics, training, and doctrine. The ships look like fighters doing fighter things. That is the fantasy many of us bought into. Not because it was simple, but because it felt believable. The current PU often feels different in practice. Between power, cooling, shields, weapons, capacitors, and sensors now all competing inside the operating equation, even advanced military ships increasingly feel like incomplete platforms that require constant component optimization to function in their intended roles. SQ42 shows the fighter as a professionally designed military machine. The PU increasingly risks turning that same fighter into a parts-management problem. Manufacturer-Spec Should Mean Something A manufacturer like Anvil, Aegis, RSI, Drake, MISC, or Origin should not be delivering ships that cannot credibly operate their intended baseline equipment. A military fighter should be able to power its sensors, shields, coolers, and standard weapons without needing a crafted workaround to make the ship viable. A stock ship does not need to be optimal. It does need to be coherent. Crafting and upgrades should matter. They should enhance specialization, efficiency, reliability, signature management, survivability, stealth, or edge-case performance. They should not be required to make a ship’s basic role work. The crafting pitch was provenance, economy, and player-driven industry. That is a compelling pitch. But if the practical result is that factory-built ships feel intentionally compromised so crafted components can fix them later, then crafting stops being depth and starts being a tax on baseline functionality. 4.7 and 4.8 Are Compounding the Problem This is not an abstract concern. The trend is showing in patch behavior. In 4.7, sensors became a real combat component drawing real power, without a corresponding adjustment to ship power generation. Ships already balancing shields, weapons, and thrusters now have to budget for radar performance too, on the same power plant that was sized before sensors became a meaningful draw. In 4.8 PTU, the situation gets worse, not better. Armor health has been reduced across a wide range of ships, capital ships included. Armor deflection thresholds have also been reduced on several mid-sized gunships and heavy fighters, including ships sold around durability, armor, and combat staying power. Weapon speeds and ranges have been reduced across many categories, with heavier weapons especially affected. Each change may be defensible in isolation. Together they form a pattern: ships are being balanced less around advertised manufacturer identity and more around an evolving progression and combat economy that undermines manufacturer quality, design intent, and role clarity. There is a difference between meaningful tradeoff and artificial deficiency. There is also a difference between balancing capital ships and flattening their role. Capital ships should not be invulnerable. They should require escort, logistics, crew, planning, engineering, and vulnerability management. But they should also represent a distinct operational layer. If every balance pass pulls them back toward the same combat logic as smaller ships, the fleet game loses structure. This Is Not Just Drift. It Is Divergence. SQ42 was always going to be curated. The PU was always going to be the sandbox. The assumption was that they would converge around the same underlying vision: believable ships, grounded combat, manufacturer identity, logistics, player skill, preparation, and teamwork. Right now, they are moving apart. SQ42 shows the cinematic clarity of the original promise. The PU keeps absorbing systems that make the same promise harder to feel in practice: constrained power budgets, crafting dependencies, sensor draw, armor and deflection reductions, weapon speed cuts, capital-ship role compression, and component balance churn. What Backers Are Actually Asking For Many of us have supported this project for a very long time, through years of funding, testing, feedback, and patience. That does not entitle us to design the game. But it does give us a legitimate reason to speak up when the direction appears to be moving away from what made Star Citizen unique in the first place. We are not asking for ships with no tradeoffs. We are not asking for combat with no engineering depth. We are not asking for upgrades, crafting, maintenance, armor, weapon choice, or logistics to be meaningless. We are asking for baseline ships to feel like professionally designed machines before they become player projects. A ship should be a machine first, and a project second. We are asking for manufacturer identity to matter. We are asking for capital ships to retain a real operational role. We are asking for the PU to retain the same internal coherence the SQ42 reveal demonstrates. Right now, it is not getting it. If an advanced military fighter cannot credibly power its own sensors, shields, coolers, and standard weapons without crafted upgrades, then the problem is not the pilot’s loadout. If ships sold around armor, durability, or capital-scale firepower are repeatedly compressed back toward the same combat logic as everything else, then the problem is not just tuning. The problem is the design philosophy.