Only recently, I began having issues with the devbuilds of GZDoom. I keep swearing it's something wrong with my computer, but whenever I load up a different version, such as GZDoom 1.9.1-- not 2.1.1, it's just as bad as what I'm experiencing now-- it works fine. The program gives me no warning of error before everything loads up. Rather, the game loads just as it should. All the menu selections and the logo are showing with no glitch, all until I launch the darn game.
This looks like some hardware problem. If it is this random that some things get rendered and others do not it has to be system specific, especially if it happens in both 1.9 and 2.1 which have completely different rendering code.
What's your graphics hardware and how does other GL software fare?
My graphics is an AMD-A4-- at least I think that's what the graphics is-- and other programs work pretty well. Zandronum, for an example. As far as OpenGL goes, I've only had issues with this. Only.
Could it be that I must have done something wrong, or a virus might have done something?
I have no idea what could cause this. If Zandronum works, can you try some other devbuilds from drdteam and see when it started, since you said it's only with recent ones.
Out of what I have tried, only the 1.x builds seem to really work. I tried four versions on both sides of 2.x and 1.x builds, and it seems only the 1.x builds work.
Even the Zandronum 3.0 beta seems to work, though I suppose that is a different code after all. To me, I find it strange as how I have two computers and this is the one that runs heavier games better, yet the other computer can run the 2.x versions. Most of the time when I played Doom or otherwise, it was on the other computer.
Can you post your entire startup log? You get that when starting 'gzdoom +logfile log'.
Also, did you have a recent graphics driver update? Not that AMD did what happened multiple times over the past few years and released a driver that had horrendously broken OpenGL support.
Last option: Start GZDoom 2.x with '-gl3' on the command line.
I can't seem to get the startup log. I see it loading everything, but I'm not sure. Could you explain that?
I've never grabbed the startup log before now.
You have to start gzdoom from a Windows command prompt where you enter 'gzdoom +logfile log'. That will save a file called 'log' to your hard drive. Please post the contents of that file.
It doesn't load any of those extensions. That's the one your hardware supports, i.e. what OpenGL returns when I ask it for its supported extensions. GZDoom only uses a tiny number - none of which your hardware supports. And that's what I wanted to know, if it's the modern render path that gets used here. It doesn't. Which also answers the question about '-gl3'.
But what about the driver? Do these problems coincide with a new driver version? Or is it something that happened from a specific GZDoom version onwards?
Alright. That does make a little more sense. As far as my driver goes, I don't believe I've had a driver update in a while. Only last year, I think. Thinking about it, could it be I need to update it? Or something else?
But as for specific GZDoom versions, it seems to happen with all of the 2.x versions.
The hardware should be good enough for GZDoom 2.x. But this is not the first time that some weird shit got reported for some of the more obscure AMD GPUs.
WinterSlave wrote:I went into the device manager and it says the processors are up to date.
And on the topic of weird shit: It's not the first time?
No, I am one of the people Graf is talking about.
On my server system, I run an HD4850. It's a great card for its time but it is 6 years old. The latest driver released for it is glitchy as hell in OpenGL. Anything GZDoom 2.x+ will not render properly.
I reported the problem to AMD but they were less than helpful.
On newer ATI's, everything is fine and dandy - they get their driver updates and this particular bug is fixed. But if your ATI is about ~4-5 years old, you're screwed.
