"-Iwad HexDD.wad" can't find Hexen.wad in Non-ZDoom Folder

[NeuralStunner]

Where "-Iwad HexDD.wad" is actually a full path to the Iwad. But topic titles are limited in length.

Hexen.wad and HexDD.wad are both in the same folder. However, using ZDL to start up with Hexen: DK informs me that I don't have any Iwads. This is because there are none in ZDoom's folder (And yet the Iwad folder is in [IWADSearch.Directories] - If I start ZDoom alone and choose HexDD.wad, it works fine).

At present, the only ways to make this work:

- Have a copy of Hexen.wad in the same folder as the program. (I was deliberately trying to keep them out of there.)
- Start ZDoom directly. (I use ZDL so I don't have to do this.)

When -Iwad HexDD.wad is used, shouldn't it look for Hexen.wad in the same folder, and then in [IWADSearch.Directories]?

[Graf Zahl]

Does this also happen when you do not use ZDL? I have no problems loading Deathkings like that.

[NeuralStunner]

Does this also happen when you do not use ZDL?

Yes and no.

This works:

Code: Select all

D:\Games\ZDoom>GZDoom -Iwad \Iwads\HexDD.wad

This doesn't:

Code: Select all

D:\Games\ZDoom>GZDoom -Iwad D:\Games\ZDoom\Iwads\HexDD.wad

[NightFright]

I put this line in [IWADSearch.Directories]
Path=iwad/raven

hexen.wad and hexdd.wad are in E:\GZDoom\iwad\raven, the port files are in E:\GZDoom.

It works when you don't use ZDL, then GZDoom tells you it detects two wads. ZDL however seems to bypass the feature, you have to enter the path to the iwad manually (as seen later in zdl.ini), and you can only enter one per entry. If you enter hexdd.wad, you will always get an error - unfortunately. This might be an issue with the launcher, but not with GZDoom.

[NeuralStunner]

Read my previous post. (G)ZDoom is certainly not finding Hexen.wad correctly from the command line either, when the Iwad is given as a full path. That's what the launcher does - it gives absolute paths to all files.

[NightFright]

Well, actually I was wondering about the same thing. ZDL has to use zdoom-username.ini after all (it's only launching the port with the iwad specified), and it seems to ignore the iwadsearch.directories entry. Maybe it should be made so that (G)ZDoom automatically looks for hexen.wad in the same dir as hexdd.wad, regardless whether it is stored in the same dir as (g)zdoom.exe or any other. That's when you should be able to add hexdd.wad in ZDL as iwad, and it should still fire up correctly. I also want to be able to directly add HexenDK addon to ZDL launching menu.

[NeuralStunner]

ZDL doesn't do anything with ZDoom's INI files. So there's nothing for it to ignore.

[NightFright]

I guess since this is the only case in which you need to combine a pwad with an iwad for official support, it should be possible to do something about it.

[Kappes Buur]

Using a batch file or command line works for me.

ZDL 3.1 only runs intermittently for me. A bit of experimenting with it shows that it runs HEX_DD properly right after installation. However, after closing ZDL and then running it again, it cannot find the IWAD.

[Guest]

This was briefly discussed here. ZDL needs an update big time.

[NeuralStunner]

So, been testing a new ZDL build and was reminded of this topic. And still 100% that this is ZDoom's fault.

Using the standard Windows command prompt:

Code: Select all

D:\Games\ZDoom\ZDoom.exe -iwad "D:\Games\ZDoom\IWads\HexDD.wad"

Fails to find Hexen.wad and bombs out with a "no IWad" error.

Code: Select all

D:\Games\ZDoom\ZDoom.exe -iwad "HexDD.wad"

Suceeds. ZDoom grabs both files from its [IWADSearch.Directories] as it should.

---

Cmd.exe needs an update big time.

[randi]

Fixed.