Installation
When I installed Brutal Doom for the first time I really had trouble finding proper and up-to-date instructions for installing Brutal Doom on Linux. I eventually got it working by combining advice from multiple sources. However, I'll be helpful this one time and provide you a step-by-step guide to installing Brutal Doom.
First of all, you need a compatible Doom source port. As far as I know you can use either GZDoom or Zandronum but I never got Zandronum to work. So I'll be using GZDoom instead. Some of you might be able to find GZDoom in your distribution repositories (yes, I'm talking about you, Arch people) but it's likely you won't. So we are going to manually compile it from source. You need libsdl2-dev or a similar SDL 2 developer package, gcc and cmake. Ubuntu people should be able to apt-get install these as is. Cmake is the most important, since it will tell you if you are missing dependencies and will tell what dependencies you are missing.
Once you have those developer tools installed, you can get the source code. The upstream version had a bug in the source code so I forked it and have my own fixed version here: https://github.com/TheSamsai/gzdoom. You can either click the Download ZIP button or use git manually. Note that I'm unlikely to actively maintain my fork.
Once you have downloaded the source code you need to navigate to the directory using terminal. I assume you know the basics of using the terminal but if you don't I'll give you a quick crash-course: use “cd” to change directory to the directory name and “ls” to list the files in the directory you are currently in. Typing “cd ..” will go back one directory level. I recommend having the source code directory somewhere in your home directory.
Once you are in the directory we can get to compiling. Type “cmake .” to configure the compilation. If you got any errors it's likely you are missing some dependencies and need to install them. If cmake finished successfully with a message that says “Generating done” you are ready to begin compiling. Type “make” and the compilation will begin.
After compilation you should have a file called “gzdoom”. This is the executable and if you want, you can copy it to your system directories to have it installed system-wide. Run it either by typing “./gzdoom” in terminal or by double-clicking it in your file manager of choice. This should generate a configuration directory along with config files in /home/NAME/.config/gzdoom and that's where we are going to mess around next. First of all, copy your doom.wad file into the .config/gzdoom directory. Brutal Doom will only work with registered Doom versions, so the shareware version isn't good. Personally I recommend buying Ultimate Doom from Steam and copying the wad file from there. Also, make sure to copy the Brutal Doom files into the same directory. Remember to extract the brutalv20.zip file!
Open up the gzdoom.ini file in the config directory with a text editor. The default file will have some config file paths and a lot of [doom.something.Autoload] lines. In order to use Brutal Doom we need to tell GZDoom to load the mod files along with the doom.wad and this is where we do it.
The change is quite simple. Depending on the Doom you want to use you need to add a couple of paths to a certain autoload area. If you bought Ultimate Doom like me, you'll need to make the changes to [doom.doom1.ultimate.Autoload]. You can also use Brutal Doom with Doom 2 or the old registered version of Doom if you so desire. You just need to apply the same changes to different areas of the file.
Right below [doom.doom1.ultimate.Autoload] add the following lines:
And there you go, you should now have a fully configured Brutal Doom installation. Launching GZDoom should bring up Doom along with the brutal changes and you can start cleansing Mars from nasty demons. Have fun! Article taken from GamingOnLinux.com.
When I installed Brutal Doom for the first time I really had trouble finding proper and up-to-date instructions for installing Brutal Doom on Linux. I eventually got it working by combining advice from multiple sources. However, I'll be helpful this one time and provide you a step-by-step guide to installing Brutal Doom.
First of all, you need a compatible Doom source port. As far as I know you can use either GZDoom or Zandronum but I never got Zandronum to work. So I'll be using GZDoom instead. Some of you might be able to find GZDoom in your distribution repositories (yes, I'm talking about you, Arch people) but it's likely you won't. So we are going to manually compile it from source. You need libsdl2-dev or a similar SDL 2 developer package, gcc and cmake. Ubuntu people should be able to apt-get install these as is. Cmake is the most important, since it will tell you if you are missing dependencies and will tell what dependencies you are missing.
Once you have those developer tools installed, you can get the source code. The upstream version had a bug in the source code so I forked it and have my own fixed version here: https://github.com/TheSamsai/gzdoom. You can either click the Download ZIP button or use git manually. Note that I'm unlikely to actively maintain my fork.
Once you have downloaded the source code you need to navigate to the directory using terminal. I assume you know the basics of using the terminal but if you don't I'll give you a quick crash-course: use “cd
Once you are in the directory we can get to compiling. Type “cmake .” to configure the compilation. If you got any errors it's likely you are missing some dependencies and need to install them. If cmake finished successfully with a message that says “Generating done” you are ready to begin compiling. Type “make” and the compilation will begin.
After compilation you should have a file called “gzdoom”. This is the executable and if you want, you can copy it to your system directories to have it installed system-wide. Run it either by typing “./gzdoom” in terminal or by double-clicking it in your file manager of choice. This should generate a configuration directory along with config files in /home/NAME/.config/gzdoom and that's where we are going to mess around next. First of all, copy your doom.wad file into the .config/gzdoom directory. Brutal Doom will only work with registered Doom versions, so the shareware version isn't good. Personally I recommend buying Ultimate Doom from Steam and copying the wad file from there. Also, make sure to copy the Brutal Doom files into the same directory. Remember to extract the brutalv20.zip file!
Open up the gzdoom.ini file in the config directory with a text editor. The default file will have some config file paths and a lot of [doom.something.Autoload] lines. In order to use Brutal Doom we need to tell GZDoom to load the mod files along with the doom.wad and this is where we do it.
The change is quite simple. Depending on the Doom you want to use you need to add a couple of paths to a certain autoload area. If you bought Ultimate Doom like me, you'll need to make the changes to [doom.doom1.ultimate.Autoload]. You can also use Brutal Doom with Doom 2 or the old registered version of Doom if you so desire. You just need to apply the same changes to different areas of the file.
Right below [doom.doom1.ultimate.Autoload] add the following lines:
Path=/home//.config/gzdoom/brutalv20.pk3
Path=/home//.config/gzdoom/DoomMetalVol4.wad
Path=lights.pk3
Path=brightmaps.pk3 And there you go, you should now have a fully configured Brutal Doom installation. Launching GZDoom should bring up Doom along with the brutal changes and you can start cleansing Mars from nasty demons. Have fun! Article taken from GamingOnLinux.com.
0 Likes
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
7 comments
#stopvideolencegames at the end? thousands of people suffer from it?
i can understand that random stuff comes to your mouth when randomly talking while casting... but thats what video edition is for
i can understand that random stuff comes to your mouth when randomly talking while casting... but thats what video edition is for
0 Likes
Quoting: aL#stopvideolencegames at the end? thousands of people suffer from it?Did you hear what I said after that? That was me poking fun at overly sensationalist media. That whole part was a huge joke. If I were truly criticising video game violence I wouldn't be praising this mod in nearly every sentence till the end.
i can understand that random stuff comes to your mouth when randomly talking while casting... but thats what video edition is for
1 Likes, Who?
Quoting: SamsaiQuoting: aL#stopvideolencegames at the end? thousands of people suffer from it?Did you hear what I said after that? That was me poking fun at overly sensationalist media. That whole part was a huge joke. If I were truly criticising video game violence I wouldn't be praising this mod in nearly every sentence till the end.
i can understand that random stuff comes to your mouth when randomly talking while casting... but thats what video edition is for
woosh... i guess... "we should make friends with the daemons...", its not very clear from what i stand, but if you say so, i believe you :)
I thought this kinda of things were a joke until ive met this kind of people in real life.... they are real and live among us... :|
0 Likes
Heh, I know. That's why I made the joke. I guess I could have made it even more over the top but I ran out of time during my recording session so I decided to leave it there.
0 Likes
I've been meaning to check this mod out for years. Perhaps I'll give it a shot next week.
-- Update --
Dammit, you've rekindled my love for all things Doom engine! :-D
My steps for installing this was a bit simpler. I added the getdeb repo for ubuntu, installed gzdoom, pointed a path at my iwads, unzipped brutal doom, and double clicked the pk3 for it, and was off.
Last edited by Magamo on 17 July 2015 at 12:31 am UTC
-- Update --
Dammit, you've rekindled my love for all things Doom engine! :-D
My steps for installing this was a bit simpler. I added the getdeb repo for ubuntu, installed gzdoom, pointed a path at my iwads, unzipped brutal doom, and double clicked the pk3 for it, and was off.
Last edited by Magamo on 17 July 2015 at 12:31 am UTC
0 Likes
Stoney_Fish Jul 17, 2015
The "double clicked the pk3" didn't work for me.
In the .zandronum folder I created a folder called "skins" and dropped the brutalv20.pk3 there.
Next I edited the zandrinum.ini and set fullscreen to be true,
and then there was bloody blood everywhere.
It's great.
In the .zandronum folder I created a folder called "skins" and dropped the brutalv20.pk3 there.
Next I edited the zandrinum.ini and set fullscreen to be true,
and then there was bloody blood everywhere.
It's great.
0 Likes
Patreon
PayPal
See more from me