UnknownUnknown
The game is currently unplayable. It launches, shows a "Known issues with graphics driver" error that incorrectly mentions AMD, and then cra
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%
Crashes after ~30 seconds
LD_PRELOAD="" PROTON_ENABLE_WAYLAND=1 mangohud %command%
Everything works and runs really good. All settings are maxed out with FSR ultra at 3440x1440, 90 FPS, 99% stable.
Freezes after 30 seconds of gameplay
Freezes after 30 seconds of gameplay
Freezes after 30 seconds of gameplay
Freezes after 30 seconds of gameplay
Just finished a ten hour session with my wife and brother-in-law. No technical issues so far with GE-Proton10-4 (installed via ProtonUp-Qt).
"/usr/share/steam/compatibilitytools.d/proton-cachyos/proton" run "/home/desez2tpunk/.local/share/Steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64/DuneSandbox_BE.exe" %command% -nosplash -BattlEye -continuesession
Game does not save the acception of privacy policy and telemetry service, prompts every time.
If you want to skip the Funcom Launcher you have to launch using this in Launch options for CachyOS with the CachyOS Proton
"/usr/share/steam/compatibilitytools.d/proton-cachyos/proton" run "/home/USERNAME/.local/share/Steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64/DuneSandbox_BE.exe" %command% -nosplash -BattlEye -continuesession
Great game, great choice with BattleEye Anti-cheat
Flawless
Playing in 4k with fsr on quality HDR works
Was even bragging to a mate that is running windows how easy it has become to run games on Linux / bazzite and how it all just works.
- infrequent flickering (black screen for a few frames) when opening menus
- texture issues (fixed by upgrading to mesa 25.1.2 from 25.0.5)
Make sure "Proton BattlEye Runtime" is installed, since this game is using BE AntiCheat. For me this got installed automatically by steam.
Switch to Proton Hotfix if you experience freezes
Good online experience
I'm below min requirements, but works out the box (25-45 fps min settings, laptop mode).
AMD drivers are a bit behind windows, so I get a warning about that; will update when available
DLSS fix: Here is the solution to our DLSS not working on linux problem. No more AMD related error message on startup and DLSS + framegen.
DXVK_CONFIG="/home/yourusername/.steam/steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64/dxvk.conf" gamemoderun %command%
Game sometimes crashes after 15m to 4h.
Go to your dune install folder and find the Win64 directory. Something like: /home/yourusername/.steam/steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64
Make a new file and name it dxvk.conf. Edit the file and insert the following text then save it. dxgi.hideNvidiaGpu = False
In your steam launch options, add the following with the path to the file you just created: DXVK_CONFIG="/home/yourusername/.steam/steam/steamapps/common/DuneAwakening/DuneSandbox/Binaries/Win64/dxvk.conf" %command%
Enjoy!
WINEDLLOVERRIDES="dstorage,dstoragecore=n,b" PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%
Without any launch options, the game complained that my hard drive didn't meet the minimum system requirments. I noticed a slight stuttery feel to the game even though the FPS was high. With the additional launch options, it fixed all my problems.
Random increases in Frametime. Nothing significant but still noticible
When you join a server, after about 2 Minutes of playing, the game will freeze for about 1 minute. You will get disconnected with error P34. If you try to open the steam overlay during this time, the game will for some reason not disconnect you and work just as normal.
Playable with minor issues.
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 PROTON_BATTLEYE_RUNTIME="/home/parzival/.steam/steam/steamapps/common/Proton BattlEye Runtime/" mangohud %command%
After completeing the Tutorial you will be disconnected from the Servers after a 10 Minute delay. The game will freeze and you loose connection.
The Game is not ready for Linux yet. My guess is the Hotfix driver changes, they recommend you to install in Windows, have not yet arroved in Proton.
Just press play and enjoy
Preview version of game is unplayable as getting P34 errors
Getting P34 Errors when trying to play the game using proton experimental. I can login and play for 30 secs and then the game freezes and when it unfreezes it end up disconnecting with the P34 error
PROTON_ENABLE_NGX_UPDATER=1 DXVK_NVAPI_DRS_NGX_DLSS_SR_OVERRIDE_RENDER_PRESET_SELECTION=render_preset_latest %command%
XeSS Quality - 50-90 fps. usually around 60
Haven't been able to get DLSS to work yet. Performs rather poorly for a 5090. XeSS quality allows playable gameplay usually 60+ fps
The game will insist that you play with controller, even when none is connectet, wherefore the navigation in the menues can be tricky sometimes
Crashed for the first hour ca. 5 times, but after being on the main server for a while there where no more crashes
I don't know how to fix the controller issue, but it might be due to the fact that most linux gaming happens on the steamdeck
%command%
I could not launch past the Launcher with the Debian 12 repository installed NVIDIA driver (535.247.01). After upgrading the .run driver from NVIDIA directly (570.153.02) it launched perfectly.
Ran great during the beta weekend! No issues found other than needing to install the anticheat
You are required to install the "Proton BattlEye Runtime" for multiplayer to work. The game does not specifically mention this, only that BattlEye failed to start. Once you install it, the multiplayer works perfectly.
The game is great and it runs okay in the lowest settings, provided your hardware meets the minimum recommended.
LD_PRELOAD="" PROTON_ENABLE_NVAPI=1 __GL_SHADER_DISK_CACHE_SIZE=5000000000 mangohud gamemoderun %command%
Some glitches, like weird spiky textures in the world and glowing artifacts after exiting the menu. Fast camera movement fixed the glitches most of the times.
Some parts are very GPU intensive, so even if your hardware seems to run the game fine, its best to use the bare minimum graphics to keep the performance more consistent.
"Proton EasyAntiCheat Runtime" must be installed manually by the user to join public areas. Just search it on Steam and install, no further settings are required.
The multiplayer is experiencing desync issues, but they are not Linux-related.
There's no need to use a custom Proton runner or tweak the command line, but installing "Proton EasyAntiCheat Runtime" is a must.
In fact, I played the beta for more than 14 hours with the default runner.
Multiplayer functionality worked fine after installing the Proton BattlEye Runtime. However, terrain textures near the player—particularly those affected by view distance—are missing or not rendering properly. This issue was observed on the RX 9070 XT. Various Proton versions, including Proton 10 Beta, were tested, as well as different GPU drivers (AMDVLK and RADV), but the problem persists across all configurations. Aside from this graphical issue, the game is fully playable.
PROTON_BATTLEYE_RUNTIME="<location of proton battleye>" %command%
Easy fix for battleye after tutorial section kicks you out.
Weekend Beta Works As Long As You Install Proton BattlEye Runtime First
Proton BattlEye Runtime required for online play.
This review is based on the "Weekend Beta" event held on 9-12 May 2025. The game will run without Proton BattlEye Runtime installed but will error out when trying to join a multiplayer server. Installing Proton BattlEye Runtime through Steam (it is not installed by default) fixes the issue and allows for unrestricted operation. The game does not require BattlEye while playing through the tutorial area.
(Beta Weekend) - Fails to join server stating Battle Eye service is not installed properly.
Post update, after character creation and selection of sietch, loading into sietch fails for both PC and Steam Deck with the error message "The Battle Eye service is not installed properly and needs to be restarted".
Couldn't remove the my previous report so doing this. I figured out the problem was they added battleye anticheat into the game now and I didn't have the proton battleye runtime enabled.
