ProtonDB | User Profile for Eraser

Graphics:Missing Textures

DX12 is not working correctly. DX11 works fine

► Multiplayer

Overall (online):Didn't Work

Proton 6.3-6

Command & Conquer Remastered Collection

Petroglyph Crash Error is appearing any time when I try to start a match. Campaign or skirmish doesn´t change anything.

Tinker Steps:Switch to experimental, Set launch options

PROTON_USE_WINED3D=1 %command% NOSPLASHPRELOAD

Installs:Yes

Opens:Yes

Starts Play:No

Proton Experimental

Command & Conquer Remastered Collection

Works out of the box.

Input:Other

Keyboard only works in Desktop-Mode

Proton 7.0-6

Distro:SteamOS Holo

Kernel:5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb

RAM:15 GB

GPU Driver:4.6 Mesa 22.0.0-devel (git-676ccacebc)

GPU:AMD Custom GPU 0405 (vangogh, LLVM 13.0.0, DRM 3.45, 5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb)

CPU:AMD Custom APU 0405

Proton 7.0-6

Distro:SteamOS Holo

Kernel:5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb

RAM:15 GB

GPU Driver:4.6 Mesa 22.0.0-devel (git-676ccacebc)

GPU:AMD Custom GPU 0405 (vangogh, LLVM 13.0.0, DRM 3.45, 5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb)

CPU:AMD Custom APU 0405

God of War

Faszinating how good this worked out of the box.

Graphics:Other

If the game have to cache new shaders or parts of the levels I experied lags and framedrops for a few seconds.

Instability:Not Listed

Shader-Caching caused framedrops

Significant Bugs:

Steam-Link is still Switching the buttons LB with LT and RB with LT

Proton 6.3-8

Distro:Ubuntu 20.04.3 LTS

Kernel:5.15.0-14.1-liquorix-amd64

RAM:32 GB

GPU Driver:NVIDIA 470.86

GPU:NVIDIA GeForce GTX 1070

CPU:Intel Core i7-6700 @ 3.40GHz

Proton 6.3-8

Distro:Ubuntu 20.04.3 LTS

Kernel:5.15.0-14.1-liquorix-amd64

RAM:32 GB

GPU Driver:NVIDIA 470.86

GPU:NVIDIA GeForce GTX 1070

CPU:Intel Core i7-6700 @ 3.40GHz

Orcs Must Die! 3

Audio:Other

Not able to switch the language of the game

Significant Bugs:

Game is crashing in some movies

► Multiplayer

Overall (online):Excellent

Proton 6.3-5

Distro:Ubuntu 20.04.2 LTS

Kernel:5.4.0-74-generic

RAM:32 GB

GPU Driver:NVIDIA 460.84

GPU:NVIDIA GeForce GTX 1070

CPU:Intel Core i7-6700 @ 3.40GHz

Proton 6.3-5

Distro:Ubuntu 20.04.2 LTS

Kernel:5.4.0-74-generic

RAM:32 GB

GPU Driver:NVIDIA 460.84

GPU:NVIDIA GeForce GTX 1070

CPU:Intel Core i7-6700 @ 3.40GHz

5 years ago

Squad

EAC is still not working. After every restart I receive the error: Failed to Create IgameClient Instance. The game it self is starting fine.

5 years ago

Installs:Yes

Opens:Yes

Starts Play:No

Proton 5.0-9

Squad

EAC blocked: Null client.

Tinker Steps:Custom Proton: GE-Proton8-4, Changed configuration

Tried EAC installation from: https://squadfm.org/#installation-linux-only

Installs:Yes

Opens:Yes

Starts Play:No

Were not able to play in multiplayer as EAC is not able to download the required module. The fix from https://squadfm.org/#installation-linux-only didn´t change this beahvior.

Custom Proton: GE-Proton8-4

Distro:Ubuntu 22.04.1 LTS

Kernel:5.15.0-46-generic

RAM:24 GB

GPU Driver:NVIDIA 515.65.01

GPU:NVIDIA GeForce GTX 1070

CPU:Intel Core i7-6700 @ 3.40GHz

Custom Proton: GE-Proton8-4

Distro:Ubuntu 22.04.1 LTS

Kernel:5.15.0-46-generic

RAM:24 GB

GPU Driver:NVIDIA 515.65.01

GPU:NVIDIA GeForce GTX 1070

CPU:Intel Core i7-6700 @ 3.40GHz

Total War: WARHAMMER

Native version do not work anymore on Ubuntu 22.04 and Proton version is missing textures.

Tinker Steps:Switch to experimental, Set launch options

gamemoderun %command%

Graphics:Missing Textures

Tedxtures are missing and Unit-placement-Preview are not visible

Proton Experimental

Distro:Ubuntu 22.04.1 LTS

Kernel:5.15.0-46-generic

RAM:24 GB

GPU Driver:NVIDIA 515.65.01

GPU:NVIDIA GeForce GTX 1070

CPU:Intel Core i7-6700 @ 3.40GHz

Proton Experimental

Distro:Ubuntu 22.04.1 LTS

Kernel:5.15.0-46-generic

RAM:24 GB

GPU Driver:NVIDIA 515.65.01

GPU:NVIDIA GeForce GTX 1070

CPU:Intel Core i7-6700 @ 3.40GHz

Warhammer 40,000: Space Marine - Anniversary Edition

Tinker Steps:Other

Controler have npt been detected. To solve this change the layout to "Mous only" and go to options -> game options and enable the game pad. If this is not possible stay in this menu and change the layout back to default again. Now your controler should be detected. At least it solved the problem for me.

Control Layout:Switch To Official

Battery Performance:

Limit frequenzen to 40 fps Using FSR on 1152x720

Input:Controller Detection

Proton 7.0-4

Distro:SteamOS Holo

Kernel:5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb

RAM:15 GB

GPU Driver:4.6 Mesa 22.0.0-devel (git-676ccacebc)

GPU:AMD Custom GPU 0405 (vangogh, LLVM 13.0.0, DRM 3.45, 5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb)

CPU:AMD Custom APU 0405

Proton 7.0-4

Distro:SteamOS Holo

Kernel:5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb

RAM:15 GB

GPU Driver:4.6 Mesa 22.0.0-devel (git-676ccacebc)

GPU:AMD Custom GPU 0405 (vangogh, LLVM 13.0.0, DRM 3.45, 5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb)

CPU:AMD Custom APU 0405

Warhammer 40,000: Space Marine - Anniversary Edition

Tinker Steps:Other

Control Layout:Switch To Official

Battery Performance:

Limit frequenzen to 40 FPS and using FSR on 1152x720

Input:Controller Detection

Controler have not been detected. To solve this issue change to the layout "Mouse only" go to options -> game options and enable the controler. If the controler is not available stay in this menu and switch to the default layout. Now it should work.

Proton 7.0-4

Distro:SteamOS Holo

Kernel:5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb

RAM:15 GB

GPU Driver:4.6 Mesa 22.0.0-devel (git-676ccacebc)

GPU:AMD Custom GPU 0405 (vangogh, LLVM 13.0.0, DRM 3.45, 5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb)

CPU:AMD Custom APU 0405

Proton 7.0-4

Distro:SteamOS Holo

Kernel:5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb

RAM:15 GB

GPU Driver:4.6 Mesa 22.0.0-devel (git-676ccacebc)

GPU:AMD Custom GPU 0405 (vangogh, LLVM 13.0.0, DRM 3.45, 5.13.0-valve10.1-1-neptune-02144-g7fffaf925dfb)

CPU:AMD Custom APU 0405

XCOM 2

I played several hours and had to kill the game a few times for being able to proceed.