Things I have attempted in order to run a PWAD on Ubuntu:
Test the WAD in SLADE:
Doesn't work.
Drag the WAD file onto GZDoom in the Dash:
Nothing happened.
Drag the WAD file onto GZDoom in Nautilus:
Nothing happened.
Run gzdoom /path/to/the.wad:
Only the IWAD opens, this with TNT as the WAD is designed for.
Run gzdoom -file /path/to/the.wad:
Only the IWAD opens.
Right-click the WAD and click "Open with...":
GZDoom is not on the menu.
Attempt to edit gzdoom.desktop in order to put GZDoom in the "Open with..." menu:
"File system is read-only", even with sudo.
Linux nerds, what are you doing that works?
Trouble with PWADs on new OS
Moderator: GZDoom Developers
Forum rules
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!
If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.
We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!
If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.
We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
-
- Posts: 8
- Joined: Wed Aug 02, 2023 9:38 pm
- Preferred Pronouns: He/Him
- Operating System Version (Optional): Ubuntu LTS x64
- Graphics Processor: ATI/AMD with Vulkan/Metal Support
-
-
- Posts: 3200
- Joined: Wed Nov 24, 2004 12:59 pm
- Graphics Processor: ATI/AMD with Vulkan/Metal Support
Re: Trouble with PWADs on new OS
Those are the things that work, which leads me to believe that either the wad is broken or "/path/to/the.wad" is wrong. Look at the console, there's probably some information near the top when it tries to read the file. (Particularly with the terminal commands you posted.)
-
- Posts: 8
- Joined: Wed Aug 02, 2023 9:38 pm
- Preferred Pronouns: He/Him
- Operating System Version (Optional): Ubuntu LTS x64
- Graphics Processor: ATI/AMD with Vulkan/Metal Support
Re: Trouble with PWADs on new OS
Update: I have found a solution. It seems like the WADs you want to play with need to go in .config/gzdoom.
-
-
- Posts: 3200
- Joined: Wed Nov 24, 2004 12:59 pm
- Graphics Processor: ATI/AMD with Vulkan/Metal Support
Re: Trouble with PWADs on new OS
They don't. That is one of the locations in the FileSearch.Directories section in the ini by default, so it is a directory that GZDoom will search if the file name you gave doesn't resolve in the working directory but otherwise nothing special about it.
-
- Global Moderator
- Posts: 2748
- Joined: Sun Jun 25, 2006 4:43 pm
- Preferred Pronouns: He/Him
- Operating System Version (Optional): Manjaro Linux
- Graphics Processor: ATI/AMD with Vulkan/Metal Support
- Location: Citadel Station
Re: Trouble with PWADs on new OS
Just a heads up as a Linux user myself, make sure everything is properly capitalized. Linux does allow you to have "folder" and "Folder" - or any variation there of in the same folder. So if you have a file for an example: ".../pwads/theWad.WAD" and you type in ".../pwads/thewad.wad" Linux will think you're looking for that exact file path, not ".../pwads/theWad.WAD"
Having just tried running GZDoom in my terminal, it works as intended.
As for the gzdoom.desktop issue you can make a new shortcut yourself. I myself use KDE and any system generated shortcut is bound to root. Just make a new shortcut - the new shortcut would have you as the owner and not root.
Having just tried running GZDoom in my terminal, it works as intended.
As for the gzdoom.desktop issue you can make a new shortcut yourself. I myself use KDE and any system generated shortcut is bound to root. Just make a new shortcut - the new shortcut would have you as the owner and not root.