Unstuck, base relocation, audio privacy and Xbox known issues

Install the client hotfix offered by your platform. Funcom reports stability fixes, including a crash during The Scourge, and a text-chat crash when changing to certain languages, including Korean and Japanese. The missing-Halloween-content fix now extends to all servers. Kingy has not reproduced the faults or tested recovery.

The travel-queue fix below belongs to the earlier 1.5.15.2 patch. Compare your current installed version with 1.5.15.3 before treating an older patch number as the latest client.

Funcom’s October 22 hotfix 1.5.15.2 requires a client-side download. Its notes list one fix: players could get stuck in the travel queue when their platform time differed significantly from the server time. The notice said servers would come back up shortly; that is a service notice, not a verified completion time.

The notes do not say whether you need to change any device setting. Install the hotfix before retrying a stuck travel queue, and keep your platform, installed build and the queue you were in if it still fails. Kingy has not installed the hotfix or tested travel or connection.

1. Check that your client includes 1.5.15.2 or a later update; the latest checked hotfix is 1.5.15.3.
2. On Steam, restart Steam if the download does not appear automatically, as the notice says.
3. On PS5 or Xbox, check the console’s downloads or updates queue for a pending Dune: Awakening update.
4. Retry the connection only after the update has finished installing.

Funcom’s October 20 client-download hotfix reports a fix for Xbox PC players unable to connect after the previous patch, including connections to private servers. If the download does not appear automatically, the notice says to restart Steam. Check the update available on your actual platform; this does not establish an Xbox console build or a universal server-access repair.

The announcement said servers would return shortly. That is a service notice, not a verified completion time. Keep your exact platform, mode, installed build and error if the connection still fails. Kingy has not installed the hotfix or tested a connection.

Funcom announced 1.5.15.0 live on all platforms October 19. It reports fixes for large-base reconstruction crashes, large buildings failing to load through Continue, and several stuck spots in Harko Village and Arrakeen. Dungeon-door interactions now confirm on hold-and-release, avoiding accidental difficulty confirmation from the opening hold.

The older October 12 support list remains linked for issues outside those named fixes. A patch note does not establish that the separate wrong-destination Unstuck, cross-device settings, microphone privacy or Xbox autosave faults are repaired. Keep the original save and record the exact platform, mode, build and failed step.

Funcom’s known-issues update dated October 12 describes a small chance of spawning under terrain after a cinematic or respawning after death. Its workaround is to exit the game, wait at least five minutes and log back in. The support entry does not identify an affected platform or build, or promise that reconnecting will recover the character.

This is separate from the Arrakeen/Harko and antenna-trap fixes in 1.5.3.7. If you encounter it, record your platform, installed build, the cinematic or death that preceded it, the wait duration and the position and outcome after reconnecting. Kingy has not reproduced the fault or tested recovery; keep a failed attempt as evidence too.

1. Exit the game.
2. Wait at least five minutes.
3. Reconnect and check where the character spawns.

Funcom's October 9 hotfix requires a client download. If it does not appear, restart Steam. The patch reports an Unstuck-button failure in Arrakeen and Harko Village, plus a spot near the Atreides Residency in Arrakeen where an antenna stay could trap players. Record the installed build and the actual location if the problem persists; a patch-note version is not proof your client has updated.

The official note gives no coordinates or exact approach to the antenna stay. Kingy has not demonstrated these locations or tested their exits. Keep a location-specific failure separate from the wrong-destination warning below.

Funcom's known-issues page, checked October 9, still says Unstuck in one of the new locations near the end of the Chapter journey can send a player to an incorrect location instead of a nearby safe spot. It does not name that location or provide a verified workaround.

Hotfix 1.5.3.7 addresses the named Arrakeen/Harko failures and the Residency antenna trap. It does not declare this destination fault repaired everywhere. Before using Unstuck for an existing trapped case, note the current journey step and position; after the action, record where you landed and whether progress remained accessible.

September 30 hotfix 1.5.3.5 reports an edge-case Xbox PC save-failure fix, several rare save failures after resuming on Xbox, and several MM3 cases when Continue was used with a multiplayer character. October 6 hotfix 1.5.3.6 separately reports a fix for autosave recovery failing. Preserve the current save and compare the exact symptom, platform and installed version; these notices do not establish recovery of already-lost progress or close every save-loading fault.

The September 28 support list observed October 6 still lists Xbox single-player autosaves failing to load. The later recovery note does not explicitly identify every affected Xbox case. Keep that discrepancy with your error report; Kingy has not reproduced either the failure or recovery.

