DRD Team

Blakestone wrote:..... I will try your file. What does it do?

It is just the ini file as generated by GZDoom when it is run for the first time.
I have it set up as to allow changes to the ini file as I update settings in the Options menus.

If you want to use it, simply rename zdoom-1200.ini to the filename of your ini file.
Because my ini file is pointing to different folders than where you have the IWADs located, I would suggest to have DOOM2.WAD in the GZDoom folder. Other than that, except for the screen resolution, everything else is fairly generic.

Well, I don't know if that will help, but it won't hurt to try.

Just out of curiosity, what make and model is your new monitor?

my monitor = Asus 22" I believe a ML22h.

I couldn't find ML22h, just ML228 or ML229.
But anyways ...

Just a thought.
If you are connecting to your computer through a DVI connection at the moment, then try an HDMI cable.
If your video card has one of those.

If that does not help, check with the store where you bought the monitor. There may be something wrong with it and they can test it.

The only thing that looks bad on my monitor is when im playing Doom. So im really thinking my monitor is not the problem. I have a gtx670 video card and is hooked up through hdmi. The picture is awesome when playing other games and when using my Doom editor of choice Deepsea, the picture is crystal clear but once I load up Doom it all goes to hell. I will try your file tomorrow when my computer buddy that knows how to try it comes around. Sorry im not the best with the software side of computers. I will let you know if the file has helped or not. Thank you again for your help dude. Doom rocks.

Well I tried your ini file and it worked, thanks man. This really improved my picture quality in Doom. A few problems just to tell you about. I play with free look off but the setting likes to switch back on its own. When that happens I have to go into the settings and turn it off. If free look is on then auto aim will not work and I love auto aim. Also the keys I choose for look up and look down (page up and page down) do not work for me. They are dead and do not do anything. The last prob I would like to address is now that the picture has cleared its self up, it plays a little choppy, like my computer is having a hard time with it. My computer is new and I built it with beautful parts so maybe the GZDoom coding is to blame for this. Maybe its the fact that a computer built in 2012 is not very compatable with a game that was pretty much made in 1994 except for the sector over sector and the no visplain overflow thing. God I hated the visplain overflow crap. When my textures and everything looked bad the game played better and smoother than now. Not your falt, its still looks better and I love it thanks dude.

GZDoom should work fine with modern computers. There's nothing choppy about it if set up properly.

I have a new system myself with a Geforce GTX 550 Ti and even on very demanding maps (like Hellcore's MAP09) I get far more than 150 fps. It's probably something in the .ini file you used that's badly configured.

The first thing you can try is set vid_vsync to 1 at the console. If the frame rate is higher than what your monitor can do you get very uneven performance. For some strange reason many players seem to think that higher = better in any case.

Depending on the game, I sometimes get sub-refresh rate FPS with VSync enabled. My 75Hz display gets upwards of 200 in most things, in a few games it'll drop down to 40-50 once VSync is on. I'd expect it to fluctuate down to 70 at worst.

Also, the software renderer looks very choppy if I enable VSync.

In most other cases there's no perceptible difference for me. But VSync is extremely helpful for certain folks, like other hardware-related adjustment it varies by system.

Ok I typed in vid_vsync in the console and it said true. Then I typed in vid_vsync 1 and it didn't give ma a message but I assume it must of done something. The game plays the same, a little choppy.

As far as a computer is concerned, 1 is true and 0 is false*, so you didn't change anything. If you wanted to turn vsync off, you needed to type vid_vsync 0.


(* Actually, 0 is false and everything else is true. -1 is true, 58.749 is true, "pie" is true, etc.)

Tried vid_vsync 0 didn't do anything that I can tell.

my computer
i5 2500k
16 gb ram
samsung ssd
asus p8z68
this thing can play anything except doom. What the *$#%&

That certainly is a capable system.

As to GZDoom settings, the values affecting the 'speed' of the game are vid_vsync, cl_capfps.
My settings are both to 1 and I get about 36 fps. To display the speed I have vid_fps set to 1 as well.

Changing them to:
with both set to 0 I get about 900 fps average
with cl_capfps set to 0 and vid_vsync to 1 I get about 60 fps

The only difference I can think of is that the latest games use Direct3D 11 and GZDoom uses OpenGL. So it stands to reason that a video driver biased towards D3D would not fare as well in an OpenGL environment. I am using version 301.42. I never had any problem with NVIDIA, but then I don't have a 'high-end' videocard, I have a GTX460. So that may be something to consider. Also, check if 3D vision is enabled, that would result in an awful picture.

Dude it worked. I did the cl_capfps thing and set it to 0 and it is awesome. Thanks man now I can enjoy Doom again. I wasn't really aware that so many settings could be configured through the console menu. I also did the vid_fps thing or whatever and this may be the program giving me a load of crap because it reads 1600. Thanks guys you rock.

May I ask why you set yours to get only 36 fps?

Some people think that the way it was in 1993 is The Only Way It Is Meant To Be.

What does the # infront of the fps counter mean? On my computer it changes so fast I can't really tell what it says. It goes up to 24 or something when the game is paused but is around 4 or 3 when playing. It really doesn't matter because now my computer plays Doom flawlessly.