Debugged game on Secondary monitor freezes on editor play

[matthewpaul-us]

Godot version

v3.3.4.stable.official [faf3f88]

System information

Windows 11 Pro 22000.258, AMD Ryzen 9 5900X, GLES2, NVIDIA GeForce GTX 1070, V. 496.49

Issue description

After setting the editor setting 'run\window_placement\screen' to "Next Monitor" or "Monitor 2" causes the white screen freeze. Returning it to the default ("Same as Editor") or "Monitor 1" with the editor on my main monitor allows the debugged project to run successfully. When the play button is pressed, the console shows the running command and a window opens, but the window freezes on a white screen and won't accept any input, including closing the window. Clicking stop from the engine closes the window without issue.

Exporting a project allows it to run without issue. This issue affects both Mono and normal version. Changing the graphics version from GLES2 to GLES3 doesn't make a difference.

I also tried testing on 3.3.2 and 3.3. Neither version successfully debugged and all presented with a frozen white screen

Log showing the project is requested to run.

picture of the window showing a white screen

Steps to reproduce

1. Create new project
2. Change editor setting run\window_placement\screen to open it on a non-main window
3. Create empty scene and save
4. Click run in the editor

Minimal reproduction project

Windows 11 White Screen MRP.zip

[matthewpaul-us]

@Calinou, I'm not sure this is a duplicate of #53485, as they aren't able to even get into the engine unless they run it from a command prompt. In my case, the editor opens and is responsive except for debugging. Additionally, I tried the work-around indicated and it still showed the white-screen freeze on play.

[Calinou]

This may be related to #20566.

Also, try compiling Godot with windows_subsystem=gui on the SCons command line. This will disable the console entirely (which means you won't be able to toggle it back on).

[matthewpaul-us]

I built the latest both with and without the windows_subsystem=gui flag and both were able to debug without issue. I'm going to see if I can pull the stable 3.3.4 down and recreate the issue.

[matthewpaul-us]

I pulled down 3.3.4-stable down and recompiled both with and without gui flag. Neither build successfully debugged and froze on white screens.

Both times I had an editor window pop up, so I wasn't sure I passed that parameter correctly. Just to make sure, after cloning, I execute the build by scons platform=windows windows-subsystem=gui. Is that correct?

[Calinou]

Just to make sure, after cloning, I execute the build by scons platform=windows windows-subsystem=gui. Is that correct?

It's windows_subsystem=gui, not windows-subsystem=gui.

[matthewpaul-us]

Ah, that was a type in the comment, when I built, I had an underscore. Good catch though.

I did just find out something that might make this not related to Windows 11. Right around the time I upgrade, I changed some of the editor settings to make it more relevant for 2D.

One of the settings is the run\window_placement\screen setting. Having that set to "Next Monitor" or "Monitor 2" causes the white screen freeze. Returning it to the default ("Same as Editor") or "Monitor 1" with the editor on my main monitor allows the debugged project to run successfully.

The bug appears to be related to showing the debugged game on my second screen. I didn't see any similar bugs, but I wasn't quite sure what to look for. I've updated the title as well. I'll make more changes to the bug report when I get a chance.

[fenix-hub]

@matthewpaul-us I'm having the same issue currently (on windows 11)

When I try to execute Godot Engine standalone version (from GodotEngine.org) or the Steam Version, whatever project I open or create, godot crashes.
The only way to make it work is to run godot from the Terminal. No error or strange logs whatsoever when it successfully opens projects anyway, which is a little bit weird (at least - I thought that something could be printed in console but not catched during crash).

I did just find out something that might make this not related to Windows 11.

I didn't have issues on W11 until this update.
May not be related, but it's the last day before Godot stopped working on my laptop.
I've been using 3.3.4.stable for a couple weeks on W11 without changing any editor settings.

[matthewpaul-us]

@fenix-hub There are several bugs that seem to hinge on Windows 11, but I think your issue might be a better fit for #53485 .

In that one, he can open the project manager, but every time he tries to launch a project, godot crashes. This crash doesn't happen when he launches from a terminal that was open before Godot was started.

For this bug, it seems that Godot can't initialize the debugged window when it is on a secondary screen. I can't test this against Windows 10, as I don't have a multi-monitor setup with Win 10 any more. This bug is tied to the editor setting run\window_placement\screen. When that setting is set so the screen opens up on the main monitor, debugging works as expected. When the debugged window opens on my second monitor, the window freezes on a white screen, but I can't see any errors thrown.

[mhilbrunner]

This may be a duplicate of #54076

[akien-mga]

Definitely looks so.

[dandeliondino]

I don't think this was a duplicate of #54076. I've been experiencing the same issue as described here. It is only the Run window that white screens and crashes, and only if it is set to open on a different monitor from the main project. Additionally, if it is set to open on the same monitor as the editor, after it opens, I can drag it to a second monitor without it crashing.

Godot 3.5 stable
Windows 11

Edit: However, this does look like a duplicate of #13208, which is still open.

[SuzukiStumpy]

I have this same issue (scene play freezes showing a white window on Monitor #2) with Godot v3.5.1 pre-built on Windows 10. Running on a nVidia 2080 card. Everything works fine on monitor #1. I've seen similar issue with the Roon application which also freezes when launched on screen #2. Not tried yet with the main editor window to see if that also hangs if launched on screen 2, but it certainly functions fine if launched on screen 1 and moved.