Dead Space 2
Ubuntu 16.04, NVIDIA GTX 970, Proton 3.7-5 Beta:
| Test | Result |
|---|---|
| Singleplayer | Working as expected^ |
| Local Co-op | N/A |
| Online Multiplayer | Not working^ |
| Configuration | ... |
|---|---|
| Input | Steam Controller |
| Display | 1920x1080^^ |
| Fullscreen | Yes |
| Preset | Medium^^^ |
| VSync | Off^^^^ |
| API | DX9 |
^ Unable to connect to EA online servers (optional for singleplayer)
^^ Default screen resolution is 1024x768
^^^ Default graphics preset is High
^^^^ Default VSync setting is On
NOTE: Optional Brightness setting not working as expected
Stuck at Activation Manager how do we bypass this with proton?
Stuck at Activation Manager how do we bypass this with proton?
I have the same issue, cannot install the game due the Activation Manager in Step 3
@aaulia kill activation manager process
@soredake Thank you, that truly helped and my game runs fine too.
But i think, it should be fixed before the game can be trul whitelisted.
When you start the Activator directly from the Filemanager in the Steam Deadspace 2 prefix, the Activator starts directly into the Window for entering the Key. So i think, it will be possible on Steam too
When you start the Activator directly from the Filemanager in the Steam Deadspace 2 prefix, the Activator starts directly into the Window for entering the Key.
How do you start the activator from individual game prefix (WINE prefix right?)
Runs & installs without issues for me, however it does take some time to launch (approx. 30-60 sec.).
Game initially activated successfully for me and signed in with my EA account.
Multiplayer: Although I didn't start a multiplayer game I successfully reached the lobby where it stated searching for players..
CPU: AMD Ryzen 5 2600X Six-Core
GPU: Vega 56
OS: Ubuntu 18.04.1 LTS (64 bit)
• Steam Runtime Version: steam-runtime-beta-release_2018-06-14
• Driver: X.Org Radeon RX Vega (VEGA10, DRM 3.26.0, 4.18.5-041805-generic, LLVM 8.0.0)
• Driver Version: 4.4 (Compatibility Profile) Mesa 18.3.0-devel - padoka PPA
@aaulia I use KDE with Dolphin Filemanager, there i can open a terminal in it, and start the activation exe inside the correct prefix. i can activate by entering the number, but the game would not start inside steam, until you pass the activation inside the Steam Client. For me it was easy like said above: stop the activation Task and a Window will open for entering the DVD Code.
Dead Space 2 - Keyboard doesn't work ingame
Issue transferred from https://github.com/ValveSoftware/Proton/issues/1363.
@P4NCH1 posted on 2018-09-09T17:32:02:
Compatibility Report
- Name of the game with compatibility issues: Dead Space 2
- Steam AppID of the game: 47780 (steam-47780-log)
System Information
- GPU: AMD Radeon R7 Kaveri 1GB
- Driver/LLVM version: Mesa 17.2.4/5.0.0
- Kernel version: 4.14.0-0.steamos.81-amd64
- Full system information report
- Proton version: 3.7-3 and 3.7-6 Beta
I confirm:
- [ x ] that I haven't found an existing compatibility report for this game.
- [ x ] that I have checked whether there are updates for my system available.
Symptoms
Keyboard doesn't work ingame or even in menu selection. Sometimes works in menu selection but when game starts and you have to move the character you can't. If you [Alt]+[Tab] out, the game freezes so this is not a workarround like in MX Linux
Reproduction
- Start game
- Keboard does not work
or
- Start game
- Keyboard works
- Start a new game
- Wait until video presentation ends
- Keboard does not work
NOTE:
The game have the same issue in another machine with MX Linux 17.1 64bits but keyboard gets detected again ingame by removing the focus off the game and returning it ([Alt] + [Tab]).
Same keyboard problem is in Dead Space (17470), both in SteamOS and in MX Linux 17.1
Like I said in that message, in MX Linux you can workarround the issue in Dead Space 2 (47780) by removing the focus off the game and returning it ([Alt] + [Tab]). That same "workarround" doesn't work with Dead Space (17470) in that distro and won't work with any game in SteamOS because "alttabing" freezes Proton/Wine.
Well, continuing with the tests over this game, the same "workaround" used on MX Linux can solve the keyboard issue but requires some more steps due to Wine can't get focus again.
This is what I do to make it work:
- Remove the focus of the game ([Alt]+[Tab])
- Close the game in a forced way ([Alt]+[F4]) since it can not get focus again.
- Cancel the forced closing by closing the sign asking for it (this way the game can get focus again).
- Go back to the game ([Alt]+[Tab]). Keyboard now works but only for a random amount of time...
If it happens that the dialogue sign is left behind the game window, with [Shift]+[Ctrl]+[Alt]+[Arrow Down] and [Shift]+[Ctrl]+[Alt]+[Arrow Up] (or Left and Right, depends on your DE) you can move windows between workspaces.
Same steps works for the first Dead Space but this one breaks again more quickly.
Game works fine with proton 5.0-2.
Same problem as https://github.com/ValveSoftware/Proton/issues/3651 but only after alt-tab.
I was unable to start the game due to the activation program crashing. Fixed by installing msxml6 using winetricks in the prefix; the activation program started normally and I could enter my CD Key.
Dead Space 2 (AppID 47780) crashes on NVIDIA + Wayland during D3D9 device creation
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9336.
@zhinchey posted on 2025-12-26T07:38:24:
System
CPU: Intel Core i9-13900K
GPU: NVIDIA RTX 3060
Driver: NVIDIA proprietary (tested via nvidia-smi)
OS: Kubuntu / KDE Plasma 6
Session: Wayland
Steam Runtime: Soldier
Filesystem: ext4 root + BTRFS Steam library (exec enabled)
Problem Summary
Dead Space 2 fails to launch on NVIDIA + Wayland.
The game window flashes or shows the EA logo briefly and then exits.
The game never reaches the main menu.
This occurs across:
Proton Experimental
GE-Proton 8.x
GE-Proton 10.x
DXVK
WineD3D
The crash occurs during Direct3D9 device creation.
From Proton logs:
dxvk: Failed to create D3D9 device
err:d3d9:Direct3DCreate9Ex Failed to initialize D3D9
The failure happens before PhysX or gameplay logic initializes.
What works
The game runs correctly on Steam Deck (AMD GPU, X11, Mesa)
The game progresses further under X11 on this system
The game consistently fails under Wayland on NVIDIA
This isolates the problem to NVIDIA + Wayland + DX9 swapchain / presentation
Filesystem validation
Initially Steam library was mounted with noexec:
/media/zhinchey/Storage 2 btrfs rw,nosuid,nodev,noexec
This was corrected in /etc/fstab:
UUID=1d0a7e81-a9bb-4c58-af62-037032c52ef5 /media/zhinchey/Storage\0402 btrfs nofail,users,exec 0 0
Then remounted:
sudo umount /media/zhinchey/Storage\ 2
sudo mount -a
findmnt /media/zhinchey/Storage\ 2
After this, Dead Space 2 got as far as the EA logo but still crashed.
Proton prefix reset
rm -rf ~/.steam/steam/steamapps/compatdata/47780
Game was reinstalled and prefix rebuilt.
Proton logging
Enabled using:
PROTON_LOG=1 %command%
Log file produced:
~/steam-47780.log
DXVK disabled test
Tried forcing WineD3D:
PROTON_USE_WINED3D=1 PROTON_LOG=1 %command%
Still crashed during device creation.
CPU-core limiting attempts
These were tested to rule out legacy engine thread bugs:
Simple core limit
taskset -c 0-7 %command%
Safe wrapper
bash -c 'PROTON_LOG=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 exec taskset -c 0-7 "$@"' bash %command%
Wine topology override (crashed Proton bootstrap)
WINE_CPU_TOPOLOGY=8 taskset -c 0-7 %command%
None resolved the issue; crash still occurred during D3D9 device creation.
PhysX attempts
protontricks 47780 physx
PhysX installed but did not affect crash.
Vulkan shader cache did build
Steam Vulkan shader pre-compilation completed successfully, confirming Vulkan itself is functional.
Conclusion
Dead Space 2 fails to create a Direct3D9 device under NVIDIA Wayland.
Both DXVK (DX9 → Vulkan) and WineD3D (DX9 → OpenGL) fail, indicating the issue lies in NVIDIA’s Wayland WSI handling of legacy DX9 swapchains.
The same game works:
On AMD GPUs
On X11
On Steam Deck
But not on NVIDIA + Wayland.
Request
This appears to be a driver-level or WSI-level incompatibility with DX9 presentation models.
Please advise whether Proton/DXVK can work around this or if NVIDIA Wayland WSI must be fixed.
Attached: steam-47780.log (Higher number = older log)
steam-47780 (1).log
steam-47780 (2).log
steam-47780 (3).log
steam-47780 (4).log
steam-47780 (5).log
steam-47780 (6).log
steam-47780 (7).log
steam-47780 (8).log
steam-47780 (9).log
Proton versions
proton experimentalx1 2025-12proton 5.0-2x1 2020-02proton 3.7-5x1 2018-08proton 3.7-4x1 2018-08
Launch options
PROTON_LOG=1x1 2025-12PROTON_NO_ESYNC=1x1 2025-12PROTON_NO_FSYNC=1x1 2025-12PROTON_USE_WINED3D=1x1 2025-12WINE_CPU_TOPOLOGY=8x1 2025-12
Launch lines
Upstream links
- ValveSoftware/Proton/issues/9336x1 2025-12
- ValveSoftware/Proton/issues/3651x1 2020-03
- ValveSoftware/Proton/issues/1363x1 2018-09
Arch Linux (4.18.5-arch1-1-ARCH)
i5-3470 / GTX 970
NVIDIA 396.54
Proton 3.7-4 Beta
System Info