this post was submitted on 27 Apr 2024
59 points (100.0% liked)

Linux Gaming

15892 readers
6 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago
MODERATORS
poVoq@slrpnk.net
Quintus@lemmy.ml
mudle@lemmy.ml
59
(SOLVED) Stutters when moving mouse after 20-30 minutes of playing (discuss.tchncs.de)
submitted 7 months ago* (last edited 7 months ago) by ECB@discuss.tchncs.de to c/linux_gaming@lemmy.ml
11 comments fedilink hide all child comments
 

I have a weird bug in TF2 where the game runs perfectly (144 FPS) for the first 20-30 minutes and then suddenly begins to have stutters(?) whenever I move the mouse or press a key on the keyboard. So far I haven't been able to isolate what causes the stutters to start, but it's always the same pattern, with perfect performance followed by sudden choppyness.

If I don't press anything, the game continues running smoothly at 144 FPS, even if I'm moving in game.

For reference, I'm on OpenSUSE Tumbleweed using Gnome Wayland and I have an AMD card.

The closest thing I've stumbled upon is some talk of polling rates being too high on the mouse, however I'm already tried reducing these and nothing happens.

Anyone have any ideas? I can't find anything really similar out there...

EDIT: The issue was solved by turning on the in-game steam-overlay. I had had it off for years, but for some reason having it off causes this issue in certain source-1 games... weird, but it's working great now!

top 11 comments
sorted by: hot top controversial new old
[–] d3Xt3r@lemmy.nz 14 points 7 months ago (1 children)

This is a known issue with TF2, you'll need to switch to OpenGL to fix it. However, you may also need additional launch options as listed here (but try just the OpenGL switch first).

[–] ECB@discuss.tchncs.de 2 points 7 months ago

Yeah, I'll have to try opengl out...

Thanks!

[–] ECB@discuss.tchncs.de 9 points 7 months ago (1 children)

Update:

Seems that this is an issue some others are having when using Vulkan with the new 64-bit build after the recent update.

I've added some information about my setup, so hopefully they figure it out at one point.

Until then...back to opengl!

[–] ECB@discuss.tchncs.de 8 points 7 months ago

Second Update:

This is (weirdly enough) an issue connected to the having had the in-game steam-overlay disabled.

I've turned on the steam-overlay and everything is working flawlessly!

I would love to see why that makes a difference...

[–] bjoern_tantau@swg-empire.de 4 points 7 months ago

Had something similar a few years ago. I think it was in combination with Lutris. No idea when it stopped.

Do you have the Packman repository enabled? Maybe it was fixed for me with a newer Mesa or something.

I can't even remember whether I had that on the Steam Deck or on my OpenSUSE desktop. Unfortunately I can't find a bugreport about this.

[–] gray@pawb.social 3 points 7 months ago (1 children)

Are you running TF2 through proton? TF2 has a native Linux build.

[–] ECB@discuss.tchncs.de 4 points 7 months ago

Nope, this is the native build

[–] ElectroLisa@lemmy.blahaj.zone 3 points 6 months ago

TF2 spaghetti code strikes again

[–] CosmicCleric@lemmy.world -3 points 7 months ago* (last edited 6 months ago) (1 children)

Honestly don't know if it's related or not, but the next version of Proton (I believe it's 9.0) that's coming out, has a lot of fixes, including for input issues.

~Anti~ ~Commercial-AI~ ~license~ ~(CC~ ~BY-NC-SA~ ~4.0)~

[–] ECB@discuss.tchncs.de 1 points 7 months ago (1 children)

This is using the native build

[–] CosmicCleric@lemmy.world -2 points 7 months ago* (last edited 6 months ago)

This is using the native build

Then I got nothing. Good luck.

Edit: Don't mean to be dismissive, I just have no knowledge on that client to help further.

~Anti~ ~Commercial-AI~ ~license~ ~(CC~ ~BY-NC-SA~ ~4.0)~