DRD Team

I tried to run a wad using GZDooM, but it crashed with the following fatal error: W_MapLumpNum: 4294967295 >= NumLumps

I ran the same wad with ZDooM, and it worked just fine. And so I have a couple of questions (which may have already been asked, but I could not find any reference to them in these forums, except this one, which does not describe my problem):

• 1. What exactly is the error message telling me? I can figure out that there is a discrepancy in the number of lumps, but what does NumLumps represent?
  2. What allows ZDooM to run a map with such a discrepancy and not GZDooM?

My wad has replacement graphics, sound, sprites, and textures and flats (these last two in png raw data format).

Mind telling us what wad it was?

Cutmanmike wrote:Mind telling us what wad it was?

It's a wad that I'm developing. I've gotten through the main resource compilation work, and will soon be moving on to DECORATE and lighting definitions, mapping etc. I can send you the wad privately if you like, if you believe you can identify the source of my problem. [The wad is around 11.3 MB, unzipped.]

I inherited some of the sprite work from another wad intended for the GP32 platform, and although I haven't yet looked through the frame sequences closely, I believe there may be some missing frames. Perhaps this is the source of GZDooM's crash?

This error means that some part of the code expects a lump to be there but can't find it. Unless I run the WAD in a debugger I can't give you any further help.

In other words: This is something in the engine that is missing a validity check and of course should be fixed.

Graf Zahl wrote:Unless I run the WAD in a debugger I can't give you any further help.

Would you like me to email you the wad? If so, you can either post your email address in this thread, or send me the address at gurkha_boy (at) yahoo.com. Thanks.

UPDATE:

I exchanged some emails with Enjay, and it turns out that he was having no problems loading the wad. He was using v1.0.22 - 2.1.7 (R434M). I checked, and I was using v1.0.18 - 2.1.3 (R266). I upgraded to v1.0.22 and the wad runs just fine.

My apologies for the confusion.