Game CluebookSearch
← Back to the cluebook

Hell Let Loose: Vietnam / issue watch

Performance & Known Issues

A playtest issue list is evidence of what the team investigated—not proof that every item remains in the launch build.

Short answer

The useful part first.

The latest detailed official issue list we could verify was for the July 24 crossplay playtest, not the final August 13 build. It documented VOIP distortion, occasional FPS spikes, some AMD GPU crashes, tactical-map drops, graphical polish, tutorial prompts, and UI/localization problems. Check the launch brief and current support channels before assuming any one item still applies.

What was officially known in the crossplay playtest?

Voice chatDistortion when opening or closing radio channels; EOS Voice Chat and FMOD integration was the stated cause
PerformanceOccasional FPS drops or spikes during intense scenes
AMD stabilityInfrequent crashes on some AMD GPUs alongside a known driver issue
Tactical mapBrief performance drops and teammate icons sometimes missing on first spawn
GraphicsLighting inconsistencies, console shadow inconsistency, and popping
Tutorial / UIIncorrect controller prompts, placeholder text, wrong icons, and HUD update issues

What did the developers say they changed?

  • Profiled client, GPU, CPU, server, rendering, networking, animation, and memory bottlenecks after the Open Beta.
  • Improved video-setting defaults, application, and persistence between sessions.
  • Added or refined resolution-scaling controls and continued console optimization.
  • Refined audio mix and directional positioning after Beta feedback.
  • Continued optimization through launch and into the live-service period.

Why this page does not give a “seven universal fixes” list

An AMD driver crash, a server-side spike, an EOS voice problem, an Epic ownership error, and a settings-save bug do not share one reliable fix. Generic advice such as reinstalling every runtime or deleting configuration files can waste time or erase useful evidence. Start by identifying the platform, exact error, hardware, build, and whether the problem also appears in official channels.

Safe first checks after launch

  1. Install the final game update and the current platform or GPU-driver update.
  2. Compare your PC against the official requirements, including the TSR/DLSS target—not only the GPU name.
  3. Check the current Team17, Steam, PlayStation, Xbox, or Epic support notice for a matching issue.
  4. Record the exact error, platform, hardware, graphics preset, and action that triggers the problem before changing multiple settings.

Epic has a dedicated official page for the HLLV LS-0021 launch error. Use that page for that code instead of treating it as a general crash.

Final-build status

At the checked time, the game had not yet reached its global unlock. This page deliberately keeps the playtest label visible. A launch-day update should move items into three groups: confirmed in final build, fixed/not reproduced, and still awaiting evidence.