


WINE_CPU_TOPOLOGY=8 PROTON_DISABLE_HIDRAW=1 PROTON_FSR4_UPGRADE=1 %command% -USEALLAVAILABLECORES
Occasional bug with radial menus, fixed with PROTON_DISABLE_HIDRAW=1
I had better results with WINE_CPU_TOPOLOGY set to my physical cores count. PROTON_FSR4_UPGRADE is an AMD GPU thing on recent custom Proton versions, it converts the game's FSR 3.1 into FSR 4, usable on GPUs 7xxx series and up, make sure you select FSR in the game's options. Image quality and performance have both improved for me with this env variable.

Worked out of the gate with no tinkering
Steam Proton Experimental was my default.

The freezing issues I've experienced might well be my own hardware or something. Apart from that, gameplay is smooth and enjoyable at 2K.
$(eval $(echo "gamemoderun %command% -USEALLAVAILABLECORES -nosplash -nostartupscreen -continuesession" | sed -E "s~/Launcher/FuncomLauncher.exe'~/DuneSandbox/Binaries/Win64/DuneSandbox-Win64-Shipping.exe '~g"))
Very sporadically, like five times in 24 hours of play, the game would freeze solid. Though existing processes kept running and my cursor would still move, no new processes could be started (including like "ps" or "kill" or "shutdown") therefore necessitating a reboot. My gut feeling, and it is just that, is that this is a video driver badness, as it seems to get the kernel itself into a weird state. I am continuing to experiment with this, including updating GEProton to latest, and trying the 6.16 kernel while still 'rc' -- I have not had the issue since those last two steps but it's only been a few hours of gameplay so maybe I've just been lucky.

WINE_CPU_TOPOLOGY=8 PROTON_FSR4_UPGRADE=1 %command%
Sometime the radial menus and navigation in the world map view stop working, once it started to happen it always does, and I have not found another solution than playing on another install
Note that this is on an AMD system. I had much better results with WINE_CPU_TOPOLOGY set to my physical cores count than that use all cores option. PROTON_FSR4_UPGRADE is an AMD thing, it converts the game's FSR 3.1 into FSR 4, usable on GPUs 7xxx series and up, make sure you select FSR in the game's options. Image quality and performance have both been improved for me with this env variable.

Runs better than Windows, by a long shot. Havent tried other Protons, using proton-cachyos
Works fine

Managed to get this working after a little trial and error.
Main thing for Ubuntu systems is that the LTS version does not work (at least not for me with AMD CPU and GPU).
Updating from LTS (24.02) to latest (25.04) worked a trick.

PROTON_USE_NTSYNC=1 PROTON_ENABLE_WAYLAND=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 $(eval $(echo "gamemoderun mangohud %command% -USEALLAVAILABLECORES -nosplash -nostartupscreen -continuesession" | sed -E "s~/Launcher/FuncomLauncher.exe'~/DuneSandbox/Binaries/Win64/DuneSandbox-Win64-Shipping.exe '~g"))
Rotating objects (L.Alt + scroll UP/DOWN) doesn't seem to work, gamepad works fine though.
FPS might start to drop during extended gameplay. So I switched from medium settings to lowest.
Funcom Launcher, splash screen & intro can be skipped with: $(eval $(echo "%command% -nosplash -nostartupscreen -continuesession" | sed -E "s/Launcher/FuncomLauncher.exe'/DuneSandbox/Binaries/Win64/DuneSandbox-Win64-Shipping.exe '~g"))

PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 DXVK_CONFIG="/home/drasek/.steam/steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64/dxvk.conf" %command%
Intermittent stuttering and game breaking freezing
With some light tinkering it runs pretty well, and I imagine it will run even better on an NVidia card once the 576 hotfix driver is available on Linux

Runs well for the most part. Minor visual artifacts.
Small, black tears appear at random intervals on the dunes. (V-Sync is ON.)
Sometimes stutters for no apparent reason.
Game runs well for the most part and looks good on Proton 9.0-4
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 DXVK_CONFIG="/home/<user>/.steam/steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64/dxvk.conf" LD_PRELOAD="" taskset -c 0-7,16-23 mangohud --dlsym game-performance "/usr/share/steam/compatibilitytools.d/proton-cachyos/proton" run "/home/<user>/.local/share/Steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64/DuneSandbox_BE.exe" %command%
Works out of the box, added commands are purely to skip intros when you lauch the game (you still get the game launcher).
gamemoderun %command% -nosplash -nostartupscreen -continuesession

Very minor artifacting during some cutscenes. Very rare.
Excellent experience. As if running natively on Windows, other than very little artifacting during certain cut scenes. Would highly recommend.
Overall great game
Works as intended. It's a new game, it's not bug free. But it's not Linux-only bugs.
I really like this game, spent like 100 hours in closed beta. And now another bunch of hours. I like it.

