TEXTURES question...

[Major Cooke]

Are TEXTURES lumps processed after every other package is scanned in, or are they processed right after the resources of the package they're included with are scanned? I need to know because I plan on a multi-res version which people can use to replace the low quality ones if their computers can withstand the extra materials. I have the specific sprites readily available but TEXTURES throws a warning about an unknown patch, presumably because its overridden...

[Graf Zahl]

Processing order is not relevant here. Textures get sorted by resource file after all have been initialized.

You have to give a bit more information about the error.

[Major Cooke]

Code: Select all

Sprite N071J5, 88, 209	{	Offset 40, 205	Patch N071B5, 0, 0	}

Now, this works when I do not have the high-definition version package loaded at the same time.
Here you can see I have entries for this.

---

[/img]

This code will throw an "Unknown patch 'N071B5' in texture 'N071J5'" if I include the hi-res package. The TEXTURES lump is only inside the original file too, not the other.

So basically the TEXTURES from the original package cannot detect that the original sprites were replaced and throws that warning.

[Graf Zahl]

What does the high definition version contain? Is there any duplicate N071B5 lump? Possibly one that isn't a graphic to begin with?

[Major Cooke]

It contains higher versions of it, they replace them with the exact names. Not all of them (yet) so it's meant to override them.

[Graf Zahl]

That still doesn't bring us any closer to analyzing the problem. Something in there must make the engine THINK that there is no corresponding patch anymore. Are you by any chance using some non-graphics placeholders or stuff like that?

And if you can't find anything you'll have to give someone a look.

[Major Cooke]

Here, I've attached two files. spr2 should be loaded after spr1.

TEXTURES lump is used in spr1.pk3.

Load #1 by itself. No warnings.
Load #2 after #1. Two missing patches.

spr2.pk3, you'll find ALL of the TEXTURES code has been commented out.

Apparently /* and */ comments are not supported. No wonder it was giving me trouble.

Is this a bug? While I cannot judge officially, I would say that broken comments reading certainly is. Either ZDoom should not accept /**/ inside the textures lump and error out or it should actually recognize/ignore everything inside of them.
If it's a bug, could have this thread moved to the bug reports section.

// works fine though.

[Graf Zahl]

Comments should work. I find that a bit surprising.

[Major Cooke]

It's only the /* */ ones that don't. Regular // does.

I'll report it.