DRD Team

I was messing around in Strife and then I noticed that some of the textures had stretched for some reason. Since starting the game (when the textures were normal) I'd given myself all the items, switch bright maps on and changed resolution from 800x600 to 640x480. Exactly when the change happened, I'm not sure but I think it was after the resolution change.



I quit and then went back into the game to try and reproduce it, but couldn't. So, I realise that doesn't give you much to go on. However, in my attempts to get the problem a second time, I did get the warping effect that has been discussed here:

http://forum.drdteam.org/viewtopic.php?t=2997&start=15

OK, Thought I'd bump this just to show a few more pics and a video of the problem in action. These shots were taken after doing nothing special other than using mdk to kill a bad guy. You can see texture stretches all over the level - including one floor which is the first time I'd seen that. Typing GL_FLUSH at the console fixes it briefly as does changing texture filter mode and texture format. In the video, if you look closely, you can see the textures getting worse as I move around the level (look at the low wall to the left as I move away from the forcefield). I have only ever got this in Strife - so perhaps it only happens there?

[edit]Brightmaps were enabled when I took the pics/video (although brightmaps.pk3 was not loaded). I just retried and got the problem almost immediately. On switching off brightmaps, the problem did not go away but after typing GL_FLUSH it did, and did not return for the next 2 minutes as I ran around the level. As other people have suggested with this problem elsewhere, it could be related to the brightmaps function.[/edit]

http://www.rowand.myzen.co.uk/strifewrong1.wmv (about 1.5MB)

Nigel, the explanation is simple. Either you broke Strife or you broke GZDooM. Heh.

I can tell you which internal setting is causing these effects but the bottom line is that this is not supposed to happen (in other words, it's a driver bug.)

I have implemented a workaround for the next version. I added a new cvar gl_clamping_bug. If you set that to 1 the problem should go away. I can't make this change unconditional because on my GF8600 on Vista changing this parameter needlessly severely brings down performance.

Graf Zahl wrote:I can tell you which internal setting is causing these effects but the bottom line is that this is not supposed to happen (in other words, it's a driver bug.)

If you can give me something that would be meaningful to the nvidia developers, I can report it over at their forums (if I can remember my password). Hopefully they will address it.

I have implemented a workaround for the next version. I added a new cvar gl_clamping_bug. If you set that to 1 the problem should go away. I can't make this change unconditional because on my GF8600 on Vista changing this parameter needlessly severely brings down performance.

OK thanks. I look forward to trying it. I know that other people have experienced it too so a work around is always welcome. Although, I just played Strife for about 20 mins with brightmaps off and no problems so I guess that's a workaround too. Is it specific to Strife or is it just coincidence that I've only seen it there?

I have the same problem.
This is from vilcore.wad:


doom2 map19:

I use Radeon X800 with Catalyst 7.10
Changing anisotropic filter makes this desappear for a short time...

StasBFG[iddqd] wrote:I have the same problem.
I use Radeon X800 with Catalyst 7.10

Interesting. Two cards with the same problem? Do you have brightmaps enabled in the opengl menu?

Enjay wrote:Do you have brightmaps enabled in the opengl menu?

Yes, I do... It's difficult to reproduce this bug sometimes, it happens randomly.

Edit: The problem is in brightmaps.pk3. When I don't use it everything seems to be normal. And I also have those green lines in strife

I've just noticed that this is the same bug:

http://forum.drdteam.org/viewtopic.php?p=26267

So presumably it should be moved to closed too?

Yes, this is EXACTLY the same problem and believe me, it has been driving me nuts ever since brightmaps were introduced.