Doomsday Engine

It appears this problem is quite simply that HEXDD.wad is being loaded twice when launched from Snowberry. A summary of what is happening in my case at least:

Selecting game 'hexen-dk'...
Loading game resources...
Loading "%HOMEPATH%\Documents\DOOM\IWADS\HEXEN.wad"...
IWAD identification: 0x166c805
Loading "%HOMEPATH%\Documents\DOOM\IWADS\HEXDD.wad"...
IWAD identification: 0x480bc0
Loading "(basedir)\data\jhexen\libhexen.pk3"...
Loading "%HOMEPATH%\Documents\Doomsday Frontend\addons\HEXDD.wad"...

First HEXDD,wad is loaded as a required/startup component for the hexen-dk game mode (as IWAD data / non-custom). It is then tried again because Snowberry specifies to load it using -file (as PWAD data / custom) suggesting that the lumps it contains are being appended to the LumpIndex and thus overriding the previously loaded lumps. (Needs verifying.)

My take is this is simply obsolete logic in Snowberry - both HEXEN.WAD and HEXDD,WAD should be specified with -iwad so that -file can be used as defined, allowing an IWAD to be passed and interpreted as a PWAD regardless of its identifier. (See relevant discussion here: #2047)

Build1595 - Snowberry is still using -file for HEXDD.wad for me.

Options.rsp:

-basedir "C:\Program Files (x86)\Doomsday" 
-file "C:\Users\DaniJ\Documents\Doomsday Frontend\addons\HEXDD.wad" 
-sfxchan 16
-notexcomp
-game hexen-dk
-iwad "C:\Users\DaniJ\Documents\DOOM\IWADS\HEXEN.wad" 

I'll do some Python debugging...

I tried it with Fedora, and it did work correctly: "-iwad" was used for both WADs, and hexdd.wad wasn't loaded twice at runtime.

On Windows the Python sources are compiled to bytecode .pyc files I believe, perhaps the executable was built from old versions?

Could you check if your copy of hexdd.wad actually identifies itself as an IWAD? I just tried 1595 on Windows and it did also work there correctly for me.

bytecode .pyc

I think py2exe bytecompiles all the Python modules when it packages the executable, so this shouldn't be a problem.

Note that regardless of whether hexdd.wad is marked as an IWAD it should be treated by Snowberry as a required/startup game data file and therefore specified with -iwad.

I'll check my copy...

My copy of hexdd.wad is indeed a PWAD

That's interesting. I wonder if yours is from a different version?

Well, this means Snowberry just has to treat the "hexdd-wad" addon as a special case and not rely on the identifier. I'll make the changes.

regardless of whether hexdd.wad is marked as an IWAD it should be treated by Snowberry as a required/startup game data file

Unfortunately, Snowberry lacks the concept of multiple startup data files, so this can't be solved without a kludge.

skyjake wrote:

That's interesting. I wonder if yours is from a different version?

Could be. Mine has been patched to 1.1

My versions of DK 1.0 and 1.1 (from patching my 1.0 Iwad) are both marked as Iwads.