Tracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com
472
stars
38
forks
source link
[LINUX] Engine behaves as if in no_focus_sleep mode, but only when focused (locked at unplayable fps unless window focus is lost) #2695
Are you using the latest stable video driver available for your system? Yes
Have you verified the game files?: Yes
Please describe your issue in as much detail as possible:
Some short while after starting a match, the FPS drops from a stable 144hz to 19-41.
Bringing a different window in front, entering GNOME activities or starting the steam overlay unlocks the FPS until bringing the game in front again.
I feel like the energy saving mode or whatever turns on when the game is minimized instead turns on when the game is NOT minimized. Reinstalling the game seemed to fix this issue, but only for one match, after which the same issue occurs.
I'll test if playing the windows version via proton fixes this issue.
EDIT: Vac doesn't want me to play via proton.
EDIT2: The problem only occurs inside a match. The dashboard is always running well.
EDIT3: The problem can also occur in the dashboard, idk how to trigger it though
EDIT4: Changing texture quality unlocks fps for a few seconds
EDIT5: Changes to engine_no_focus_sleep have no effect.
EDIT6: Does not Occur on KDE Plasma, only on gnome.
Steps for reproducing this issue:
Start a Match
Wait a few seconds. Sometimes it takes a few minutes.
Your system information
https://gist.github.com/Bra7wurs7/9fee22a2b22b05f1e0dd0b0ba7d7769a
Please describe your issue in as much detail as possible:
Some short while after starting a match, the FPS drops from a stable 144hz to 19-41. Bringing a different window in front, entering GNOME activities or starting the steam overlay unlocks the FPS until bringing the game in front again. I feel like the energy saving mode or whatever turns on when the game is minimized instead turns on when the game is NOT minimized. Reinstalling the game seemed to fix this issue, but only for one match, after which the same issue occurs.
I'll test if playing the windows version via proton fixes this issue. EDIT: Vac doesn't want me to play via proton.
EDIT2:
The problem only occurs inside a match. The dashboard is always running well.EDIT3: The problem can also occur in the dashboard, idk how to trigger it though EDIT4: Changing texture quality unlocks fps for a few seconds EDIT5: Changes to engine_no_focus_sleep have no effect. EDIT6: Does not Occur on KDE Plasma, only on gnome.Steps for reproducing this issue: