It’s been another busy week for Hell Let Loose: Vietnam, with Hotfix 1.5.2 now live[www.hellletloose.com] across all platforms.

The hotfix introduced the much-requested AMD FSR 4.1 support, alongside further improvements to stability, VOIP, memory usage, server replication and several other community-reported issues.

Since the update went live, we’ve been closely monitoring your reports and our internal data to understand the impact of these changes. While it is still early, we’re already seeing some encouraging signs, particularly around stability and the server replication issues we discussed in last week’s Community Feedback update.

Alongside monitoring Hotfix 1.5.2[www.hellletloose.com], development continues on Patch 1.6, with several community-requested quality-of-life improvements now confirmed for the update.

https://youtu.be/6wlHh2fXD2s

Here's the latest:

Stability remains one of our highest priorities, with Hotfix 1.5.2 introducing several additional changes designed to reduce the frequency of crashes across all platforms.

The initial crash data following the hotfix is showing a significant reduction in crashes compared with previous releases. During an initial monitoring period following deployment, the number of recorded crashes was substantially lower than we have previously seen, with no immediately obvious AMD-specific crash pattern appearing within that data.

Whilst this is an encouraging early result, we will be continuing collecting data over a longer period to ensure that our next improvements are focused on remaining areas of instability.

For AMD players, FSR 4.1 is also now available following Hotfix 1.5.2[www.hellletloose.com]. Alongside overall stability, we will of course continue monitoring feedback of this addition’s performance as more of you get hands-on with the new addition.

As always, crashes can have a wide variety of causes depending on hardware and individual configurations. Please continue reporting any crashes you are having and will ensure to keep addressing the highest-impact issues as they are identified.

Status: Improvements Live | Monitoring Ongoing

We’ve continued to see reports around blurry foliage, asset pop-in and instances where environmental cover can stop rendering before the players behind it.

Some individual foliage issues were addressed as part of Hotfix 1.5.2[www.hellletloose.com], but there is still more work underway.

The team is continuing to review LOD and culling distances, with the goal of pushing environmental detail further into the distance whilst maintaining acceptable performance. We’re also working through individual assets where incorrect LOD or HLOD settings can cause objects to transition or disappear at the wrong ranges.

Further improvements are being worked on for upcoming updates, including Patch 1.6 and beyond.

For console specifically, we’re also actively testing further improvements to areas such as resolution and LOD distances. These changes need to be carefully balanced against performance, but we currently expect further visual improvements across Update 2.0[www.hellletloose.com] and beyond.

Hell Let Loose: Vietnam currently outputs in SDR.

For console players experiencing unusually dark, bright or washed-out visuals, we recommend checking that your console or display is not forcing HDR for SDR content.

On PS5 in particular, we recommend allowing the console to automatically enable HDR “On When Supported”, rather than using the setting that forces HDR across all games.

Status: Improvements Ongoing

Hotfix 1.5.2[www.hellletloose.com] introduced several fixes to Iris, the replication system used to communicate game state between servers and players.

As we explained in Community Update #5[www.hellletloose.com] and Hotfix 1.5.2[www.hellletloose.com], problems within this system could contribute to server degradation over longer sessions, potentially resulting in spawn points, HQs and other gameplay elements no longer behave or appear correctly.

Early feedback following Hotfix 1.5.2 has been encouraging. We’ve spoken with several Community Server owners who had previously experienced these issues, and so far they have not reported the same behaviour returning following the hotfix.

We don’t want to consider the issue completely resolved based on only a short period of testing, so we’ll continue monitoring servers over the coming days.

We’re also continuing to track remaining reports around Mortars and other deployable objects not always spawning or displaying correctly, and will update you as soon as possible on this issue.

Status: Fix Live | Monitoring Ongoing

Hotfix 1.5.2 introduced additional safeguards designed to reduce instances where players could become silently muted and unable to hear one another, and we’re continuing to monitor those changes, alongside several other areas, of VOIP feedback.

One issue we’re actively investigating involves Voice Chat volume, where some players report that other players can remain excessively loud even when their voice volume has been reduced significantly. We can confirm that a fix for this issue is currently targeting Patch 1.7, although we’ll look to introduce it sooner if possible.

