0003359: Zandronum not taking mouse\keyboard input in fullscreen.

Notes
(0018993) WubTheCaptain (reporter) 2018-01-18 04:17	Ditto here on GNU/Linux, I haven't touched Zandronum for a month or two. I can't stay in fullscreen either, it throws me back into windowed after few seconds. No stdout/sdterr. No idea how to debug this.

(0018994) WubTheCaptain (reporter) 2018-01-18 04:46 edited on: 2018-01-18 04:46	Happens (mostly) with the OpenGL renderer, but not the software renderer. Happens at 2560x1440 resolution, but not 5120x1440. Software renderer gets confused of resolutions with "toggle fullscreen". Might go into windowed 1600x900 or so, but the game thinks it is in fullscreen. May also go to 1600x900 fullscreen with blackboxing. Native resolution is 2560x1440. The cursor in menu may be selected over a non-existent resolution (blank) after some trickery. Same with no PWADs, clear configuration.

(0018995) WubTheCaptain (reporter) 2018-01-18 04:57 edited on: 2018-01-18 05:00	The OpenGL renderer won't take my mouse input at all in fullscreen (except for 1 frame during Ctrl + F shortkey in i3 window manager for toggle to windowed/fullscreen). Software renderer is odd and follows this cycle with "toggle fullscreen" in console: Fullscreen 2560x1440; fullscreen is true Windowed 2560x1440; fullscreen is false Windowed 1920x1080; fullscreen is true; mouse won't work, keyboard works; Windowed 2560x1440; fullscreen is false; Sometimes it gets stuck between 3 and 4, until the resolution is changed again in the menu. Also very rarely, 2560x1440 fullscreen true but it appears as windowed on desktop.

(0018996) WubTheCaptain (reporter) 2018-01-18 05:06	Okay, this happened: Start with fullscreen 2560x1440. "fullscreen false" in console to go to windowed 2560x1440. "fullscreen false" (again) in console to go to windowed 1920x1080 and it gets confused. "fullscreen true" attempts to fullscreen, but goes back to windowed 1920x1080. Then it resets to fullscreen 1920x1080 few seconds later and loses both keyboard and mouse input. I had to switch to tty2 and pkill zandronum.

(0018997) WubTheCaptain (reporter) 2018-01-18 05:09	None of this happens in GZDoom 3.1. I don't have GZDoom 1.8.6 installed right now, but I can try there if needed.

(0018998) Leonard (developer) 2018-01-18 16:30	That would help, we could then think about back-porting the relevant GZDoom fix if it happens there too. 1.8.6 can be downloaded from the rules page.

(0019000) WubTheCaptain (reporter) 2018-01-18 21:03	I built GZDoom 1.8.6 from source on Debian GNU/Linux buster/sid, using git tag g1.8.6. Happens there too. Toggling the fullscreen option in the menu with Enter key, the game remains in windowed mode and doesn't go fullscreen. I also sometimes lose mouse input, as previously described. Also in this situation where GZDoom 1.8.6 appears to be windowed on desktop: "fullscreen" is "true", "use_mouse" is "false" → mouse1 "+attack" goes through (system cursor shown). "fullscreen" is "true", "use_mouse" is "true" → mouse1 "+attack" doesn't work (system cursor not shown/captured by the game).

(0019001) WubTheCaptain (reporter) 2018-01-18 21:05	Worth noting the resolution doesn't screw up to 1920x1080 in GZDoom 1.8.6 with double-command "fullscreen false" at least, while it does in Zandronum.

(0019002) WubTheCaptain (reporter) 2018-01-18 21:11 edited on: 2018-01-18 21:14	Hardly relevant, but I'll mention it anyway: Also in GZDoom 3.2.5, the i3 window manager "Meta + F" [sic to previous] fullscreen toggle is independent of the ingame's fullscreen option. Essentially, the "fullscreen" cvar is disregarded and the cursor boundaries aren't respected in any scenario (while they are in Zandronum 3 and GZDoom 1.8.6).

(0019003) HellBlade64 (reporter) 2018-01-19 09:03	I dunno about anyone else, but I was able to fix my case. I just have to close TeamViewer when Zandronum is open. Conveniently, there's another tracker tracking that very issue.

Only registered users can voice their support. Click here to register, or here to log in.
Supporters:	WubTheCaptain
Opponents:	No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2017-12-28 06:00	HellBlade64	New Issue
2018-01-18 04:17	WubTheCaptain	Note Added: 0018993
2018-01-18 04:46	WubTheCaptain	Note Added: 0018994
2018-01-18 04:46	WubTheCaptain	Note Edited: 0018994	View Revisions
2018-01-18 04:57	WubTheCaptain	Note Added: 0018995
2018-01-18 05:00	WubTheCaptain	Note Edited: 0018995	View Revisions
2018-01-18 05:00	WubTheCaptain	Note Edited: 0018995	View Revisions
2018-01-18 05:06	WubTheCaptain	Note Added: 0018996
2018-01-18 05:09	WubTheCaptain	Note Added: 0018997
2018-01-18 16:30	Leonard	Note Added: 0018998
2018-01-18 16:30	Leonard	Status	new => feedback
2018-01-18 21:03	WubTheCaptain	Note Added: 0019000
2018-01-18 21:05	WubTheCaptain	Note Added: 0019001
2018-01-18 21:11	WubTheCaptain	Note Added: 0019002
2018-01-18 21:12	WubTheCaptain	Note Edited: 0019002	View Revisions
2018-01-18 21:14	WubTheCaptain	Note Edited: 0019002	View Revisions
2018-01-19 09:03	HellBlade64	Note Added: 0019003
2018-01-19 09:03	HellBlade64	Status	feedback => new

Relationships