|
|
| Reporter | AFADoomer | |
|---|
| Assigned To | | |
|---|
| Priority | normal | Severity | major | Reproducibility | always |
|---|
| Status | resolved | Resolution | fixed | |
|---|
| Platform | | OS | Windows | OS Version | 10 |
|---|
|
|
| Summary | 0000402: Replacement IWADs that don't replace menu graphics cause fatal error on MENUDEF parse |
|---|
| Description | If you try to run an IWAD replacement (that isn't coded into the engine as such, but depends on being loaded with '-iwad' or via another game file's gameinfo IWAD section), GZDoom still parses the default MENUDEF for that game type and throws a fatal error if the image lumps aren't found.
Specific use case:
The Wolf3D TC bombs out with an error message... It contains a MAP01 placeholder lump that causes the engine try to load the IWAD as doom2.wad when you run 'gzdoom -iwad .\Wolf3D.pk7'. In the past this worked with no issue.
"Execution could not continue.
Script error, "gzdoom.pk3:menudef.txt" line 42:
Unknown texture M_DOOM" |
|---|
| Steps To Reproduce | Try to run the Wolf3D TC.
-or-
Load the attached .pk7 with -iwad... It should dump you to a menu with an ugly title graphic over a missing titlepic if it loads properly, since it's essentially empty, but generates the same load error in current GZDoom (ge5a3d22).
The "IWAD" is detected as doom2.wad, GZDoom tries to parse the default doom2 menudef entry, then errors out. |
|---|
| Tags | No tags attached. |
|---|
|
|