We’ve seen your requests to be able to choose your audio output for Voice Comms (VOIP), so you can separate them into different audio streams. Improved control over audio routing is something we are very keen to support, although this requires additional work across our audio and communications systems. We’ll keep you updated as development progresses.

Status: VOIP Improvements Live | Further Improvements In Development

Last week[www.hellletloose.com], we discussed several Server Browser issues, including filters not persisting correctly and difficulties finding particular servers.

We can now confirm that persistent Server Browser filters have been fixed in Patch 1.6. Your selected filters should now remain correctly configured between sessions.

We’re also changing how servers are initially presented within the browser.

During launch, changes were made to the server browser, designed to prioritise servers with available spaces to make it easier for players to immediately join a match. Following feedback from both players and Community Server owners, we’ll be adjusting this behaviour so that higher-population servers once again appear towards the top of the Server Browser, similar to how it operates in Hell Let Loose.

This change is also planned for Patch 1.6.

Alongside this, we’re increasing the availability of PC-only official servers across Europe, North America and Australia for players who would prefer to play without Crossplay enabled.

Status: Improvements Coming in Patch 1.6

We’ve seen an increase in discussions around team killing, trolling, disruptive leadership and other forms of griefing.

There is no single change that can prevent every instance of disruptive behaviour, but we’re looking at several areas where the game can give players better tools to respond.

Starting with Patch 1.6, Vote Kick notifications will now be visible by default, addressing one of the most common requests we’ve received around the current moderation tools.

We’re also increasing the Vote Kick response window from 20 seconds to 30 seconds, giving players more time to see an active vote and make their decision.

Looking further ahead, we’re investigating additional measures targeting some of the most common forms of deliberate team killing and disruptive behaviour. These include situations involving vehicles and players deliberately killing teammates to take control of particular vehicle seats.

We’ll have more to share on those changes as development progresses.

Status: Vote Kick Improvements Coming in Patch 1.6 | Further Moderation Improvements Under Investigation

Another area of teamplay feedback involves transport boats being left with their engines running.

Because an active boat cannot be used as a spawn point, a player abandoning a boat without switching off the engine can prevent their team from spawning there.

We’re investigating a number of potential changes to how boat spawns work to minimise how often engines are left on, blocking spawns. For example we’re considering turning off the engine automatically when a player exits, having it turn off automatically after an idle period, along with other suggestions that we’ll be testing.

These concepts are still being worked through, and we would love to hear your suggestions for what improvements could be made in the future.

Status: Improvements in Progress

We’re continuing to work on the Aim Assist behaviour previously discussed in our Community Feedback updates.

The team is targeting further improvements to how Aim Assist operates, and subject to development and testing, our current aim is to have these improvements implemented by Update 2.0.

We’ll share more specific details once the implementation has progressed further.

Status: Improvements Targeting Update 2.0

Alongside the larger issues above, we’ve also been reviewing some of the smaller quality-of-life requests you continue to raise.

We’ve seen requests to increase the current text chat character limit, particularly from players trying to help explain mechanics or coordinate with newer players.

Increasing the limit itself is relatively straightforward, but doing so creates additional usability challenges because players currently have limited ways to scroll back through longer conversations.

We’re investigating improvements to the wider text chat experience, including its size, positioning and the ability to navigate previous messages.

We’ll have more to share on those changes as development on this progresses.

We’re also continuing to see feedback around mounted Machine Guns, particularly around deployment, elevation and the experience of being forced into ADS while using them.

The team agrees that mounted weapons are not currently as easy to use as we would like, and this feedback is being tracked for future improvements. Stay tuned for MG updates as the roadmap progresses.

Our next update is Patch 1.6, and we’ll have the full details on everything included very soon.

Alongside a new deployables overhaul, unit changes and a major audio pass, this week we can confirm that several changes that have specifically come from community-requests:

• Vote Kick notifications enabled by default

• Vote Kick response window increased from 15 to 30 seconds

• Server Browser filters will persist correctly

• Higher-population servers will once again be prioritised within the Server Browser

• Increased PC-only server availability

These are all areas that have repeatedly appeared in your feedback, and we’re pleased to be able to turn several of them around for the next update.

