Quick answer

Use this Hell Let Loose: Vietnam guides hub according to the problem in front of you. New players should start with the beginner guide; pilots should open the helicopter controls guide; PC players dealing with launch-build stability should read best settings; and squads planning around NVA tunnel networks should read Tunnel Warfare.

For a specific helicopter task, use How to Land a Helicopter, Helicopter Supply Drop, or Hot LZ Insertion. Each page keeps the task answer separate from the live-client controls and from claims that the current sources do not support.

These pages are written for the August 2026 launch build and connect each practical recommendation to an official launch or store source. When a detail belongs to the live client—such as a platform-specific control binding or a hardware-specific result—the guide sends you to the current in-game menu or a reproducible test instead of turning an old playtest post into a permanent rule.

Choose a guide by your next task

I am playing my first match

Read the Hell Let Loose Vietnam Beginner Guide. It starts with the official Getting Started tutorial, joining a squad, choosing a role with a clear responsibility, identifying the current mode and communicating the objective. It covers the four named modes—Warfare, Offensive, Conquest and Domination—separately because the same movement plan does not apply to every mode.

The guide also links the roles page and maps page. Use those pages after a match to compare the role you selected, the battlefield setting you saw and the objective the squad was trying to complete.

I need to fly or understand helicopter inputs

Open the Helicopter Controls Guide. Official game and store pages confirm playable US helicopter units and describe fire-support and supply-drop use cases. The reviewed first-party pages do not print a single PC or controller key table, so the guide tells you how to read and test the live client’s current bindings before taking a flight slot.

It also connects the flight task to the launch map list and the beginner guide. A control can be technically correct and still fail the squad if the pilot does not know the current objective, map setting or requested support job.

I need to land, deliver supplies or insert a squad

Use the landing guide when forward movement, descent or a go-around decision is the blocker. Use the supply-drop guide when the squad needs logistics context, and the Hot LZ guide when the task is a communicated insertion under risk. The official Patch 1.3 notes are linked on each page; prompts and bindings still belong to the current client.

I am troubleshooting FPS, crashes or visibility

Read Best Settings for FPS and Stability. The page separates AMD launch guidance, reset steps for settings carried from the Crossplay Playtest, general frame-time testing and visibility decisions. It does not promise a universal frame-rate increase because the official launch article describes system-dependent results and the Steam page provides requirements rather than a benchmark for every machine.

Change one variable at a time, record the build and hardware context, and keep temporary launch options separate from a permanent graphics preset. Revisit the dated official launch information after an update instead of assuming that an August workaround remains current forever.

For a wider symptom-first route, open Issues & Performance. It separates AMD stability, FPS and stutter testing, audio or VOIP reports, tutorial prompts and map or role display problems so a launch-build note is not mistaken for a universal fix.

I need to understand tunnels and movement

Read Tunnel Warfare. Official descriptions establish NVA tunnel networks as a Vietnam-specific system that can support surprise attacks and change how squads approach the battlefield. The guide explains how to observe a live match, communicate a tunnel-related change and connect the system to the map and objective without inventing a distance, capacity, cooldown or universal counter.

Use the maps page alongside the tunnel guide. The six launch maps include different combinations of rivers, waterways, jungle, villages, cliffs, caves, an airfield and a port; the route problem depends on the current map and mode, not only on the word “tunnel.”

What these guides cover together

The hub follows a practical learning order:

  1. Understand the match loop. The beginner guide explains squads, objectives, modes and communication.
  2. Choose a responsibility. The roles page lists the named storefront records across Command, Infantry, Recon, Armour, Helicopter and Mortar Squad units, while keeping the official 17-versus-19 conflict visible.
  3. Read the battlefield. The maps page records the six official launch names and the terrain descriptions published for each one.
  4. Solve the immediate task. The helicopter, settings and tunnel guides handle controls, launch-build troubleshooting and Vietnam-specific movement questions.

This order prevents three common category errors. A graphics setting cannot prove a role is stronger, a weapon description cannot supply a missing control binding, and a map name cannot by itself establish a permanent vehicle route or tunnel rule. Keep the question, the source and the live-client check together.

Current source boundary

The official game page, launch articles, Steam listing and PlayStation Store listing establish the game’s factions, launch maps, modes, roles, helicopters, patrol boats, tunnel networks and launch guidance used across this hub. The current official game page displays 19 specialised roles, while the current store pages list 17 named storefront records; the roles page keeps that first-party conflict visible rather than combining the numbers.

The guides do not fill gaps with guessed values. Exact helicopter bindings, hardware-specific FPS gains, permanent landing zones, tunnel distances, tunnel capacity and complete weapon-by-role assignments require a current client observation or a dated first-party source. When a page reaches that boundary, it gives you a reproducible next check and preserves the date of the evidence used.

Sources

Last verified: September 3, 2026. The official source wording, Patch 1.3 notes, task links and current launch-build guide boundaries were checked; live-client controls and hardware-specific results still require their own verification.