DRD Team

with latest official version of GZDooM. It usually happen after playing a while.

Using HP Pavilion dv6700 Special Edition
Processor - Intel Core 2 Duo T8100
RAM - 2 GB
Operating System - Microsoft Windows Vista Home Premium
Graphics - NVIDIA GeForce 8400M GS - 256 MB

Looks like an old problem that has been known about for some time - many versions. There is a cvar to fix it, which should be enabled by default with newer versions.

Try typing gl_clamping_bug 1 at the console.

If you do a search for that cvar, you'll see it's been an issue for quite a few people. However, apparently it has to do with poorly written drivers. GZdoom is doing things according to spec.

I changed the CVAR to a default of 1 long ago. Apparently no driver is doing this properly. There was only one revision of NVidia's driver that apparently did - and my guess would be that it caused total chaos with lots of software. The later versions are back to the old behavior.

I think I should remove it altogether as it's useless and only causes glitches.

I'd say keep it in but default it back to 0. As far as the NVidia drivers are concerned, they never do anything right. So people write them for the wrong way to do it, that way when they fix it, it's wrong. *shrugs*

I think I've had some configurations where it worked better at 0, and others where it worked better at 1. So honestly, I don't see any need to be rid of it.

My ATI works better with it set to 1.

SoulPriestess wrote:I'd say keep it in but default it back to 0.

0 allows the visual glitch to happen. 1 should be the default IMO and people can switch off the "protection" from the glitch if they like. My guess is that NeoWorm probably had it at 0 from using an older ini or something?

It helped, the glitches are gone. But another ones appeared. GL lights sometimes mess up with neighbouring walls...

Not sure what you mean by that one. Got a screeny?

The CVAR is gone now, too.