Since our last Community Feedback update, Update 1.5 has arrived, bringing the officially licensed Bell UH-1 Iroquois ‘Huey’, the M14 and Type 56 SKS, our first weapon balancing pass and 100+ fixes and improvements.
This was followed by Hotfix 1.5.1, which introduced further improvements to ADS visual stability, mounted weapons, UI, and controller haptics for the M14 and SKS.
We’ve been closely following your feedback throughout the first week of Update 1.5, and have been pleased to see the positivity around the new weapons and the Huey Radio in particular, and that the M16 ammunition changes have also been welcomed as a direct response to previous community feedback.
Alongside that feedback, we’re continuing to investigate several of the issues you’ve been reporting, including spawning and deployment failures, audio reliability, crashes, Server Browser visibility and visual quality.
Here’s where things currently stand.
We have see your reports surround spawn and deployment issues, including HQ spawn points disappearing, Garrisons and Outposts becoming unavailable, and some players being unable to select or place spawn points.
Following investigation, the team believes it has identified an issue within the game’s replication system that could be contributing to several of these behaviours, and are working on fixes including one we’re hoping will be added into our next Hotfix 1.5.2.
In some circumstances, certain information was not being correctly cleared when a match ended. Over multiple matches, this could increase the likelihood of elements failing to replicate correctly, including HQ spawn points and potentially other objects within the environment.
A fix has now been implemented internally and is undergoing QA verification. Because this underlying issue may be connected to several different reports, we want to complete that testing before confirming exactly which problems it resolves.
The fix is currently planned for Patch 1.6, although we’re also investigating whether it can be safely introduced sooner once verification is complete.
In the meantime, we also recommend that server owners restart their servers on a regular basis just to help with any potential server degradation issues.
Status: Fix Undergoing QA Verification
Following the improvements made to the prolonged robotic Proximity Chat issue, the majority of current VOIP reports are now focused on different behaviours, including communication channels failing, dropouts and some console transmission or routing issues.
Our Code team has continued working alongside Epic to investigate these issues, including implementing additional changes based on suggested workarounds for known underlying problems.
The latest changes are scheduled to be tested during larger-scale playtests, where we’ll be able to better assess their impact under conditions closer to a live server.
Whilst we’re hopeful these changes will improve VOIP reliability, we don’t yet want to suggest that every remaining communication issue has been resolved until that testing is complete.
Status: Additional Improvements in Testing
Stability remains one of our key areas of focus across all platforms.
Following each release, the team continues to review incoming crash data and work through the highest-impact issues, with further safeguards and fixes being introduced as they are identified. AMD crashes and driver timeouts remain amongst the more prominent PC reports, alongside console crashes and freezes and a smaller number of NVIDIA-related reports.
AMD FSR 4.1 remains targeted for Patch 1.6. We’re also assessing whether it could safely be introduced earlier, but this will depend entirely on the results of our testing and integration work, and will keep you updated.
Status: Stability Improvements Ongoing | FSR 4.1 Targeting Patch 1.6
Server visibility has continued to generate reports, particularly from console players and Community Server owners.
From your reports, we’ve identified and fixed several Server Browser issues, including problems with filters not always being remembered or correctly reapplied during an automatic refresh. These fixes are currently planned for Patch 1.6.
There is also a wider limitation we’re investigating around how server sessions are returned to the game. The current system can return a maximum of 200 sessions from a single search, whilst considerably more servers can be active globally at any one time. This means a particular server may occasionally not appear as part of a broader search. We are therefore currently investigating improved ways of running multiple targeted searches and combining those results to increase overall server visibility.
For now, using more specific filters can help narrow the available results. We also recommend favouriting the servers you regularly play on to make them easier to find.
We’re also making changes to our official server offering to give players greater control over the modes they join. This includes introducing dedicated Warfare and Offensive servers alongside servers that continue rotating between multiple modes.
At the same time, we’ll be reducing the overall number of official servers to create more space for Community Servers and further support the community-run server ecosystem.
Status: Patch 1.6 Fixes Planned | Further Improvements Under Investigation
We’re continuing to track reports from some NVIDIA users where their selected Frame Generation setting appears correctly within the menu, but needs to be reapplied after restarting the game before the performance benefit activates.
The team believes a fix for this behaviour has been implemented for Patch 1.6, although it still requires final QA verification before we can consider the issue resolved.
Status: Fix Targeting Patch 1.6, Pending Verification
Visual quality remains one of the most common areas of console feedback, including reports around image resolution, asset pop-in, foliage quality, lighting and perceived draw distance.
Hotfix 1.5.1 introduced an improvement to how visual elements are handled while entering ADS. This keeps objects within your view in a more consistent state while aiming, reducing instances of shadows, LODs and other visual elements visibly changing during the transition.
That being said, there is still further work to do. One of the remaining areas involves individual assets' HLOD distances, which can cause objects to appear or disappear at noticeable ranges. These are being continuously improved on an asset-by-asset basis by our Tech Art team. If you find any specific affected object, be sure to let us know.
This remains part of our wider ongoing work to improve image quality and visual stability across the game.
Status: Ongoing
One recurring conversation we continue to see is whether development of new content should be paused while outstanding bugs and stability issues are addressed, and we want to provide some additional context around how development works across the team.
Different areas of Hell Let Loose: Vietnam are developed by specialist disciplines, each with their own expertise and responsibilities. For example, Environment Artists, Weapon Artists and Animators focus on creating and refining game content, while code-related issues require dedicated engineering expertise and are addressed by the relevant development teams.
Whilst some Code support is naturally required to implement new content, the majority of the Code team’s current time is being spent investigating bugs, stability and other live-game issues, especially those reported by the Hell Let Loose: Vietnam community. At the same time, our content teams can continue developing upcoming maps, weapons and other additions.
This allows us to continue improving the live experience whilst development on future content progresses in parallel, rather than one area having to stop entirely for the other to continue. That’s why, alongside new content, you’ll continue to see a wide range of fixes and improvements reflecting the work our Code team is doing to improve the overall game and player experience.
It has been wonderful to see how positively the M14 and Type 56 SKS have received since arriving in Update 1.5, with players particularly enjoying their stopping power and the additional variety they bring to infantry loadouts.
Their introduction has also generated further discussion around the wider weapon pool. We’re currently tracking feedback around M16 recoil and lethality, alongside requests to make the M14 and SKS available to additional roles.
Update 1.5 marked our first balancing pass on the launch weapon roster, and this is an area we intend to continue reviewing as more gameplay data and feedback becomes available.
Status: Monitoring Feedback & Gameplay Data
Alongside bug reports and balancing feedback, we’ve continued collecting your most requested additions for the future.
Some of the most common discussions this week include:
More weapons and wider role access.
New vehicles, including attack helicopters.
New maps, including urban environments, night combat and weather.
Greater asymmetry between the NVA and US Forces.
The return of Hell Let Loose features such as Commendations, Clan Tags and Party Chat.
While we cannot confirm when, or if, all of these will make their way into the game, we can confirm that the suggestions you’ve submitted continue to play an important role in our future planning discussions for 2027 and beyond.
As always, a feature being discussed or tracked does not mean it is confirmed for development, but your feedback helps us understand what you would most like to see from Hell Let Loose: Vietnam in the future. We can also confirm that some of these discussion areas may come to fruition sooner, in 2026.
We’ll have more to share in our upcoming Command Post Dev VLOGs, so be sure to follow us on YouTube and across our Hell Let Loose Official social channels so you don’t miss any future reveals.
Thank you once again to everyone who has been sharing reports, feedback and suggestions following Update 1.5.
It’s also been great to see the response to some of the update’s newest additions. The M14 and Type 56 SKS have been welcome additions to the arsenal, the Huey Radio has quickly become a community favourite, and the M16 ammunition changes have addressed one of the more common pieces of weapon feedback we had been tracking before Update 1.5.
We’ll continue working through your reports as we move towards Patch 1.6 and further updates.
When reporting an issue, please continue to include as much information as possible, including your platform, hardware where relevant, what happened immediately before the issue occurred and any screenshots or video that can help us reproduce it.
We’ll be back with another Community Feedback update soon.
See you on the battlefield.
