Page 1 of 2
Gzdoom blank screen when booted
Posted: Mon Aug 08, 2011 17:54
by Mr. X
I've had this for a little while now. When i boot gzdoom i get the typical "unsupported" display screen with a few moments of it being blank. This seemed to happen when i deleted my .ini file.
Is something wrong with my drivers? I have a Nvidia GT 240
Re: Gzdoom blank screen when booted
Posted: Mon Aug 08, 2011 22:21
by Gez
Does it create a new ini? Does ZDoom work?
If so, use ZDoom to set the video mode to windowed and try again.
Re: Gzdoom blank screen when booted
Posted: Wed Aug 10, 2011 3:59
by Mr. X
Yes a new ini file appears upon starting. Software renderer seems to boot just fine when alternating windowed mode as well.
I just did a fresh driver install and the problem still persists. The opengl renderer simply refuses to show up.
Re: Gzdoom blank screen when booted
Posted: Sun Aug 14, 2011 22:55
by Mr. X
Bumping to make sure the devs seen my reply
Re: Gzdoom blank screen when booted
Posted: Mon Aug 15, 2011 5:05
by Edward850
By any chance, do you have
triple buffering switched on?
GZdoom doesn't work (for me anyway) when this is switched on.
Re: Gzdoom blank screen when booted
Posted: Mon Aug 15, 2011 8:56
by NeuralStunner
Interestingly, it works for me with triple buffering, though it messes with the transitions (wipe, fade, &c.).
Re: Gzdoom blank screen when booted
Posted: Mon Aug 15, 2011 9:38
by Edward850
Must be a case-by-case then. It completely dies on my laptop.
Re: Gzdoom blank screen when booted
Posted: Tue Aug 16, 2011 21:40
by Mr. X
Edward850 wrote:By any chance, do you have triple buffering switched on?
No, settings are the exact same as yours however.
I got the opengl renderer to show up, but only in windowed mode. It goes blank and flashes black and grey upon switching to fullscreen.
Re: Gzdoom blank screen when booted
Posted: Tue Aug 16, 2011 21:45
by Gez
Is vsync off?
Re: Gzdoom blank screen when booted
Posted: Tue Aug 16, 2011 21:56
by Mr. X
No i always use v-sync
Re: Gzdoom blank screen when booted
Posted: Fri Sep 02, 2011 22:14
by Mr. X
Well i think i've finally got the solution to this problem. It seems my screen resolution was far too small when in fullscreen (something along the lines of vanilla doom's resolution) and it would not let me view it. I set my res to 1280x720 and that seemed to fix my problem. I'm still not sure where the core issue lies.
Re: Gzdoom blank screen when booted
Posted: Mon Sep 26, 2011 18:43
by Mr. X
Just figured out the source of the problem. It's caused from Jodwin's C#4rp Doom launcher. Upon using gzdoom with it (and possibly a pwad) It causes the - and = screen adjustment keys to become unusable. THEN upon deleting the ini file after restarting the screen becomes blank. The method i posted above fixes this problem. I'm not sure if Gzdoom is at fault here or the launcher, but i will bring it to Jodwin's attention as well just to reassure.
Re: Gzdoom blank screen when booted
Posted: Mon Sep 26, 2011 19:36
by Gez
Now that's weird. Why would it hijack the -= keys?
Re: Gzdoom blank screen when booted
Posted: Mon Sep 26, 2011 19:44
by Jodwin
Gez wrote:Now that's weird. Why would it hijack the -= keys?
It doesn't. -= keys work just fine for me, and in fact the launcher goes into a frozen state whenever the game starts (this is done to ensure proper cleaning of temporarily extracted zips after game ends):
Code: Select all
(.net 2.0)
private void RunThePort(string portPath, string commandLine)
{
this.Enabled = false;
Process p = new Process();
p.StartInfo.WorkingDirectory = Path.GetDirectoryName(portPath);
p.StartInfo.FileName = portPath;
p.StartInfo.Arguments = commandLine;
p.Start();
p.WaitForExit();
this.Enabled = true;
}
Re: Gzdoom blank screen when booted
Posted: Mon Sep 26, 2011 20:10
by Mr. X
Jodwin wrote:Gez wrote:Now that's weird. Why would it hijack the -= keys?
It doesn't. -= keys work just fine for me, and in fact the launcher goes into a frozen state whenever the game starts (this is done to ensure proper cleaning of temporarily extracted zips after game ends):
Code: Select all
(.net 2.0)
private void RunThePort(string portPath, string commandLine)
{
this.Enabled = false;
Process p = new Process();
p.StartInfo.WorkingDirectory = Path.GetDirectoryName(portPath);
p.StartInfo.FileName = portPath;
p.StartInfo.Arguments = commandLine;
p.Start();
p.WaitForExit();
this.Enabled = true;
}
That's very strange. I'm assuming this a minority case im dealing with then.