Bug 1029 – Dehacked lumps in WAD files will be ignored if also loading dehacked files separately

Bug 1029 - (ARRAY(0x5d38c28)) Dehacked lumps in WAD files will be ignored if also loading dehacked files separately

(ARRAY(0x5d38c28))
Summary:	Dehacked lumps in WAD files will be ignored if also loading dehacked files se...

Status:	NEW

Product:	Odamex
Classification:	Unclassified
Component:	Server & Client
Version:	0.6.x
Hardware:	All All

Importance:	P1 normal

URL:

Depends on:
Blocks:
	Show dependency tree

Reported:	2013-12-07 20:45:53 CST by Dr. Sean
Modified:	2013-12-07 20:45 CST (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dr. Sean 2013-12-07 20:45:53 CST

If multiple WAD files are added and more than one have a DEHACKED lump, only the most recently added DEHACKED lump will be used. The correct behavior would be to apply the DEHACKED lumps starting from the first WAD and moving toward the last WAD.

If DEH/BEX files are added on the command line with the -deh switch, any DEHACKED lumps in WAD files are ignored.

The correct behavior would be to apply DEHACKED lumps in the order that they appear on the command line. For example:

./odamex -iwad dehacked1.wad -file dehacked2.wad -deh dehacked3.deh -file dehacked4.wad