by wildweasel » Mon Apr 18, 2022 2:11 pm
You can
sort of coax Linux GZDoom into working on Steam Deck, but it does take some roundabout approaches, and
I have not yet figured out how to get it to load external WAD files. The steps I took are as follows:
- From Desktop Mode, install GZDoom from the Discover app. (This installs it as a Flatpak - I've yet to figure out any other way.) DO NOT RUN IT YET, or it may be difficult to escape from it!
- Open Steam from the Desktop and add GZDoom as a Non-Steam Game.
- You'll probably want an external keyboard for this: put your IWAD files somewhere, then add that location to the gzdoom.ini file. As a Flatpak, you'll find that in, if I recall correctly, /home/deck/.var/app/org.ZDoom.GZDoom/.config. You could place the IWADs in the usual Linux locations, but the Flatpak needs special permissions to access them, and I don't know how to grant them.
- From Gaming Mode, you should be able to configure the GZDoom app from the Steam library, in order to select one of the community-made controller configs for it. This is EXTREMELY IMPORTANT, as even if you enable Controller support, GZDoom does not directly recognize the Deck controls as a controller. Fortunately, this is as easy as picking the top-rated community config for it.
If all you wanted to do was run a single IWAD, this will get you into a game and enable you to play it. A Linux-expert friend of mine was trying to figure out how to get a copy of ZDL to recognize a Flatpak GZDoom and not making much headway, though, so I think if we want more functionality than just "runs doom2.wad," we might have to figure out how to install GZDoom as a
normal friggin' program first.
Another huge caveat is that the Steam Deck on-screen keyboard app will not render over GZDoom, so if you didn't follow my advice and set it up with a controller config first, you will need to be able to type blindly using only the haptic feedback to "feel" where the keyboard keys are. Typing "quit" in the console took me 5 minutes to do the first time and I do not recommend it. If you wanna get risky with it, get either a Bluetooth keyboard or a USB-C OTG adapter.
You can [i]sort of[/i] coax Linux GZDoom into working on Steam Deck, but it does take some roundabout approaches, and [b]I have not yet figured out how to get it to load external WAD files[/b]. The steps I took are as follows:
[list=1][*]From Desktop Mode, install GZDoom from the Discover app. (This installs it as a Flatpak - I've yet to figure out any other way.) DO NOT RUN IT YET, or it may be difficult to escape from it!
[*]Open Steam from the Desktop and add GZDoom as a Non-Steam Game.
[*]You'll probably want an external keyboard for this: put your IWAD files somewhere, then add that location to the gzdoom.ini file. As a Flatpak, you'll find that in, if I recall correctly, [b]/home/deck/.var/app/org.ZDoom.GZDoom/.config[/b]. You could place the IWADs in the usual Linux locations, but the Flatpak needs special permissions to access them, and I don't know how to grant them.
[*]From Gaming Mode, you should be able to configure the GZDoom app from the Steam library, in order to select one of the community-made controller configs for it. This is EXTREMELY IMPORTANT, as even if you enable Controller support, GZDoom does not directly recognize the Deck controls as a controller. Fortunately, this is as easy as picking the top-rated community config for it.[/list]
If all you wanted to do was run a single IWAD, this will get you into a game and enable you to play it. A Linux-expert friend of mine was trying to figure out how to get a copy of ZDL to recognize a Flatpak GZDoom and not making much headway, though, so I think if we want more functionality than just "runs doom2.wad," we might have to figure out how to install GZDoom as a [i]normal friggin' program[/i] first.
Another huge caveat is that the Steam Deck on-screen keyboard app will not render over GZDoom, so if you didn't follow my advice and set it up with a controller config first, you will need to be able to type blindly using only the haptic feedback to "feel" where the keyboard keys are. Typing "quit" in the console took me 5 minutes to do the first time and I do not recommend it. If you wanna get risky with it, get either a Bluetooth keyboard or a USB-C OTG adapter.