Zen_fail 4 'ERROR: Could not create or access brutal-doom-64 XDG config directory 'Ĭp ' $CONFIG_SOURCE ' ' $CONFIG_TARGET ' || Please specify a WAD directory containing at least one of these. Zen_fail 3 'ERROR: Missing Brutal Doom 64 main configuration file: $CONFIG_SOURCE ' Zen_fail 2 'ERROR: Could not access user home directory ' Zenity -width 400 -warning -text ' ' 2> /dev/nullĬONFIG_DIR= ' $HOME/.config/gzdoom/brutal-doom-64/ 'ĬONFIG_SOURCE= '/usr/share/games/brutal-doom-64/gzdoom.ini 'ĬONFIG_TARGET= ' $CONFIG_DIR/gzdoom.ini ' Allows a per user configuration directory and makes sure essential IWAD are available for the game. Learn more about bidirectional Unicode characters To review, open the file in an editor that reveals hidden Unicode characters. I don't rember which version you need to use exactly, but in the Brutal Doom ModDB page you can download a compressed file containing the mod and the needed version of GZDoom.

However, It returns this fatal error: newconsolefont.hex not found. Surely I had seen my video of how this error happened in Brutal Doom V. What version of GZDoom are you using Recent ones won't work with Brutal Doom. So I installed GZDoom, downloaded Brutal Doom, copied all the wads and pk3s from Brutal Doom to GZDoom, changed the config file so it loads everything Brutal Doom needs. GZDoom is the daddy of Doom source ports, supports mods AND is the only one the supports Heretic, Hexen and Strife. This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. As I said earlier on, GZDoom is required for this installation. Chocolate Doom was literally ported in an hour as a fun little aside project and doesn't have very good analogue controls at all.

Brutal doom gzdoom error