Page 1 of 1

[1.0.0.2] (and newer) Display Problems.

Posted: Thu Mar 23, 2006 1:52
by solarsnowfall
Starting GZDoom on higher resolution settings seems to have a 50/50 chance of completely glitching out the display, and I mean horridly. Unfortunately, any attempt at capturing this in action results in a normal screenshot. Changing the display settings, then back again, as well as starting it up on a setting of 800x600 seems to get rid of the problem. I can say with certainty, that at least half of the time I start up at 1280 x 1024 it happens.

What seems to be happening, is that the display is cut up in horizontal segments, which are displayed in varying erratic positions. It's not something minor either, it makes GZDoom completely unplayable. And managing to get into the video settings to alter them to get rid of the problem involves a bit of guess work. I hope this isn't deemed as yet another ATI specific hardware problem to remain unresolved...

Posted: Thu Mar 23, 2006 6:25
by Shinjanji
I noticed it happening in many versions, even before 1.0... It actually seems to happen less for me in the newer versions than before.

Also, instead of going to your display settings, just ALT+TAB to toggle window/fullscreen and back again. Or you could bind some out-of-the-way key to "vid_restart"

Re: [1.0.0.2] (and newer) Display Problems.

Posted: Thu Mar 23, 2006 10:08
by Graf Zahl
solarsnowfall wrote: I hope this isn't deemed as yet another ATI specific hardware problem to remain unresolved...

This is most definitely a driver problem. Since the screenshots come out correctly the cause must be somewhere between the driver and the hardware.

One thing you can try is to set gl_vid_refreshhz to a value you know to work. Some monitors like to report incorrect capabilities and this can easily result in garbage on the screen if the monitor isn't smart enough to swirch off.

Also check your 'rendering quality' settings. These should be as high as possible.

Posted: Mon Apr 03, 2006 5:18
by kc32
It's doing this to me, too. Usually restarting GZDoom fixes it though.

EDIT: ALT-TAB fixes it for me too.