4.8 causes white screen when launched from UDB

Is there something that doesn't work right in the latest GZDoom? Post about it here.

Moderator: GZDoom Developers

Forum rules
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.

If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.

Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!
peewee_RotA
Posts: 394
Joined: Fri Feb 07, 2014 6:45 am

4.8 causes white screen when launched from UDB

Post by peewee_RotA »

I updated to 4.8 for compatibility with Hands of Necromancy. Ever since upgrading, launching a test from Ultimate Doom Builder causes a white screen to appear. When I press ~ or Esc, the white screen goes away and the game functions normally.

The only other thing I could find was that iwad selection is off by default now. I know that there can be weird results when the wrong IWAD is loaded. So I turned the selection back on, and loaded the game normally to see if I could reproduce, but no dice.

Here's the resulting command line that the map editor launches:

Code: Select all

-iwad "C:\Games\hexen\base\HEXEN.WAD" -skill "3" -file "C:\Games\packs\xrpglevels" "C:\Games\packs\xrpglevels\xrpglevels.wad" "C:\Users\user\AppData\Local\Temp\4l080n3n\fxnvaf75.wad" +map MAP16  -file "C:\Games\xrpg\pk3\v1_4_1\xrpg.pk3" +playerclass "Random"
OS: Windows 10

Will follow up with a video.
peewee_RotA
Posts: 394
Joined: Fri Feb 07, 2014 6:45 am

Re: 4.8 causes white screen when launched from UDB

Post by peewee_RotA »

Video comparing 4.6.1 to 4.8
https://youtu.be/QxsJEeW7Nwc
Blue Shadow
Posts: 5032
Joined: Sun Nov 14, 2010 12:59 am

Re: 4.8 causes white screen when launched from UDB

Post by Blue Shadow »

I got this problem today (I'm assuming it's the same) with GZDoom 4.8.1 and OpenGL as the backend. Here is how it can be reproduced:
  • Start GZDoom from the command-line with the attached file, and Heretic as the game, while warping to E1M1. You shouldn't notice anything strange. Everything is fine.
  • Quit GZDoom, then start it again (from the command-line just like before), only this time warp to E1M2. The result is that you get a black/white screen.
Things to note:
  • The difference between the two maps is that in E1M2, in which the glitch happens, the player is facing away from the sky. Once the player turns around, and the sky comes into view, the glitch disappears.
  • You need to run a game that has a startup screen, like Heretic, Hexen and Strife. If you try the steps above with Doom (no startup screen), you won't get the glitch.
You do not have the required permissions to view the files attached to this post.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49188
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: 4.8 causes white screen when launched from UDB

Post by Graf Zahl »

Just warping to the original E3M8 will do the same. It looks like it needs one frame without 3D scene to fully initialize from the startup. Toggling the automap will also bring it back on track. It's also only in the regular GL backend. That's not going to be easy to find...
peewee_RotA
Posts: 394
Joined: Fri Feb 07, 2014 6:45 am

Re: 4.8 causes white screen when launched from UDB

Post by peewee_RotA »

Thanks for looking into this.
Laskow
Posts: 100
Joined: Tue Feb 16, 2021 7:35 am
Preferred Pronouns: He/Him

Re: 4.8 causes white screen when launched from UDB

Post by Laskow »

Sorry for bumping, has this bug been solved? I've checked the changelog since 4.9.0 but couldn't find anything related to it.

EDIT: Stupid English mistakes.
Last edited by Laskow on Sat Nov 16, 2024 10:32 am, edited 1 time in total.
User avatar
Rachael
Posts: 13835
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her

Re: 4.8 causes white screen when launched from UDB

Post by Rachael »

If it's still not moved to the closed bugs forum then no it has not been solved.

Return to “Bugs [GZDoom]”