I've seen this same issue with all my proton games. I'm on fedora under wayland with an amd rx 580 and a ryzen 7 5800x. I'm glad I'm not the only one. I've been looking for so long for someone else with this error. Can you tell me what version of mesa you're running? I started noticing this kind of input lag after updating to version 24.0.8. But it might be another kind of package. I've tried using older versions of proton, and it still did it, so I believe it may be a different package that's doing it.
When I saw you also mentioned mangohud, I tried uninstalling mango hud from my system to see if that would solve the issue. I found that a lighting issue that I had been experiencing is now gone, I'll see if I experience this issue again, but I would assume that mangohud might be what is causing the issue as well.
When I saw you also mentioned mangohud, I tried uninstalling mango hud from my system to see if that would solve the issue. I found that a lighting issue that I had been experiencing is now gone, I'll see if I experience this issue again, but I would assume that mangohud might be what is causing the issue as well.
If I don't limit it with Mangohud to 30fps, I end up with weird frame rate issues. It runs at 50fps standard, then every mission I did it dropped 15fps additive. I can't play some games (AC:Valhalla) without doing so. Besides, I think I've tried it without and ran into the same issue, it just happened a bit less. Still ended up in me dying too many times.
I just ran into it tonight again, so I'd have to agree with you. One other thing I noticed is that it happened with timeshift was doing a backup. Do you use timeshift at all to image your system?
I just ran into it tonight again, so I'd have to agree with you. One other thing I noticed is that it happened with timeshift was doing a backup. Do you use timeshift at all to image your system?
I did, ages ago. It stopped compiling a few years ago on Arch, so I removed it and it has not run since.
Accidental close issue tap, apologies. Issue still open.
I've seen this same issue with all my proton games. I'm on fedora under wayland with an amd rx 580 and a ryzen 7 5800x. I'm glad I'm not the only one. I've been looking for so long for someone else with this error. Can you tell me what version of mesa you're running? I started noticing this kind of input lag after updating to version 24.0.8. But it might be another kind of package. I've tried using older versions of proton, and it still did it, so I believe it may be a different package that's doing it.
Currently on 24.0.7-3 here on Arch rolling, so this seems unrelated.
I just ran into it tonight again, so I'd have to agree with you. One other thing I noticed is that it happened with timeshift was doing a backup. Do you use timeshift at all to image your system?
I did, ages ago. It stopped compiling a few years ago on Arch, so I removed it and it has not run since.
Timeshift uses cronie to schedule rsync. Make sure that the cron job is not still configured. I uninstalled timeshift and it deleted cronie with it, and I haven't experienced the issue since. You can check your crontab with crontab -e. The cron job is configured under root so make sure your root before running.
Replying to https://github.com/ValveSoftware/Proton/issues/7722#issuecomment-2151050839
Checked, nope that's not it. Empty for root. For non-root, there's only a mention of Bluetooth.
I get all these symptoms on a whole bunch of games, too. A non-exhaustive list I've see this bug on: Ravenfield (when running the Windows version), Mechabellum, Tom Clancy's Ghost Recon Wildlands, Road to Vostok Demo, and Crime Boss: Rockay City. As with OP, the mouse in unaffected; it's only keyboard input.
I'm running Artix Linux with kernel 6.9.7-hardened1-1-hardened, NVIDIA GeForce RTX 2080 Rev. A using their dkms driver 555.58.02, and 12th Gen Intel i5-12600K. I don't have mango hud installed, and I've tried multiple Proton versions without a change in behavior.
It seems more likely to happen when the system struggles under high load, but I've noticed it happen with FPSes in the hundreds as well. If I run Ravenfield with a hundred bots on a small map and I get around 20 FPS then the problem happens constantly, my inputs fall behind more often than functioning normally.
Replying to https://github.com/ValveSoftware/Proton/issues/7722#issuecomment-2209458709
I am willing to believe this is potentially the problem too. Also, something to note here - we're both using the DKMS Nvidia drivers. I wonder if that could be the culprit?
Replying to https://github.com/ValveSoftware/Proton/issues/7722#issuecomment-2209458709
I am willing to believe this is potentially the problem too. Also, something to note here - we're both using the DKMS Nvidia drivers. I wonder if that could be the culprit?
I'm not sure that it's the drivers because I experienced the same thing with AMD, but it was only when timeshift was making an image and taxing my system, so it could just be when the system is under heavy load.
I'm not sure that it's the drivers because I experienced the same thing with AMD, but it was only when timeshift was making an image and taxing my system, so it could just be when the system is under heavy load.
Although that should be so, I've made sure that in these applications that:
Also, this problem is getting worse over time, as if decay is involved. I noticed it in Blender recently a bit, which is not running on proton, so this is some system issue.
I noticed it in Blender recently a bit, which is not running on proton, so this is some system issue.
I don't notice the issue on native Linux programs myself. For example, running Ravenfield's linux port (it has issues with the shaders of mods, so I use the Windows version normally) under the same conditions works fine. I don't know Blender enough to do something to tax my system, so if it is system related, it's specific to how Proton and Blender interact with it.
I've seen this happen with a few games now:
Helldivers 2 is by far the worst of the bunch. Just sitting on the settings menu I can watch the rgb turn off and on on my keyboard. Many of these games end up either not registering a press or registering as a sticky key press so I keep moving even though I'm not longer pressing the key. I can watch the rgb cut out on occasion when playing games as well.
I've checked a lot of similar things to @ThorinWolf. My issues also seem to get worse as I play over time. All of my devices are wired. It doesn't seem to matter if I'm using mangohud or not to limit FPS or if it is even installed. I've also seen this persist over a couple setups, both Linux Mint and now Bazzite. Many of the culprits that have been suggested I've also looked into like making sure my CPU/GPU aren't sitting at 100% all the time. I don't current have Timeshift setup on Bazzite, but it has the same issue so I don't think it is Timeshift either.
I'm also on an nvidia card, a GTX 1070 with an AMD CPU. Both installs I did are on X11, so I don't think this is a wayland issue either.
A couple oddities I have seen and not mentioned in the thread are these:
I wonder if anyone else has tested a controller in some of these games vs the keyboard. I need to retest them, but so far in games I use a controller I don't have input issues vs the games I use my keyboard and mouse.
Edit: When double checking D3, I noticed both Helldivers 2 and D3 regularly cut out my keyboard during the opening cinematic.
I've been looking around, and I've found a couple other issues that describe very similar problems to what I'm seeing:
ibus restart also didn't work as with setting IBUS_ENABLE_SYNC_MODE=2.ibus restart and export IBUS_ENABLE_SYNC_MODE=2 solving his issue. Installed Steam with Flatpak.killall ibus-daemon; I need to test if this works for me.Installing "fcitx5" and adding the following in steam game command line args has helped so far (I'll edit this post if it did not work):
XMODIFIERS=@im=fcitx %command%For those coming here for a Manjaro (possibly Arch) solution.
This suggests that this is an ibus issue, and I am running ibus 1.5.30-1 on my machine. Trying the above workaround of using fcitx5 as the input method instead on Ravenfield under the same (100 bots) and worse (200 bots) conditions that showed the bug before, no longer gives me the symptoms. I'll report back in a few days if I see anything noteworthy on any other titles.
Longer discussion. Closed as solved, but people are still reporting seeing it. One workaround from this comment worked for me (Regression) TrackMania Nations Forever under Wine does not always register key releases under IBus 1.5.28 ibus/ibus#2480 (comment)
Installing "fcitx5" and adding the following in steam game command line args has helped so far (I'll edit this post if it did not work):
XMODIFIERS=@im=fcitx %command%
For those coming here for a Manjaro (possibly Arch) solution.This suggests that this is an ibus issue, and I am running ibus 1.5.30-1 on my machine. Trying the above workaround of using fcitx5 as the input method instead on Ravenfield under the same (100 bots) and worse (200 bots) conditions that showed the bug before, no longer gives me the symptoms. I'll report back in a few days if I see anything noteworthy on any other titles.
This also works for me (in Helldivers II), after I fully switched to fcitx5 to replace iBus. This is indeed the cause of this bug.
I've been testing fcitx5 and it is not resolving all of my issues. I still have my keyboard cutting out in specific spots. Intro videos and settings menus continue to be the worst offenders. The intro video, settings menus, and drop pod menu of Helldivers 2 all cause my keyboard to cut out over and over every few seconds. Nothing else cuts out. Mouse and game controllers are fine.
ge-proton8-11x1 2024-05ge-proton9-4x1 2024-05XMODIFIERS=@im=fcitx %command%x2 2024-07
Compatibility Report
System Information
I confirm:
Symptoms
Movement gets stuck in one direction for a time, refusing all keyboard inputs. Tabbing to another window still allows me to type, and stops the movement, but still refuses input. It still accepts mouse input and nothing else. When it become unstuck, all attempted key presses execute in sequence (like a buffer) - if keys were only pressed, it will be rapid; if they were held down, it becomes stuck again until the time held has passed and buffer is empty. This makes Helldivers II unplayable, though it's not as egregious when it occurs for Timberborn as it doesn't necessitate constant keyboard input. Video attached to show what occurs during this time.
Reproduction
Simply move around using movement. Not limited to WASD, have tested with TFGH also. Occurs at random. Seems to happen more if I limit frame rate using mangohud to 30fps. Using gamemoderun in order to double performance.
steam-553850.log
https://github.com/ValveSoftware/Proton/assets/59799077/fb707707-701b-4cbd-8975-7b1883b26312