[fixed]0.9.20 Something wrong with textures

Post by **Enjay** » Sat Dec 10, 2005 7:50

It's late and I haven't had time to investigate this fully, but 0.9.20 is doing something odd with textures. I think they are ignoring X offsets, or getting them wrong or something. The textures I have noticed it with so far are all on 2S walls, have transparent space in them and some are quite large. Whether any of that is relevant I don't know.

The screenshots show the problem. The trees in the foreground are made from 128x256 single patch textures. A similar thing also happens with some 256x256 patch trees (shown in the lower half of the second graphic. The skybox is also screwy. The towers are a 512x256 2 patch (256x256) texture. The flags are interesting as they don't all display the problem. These are animated and are 128x64 textures using a single PNG as a patch. The ones that are screwed up are actually on split lines because they cross the sectors between the grass and the path.

Post by **Graf Zahl** » Sat Dec 10, 2005 10:56

Well, I'd have to say that this particular bugfix backfired miserably.

Post by **Enjay** » Sat Dec 10, 2005 16:09

Certainly seems to have. This one's a real PIA.

What was it trying to fix, and what was it actually doing? It looks like it's ignoring X offsets, but I've only noticed it on 2S lines (can't check further ATM). Is that the case?

Post by **Graf Zahl** » Sat Dec 10, 2005 16:27

It was trying to fix a problem with mid textures when antialiasing is on but I checked against the wrong value. As a result all texture offsets for textures that are shorter than the linedef were destroyed (not necessarily to 0 though.)

I had to uncomment the fix for now because it doesn't work well with the current fixed point system.

nwbeeman · Post by **nwbeeman** » Tue Dec 13, 2005 12:58

THATS DOOM?

Damn. We need more wads like this