ECB

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

Yes, but the pay for other jobs is even worse!

[–] 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...

[–] 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 1 points 7 months ago (1 children)

This is using the native build

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

Nope, this is the native build

 

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!