Hiya, there seems to be a bug with the loading of map10 in Hexen.  I get either Aborted or segfaults in both Windows XP (using precompiled from website) and Debian (release and CVS versions).<br><br>I have a debug.txt that I am emailing presently, but here is the tail end of it.  This is from a binary compiled using gcc 2.95.4, 3.3.3 version aborts instead of segfault:<br><br>[pre]Log: >map map10<br>Dev: Spawning server map10<br>- (.SpawnPolyobj)<br>- PO_SpawnPolyobj<br>- TProgs::ExecuteFunction<br>- (P_SpawnMapThing)<br>- SV_SpawnServer<br>- COMMAND Map<br>- Host_Frame<br>STACK TRACE:<br><br>stack 0 0x8077008 frame 0 0xbffffa18<br>stack 1 0x400fefd8 frame 1 0xbffffa38<br>stack 2 0x402b87f8 frame 2 0xbffffa58<br>stack 3 0xbffffbf2 frame 3 0xbffffae4<br>stack 4 0x6d6f6f76 frame 4 0xbffffbe5[/pre]<br><br>I tried futzing around with -minzone and -maxzone but didn't have any luck.    The Hexen wad is version 1.1.  Is it just me?  This is the only map that doesn't want to work.<br>--<br>Failure

The Hexen wad is version 1.1.  Is it just me?  This is the only map that doesn't want to work.

<br>I just tried warping there, and mine loads up fine (Win98)<br>Start a new game, and go into the console and type "map map10" and see if it starts that way.  If so, it probably ran out of memory at some point, and that was saved in your save-game (assuming you've been playing through).  If not, maybe you need a new wadfile?  Unless someone else has this problem as well.  If need be, I can set up an ftp server for you to get my version of the wadfile, though it should be the same I think.<br><br>Windows reports:<br>hexen.wad<br>19.1MB (20,083,672 bytes)<br>modified: Thursday, March 14, 1996 1:01:00 AM<br>

Strange.  You said:<br><br>

hexen.wad<br>19.1MB (20,083,672 bytes)<br>modified: Thursday, March 14, 1996 1:01:00 AM<br>

<br><br>I get for size and modification date the same, and md5sum of the freshly patched wad matches the md5 of the file Vavoom is using.<br><br>[pre]failure@shodan:/windows/HEXEN$ ls --full-time HEXEN.WAD<br>-r--------    1 failure  failure  20083672 1996-03-14 00:01:00.000000000 -0500 HEXEN.WAD<br>failure@shodan:/windows/HEXEN$ md5sum HEXEN.WAD <br>abb033caf81e26f12a2103e1fa25453f  HEXEN.WAD<br>failure@shodan:/windows/HEXEN$ md5sum /usr/local/games/Vavoom/hexen.wad <br>abb033caf81e26f12a2103e1fa25453f  /usr/local/games/Vavoom/hexen.wad[/pre]<br><br>Would you mind checking if you get the same value?<br><br>Also I did try warping directly via console, same result.  Also tried the application on different hardware, same result.  I am confused, heh.<br>--<br>Failure

Also for me it works fine.

abb033caf81e26f12a2103e1fa25453f

<br><br>D:\vavoom>md5sum hexen.wad<br>abb033caf81e26f12a2103e1fa25453f *HEXEN.WAD<br><br>Yup, looks the same...  <br>I guess it's fun time with Janis time!  ;D<br><br>Or not...<br>hold that thought...<br><br>Nope, never mind.  I got a different error using XP, but it was a one time deal, probably because something messed up previously, because I tried again and it worked fine...<br><br>What kind of settings are you running with?  (Audio?  Video? etc.)

I probably should have mentioned game settings in the beginning.<br><br>I'm running 640x480x24 on one, 1600x1200x24 on another with DGA2 OpenGL on both.  OSSD sound driver and CD audio for music in Linux, whatever sound defaults are in Windows (nothing checked in the launcher).  Linux binaries using Allegro.<br><br>I ran a control using software rendering and no sound in both Windows and Linux with no change in the behavior warping to map10.  Tried Win98SE and XP, Debian stable (old) and unstable (not old).  I have the same crash in all cases.  I can provide hardware specs if that is deemed necessary, but there are two different graphics chipsets (Intel, nvidia), Athlon, Celeron, and PIII CPUs so hardware seems unlikely.  Could still be I haven't found the right minzone/maxzone settings although I have tried a few.  Have tried with and without running the standalone glvis utility.<br><br>So that is what I know, I warped to every other map and they are all fine it is just this map10 that crashes the game every time for me.<br>--<br>Failure

The crash happens in polyobject spawning, so it should have nothing to do with your system. I'll check what could go wrong there.

Yay!  I managed to work around this bug as follows.  Hopefully it will help figure out what is broken.<br><br>I downloaded and compiled 1.15.1, and executed "map map10" in the console, and it got there no problem.  But when I loaded my saves from 1.15.2 the game crashed.  I solved that by copying sv_save.cpp from 1.15.2 into the 1.15.1 source tree and recompiling, after noting the changelog at the bottom.<br><br>Hopefully that will help.  I am just happy to continue playing <!-- s:-) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":-)" title="Smile" /><!-- s:-) --> <br>--<br>Failure

I think I found a way to replicate the bug.  You must generate the hexen.gwa file with the 1.15.2 binary.  When upgrading from 1.15.1 that has already made the file, it doesn't make a new one and the 1.15.2 binary loads map10 just fine.  But after regenerating the gwa file it exhibited the same behavior, crashing going to map10.<br><br>You should be able to replicate this by deleting hexen.gwa, hexen.~gw and running Vavoom 1.15.2, teleporting to map10.<br>--<br>Failure

Maybe it's a bug in the new version of the glbsp that I upgraded to recently.

Updated to latest version of glBSP that should have fixed this bug, at least it says that it fixed problems with jHexen.