Best Hell Let Loose: Vietnam Settings

October 1 official checkpoint

Hotfix 1.5.2 is the current verified live hotfix. It adds FSR 4.1 for supported Radeon RX 7000 Series and above, with no universally benchmarked best preset here. The publisher asks PC users to finish shader caching and reset Video Settings after the update; record your previous choices first. Console output is SDR, and the October 1 advice is to avoid forcing HDR for SDR content.

Historical checkpoint: September 25 status

There is no independently benchmarked universal best preset on this page. Start with a stable platform-specific baseline and change one setting at a time. The September 25 publisher update identifies a DLSS Frame Generation restart issue, ongoing console visual work and an FSR 4.1 target for Patch 1.6; use the linked symptom guides before applying older advice.

What Patch 1.2 changed

Patch 1.2 says Stereo Balance now saves after restart, custom Tactical Map keybindings display correctly, assigning a key to a new action removes it from the previous action, duplicate-key warnings were added and inputs can be unbound correctly. If one of those exact defects remains, record the Patch 1.2 build and a reproduction instead of assuming an old workaround still applies.

Profile A: official stability baseline for affected AMD PCs

This profile follows the launch workaround while the latest official status remains Under Investigation; it is not a universal FPS preset.

• Update AMD Software: Adrenalin Edition and reboot.
• Restore Video settings to defaults if this PC joined the Crossplay Playtest.
• Set Graphics Quality to High, as specified in the official launch workaround.
• Disable AMD Overlay and other capture overlays.
• Test the full -dx12 -USEALLAVAILABLECORES -malloc=system line; replace it with the full -dx11 -USEALLAVAILABLECORES -malloc=system line only if DX12 still crashes.

Profile B: controlled performance test

Use the same map, route and camera direction for each pass. Record display resolution, graphics preset, upscaler or reconstruction mode, VSync state, frame cap, average FPS and the lowest repeatable frame-rate event. Keep all but one variable fixed.

Tune in a safe order

First lower the overall preset by one step and compare frame time. Then test expensive effect groups before reducing texture clarity. Only change resolution or reconstruction mode after you have a stable same-resolution baseline, because those changes make before/after comparisons harder.

Protect visibility and communication

Do not optimize solely for a higher counter. Reject a profile that makes uniforms, terrain edges or map markers harder to read. Keep voice-chat volume clearly above nonessential effects; squad and leadership information has more tactical value than louder ambient sound.

What this page does not claim

No hardware-specific benchmark has been completed by this site yet, so it does not publish an invented RTX, Radeon or console preset. Future measured profiles must name CPU, GPU, driver, resolution, game build, map, capture method and sample duration.