Thank you once again to everyone who continues to send us reports[support.team17.com], feedback and suggestions.

Hotfix 1.5.2 appears to have made meaningful progress in several areas we’ve been discussing since launch, but we know there is still plenty more work ahead.

We’ll continue monitoring the impact of the hotfix while preparing Patch 1.6 and the updates that follow.

Please keep sharing what you’re seeing in-game, particularly around stability, server replication, VOIP and visual quality. The more information you can provide about your platform, hardware and the circumstances surrounding an issue, the easier it is for the team to investigate.

We’ll be back with another Community Feedback update soon.

See you on the battlefield.

This week’s hotfix introduces the much-requested AMD FSR 4.1 support, alongside further improvements to stability, VOIP, memory usage, server replication and several other community-reported issues.

Following each update, shaders will be cached when you first launch the game. Please allow this process, and the initial loading screens, to fully complete before continuing.

Continuing while shader caching is still taking place may result in the game crashing.

We’re looking at ways to improve how shader caching is handled in future updates to make this initial experience smoother, and we’ll share more details once those improvements are confirmed.

We also recommend that all PC players using either AMD or NVIDIA GPUs reset their Video Settings to default following the update. This will allow the game to correctly recalibrate your settings following the introduction of AMD FSR 4.1.

AMD FSR 4.1 support is now available for players using AMD Radeon RX 7000 Series GPUs and above.

AMD has also confirmed plans to back-port FSR 4.1 support to the Radeon RX 6000 Series in 2027.

FSR 4.1 uses machine learning to reconstruct higher-quality visuals from lower-resolution frames, helping improve performance while maintaining image quality.

Players can choose between several FSR 4.1 quality modes depending on whether they would prefer to prioritise image quality or performance:

• Native AA - Provides image quality superior to native rendering, with a modest performance cost.

• Quality - Provides image quality equal or superior to native rendering, alongside a significant performance gain.

• Balanced - Offers a balance between image quality and improved performance.

• Performance - Provides image quality similar to native rendering, with a larger performance gain.

• Ultra Performance - Provides the highest performance gain while maintaining image quality representative of native rendering.

We identified several edge cases that could cause other players to become silently muted, resulting in some players being unable to hear one another.

Hotfix 1.5.2 introduces additional safeguards designed to reduce the likelihood of this occurring and improve the overall reliability of player communications.

We’ll continue monitoring VOIP reports following the hotfix.

Fixed an issue where signing out of Epic Online Services (EOS) could cause game settings to reset after signing back in.

Your game settings should now be retained when signing in and out of EOS.

We’ve made further improvements to how the game manages memory during gameplay.

These changes reduce the amount of data being held in memory, helping free up additional VRAM. This should provide performance improvements, particularly for players using GPUs with lower amounts of available VRAM.

We’ve made a series of improvements to Iris, the replication system used to communicate game state between the server and players.

Over longer periods of server activity, replication issues could contribute to what we refer to as server degradation, where elements such as spawn points, HQs, vehicles, ladders and other objects could stop behaving or appearing correctly.

Hotfix 1.5.2 introduces several fixes designed to reduce instances of this behaviour and improve server reliability over longer sessions.

We’ll continue monitoring reports following the update to assess the impact of these changes.

A number of further stability improvements have been introduced with Hotfix 1.5.2.

This includes a fix for a potential memory corruption issue that could result in a crash, alongside fixes for several VFX-related issues involving flares.

We’ll continue reviewing incoming crash data and addressing further stability issues as they are identified.

We identified a rare issue on PS5 that could result in players losing their save data.

Additional safeguards have now been introduced to further protect against this occurring.

Fixed an issue where certain trees could incorrectly display their distant 2D impostor versions when close to the player.

These assets will now correctly transition to their full 3D models at the intended distance, improving visual quality and reducing noticeable tree pop-in.

Patch 1.6 is coming next, and we’ll be sharing more details on what’s included very soon, so keep an eye on our channels for the full breakdown. 

As always, thank you for continuing to share your reports and feedback. We’ll continue monitoring the impact of Hotfix 1.5.2 as we work towards Patch 1.6.