Dune Awakening 1.5 problems are being patched quickly after the September overhaul introduced single-player, console Head Start and the new character-centred server system. Funcom shipped hotfix 1.5.3.1 on September 19 and hotfix 1.5.3.2 on September 21, while its support page still lists several single-player and interface issues that players should know about.
This is a living tracker for Dune Awakening 1.5 problems, not a generic list of every bug ever reported by the community. It separates current developer-confirmed issues from faults that have already been fixed, and it will need another review after the full PS5 and Xbox launch on September 22.
Dune Awakening 1.5 problems: current known issues
Image credit: Funcom
- Single-player custom settings do not sync correctly across multiple devices. Disabled Sandworm or Building Stability settings can be re-enabled when the save is opened elsewhere.
- Some custom settings can block mission progress. Funcom recommends returning affected settings to defaults, restarting and trying the section again.
- Max Durability Decay does not affect vehicle parts as expected.
- Building and sub-fief limits shown in the UI may not refresh after changing custom settings.
- Dropped items may not despawn after leaving and rejoining a map.
- Some Testing Station and Shipwreck map markers are inaccurate.
- Controller UI faults remain, including D-pad map navigation and cases where holding a button on a Palm Lock can skip the dungeon-difficulty selection.
Those are developer-listed Dune Awakening 1.5 problems from Funcom’s current Help Center entry. The list can change independently of the main patch notes, so the official known-issues page should be checked before assuming a problem is unique to your save.
BattlEye-free single-player launch is still paused
One of the most confusing Dune Awakening 1.5 problems involves BattlEye. Hotfix 1.5.3.1 added an option for Steam users to launch single-player, private servers and self-hosted servers that do not require BattlEye without the anti-cheat enabled. Multiplayer servers configured for BattlEye would still require it.
Funcom then disabled that change because the new Steam launch options were not replicating correctly for all clients, causing BattlEye errors for players trying to enter multiplayer. The September 21 hotfix notes do not say the option has been restored, so the safe current status is that the change remains paused pending another deployment.
What hotfix 1.5.3.1 fixed
Hotfix 1.5.3.1 addressed several early Dune Awakening 1.5 problems, including players spawning under terrain in single-player, vehicle module stats being overwritten, the final Book One dialogue/cinematic being missed, a sandbike refuelling Journey step not registering and the Deep Desert 50% building-cost reduction failing to apply.
The same update improved server and client stability, fixed a UK/Australia Xbox age-verification multiplayer issue, fixed certain Plant Fibers failing to yield resources and corrected several combat, texture and movement faults.
What hotfix 1.5.3.2 fixed on September 21
Hotfix 1.5.3.2 is a smaller client update but is still relevant to Dune Awakening 1.5 problems. Funcom optimized the server page so players are directed toward better recommended servers, fixed the Assault Ornithopter cockpit appearing offset above the vehicle body, and corrected the Control Scheme image placement in settings and initial setup.
The patch requires a client-side download. Steam users who do not see it should restart Steam, while single-player users should restart the game after maintenance to make sure the current client build is installed.
What to try if single-player progression is blocked
- Check Funcom’s known-issues page for the exact mission or setting.
- Return heavily modified custom settings to their default values.
- Fully restart Dune: Awakening and retry the blocked section.
- If you use the same single-player save on multiple devices, avoid switching devices while Sandworm or Building Stability is disabled.
- Restart Steam if a new client hotfix does not begin downloading automatically.
These steps target documented Dune Awakening 1.5 problems rather than generic advice such as reinstalling Windows or changing unrelated drivers. If the problem appeared immediately after a patch, first make sure the client is actually on the latest build.
Console launch issues will be added after September 22
The full console launch has not happened yet, so this Dune Awakening 1.5 problems tracker will not invent PS5 or Xbox launch faults before players encounter them. Deluxe and Ultimate owners already have Head Start access, but September 22 will bring a much larger console population and Game Pass players. Confirmed launch-specific problems and fixes should be added here as Funcom publishes them.
Use Funcom’s official patch notes for hotfix history and the known-issues page for unresolved problems. Our Dune Awakening Update 1.5 hub covers the actual features rather than troubleshooting.
