[r-???-r323]Offset Error?

[Dethernal]

Very strange error...

---

DB_Offset.jpg

---

GZ_offsets.jpg

Scale in TEXTURE1 (Slumped).
"Door" also separated on 4 segments. Earth blocks offsets is 0, 32, 64, 96

[Enjay]

Strange. I'm not sure what is going on here because I saw someone else mention something very similar very recently. However, I've just checked a whole bunch of my hi-res textures in game and they are aligned correctly in the way that I would expect them to be and which they have been for as many (G)Zdoom versions as I can remember.

[Rachael]

What about in ZDoom? Are the offsets correct there?

What seems to be going on to me is GZDoom is using the scaled offsets, whereas DB2 is using relative offsets; what it WOULD be if an equivalent texture was made unscaled.

You really should post the wad where this came from.

[Dethernal]

Test Wad.
First column :
Scale over TEXTURE1, offsets 0,32,64,96
Second column :
Scale(and rotate) over TEXTURES Lump. Offsets 0, 32,64,96
Thrid column :
Scale(and rotate) over TEXTURES Lump. Offsets 0, 128,256,384 (!!! Its wrong offsets, without taking into account the Scale)
fourth column :
Plain standard texture of door(from TEXTURE1). Offsets 0, 32,64,96

[Rachael]

Hmm... this looks like either it's intentional, or it's a bug inherited from ZDoom. I tested this with ZDoom itself.

Bear in mind, it's also possible the error exists in DB2, and not either (G)ZDoom.

And by the way, I hope you don't mind, I edited the topic title.

[Enjay]

What seems to be going on to me is GZDoom is using the scaled offsets, whereas DB2 is using relative offsets

Seems to be that way. Looking at the TEXTURE1 lump, the texture is not set to use world units so I would expect (G)Zdoom to use scaled offsets. Without altering the test file in any other way, I set the TEXTURE1 lump to use world offsets and test panels 1 and 3 looked fine. Looking at the offsets on the sides in the level, that is what I would expect.

I'm not particularly familiar with the TEXTURES lump, but I don't see anything in the test lump to specify world offsets there either.

I can't test in DB2 as I don't have it set up. However, it's my guess that the problem is with DB2's 3D mode, not GZdoom. Perhaps DB2 is forcing "world units alignment" even when world units are not specified in either the TEXTURE1 or TEXTURES?

[Rachael]

However, it's my guess that the problem is with DB2's 3D mode, not GZdoom. Perhaps DB2 is forcing "world units alignment" even when world units are not specified in either the TEXTURE1 or TEXTURES?

I think this is the case.