Issues Loading .WAD Files in GZDoom on Linux (20.04)

[the doc sataper]

Hello,

I'm encountering an issue while trying to load additional .wad files (like custom maps) on Linux. When I attempt to load a .wad file, GZDoom seems to act as if the file doesn't exist. However, .pk3 files (for example, "brutal doom v21.pk3") load perfectly fine.

I’ve checked the permissions on my .wad files, and they match those of the .pk3 files. Currently, I’m using GZDoom version 4.13.1, but I noticed this issue with earlier versions too, likely around version 4.10 or 4.11.

Since I’m not very experienced with Linux, I’m unsure if this is a bug or a misconfiguration on my end.

Thank you for your time and assistance!

[Rachael]

What exactly are you doing to load them? What shells, desktop environments, and/or launchers?

[the doc sataper]

I'm using Ubuntu 22.04 (I made a typo in the topic title) with the Gnome environment.
I tried loading the file in two different ways:

- Through the terminal by typing gzdoom "-file myfile.wad" (without quote)
- Through the GZDoom launcher, entering "-file myfile.wad" (without quote) in the text field for command line parameters.
My WADs are placed in a valid folder for gzdoom (same than my mods)

I also tried placing a WAD file in an empty PK3 archive, but that gave the same result. However, mods like Brutal Doom and Tobby's Accessibility Mod (a mod that adapts Doom for blind players) work without any issues.

I installed the Debian GZDoom package by downloading it from https://zdoom.org/downloads.

[Blzut3]

Assuming the files that work and the ones that don't are in the same folder I'm not sure why it wouldn't be loading. If GNOME has a right click "open with" option in the file manager, that should work.

Otherwise with the terminal instead of typing out "myfile.wad", drag and drop the file onto the terminal. It will then write out the full path to the file which should work regardless of the working directory so that would rule out that.

If it's still not loading, have you ruled out that your mod isn't just broken and GZDoom is loading it and not doing what you expected? (i.e. There's definitely no "adding" line in the console.)

[the doc sataper]

I tried that with NERVE.WAD, the two methods work fine for me, thank you so much.

[Rachael]

Do remember also that Linux uses a case-sensitive file-system by default. So Nerve.wad is not the same as nerve.wad is not the same as NERVE.WAD each can be a distinct separate file.

[the doc sataper]

I didn't know that uppercase letters matter in file names on GNOME. That might be the cause of my issue. I’ll be more careful the next time.

[axredneck]

I didn't know that uppercase letters matter in file names on GNOME.

It's not because of Gnome but because of file system (ext4, btrfs...)

[DukeNukem]

I'm struggling with this. I've installed GZDoom as flatpack (Linux Mint 22), it runs, yay. I have a folder with hundreds of wad files and I want to play one of them. However GZDoom just ignores the "Additional Parameters".

For example these do nothing (no errors/warnings, just runs GZDoom ignoring the wad I specified):

-file ~/Games/Doom/SomeWad.wad
-file "~/Games/Doom/SomeWad.wad"
file ~/Games/Doom/SomeWad.wad
~/Games/Doom/SomeWad.wad

Yes, the case is correct and in a terminal "cd ~/Games/Doom" switches me to the directory.

So, I edited gzdoom.ini (in ~/.var/app/org.zdoom.GZDoom/.config/gzdoom") to specifically add the directory:

Code: Select all

# These are the directories to search for wads added with the -file
# command line parameter, if they cannot be found with the path
# as-is. Layout is the same as for IWADSearch.Directories
[FileSearch.Directories]
Path=$HOME/.config/gzdoom
Path=$HOME/.local/share/games/doom
Path=$HOME/Games/Doom                       <---------- I Added this
Path=/usr/local/share/
Path=/usr/local/share//doom
Path=/usr/local/share//games/doom
Path=/usr/local/share/doom
Path=/usr/local/share/games/doom
Path=/usr/share/doom
Path=/usr/share/games/doom
Path=$DOOMWADDIR

then tried:

-file SomeWad.wad
-file "SomeWad.wad"
file SomeWad.wad
SomeWad.wad


Still nothing - gzdoom just runs like nothing was specified. Wish it'd just error if it doesnt understand something

What am I missing ?

I previously ran these wads (Mint 18!) by dragging the wads onto the gzdoom executable - not ideal, but it worked.

TTFN,
Jon

[m8f]

Are you running GZDoom from a terminal or from a launcher? Which one?

What happens if you try to specify the wad file via shell autocompletion? Like this, in a terminal:

Code: Select all

gzdoom -file ~/Games/Doom/So[tab]

Will the shell autocomplete the file name? What will it suggest you?

[DukeNukem]

I'm running GZDoom from desktop icon;. I installed GZDoom as a flatpack, which installed GZDoom entry on the main menu which I then right-clicked and "Add To Desktop".

Running GZDoom directly on the command line => command not found - not a shock as its a flatpack I guess?

Copying the desktop icon's Properties->Launcher and pasting to command line launches gzdoom as expected:

Code: Select all

/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=gzdoom.sh org.zdoom.GZDoom

If I add a wad file:

Code: Select all

 /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=gzdoom.sh org.zdoom.GZDoom -file SomeWad.wad

... then GZDoom runs but still no sign of the wad file. Putting the command in quotes "gzdoom.sh org.zdoom.GZDoom -file SomeWad.wad" gives error "error: APP must be specified"

So, I run GZDoom, it starts with a dialog to select which game (DOOM2, Ultimate DOOM, DOOM registered) which has an additional text box [Additional Parameters]. It seems that [Additional Parameters] is ignored, as if I enter complete gibberish GZDoom still launches without errors.

TTFN,
Jon

[Blzut3]

GZDoom doesn't error on invalid command line parameters.

I'm not an expert with flatpaks but it looks like it can only access files in ~/.var/app/org.zdoom.GZDoom/.config/gzdoom by default. Note that while applications supporting the ~ notation is common, it's actually syntax that bash expands so if you're passing via the Additional Parameters box you will need to write out /home/<username>/ and not ~.

I would think the flatpak should be able to load a file from anywhere if passed through the desktop file. But that would require the Exec line to include %F which it doesn't appear to. Something you'll need to take up with the maintainer of the flatpak (Eonfge).

[axredneck]

Also you can try some sort of https://flathub.org/ru/apps/com.github.tchx84.Flatseal to grant GZDoom access to folders where wads are.

[DukeNukem]

Thanks for the replies. Looks like it is a flatpack issue From https://www.linuxfordevices.com/tutoria ... all-gzdoom:

However, even this method of installation doesn’t play nice with mods, as GZDoom doesn’t come up as an app which we can choose to run .WAD files. For proper mod playability, we would need to go to manual installation techniques, which are more prevalent on Windows.

Dang Same page goes on to to mention installing from a .deb file so I tried that and now it works, yay ! I edited the GZDoom.Ini (as previously posted) to include the dir with all my wads in, so I just need to enter "-file SomeWad.wad" without any paths and it works.

TTFN,
Jon