ZDoom

SDL2 currently has problems with ibus, uim and other input systems. One thing you can do is wrap around gzdoom through a script that unsets XMODIFIERS before launching it.

yeah, but afaik ibus works with gtk/qt if specific env variables are set, not globally. then again, maybe not.

i wonder what will happen if i switch to another kb layout in ibus.

edit: it seems to have something to do with it. when i switch to german layout i can open the console. but i cannot close it, though - odd. i can do it if i switch back to original layout
i'll try disabling ibus globally


edit: i disabled ibus and went back to xcompose. things appear normal now.

yoshi314 wrote:not sure of that affects games, though.

I wonder about that, actually. Doesn't ZDoom handle keyboard input in some kind of raw fashion? So there's a possibility that it's interpreting both the raw signals from your input device, AND the signals already interpreted by iBus.

I'm assuming you're talking about this one: https://github.com/ibus/ibus

currently i am runnning g3.0pre-96-gdcded0e18 on linux, and it might be relevant that i use iBus as my input method on my desktop - not sure of that affects games, though.

Can you tell us which operating system, and which exact version of GZDoom?

I am using git gzoom, the problem appeared well before 3.0. Basically it seems that the inputs get doubled. Trying to open console opens and instantly closes it. Similarly trying to exit the menu to return to game brings it up again with instant flicker - i have to use the mouse.

The console messages report e.g that the follow mode on map switches instantly on and off per keypress. I am not exactly sure why is this happening. I can reproduce it on default configuration with no mods on stock wads.