ZDoom

So today I made several tests building Raze; for now just with Raze with DN3D, and only testing starting a new game in any map. I tried building it several times, by gradually installing one dependency package (from OP) at a time, then seeing what happened, either CMake complaining or if not going ...

This is actually following from the other thread here: https://forum.zdoom.org/viewtopic.php?t=79911 but since original question there was already solved I thought better to start another thread. Back in the vcpkg brief time, I used to follow this process https://forum.zdoom.org/viewtopic.php?p ...

Thanks very much again. It's very similar to the process I followed last time I tried (many months ago), in a Debian box. Some doubts then: ---Aren't you missing all the gl Mesa / Gtk development libraries? Last time I tried they were not pulled automatically with the other dependencies. ---Couldn't ...

Thanks very much for your answer.

With vcpkg updates, do you mean lack of them as well?

Does this mean the only way to build for Linux systems is again the one at ZDoom wiki, even though it still needs some fixes?

I saw in GZDoom 4.13.0 release that this option was added, to automatically start all levels with "pistol start" without keeping inventory and health from previous levels.

I'm wondering if this could be possible for Raze as well, at least for DN3D.

I would like to ask what happened to these builds, which are no longer updated for close to a year already. Or if maintainer just quit for good, I'd like to ask who it was and how did he made the builds to try myself, because the ZDoom wiki for this is long outdated and, given all the libraries ...

Partially solved on Discord; basically with AutoExec.

But how can one make autoexec.cfg applying ONLY to specific mods, PWADs or PK3, overriding those of IWADs?

Thanks.

Jekyll Grim Payne wrote: ↑Wed Apr 10, 2024 3:10 am I removed the claim about memory corruption from the wiki. However, please do NOT store full WADs inside PK3s.

Could you, user Jekyll, explain why this must NOT be done then?

Because, like most good Wiki's, it explains a rather obvious flaw when you attempt to do this. The fact that the Wiki documents this means people in the past have tried to do this - with disastrous results. :) Then this would make user SPZ1 a complete fool, and either he has no dignity, or you are ...

Thanks, that finally made sense.

Lastly, why the info at that wiki link regarding PK3 and RAM corruption?

Then why the info there at wiki?

And, is the mapinfo directory inside gzdoom.pk3 actually not a PK3 core lump, so "nothing loads mapinfo directory"?

1.- RAM leaking/corruption:
https://zdoom.org/wiki/Using_ZIPs_as_WA ... ent#How_to

2.- So the mapinfo directory inside gzdoom.pk3 is actually not a PK3 core lump?

Then full WADs must never be inside directories? Will there never be a way to avoid "RAM leaking" if putting full WADs inside PK3?

If packing like this: --mapinfo.txt --graphics ----titlepic.png --NERVE.WAD everything works (even all GZDoom core lumps seem to be inherited or the like). But if packing like: --mapinfo ----mapinfoNerve.txt --graphics ----titlepic.png --maps ----NERVE.WAD (in order to prevent RAM leaking according ...

Thanks for explanation.

Now, for last, could you help with the PK3 packing other issue?