%command% -USEALLAVAILABLECORES
The game loads windowed by default, and when putting it in fullscreen mode, it became graphically distroted, and input no longer works (necetating a force-quit from outside the game.) To get it to NOT load full screen anymore, I had to actually resinstall the game because it was not possible to change the setting back (despite messing around in the game's settings files).
This issue was resolved (see below) after disabling fractional scaling in Gnome.
As other reporters noted, the mouse did not lock into the window. After searching, the fix is to disable fractional scaling in (e.g.) Gnome. Apparently, that plus Wayland can cause weird issues with the coordinates the game detects the mouse at. After disabling fractional scaling (which sucks, but you can increase font size/UI elements in other ways), the cursor will 100% stay locked in the game.
I was originally experiencing a lot of stuttering and minor performance issues. After using -USEALLAVAILABLECORES
(suggested by another poste), frame pacing & stutter has drastically improved, but it can still degrade after a while. I noticed that in some versions of proton (and without the avilablecores flag), the GPU's VRAM would be totally utilized down to the last byte. I also reduced graphics settings from ultra to high in several cases which helped improve stuttering. (Note: I also played this on Windows on the same hardware with significantly better performance & perfect stability.)
Another easy way to trigger stutter was by opening game menus. That was much improved by the CPU flag, but loading in the map view (no matter how recently you viewed it) is the easiest way to trigger stutter.
Many contributors have noted the stuttering and freezes. I think this counts as a significant performance problem. Due to the nature of the game, a freeze like that in an unlucky situation means death -- and certain types of death in this game will wipe your entire inventory & equipped gear. I have experienced a freeze + crash in nearly every game session. Sometimes after a couple hours, and (rarely) after a few minutes.
I've tried several of the workarounds posted by others. I think the hotfix version of Proton feels the most stable, but I still experienced the freeze on it. It is pretty unpredictable, and can happen even outside of "heavy" situations. Essentially, the game becomes completely frozen & unresponsive, though the music is still playing. The steam client also completely freezes. After about 5min or so, it'll crash and you can send a report to Funcom.
This game honestly does play very well, but it really just needs a few core fixes on Linux. The crashes are the only game-breaking problem.
- Fix stuttering/odd CPU usage out of the box.
- Fix the intermittent freeze/crash.
- Fix weird issues with Wayland & fractional scaling, like fullscreen mode & mouse locking.

PROTON_ENABLE_WAYLAND=1 MANGOHUD=1 gamemoderun %command%
little stutering on first few minutes of playing

Ran just fine with default settings, no configuration was needed.
I only had to lower the graphics to the lowest (+ enabling "Low-End Laptop Mode" in settings) due to my setup, rather than due to the game or Proton itself. I'm able to run it above 30 FPS, usually around 45, just fine. I only have 4 GBs of VRAM, which is already below what this game has a minimum requirement, yet it has caused no unexpected issues.

PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 DXVK_CONFIG="/home/drasek/.steam/steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64/dxvk.conf" %command%
As of the patch released 7/3/25 The issue where the game would freeze for 30 seconds after loading into any new zone has gone. The game ran fine outside of the freeze issue before this patch, but the performance has gone way up since this patch.
Currently the game runs like butter without issue.

Works right out the box.
Really rare stutters

Valve experimental proton seems to cause intermittent 30 second freezes which is why I use GE-Proton.
Game can freeze at times, but its not a given it will happen.
NVIDIA and GE-Proton10.4 or higher WORKS GREAT with this game. Had one (1) Intermittent freeze during 8 hours of continues gameplay forcing me to crash the game client.

PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%
some stuttering
game is mostly playable without any tinkering its just the increase in stuttering and less performance, once i tinkered tho its pretty much back up to as it was on windows (recent convert)

PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 DXVK_CONFIG="/home/[USER]/.steam/steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64/dxvk.conf" mangohud gamemoderun %command%
dxvk.conf contains: dxgi.hideNvidiaGpu = False
I was previously getting P34 after playing for 10-30 seconds after trying many tinkering steps. The behavior led me to believe it was due to BattlEye AC, but I wasn't sure. I haven't tried it with fewer run commands, I haven't verified all of the individual commands are contributing to the running of the game, but I can confirm it runs with all of them there. Dune 1.1.10 patch notes include: Fixed issue that would cause a server to become unresponsive to logins. BattlEye has been updated in order to fix some rare crashes.

Can sometimes break up
I use Proton Hot Fix, no issues.

Unless you are using an AMD graphics card I would hard pass on trying this game -- unless you are a masocist.
If you are on Nvidia you will have a bad time
Used a custom dxvk.conf under /DuneAwakening/DuneSandbox/Binaries/Wine64/dxvk.conf
Difficulty keeping the mosue captured.
Freezes all the time crashing out the game. Best case scenario is about an hour of gameplay before it crashes. Some people have had success with turning off hyperthreading, but this has not been successful for me. For the record it's sudo sysctl kernel.split_lock_mitigate=0.
Freezes, crashes and stuttering.
This game is painful...

Esse jogo é muito bom e no linux rodou super bem, atualmente está com suporte ao DLSS e ficou muito bom mesmo.
Antes de incluírem o DLSS erá ruim o desepenho, depois melhorou muito...

gamemoderun %command%
The game will freeze for about 30 seconds after joining a server once the tutorial is completed. The server will then drop the connection and you will be send back to menu.
You can workaround this issue by disabling the kernels split lock mitigation for the current session (sudo sysctl kernel.split_lock_mitigate=0
) or by running the game with gamemode (gamemoderun %command%
).

gamemoderun DXVK_CONFIG="/home/*USERNAME*/.local/share/Steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64/dxvk.conf" mangohud MANGOHUD_CONFIG="fps_limit=165,fps_limit_method=early" LD_PRELOAD="" PROTON_ENABLE_NVAPI=1 %command%
Only 60+ (~100) FPS with FSR Framegen, FPS Drops in sandstorms
Game recognized an AMD GPU on nVidia system. Created "dxvk.conf" in /home/USERNAME/.local/share/Steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64/ folder with "dxgi.hideNvidiaGpu = False" (without "") inside. It fixed the problem and my GPU is recognized correctly. 1440p max details without Lumen, DLSS turned on, DLSS mode quality, FSR Framegen turned on, game is running between 70-110 FPS, with relatively okayish frametimes and heavy framedrops to <30 FPS for 1-2 secs when sandstorms end.

PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command%
I haven't had a single problem running Dune Awakening at 4k (windowed fullscreen) using Ultra settings. Buttery smooth!
Had audio crackling when entering the fourth trial of aql. After finishing it and restarting the game i haven't had it since

As i told before need to disable splitlock sudo sysctl kernel.split_lock_mitigate=0 And guys, who has intel processors (i have i7 12700k) YOU NEED TO DISABLE HYPER-THREADING in your bios and FREEZES WILL GO AWAY

mangohud %command%
Performance on occasions takes a dive. Noticeable when entering a big home base. Otherwise: very smooth, always over 60fps
I use mangohud for every game on Linux, but would not classify this as "tinkering". The game would also run smoothly, out of the box.

Dune: Awakening often stutters in Windows, but it's been butter-smooth in Fedora 42 so far. The game warned me about drivers and hardware compatibility, but I did not detect any issues.
However, it did not automatically detect the character that I had created when playing this game on Windows. I was able to locate this character by selecting the region and server I had played on. Then I could play that character by clicking on the "Join" button in the bottom right corner.

Fantastic game, runs fantastically when testing out some launch options. Only played around with launch options and use experimental
gamemoderun PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=force_cbuffer_cbv __GL_THREADED_OPTIMIZATION=1 %command% -dx12 -USEALLAVAILABLECORES
Just a clean install and playing was terrible. Had to use different launch options and see what worked for me. I landed on what I'm using right now and it runs better than the windows version did.

Based on the consensus, I ran the game perfectly on my machine for three hours with Proton Experimental. Zero tinkering with sysctl kernel.split or launch options. Just forced Proton compatibility and that was that.

Dunno if it's the game being an Unreal Engine 5 game. But judging by the visuals (which are nice no doubt) it shouldn't run on 80fps in the open desert on an RTX 3080 on 2.5K and drop don below 40 in interiors. The worst part was the first "spice dream" there it crashed down to 20-30ish fps.... I suspect it to be the game though. All with DLSS enbaled and such ... THIS shouldn't be the case. But I guess that's Unreal Engine 5 for you.
Crashed 2 times in 4h of game play. So one crash every 2h. Wish kinda sucks in an MMO where you keep 5min on the field after logout. So you just die if in an inappropriate spot or mid fight.
Does not launch with Proton 9 due to asseration faults in VKD3D. But works with Proton Experimental.
LD_PRELOAD="" %command%
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%
Freeze on connection lessened to about ten seconds with sysctl kernel.split_lock_mitigate=0
Game constantly crashed on other proton versions and without command line arguments.

Game freezes after a minute or two for about a minute. It is then very likely to disconnect (about 3/4 of the time), although if it does not it will play fine after the freeze.
However, the fix listed here fixed it - sudo sysctl kernel.split_lock_mitigate=0. Keep in mind, that only changes the setting for that session. To make the change persistent, add the following line to /etc/sysctl.d/99-splitlock.conf: kernel.split_lock_mitigate=0.
In my case, it stops it from both freezing and disconnecting. Some here have reported that it only keeps them from disconnecting, so ymmv.