Yeah 150% scaling. But not really sure why it would say as 1920x1080 there though.
Yeah 150% scaling. But not really sure why it would say as 1920x1080 there though.
HThanks for the advice. I used command prompt to verify SHA256 checksum that way and opened the text file and the checksums appear to match
HSo that rules that out...
WUpdate: Celeste DOES NOT exhibit the same keyboard behavior.
W
Aceleste is native
Aprobably proton lol
WWhat could be different about Celeste that Helldivers 2, Rocket League, and Doom Eternal all share. It's a much simpler game visually, but I couldn't manage to get even a little bit of keyboard input to queue up.
WIs Doom Eternal native? It has no compatibility layer selected:
W
Ano means default selected by valve
Aor default from your setting
Acheck game page if you want to know it native or proton
ODoom Eternal store page says OS is Windows only
WWait, I'm using
env OBS_VKCAPTURE=1 %command%see steam logo it means native
WOmiting
env OBS_VKCAPTURE=1 %command%
FSays 4k on the settings as well 
Aah maybe fastfetch detection being funny
WGotcha.
JOk yeah 150%. But yeah it just means even though its 4k, you’ve scaled it so it gives you as much screen real estate as 1080p
JIf 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 -fXMODIFIERS="@im=null" %command%I 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%XMODIFIERS="@im=null" %command%env OBS_VKCAPTURE=1 XMODIFIERS="@im=null" %command%Yep
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
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
