[zdaemon/zdoom 1.23] large textures - fucked up offsets?

[Shockwav3]

okay, following problem: i have a texture which has a dimension of 320x240
now see the problem for yourself

problem 1: fucked up offsets

---

zdoom:


zdaemon:

i've also encounter the same problem in my map LA Rumble CTF, just that it fucks up the other additional textures as well and causes this shit

problem 2: fucked up textures

---

zdoom:


zdaemon:

maps are completly identical, yet zdaemon cuts off the texture after a width of 256 [?] pixels. as a possible solution i split up the linedef into two, but that didn't help much either.
if anyone knows a solution WITHOUT splitting the texture(s) up into two parts, it would be greatly appreciated, as i'm not in the mood to crop 26 textures now. if it helps, i imported those textures using XWE.

[jallamann]

If you didn't notice, these aren't the ZDaemon forums.
If you have an issue with ZDoom, download the latest version. If that doesn't work, then whine.

[Shockwav3]

this is exactly the reason why i usually don't use these forums.

i know the question is regarding an outdated version, yet i thought people could maybe help me [faster] on here. i've posted an almost identical thread on the zdaemon forums, but thought you guys might be a little more competent/faster than over there (even if it's regarding an outdated version [maybe someone of you had identical issues]).
but i guess it's better to flame than to shut up here.

[Graf Zahl]

Jallamann, you are an idiot!

In the recent weeks your bitching and flaming has gone beyond annoying. Please stop it!

@Shockwav: I'm sorry but 1.23 is such an outdated version that any attempt of help might be futile. Nothing of its texture handling code exists anymore in ZDoom and the new code appears to be much more robust. I fear you have to alter your textures if ZDaemon can't handle them.

[Cutmanmike]

That looks like what happens if you have transparecy in the texture. Have a close look to see if there's any cyan pixels hiding around in it.

[Enjay]

I suspect the problem is the size of your texture. Textures that are values like 8, 16, 32, 64, 128, 256, 512, 1024 etc should tile and offset fine. I've certainly experienced your problem with textures that use unusual values.

[jallamann]

Jallamann, you are an idiot!

Cry me a river.

[Shockwav3]

That looks like what happens if you have transparecy in the texture. Have a close look to see if there's any cyan pixels hiding around in it.

nope, no transparent pixels there, thing is, the textures which fuck up in that shot aren't mine, neither added in the wad containing my level (i add them via the -file command using a resource wad) yet work fine on the original wad (zdctfmp.wad)

EDIT: i just created a new pnames/texture1 lump for the custom textures i had in my wad, now my own textures work fine (except for the offset, gotta try to hunt that down later on) but i get ashwall (no texture) for the textures loaded from the resource wad when using zdaemon, yet it works fine in zdoom

[jallamann]

How come there's a different texture in the two shots?

[NiGHTMARE]

Perhaps ZDoom is capable of processing multiple TEXTURE1 entries, but ZDaemon isn't? I could well be wrong, however.

[Graf Zahl]

Perhaps ZDoom is capable of processing multiple TEXTURE1 entries, but ZDaemon isn't? I could well be wrong, however.

That feature exists since 2.0.48, hence not in ZDaemon.

[Shockwav3]

Perhaps ZDoom is capable of processing multiple TEXTURE1 entries, but ZDaemon isn't? I could well be wrong, however.

That feature exists since 2.0.48, hence not in ZDaemon.

okay, got rid of the fucked up texture problem shown in shot4 then thx guys
prolly was due to not synchronizing the pnames/texture1 lumps back then
EDIT: okay those long textures now work in zdaemon as well after i did what enjay recommended, props to you guys. feel free to lock this thread now.