F5F Stay Refreshed Software Operating Systems All Proton games display very weak results

All Proton games display very weak results

All Proton games display very weak results

B
Beder822
Member
80
02-25-2018, 06:02 AM
#1
Hi everyone. I'm experiencing problems with my Arch running on KDE, especially with Proton games. Recently, GTA V, War Thunder, and BeamNG.drive have become much slower—sometimes freezing or stuttering. GTA V is particularly affected, dropping to around 10 FPS even when fully loaded. BeamNG.drive only works on smaller maps, which isn’t typical for my system. I’ve checked every Proton version, including two Glorious Eggroll updates, but the issue persists. I’ve tried reinstalling Steam, Proton, Wine, DXVK, and updated drivers, yet nothing improves. No unusual resource usage appears in htop, and temperatures are normal. I’ve also reinstalled the games themselves without success. My GPU isn’t failing, so it’s likely a software problem. Anyone else face this? I’m looking for advice or possible solutions. Thanks!
B
Beder822
02-25-2018, 06:02 AM #1

Hi everyone. I'm experiencing problems with my Arch running on KDE, especially with Proton games. Recently, GTA V, War Thunder, and BeamNG.drive have become much slower—sometimes freezing or stuttering. GTA V is particularly affected, dropping to around 10 FPS even when fully loaded. BeamNG.drive only works on smaller maps, which isn’t typical for my system. I’ve checked every Proton version, including two Glorious Eggroll updates, but the issue persists. I’ve tried reinstalling Steam, Proton, Wine, DXVK, and updated drivers, yet nothing improves. No unusual resource usage appears in htop, and temperatures are normal. I’ve also reinstalled the games themselves without success. My GPU isn’t failing, so it’s likely a software problem. Anyone else face this? I’m looking for advice or possible solutions. Thanks!

C
CrazyCake15
Junior Member
5
02-25-2018, 07:27 PM
#2
Checking your runtime setup: are you using Steam Runtime or Steam Native? If it's Steam Native, have you tested this Proton-GE Build (the one that doesn't depend on Steam Soldier Runtime, unlike regular builds)? Make sure you choose it under the compatibility settings for the game you're trying to test.

For launch options, consider adding "DXVK_HUD=full %COMMAND%" and capture the in-game output when stuttering. If no HUD appears, it might be falling back to Wine's OpenGL.

If the game doesn't launch, include "PROTON_LOG=1 %COMMAND%" in its launch settings and save the log to your home folder.
C
CrazyCake15
02-25-2018, 07:27 PM #2

Checking your runtime setup: are you using Steam Runtime or Steam Native? If it's Steam Native, have you tested this Proton-GE Build (the one that doesn't depend on Steam Soldier Runtime, unlike regular builds)? Make sure you choose it under the compatibility settings for the game you're trying to test.

For launch options, consider adding "DXVK_HUD=full %COMMAND%" and capture the in-game output when stuttering. If no HUD appears, it might be falling back to Wine's OpenGL.

If the game doesn't launch, include "PROTON_LOG=1 %COMMAND%" in its launch settings and save the log to your home folder.

C
crost95
Member
189
03-18-2018, 06:16 PM
#3
I think it's Native but I'm unsure. There might be a way to verify. I'll attempt it too.
C
crost95
03-18-2018, 06:16 PM #3

I think it's Native but I'm unsure. There might be a way to verify. I'll attempt it too.

A
Arte28
Member
68
03-18-2018, 10:01 PM
#4
Steam (Native) appears in the generated link. You can launch it using "steam-native" from the terminal. It's included in the "steam-native-runtime" package.
A
Arte28
03-18-2018, 10:01 PM #4

Steam (Native) appears in the generated link. You can launch it using "steam-native" from the terminal. It's included in the "steam-native-runtime" package.

T
Timoteus2811
Member
56
03-20-2018, 04:16 PM
#5
It appears the focus is on execution time, not native performance. With your guidance on logging, I can't reproduce the crash during startup. I'll keep working on it.
T
Timoteus2811
03-20-2018, 04:16 PM #5

It appears the focus is on execution time, not native performance. With your guidance on logging, I can't reproduce the crash during startup. I'll keep working on it.

A
Amicaty
Member
140
04-04-2018, 07:23 AM
#6
A
Amicaty
04-04-2018, 07:23 AM #6