Are you watching your cruise missiles crater a runway, only to see the enemy airfields 80/80 health Salvo bug instantly erase your hard-earned damage? You are not alone. This progression-blocking glitch occurs because an aggressive mid-war repair loop out-heals incoming strikes, locking the airfield’s durability at a permanent 80/80 state regardless of the ordnance you drop on it. The definitive fix is downloading the June 2026 patch, which drastically reduces enemy repair speeds so your structural damage finally sticks. However, if you are playing on a legacy build, you can still bypass the bug using a perfectly timed, single-frame saturation attack.
SALVO is not a forgiving game. It is a deep, brutal tactical simulator that demands a working knowledge of layered air defenses, radar logic, and munition types. The in-game encyclopedia, ARPHA-NET—the knowledge archive of the underground command network—teaches you the fundamentals of CEP (Circular Error Probable), why the radar horizon matters, and the operational differences between cruise and ballistic missiles. But ARPHA-NET does not warn you about the game’s early-access engine quirks. When SALVO launched, players quickly realized that standard attrition warfare was mathematically impossible against certain targets.
We are going to break down exactly why this health-lock happens at the engine level, how the recent developer patch resolves it, and the advanced Time-on-Target (ToT) strategies you can use to obliterate these airbases if you are forced to play on an unpatched version.
The Engine Math Behind the Enemy Airfields 80/80 Health Salvo Bug
To understand why your missiles are failing, you have to look at how SALVO calculates structural integrity and mid-war healing. In the game's architecture, forward operating bases and airfields are designed to recover from light damage between active combat phases. This simulates runway repair crews patching craters and restoring operational capacity.
However, in the launch build of the game, an integer error tied the repair tick rate to the game's framerate rather than the in-game chronological clock during active combat. Instead of healing a few hit points every minute, the airfield was executing its repair logic every single frame.
When a standard cruise missile impacts a target, it deals a calculated amount of damage based on its yield and CEP. Let’s say your strike deals 45 damage to a pristine airfield. The structure's health drops from 80/80 to 35/80. But before your second missile—arriving just two seconds later—can impact and finish the job, the game engine processes roughly 120 frames. At a repair rate of even 1 HP per frame, the airfield instantly snaps back to 80/80 health.
This creates the illusion of an indestructible target. The HUD registers the hit, the explosion renders, but the underlying database immediately overwrites the damage. You can dump your entire underground command network’s depot onto a single hex, and the runway will remain fully operational. Steam community members like Traslo and n0b3TC1 were among the first to document that the structure wasn't actually invulnerable; it was just out-healing the player's damage output in real-time.
Infographic: The 80/80 Repair Loop Error in Salvo
How the June Patch Fixes the Enemy Airfields 80/80 Health Salvo Issue
On June 1, 2026, the developers released a comprehensive patch addressing the most severe progression blockers reported by the community. The patch notes directly targeted the repair loop engine flaw.
The fix was simple but structural: "Enemy airfields no longer heal back to full mid-war — repair speed has been greatly reduced, so the damage you deal actually sticks."
By decoupling the repair tick from the rendering framerate and strictly enforcing a delayed chronological timer, the developers ensured that airfields behave as intended. Now, when you land a hit that drops an airfield to 35/80, it stays at 35/80 for the duration of the immediate engagement. You can follow up with a secondary strike minutes later to close the runway, allowing you to actually progress the campaign map.
This patch also cleaned up several other frustrating UI and mechanical glitches that plagued the launch window:
- The "Yellow X" Tunnel Lock: Previously, cancelling a salvo plan would lock your missiles in the launch tunnel with a yellow X warning, rendering them unusable. The patch ensures unfired missiles are cleanly returned to your depot.
- The MANPADS Deployment Trap: Spent MANPADS used to bug out after firing a single shot. They would remain permanently on the map, unusable, but occupying the hex so you couldn't build replacement air defenses. They now clear correctly.
- ARPHA-NET Keybinding: The encyclopedia was moved to the TAB key, preventing players from accidentally opening it when pressing 'W' to pan the camera (which now supports full WASD panning).
- Audio Persistence: The atmospheric Farsi numbers station—the background shortwave radio—received new, more realistic operator voices, and the volume sliders finally save and persist between sessions.
- Stuck UI Elements: The infamous "surrender" notification that appeared when Tel Aviv was hit and permanently locked onto the screen has been removed.
If you are playing through Steam, ensuring your game is updated to the June 1 build is the absolute fastest way to resolve the airfield health lock.
Bypassing the Enemy Airfields 80/80 Health Salvo Bug on Older Builds
For players participating in offline tournaments, using legacy mods, or otherwise unable to update their client, you cannot rely on attrition. You have to beat the engine at its own game. If the airfield heals every frame, your only option is to deal a lethal 80 points of damage in a single frame.
This requires executing a flawless Saturation Attack—a doctrine heavily detailed inside ARPHA-NET, but rarely executed correctly by novice commanders.
The Mechanics of a Single-Frame Saturation Strike
To bypass the bug, you must coordinate multiple munitions to impact the target at the exact same millisecond. This is known as a Time-on-Target (ToT) strike. Because no single conventional missile in the early-game arsenal deals 80 damage on its own, you must stack the damage values of two or three simultaneous hits.
Analysis Report Poster: Saturation Strike Metrics
Here is the tactical breakdown of achieving a ToT strike against a bugged airfield:
- Calculate Flight Times: A ballistic missile travels at a high arc and impacts quickly, but gives the enemy early warning radar ample time to track it. A cruise missile travels slower and lower, staying under the radar horizon until the terminal phase. You must launch your cruise missiles first, wait for them to cover the distance, and then launch your ballistic missiles so their flight paths converge on the target simultaneously.
- Mitigate CEP (Circular Error Probable): If you launch three missiles and one scatters outside the effective blast radius due to a high CEP, your total damage in that frame will fall below 80. The airfield will survive and instantly heal. Use your ARPHA-NET data to select munitions with a CEP of less than 15 meters for this specific strike.
- Overwhelm the Air Defense Layers: An airfield at 80/80 health is usually guarded by layered air defenses. If a single interceptor shoots down one of your cruise missiles, your single-frame damage output drops, and the bug saves the airfield. You must send decoy radar-spoofing drones slightly ahead of your primary payload to absorb the enemy MANPADS and terminal CIWS fire.
Missile Comparison for Saturation Strikes
| Munition Class | Base Damage | Flight Profile | CEP (Accuracy) | Role in Bug Bypass |
|---|---|---|---|---|
| Sub-sonic Cruise | 35 | Sea-skimming (Under radar horizon) | 10m (High) | First launch. Evades early warning. |
| SRBM (Ballistic) | 50 | Exo-atmospheric arc | 25m (Medium) | Second launch. High damage, fast impact. |
| Decoy Drone | 0 | Variable | N/A | Absorbs terminal defense fire. |
By timing a Sub-sonic Cruise missile (35 damage) and an SRBM (50 damage) to impact on the exact same frame, the engine registers 85 simultaneous damage. This exceeds the 80/80 maximum health cap, triggering the "Structure Destroyed" state before the mid-war repair tick can execute. The runway closes, and the map hex changes hands.
Comic Grid: The Yellow X Depot Error
Managing Other Early-Game Progression Blockers
While the airfield bug is the most notorious, surviving SALVO requires navigating a minefield of both intentional tactical challenges and unintended engine quirks. If you are mastering the underground command network, you need to keep your logistics clean.
Save/Load Corruption: Prior to the recent hotfixes, loading a save directly from the main menu would occasionally leave leftover data from your previous session floating in the RAM. This could result in ghost markers on your map or incorrect active counters for your layered air defenses. Always fully quit to the desktop and relaunch the game before loading a deep-campaign save file to ensure a clean memory state.
The Yellow X Depot Error: If you are meticulously planning a complex ToT saturation attack, it is easy to make a mistake and hit cancel. In older builds, cancelling a salvo plan locked the missiles in the launch tunnel. If you encounter this, do not save your game. Reload your last autosave (which now correctly runs during combat phases) to recover your munitions.
Annotated Diagram: Radar Horizon and Layered Air Defense
The beauty of SALVO lies in its brutal, uncompromising vision of modern missile command. The atmospheric dread of the Farsi numbers station crackling over the radio, the tension of watching a radar track blip across the horizon, and the deep satisfaction of executing a flawless saturation attack make it a standout title in the tactical genre. The bugs at launch were severe, but they forced players to truly understand the math behind the warfare.
Whether you update your client to squash the mid-war healing loop, or you choose to outsmart the engine with a perfectly timed single-frame strike, the skies belong to the commander who understands their arsenal.
Frequently Asked Questions (FAQ)
Why won't my missiles destroy the runway in Salvo? If your game is not updated to the June 2026 patch, you are experiencing the mid-war repair loop bug. The airfield is healing its damage every single frame, instantly recovering to 80/80 health before your next missile can hit.
How do I fix the enemy airfields 80/80 health Salvo bug? The most reliable fix is downloading the latest patch, which reduces the enemy repair speed so damage sticks. If you cannot patch the game, you must use a Saturation Attack to deal 80+ damage in a single frame, instantly destroying the structure before it can heal.
What does the "Yellow X" mean on my missile silos? The yellow X indicates a bug where missiles get stuck in the launch tunnel after a salvo plan is cancelled. The June patch fixes this, returning unfired missiles to your depot. On older versions, you must reload an autosave to clear the lock.
How do I open ARPHA-NET without accidentally triggering it? In the launch build, ARPHA-NET was bound to the 'W' key, causing conflicts when trying to pan the camera. Update the game to move the encyclopedia to the TAB key, or manually rebind it in the settings menu (which now correctly saves your preferences).