Quick answer

Patch 1.3 went live on August 28, 2026. It doubles the NVA Tunnel placement cooldown from five minutes to ten, blocks travel to a hot Tunnel destination, lets tank drivers change gear without throttle, adds an AMD stability workaround and includes further fixes for vehicles, controls, VOIP, community servers and all six launch maps.

The changes that affect a normal match

The table below groups the full changelog into the changes most likely to alter a match or a troubleshooting decision. It is a player-facing summary, not a replacement for the official list.

AreaPatch 1.3 changeWhy it matters
NVA TunnelsPlacement cooldown increased from 5 to 10 minutes; hot destinations cannot be used for travelPlan the next route before placing a tunnel and keep a backup path
ArmorTank drivers can change gear without holding the throttleDriving and gear changes should require less awkward input timing
HelicoptersVehicle, pilot and co-pilot control fixes were includedRecheck bindings and aircraft behavior after the update
PC stabilityThe notes include an AMD stability workaround and additional performance fixesAMD players should read the current official workaround before trying random launch options
Servers and VOIPCommunity-server, server-browser and voice-related fixes were addedRetest filters, server joins and team communication before changing local settings
MapsMore than 100 fixes were applied across the six launch mapsOld map-specific reports may no longer reproduce in the same way

What changed for NVA Tunnel players?

The most important tactical change is the longer placement cooldown. A new Tunnel is now a more deliberate commitment: placing one in an exposed or low-value position can leave the team waiting ten minutes for the next attempt. The hot-destination rule also means that a Tunnel route can temporarily stop being a safe fast-travel option.

Use the NVA Tunnel Network guide for a practical place, connect, test and maintain workflow. Keep one route for reinforcement and another for a fallback when the front line moves.

What changed for pilots and vehicle crews?

Patch 1.3 includes vehicle and helicopter control fixes, so a control problem that appeared before the update may not have the same cause afterward. Open the current Pilot controls, test one input at a time and confirm your inversion preference before entering a full server.

The helicopter controls guide keeps launch-era keybinds clearly labeled as a reference snapshot. It does not treat an old third-party table as more authoritative than the current in-game menu.

What should PC players check after updating?

  1. Restart the game and confirm that the client actually received the 1.3 build.
  2. If you use an AMD GPU and still have stability problems, read the official workaround in the full changelog before adding unverified commands.
  3. Test your normal resolution and upscaling mode in an empty or low-pressure situation, then compare the best PC settings guide.
  4. If the game still crashes, record when it happens and follow the PC crashing checklist rather than assuming every crash is a Patch 1.3 issue.
  5. Recheck server filters, voice input and pilot bindings after any control or network change.

Are all known issues fixed?

No. The Patch 1.3 notes include many fixes, but they also identify at least one helicopter inversion issue as planned for Patch 1.4. Treat the current changelog as a precise record of what changed, not a promise that every launch problem is gone.

If a problem still reproduces, save the map, role, platform, GPU and exact steps. That information is more useful than a general report that the new patch is “broken.”