Open u00101010 opened 2 weeks ago
Hello @u00101010, your issue reads like https://github.com/ValveSoftware/Source-1-Games/issues/5767. Please check if the Steam overlay is enabled and working.
Have same behavior on CachyOS 6.11.5-2 same with enabled and disabled overlay what need to do?
It's all part of the ascension process, just a small foretaste of the new Mac/Linux GPU driver bugs that are about to drop. Embrace it brother, we're in for a ride ⬆️⬆️⬆️
Although I had Steam overlay disabled for a while and it only started happening now, turning it back on seemed to remedy the issue. I'll report back if anything changes.
I have to add something that I just found out. Could this possibly be a Steam-related issue?
I just had the exact same issue happen to me but with Warframe, which isn't a Valve/Source game (although it is running with Proton 9.0-3). The game had the same kind of lagging after about 30 minutes of playtime (once the camera and/or the cursor stopped moving) and when I restarted with Steam Overlay enabled it didn't happen anymore. Could this be related or just a coincidence? (Also, the overlay popup saying what keybinding you need to press to open the overlay that shows up on game start is forced English for some reason, it used to be correctly translated to match the Steam client language.)
I just wanted to add this, hope it helps somewhat.
I'm not having the same issue as you, but I can confirm that something seems off with steam. I just got a trap invalid opcode
error from steamwebhelper
process 🤷🏻♂️.
Folks over here are also reporting my beloved GPU errors.
I have this issue as well (with a different game though) since about a month (steam beta channel). I used to have this issue a couple of years ago (see https://github.com/ValveSoftware/Proton/issues/3316) but at some point it was fixed. Now it has reappeared. For me the solution is to set "LD_PRELOAD=" to empty in a game's launch options. Disabling Steam Overlay did nothing for me.
This is with CPU: 5950x GPU: 6900xt (amdgpu mesa-git) kernel: CachyOS 6.11.5-2
I tested with known good kernels and mesa versions but I still run into this issue.
I am on Kubuntu, also have this issue and it started like 2 days ago. Its quite a big issue, game does become unplayable.
I think I have the same issue after the Kez Update. I am stuck in the Home Screen cause my mouse clicks don't work at all. I can move the cursor but click does not work. Only after the new update. Hover effect also doesnt work.
I have same problem on Ubuntu.
I have same problem on OS: Linux Mint 21.3 x86_64 Kernel: 6.8.0-48-generic
Somehow enabling steam overlay fixing this issue for WH40K: Darktide.
Probably related and matches my experienced timeframe with the beta client: https://github.com/ValveSoftware/steam-for-linux/issues/11446
Lags occur with overlay on and off. If the game is started and minimized, then even after an hour there are no lags
*UPD: In the steam shortcut, I added the variable LD_PRELOAD="" In the properties of the game, I enabled overlay and wrote in the launch options LD_PRELOAD="" %COMMAND% In Steam setting (in game block), i enabled overlay
After that, the lags passed (maybe I'll check later which of these helps solve the problem)
I solved this issue by enabling steam overlay from steam settings .
Same on Linux pop-os 6.9.3-76060903-generic
I played 3 game and all of them started lagging on 29th minute.
Tested w/ both overlay enabled and disabled
Your system information
Please describe your issue in as much detail as possible:
Since yesterday's update, the game seems to suddenly have low FPS, but only when the camera or the cursor is in motion. It also lags when I move the camera with the arrow keys and not moving the mouse at all, and the cursor movement also does cause the issue regardless of the camera. I didn't experience anything similar before and I did not change anything myself.
Disconnecting and then reconnecting using the game interface does not solve the issue, but restarting the game itself does seem to help for a while.
Steps for reproducing this issue:
The closest I can give in this regard is that the error happened in this match 8023308342 at around the 30 minute mark, then I restarted the game and it did not happen at all in this 8023365960 but then I started this game 8023406556 and it happened at around 5 minutes in the game maybe.
Now writing this I noticed that in both cases it started happening when the game was running for about 30 minutes, regardless of the match (since the second match mentioned only lasted for 24 minutes + queue and pick time seems to add up to the 30 minute mark in the second occurrence in the 3rd game).