Hi all, I have recently installed Bazzite, after previously being on Nobara.
I have been playing Dave the Diver and DOOM (2016), both through Steam, and I get pretty serious input lag. A second or more delay at times, generally when FPS is struggling.
I’m running on a laptop with integrated graphics, so the struggling integrated GPU is not a surprise, but I didn’t have this input lag issue with the same games on Nobara.
Any tips on a setting or something to help this?
I have lowered graphics settings to help with FPS, but ultimately I am not going to be able to avoid occasional FPS dips. The mouse input is instant, it’s just an issue with the keyboard.
Any help appreciated!
Edit with solution: it seems the problem is IBus, see this comment: https://lemmy.nz/post/23401044/15684126
Basically the solution is to add IBUS_ENABLE_SYNC_MODE=2 to /etc/environment and restart.
Hmm.
Both games you listed appear to run in Proton.
Dave the Diver is a Unity game, and Doom (2016) uses id Tech 6, so not a lot of common underlying technical infrastructure at the game level. I can’t imagine that it’s a common bug in both games.
That does kind of suggest something related to Proton, between Linux and the game, but I don’t know of anything that could create a backlog at the Proton level. I mean, keyboard events aren’t terribly heavyweight.
I haven’t played Doom (2016), but it’s a multiplayer game and some multiplayer games might have network latency for movement produce delay, but not for simply panning the camera — though I’d think that this would have more-sophisticated client-side prediction stuff; Quake II did. Dave the Diver is singleplayer, though, so if the mechanism is the same, shouldn’t be a network issue.
I don’t know, frankly. Kind of drawing a blank. Maybe try, in Steam’s Compatibility settings for the game, a different version of Proton? Not that I can think of a specific mechanism that would cause this, but I can’t think of much else that would be shared between the games, wouldn’t affect the mouse, and would affect the keyboard, and that you could readily change.
EDIT: One other possibility — maybe try disabling Steam Input for the game and see if it affects the issue? Steam does do some processing. I can’t think of any reason that it’d insert a lot of latency, but it’d be one of the few other things that would live between the kernel and the game.
EDIT2: Actually, no…I don’t think that Steam Input touches keyboard input, based on a quick search. Just controller stuff.
So this is a bit of a dumb solution, but I went to the accessibility settings in the OS and dropped the repeat frequency a bit. Now it seems to work fine!
It did seem like the events were triggering faster than the games could process them, so dropping the repeat speed a little stopped the events queueing up.
Okay, sounds good! Glad to hear it.
That’s getting old school. I had to do the same thing to get Shovel Knight to accept input properly about 10 years ago.
I sent a message to the dev about it, but there wasn’t a Linux port yet so they were stumped. I changed the repeat rate of the key input in kde and there it went like magic.