-
Notifications
You must be signed in to change notification settings - Fork 552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Multi-player: host opens windows before all players are connected - bad with fullscreen #2643
Comments
FWIW, on Ubuntu 22.04, I see the same behavior with 4.12.2 (was previously running 4.7). Last lines I see in the terminal as the game is starting (I am the host), is:
After that, I see nothing until the second player joins (only playing in 2 player coop mode). Also, In this state, I cannot hit 'Q' to quit like I used to be able to do in previous versions. I have to login remotely and kill it. |
i think this is from the launcher UI refresh? but there are big changes coming to networking, so it will probably be fixed only then |
Well I do everything on the command line, so not using any kind of GUI launcher... |
I think the OP is correct, gzdoom creates a window after the 'EFX Enabled' line I see:
Those are the lines I see after the 'EFX Enabled' line I quoted above - though I never see anything after that line in the terminal until I exit the games. I also run in fullscreen, so that whole monitor is unusable ("frozen") until either a player joins, or I kill the game remotely. |
the old launcher code handled the netgame connection window as well |
Fixed with f0ff273 |
GZDoom version
4.12.2
Which game are you running with GZDoom?
Doom 2
What Operating System are you using?
Linux x86_64
Please describe your specific OS version
Fedora 39
Relevant hardware info
Intel
Have you checked that no other similar issue already exists?
A clear and concise description of what the bug is.
The application windows opens before all players are connected.
This is especially a problem in fullscreen mode.
The first time I thought gzdoom had crashed (or became unresponsive).
Steps to reproduce the behaviour.
Explain how to reproduce
(because the application window has already opened and is full screen.)
This seems new with 4.12.x
Your configuration
Provide a Log
No response
The text was updated successfully, but these errors were encountered: