When using “Play In” to launch the game from the editor, I usually use “New Window At / Default Player Start.”
Since Beta 5, I’ve increasingly been seeing that the gameplay window often (but not always) sorts behind the editor window, and refuses to put itself in the foreground even if I alt-tab over to it. Sometimes I can get around this by repeatedly hitting “Stop” and then “Play In” again, but not always.
I’d like to believe this could be a problem with my code, but I don’t see anything or any changes that could be causing it.
Is there something I can do to make sure the window stays in the foreground, or is it an editor setting I can tweak, or a bug …?
It doesn’t happen to me so often but when it happens i hit the windows key then click on the game window to get it to foreground.
Thanks – that’s a good workaround, but I’m wondering if there’s a more proper fix. It shouldn’t happen in the first place.
OK – I’ve figured this out. It’s consistently caused by the little popups that appear in the lower right – “Navigation building completed [OK]”, “Static light building completed”, and “Map check OK.”, as well as “Autosave in N seconds.”
Whenever those are up, running “Play In / New Window At / [X]” ensures that the editor window is the foremost window, and my actual game window is behind it.
If I close these little message boxes and hit Play In again, my window appears in the foreground, as it should.
So, this is clearly a bug.
Hey Mothership team,
Thanks for your information! We have been able to reproduce this issue internally and have filed a defect report. Hopefully this issue will be fixed for a future Rocket Beta release.
Thanks!
-Steve