If you change scaling to 100% it will remove that as 1080p thing I think
If you change scaling to 100% it will remove that as 1080p thing I think
WOkay, still happens after removing
env OBS_VKCAPTURE=1 %command%
FYes 100% scaling removed that! Thanks! Now i’m at peace.
A@Wheeler try adding this to launch option
WOn it. What does that do? I'm in wayland currently, that seem fine?
Ait disable ibus-daemon, seen someone reporting that affect keyboard
WI will also search for another native game I have after that.
Ai think proton still run as xwayland?
WThis appears to eliminate the unwanted behavior.
WAhttps://discussion.fedoraproject.org/t/keyboard-lag-in-games-after-upgrading-to-fedora-40-gnome/115506/4
https://discussion.fedoraproject.org/t/ibus-daemon-introduces-delays-and-even-locks-keyboard-up-in-some-steam-games/118095
maybe you can investigate further
https://discussion.fedoraproject.org/t/ibus-daemon-introduces-delays-and-even-locks-keyboard-up-in-some-steam-games/118095
maybe you can investigate further
Fedora Discussion
I found this bug report Proton#4571, and reading through it and the linked issue it seems some people have a similar situation to what you describe. It is suggested by some that the issue can be worked around by disabling repeating keys in Gnome. Give it a try and see if it helps: settings → accessibility → repeat keys
Fedora Discussion
So after rocking Fedora 40 Gnome for 2 weeks now, i came across a strange bug where the ibus system seems to lock up all keyboard interaction in some games (in Mechwarrior 5 it happens all the time). Before encountering the lock up problem, i always had the feeling that keyboard interactions seemed a bit delayed all around, especially compared t...
Aor maybe dev here knows whats going on
WThe problem in the 2nd link is exactly my problem. Seemed off, then seemed bad, then testing showed locked input and delayed input. I also tried
journalctl -f to no avail. The XMODIFIERS="@im=null" %command% you recommended seems to have fixed it, same as in the thread.WI appreciate the help with that. Would your guess be that this is a temporary workaround and that this sort of thing would get solved at some point?
AGitHub
Which distribution and version?: Fedora 40 Which desktop environment and version?: Gnome 46 Which session type?: Wayland Which application and version?: Xwayland Wine Games (mostly Guild Wars 2) IB...
KHow goofy
KNice find
WYeah I appreciate it!
WAnd if I wanted to combine
env OBS_VKCAPTURE=1 %command% with XMODIFIERS="@im=null" %command%, do you think env OBS_VKCAPTURE=1 XMODIFIERS="@im=null" %command% would do the job?KYep
Ayou just list it as key=value separated by space
Ano need for env right?
WSomeone in the github discussion of the issue recommended
killall ibus-daemon after booting.
RInstalling Bazzite on new hardware
RTesting things out
Ayou could try that, im recommending the env variable cause less intrusive
WYeah, I like that.
Athat bar is tiny lol
KIf that has no downsides it could be added to bazzite-steam
KAs a workaround
WIt took me a few days or weeks of "I think something is wrong but I'm not sure what." So some others -might- be affected but haven't identified what the deal is yet?
KI think Japanese and Chinese input make heavy use of ibus though
KYeah I'd love to know what sets it off, clearly not consistent
RI am running a 4K screen after all lol
WI don't know the first thing about ibus, but someone else in that thread mentioned that
IBUS_ENABLE_SYNC_MODE=2 makes it stop as well which could be lower-impact than disabling?
JYeah p. much reliant on it for IME features
Jit's possible to use fcitix with gnome I think but ibus is pretty well integrated standard
RWhat're you folks working on right now?
KLet me know if that works for you
WIBUS_ENABLE_SYNC_MODE=2 as a steam variable did not work for me.KIf it does I can see about automating it
KRip
JLinux be like we finally got good GPU support lets break keyboards now
WI am also including my vcapture thing, so will test the other recommended one with it to troubleshoot.
Aits all gui anyway you can just click it who need keyboard
WIncluding the obs_vkcapture=1,
OBS_VKCAPTURE=1 XMODIFIERS="@im=null" %command% works great. OBS_VKCAPTURE=1 IBUS_ENABLE_SYNC_MODE=2 %command% does not work.Atry =0 maybe?
WOn it.
WTho the github commenter said "It only happens with IBUS_ENABLE_SYNC_MODE=1 not in mode 0 or 2, seemingly because it never hits that codepath in mode 0 or 2."
WConfirmed with mode=0, the problem is still present.
WYour original suggestion still seems like the winner.