The September 22 hotfix requires a client download; restart Steam if the update does not appear. It reports fixes for some progression loss and incorrect character data after a failed server join. Verify the character identity before deleting or joining anything.

For the Forty Fears Awakening cinematic, the patch adds automatic completion after 10 seconds if QTE inputs do not register. On PS5 it removes the obsolete Balanced graphics option; that mode had been replaced by Quality. These are developer-reported fixes, not Kingy gameplay retests.

Funcom's September 24 hotfix reports a fix for Xbox saves becoming unavailable after suspending the title during startup, previously requiring a game restart. It separately reports a Windows/Steam fix for ‘Failed to save database: IO operation failed with error code 0x000497’ caused by external file locks. These are distinct platform faults. Check that the installed client includes 1.5.3.4, preserve the current save and record the exact error if it persists; do not delete or replace a save on the assumption that the patch restored lost progress.

The same notes say they fixed live 7X3 errors and added logging for some Microsoft platform-login failures. That does not retire the separate Xbox Game Data Error (2V2) workaround still listed by support below.

Funcom's September 24 known-issues list says AMD Software: Adrenalin Edition 26.6.2 can cause crashes and recommends rolling back to an earlier driver version. Check your installed driver version before changing it, and use AMD's official driver instructions if you choose to roll back. The support note does not name a specific replacement version or say that every crash has this cause. Kingy has not reproduced the driver fault or tested a rollback.

Hotfix 1.5.3.3 reports fixes for incorrectly positioned reconstruction pieces and the Place your backed up base Journey step. Hotfix 1.5.3.4 reports a fix for an offset backed-up-base origin marker after server restart. Funcom's September 24 support list still advises against relocating an existing base while missing or misplaced pieces are investigated. Neither patch promises recovery of pieces already lost.

Funcom's September 24 support list still warns that switching devices can re-enable sandworms and building stability, causing irreversible progression loss. A synced save does not mean custom settings followed it.

Funcom's known-issues page, updated September 24 and checked September 26, says the microphone may become unmuted system-wide when you switch audio devices in game. Before speaking or joining voice chat after a switch, check the operating system's microphone mute and the voice app's mute state. This is a precaution based on the developer's warning, not a tested fix; the page does not identify affected platforms or give a workaround.

Stay on the same device if those protections are disabled. For PC-to-PC moves, support lists ServerCustomSettings.ini at %localappdata%\DuneSandbox\Local\DuneSandbox\Saved\Config\Windows\ as the settings file to copy. This PC instruction is not an Xbox file-transfer procedure; Kingy has not reproduced it.

If Continue fails with MM3 after playing on multiple devices, Funcom says to open Characters, use Change Server and manually select the Sietch.

On consoles, party invites may be absent from the in-game Party Invites tab even though the invite succeeded. Funcom says they can still be accepted from console notifications. These workarounds remained in the September 24 support list checked September 25; check the linked page for newer status.

Funcom's patch notes and support list say a fix for Xbox Ultimate Edition owners missing these building pieces rolled out to multiplayer in hotfix 1.5.3.4; the single-player fix is still scheduled for a future update. Check your mode and installed patch before troubleshooting or buying anything again. This is a developer-reported fix, not a Kingy-tested entitlement result.

Funcom's September 24 known-issues page lists this launch error. Its workaround is a full console shutdown: hold the Xbox button for about 10 seconds, unplug power for 10 seconds, reconnect, then restart. This is developer guidance, not a guaranteed Kingy-tested repair; report the exact error if it persists.

Funcom's current support list asks affected German Xbox players using O2 as their internet provider to contact O2 about Q54 or other FLS connection errors. It does not provide a verified in-game setting or universal fix. Record the exact error and provider before contacting support.

Funcom marks the Xbox multiplayer account-restriction issue solved on September 19; hotfix 1.5.3.1 records the UK/AU age/ID fix. If the error persists, check the installed patch and report the exact message instead of assuming the old issue remains active.

Funcom’s September 21 hotfix 1.5.3.2 reports fixes for an Assault Ornithopter cockpit appearing above its body and the control-scheme image appearing on the wrong side or missing during initial setup. It also improves server recommendations.

If you see either display problem, check whether your installed build includes this hotfix. If it persists, include your build and a screenshot in the report. This is a patch-based check, not a Kingy-tested repair. The patch does not announce a fix for the separate base-relocation or cross-device settings issues above.

1. Open the linked support page for any newer status.
2. Record the patch number, affected device and whether you are playing solo or multiplayer.
3. Keep the current issue separate from a confirmed fix when reporting a problem.