- How To Install Brutal Doom
- How To Install Gzdoom Steam
- Gzdoom Android Apk
- How To Install Gzdoom For Doom 2
Did you install GZDoom properly? You can do either of the following: 1. Place one or more of these wads in the same directory as GZDoom. Edit your gzdoom-username.ini and add the directories of your iwads to the list beneath IWADSearch.Directories. Into your pk3, open a folder named Hires and put in the texture HD and be sure to install the patch of the original texture ( on this case, the burtalized baron ). If you only using a wad file, you must create a zip ( called pk3 when finish ) file where you will put: - the map.wad - folder named HIRES. Remember: both texture must have the same. Re: GZDoom Doom2 - Redemption Of The Slain - Full Install by KillsAlone ยป Sun Aug 23, 2020 6:12 am Just after the first big outside Caco attack, inside the building there is rox ammo surrounded by acid. Purchase & Install Ultimate DOOM 3. Go to your folder where Ultimate DOOM is installed & create a new Folder called GZDOOM DOOM. Extract the gzdoom-bin-4-2-0-Windows-x64 Files to your GZDOOM DOOM Folder 5. Download the Chex3 WAD File into your GZDOOM Folder 6. Go to Add a Game on Steam. Select GZDOOM and add it as a Non-Steam game as.
Open a terminal and copy and paste the whole code box for each step.
- 2Install dependencies
- 6Compiling
- 9Installation
- 10Developing
- 11How to increase Zandronum/GZDoom OpenGL FPS
Notes
Starting with commit c219811a5:
consider GZDoom as licensed under the GPL, therefore; the following is unnecessary but will be keep in this tutorial for the users who still need to use GZDoom 2.x or older versions: #Download FMOD, liboutput_sdl.so, the FMOD library file, the environment variable LD_LIBRARY_PATH and the CMake variables NO_FMOD, FMOD_LIBRARY and FMOD_INCLUDE_DIR.
The minimum requirement for GZDoom 2.2 and later is OpenGL 2.0, so if you get the following error:
Unsupported OpenGL version.
At least OpenGL 2.0 is required to run GZDoom.
you will have to use #GZDoom 1.8.6 instead. Keep in mind that this version is several years old and no longer maintained. It will also have problems with more recent actively maintained mods.
Install dependencies
GZDoom needs certain tools and development files in order to compile:
- Required
- gcc 4.8 or later
- make
- cmake 2.8.7 or later
- SDL 2.0.2 or later
- libGL and libGLU (SDL or libSDL pull in libGLU) or any other GL implementation provider.
- Recommended
- GTK3 or GTK2
- git (needed in order to download the source and compile in commit meta data)
- nasm 0.98.39 or later (x86-32 only)
- Optional
- zlib (GZDoom has a copy of it and will be statically compiled in if not found)
- libbzip2 (possibly static)
- libjpeg (possibly static)
- libgme or game-music-emu (possibly static)
- SDL 1.2.8 or later 1.2.x versions (for GZDoom 1.x)
- libglew (for GZDoom 1.x)
- FMOD Ex 4.36.x or later or FMOD Studio(for GZDoom 1.x and 2.x)
- Runtime
- gxmessage (optional - needed to show the crash log in a window)
- kdialog (optional - for KDE users)
- fluidsynth (optional - for MIDI playback)
In addition to or instead of FMOD, OpenAL can be used for sound in which case the following are required:
- libmpg123
- libsndfile
Install the following as root/superuser:
Debian/Ubuntu
Fedora
openSUSE
Mageia
Arch Linux
Gentoo
Update (29.12.2016):Jacendi overlay has an ebuild for gzdoom Us army great skills program.
PCLinuxOS
Solus
Do the following sections as normal user.
Create gzdoom_build directory
Download and prepare the source
Download the GZDoom source and create an out of tree build directory:
and run the following commands:
Download FMOD
For GZDoom 2.x or older versions.
Download FMOD and extract files to gzdoom directory:
Starting with commit 3ddc3d8fe, now you can compile GZDoom with OpenAL sound support and optinally disable/enable FMOD sound support. If you want to disable FMOD sound support, run:
and compile.
If afterwards you want to enable FMOD sound support, run:
Compiling
To compile GZDoom:
A development version of GZDoom will be compiled if you do not do #Latest stable version or #GZDoom 1.8.6.
Assuming all goes well, a gzdoom binary should be produced. To start GZDoom, the following command should work:
If GZDoom complains you do not have any IWADs set up, make sure that you have your IWAD files placed in the same directory as GZDoom, in ~/.config/gzdoom/, $DOOMWADDIR, or /usr/local/share/. Alternatively, you can edit ~/.config/gzdoom/gzdoom.ini or ~/.config/gzdoom/zdoom.ini to set the path for your IWADs.
Latest stable version
Show the latest stable version:
If you want to compile the latest stable version, run:
and compile.
After compiling, backing up and optionally installing the latest stable version, run:
GZDoom 1.8.6
If your graphics card does not support OpenGL 2.0 or higher, you may want to compile GZDoom 1.8.6. The minimum requirement is OpenGL 1.3.
First, you need to install gcc 5.x or lower:
Inside the build directory, run cmake with these arguments -DCMAKE_C_COMPILER=/path/to/compiler/gcc -DCMAKE_CXX_COMPILER=/path/to/compiler/g++, for example:
Now checkout GZDoom 1.8.6:
and compile. Please note that GZDoom 1.8.6 is old and unsupported. If you run into problems you are on your own.
Backup
If you want to backup GZDoom, do the following:
Create and name a directory with the corresponding GZDoom version/revision, build type and copy gzdoom, gzdoom.pk3, lights.pk3, brightmaps.pk3, game_support.pk3 and game_widescreen_gfx.pk3 to it. If you compiled GZDoom 2.x or older versions with FMOD sound support, copy liboutput_sdl.so to the destination directory.
Files are located at:
/home/<your username>/gzdoom_build/<your newly created directory>
Updating
When you wish to update GZDoom, copy and paste the following:
When the update finish, go to #Compiling.
Installation
- gzdoom = Stable version
- gzdoom-alpha = Development version
Commands beginning with 'sudo' will require temporary superuser privileges.
If you want to install GZDoom, do the following:
Create /usr/games/gzdoom and /usr/games/gzdoom-alpha directories:
Copy gzdoom, gzdoom.pk3, lights.pk3, brightmaps.pk3, game_support.pk3, game_widescreen_gfx.pk3 and the soundfonts directory to /usr/games/gzdoom/ or /usr/games/gzdoom-alpha/. If you compiled GZDoom 2.x or older versions with FMOD sound support, copy liboutput_sdl.so and the FMOD library file to the destination directory.
Create launch script:
Now from a terminal you should be able to run gzdoom or gzdoom-alpha from any user account.
Uninstallation
Remove /usr/games/gzdoom directory and all its files:
Remove gzdoom script:
Remove /usr/games/gzdoom-alpha directory and all its files:
Remove gzdoom-alpha script: Mods for the escapists.
Developing
This page has helped you compile GZDoom, but perhaps you are interested in debugging the code or submitting code changes or fixes for inclusion. This section is intended for more advanced users who may be unfamiliar to CMake or debugging on Linux systems.
Debugging
Prerequisite:
Maybe you have found a way to make GZDoom crash, and are interested in debugging it. First, you need to compile a debug build of GZDoom. Inside the build directory, invoke CMake to set up for compiling, but this time, the build type is set to Debug:
Optionally, you may want to use some of the #Build options.
After CMake is done, run
make
or to speed up compilation, run make -j<number>
, a recommended value for the -j
option is the number of physical cores:To run GZDoom under a debugger such as gdb, use the following command:
Now gdb should have you in its own command prompt:
You probably want to log the output, so lets output to a file gzdoomdebug.log:
Now start GZDoom by typing in run, and pressing enter:
Or put any command line parameters to gzdoom after run:
If GZDoom crashes, gdb may be able to tell you the source file and line number it crashed in. Typing in the command backtrace or bt will produce information telling the last function calls, showing how execution got to the point where it crashed:
All output will be copied into the gzdoomdebug.log, which can then be scrutinized later, or perhaps posted to the Bugs forum for other developers to look at.
To exit gdb's command prompt, type quit, q or press Ctrl-D:
If you want to free up space, run
make clean
to remove the files generated by the compilation.Build options
Options | Description | Example |
---|---|---|
NO_GTK=ON | Disable GTK+ dialogs. | cmake . -DNO_GTK=ON |
NO_FMOD=ON | Disable FMOD sound support. | cmake . -DNO_FMOD=ON |
NO_OPENAL=ON | Disable OpenAL sound support. | cmake . -DNO_OPENAL=ON |
FMOD_LIBRARY | Set path for FMOD library file. | cmake . -DFMOD_LIBRARY=/path/to/libfmodex(64)-x.y.z.so |
FMOD_INCLUDE_DIR | Set path for FMOD include directory. | cmake . -DFMOD_INCLUDE_DIR=/path/to/include/dir |
CMAKE_C_COMPILER | Set path for C compiler. | cmake . -DCMAKE_C_COMPILER=/path/to/compiler/gcc |
CMAKE_CXX_COMPILER | Set path for C++ compiler. | cmake . -DCMAKE_CXX_COMPILER=/path/to/compiler/g++ |
Types | Description | Example |
---|---|---|
Debug | Debug information, -O1 optimization. | cmake . -DCMAKE_BUILD_TYPE=Debug |
Release | No debug information, -O3 optimization. | cmake . -DCMAKE_BUILD_TYPE=Release |
RelWithDebInfo | Debug information, -O2 optimization. Useful for finding optimization bugs that only show up in Release. | cmake . -DCMAKE_BUILD_TYPE=RelWithDebInfo |
MinSizeRel | Similar to Release but with less optimizations in order to save space. | cmake . -DCMAKE_BUILD_TYPE=MinSizeRel |
How to increase Zandronum/GZDoom OpenGL FPS
Commands beginning with 'sudo' will require temporary superuser privileges.
Run Zandronum/GZDoom, start a new game, open console and type vid_fps 1, see how many FPS are displayed and exit Zandronum/GZDoom.
If you do not use Intel graphics, go to #Disable Vertical Synchronization for Zandronum/GZDoom.
Enable SandyBridge's New Acceleration
Prerequisite:
Debian/Ubuntu
- xserver-xorg-video-intel >= 2.19
Fedora
- xorg-x11-drv-intel >= 2.19
openSUSE
- xf86-video-intel >= 2.19
Mageia
- x11-driver-video-intel >= 2.19
Arch Linux
- xf86-video-intel >= 2.19
Gentoo
- x11-drivers/xf86-video-intel >= 2.19
PCLinuxOS
- x11-driver-video-intel >= 2.19
Solus
- xorg-driver-video-intel >= 2.19
How To Install Brutal Doom
If your Intel driver version is 2.21.14-1 / 2.21.15-2 or higher:
go to #Disable Vertical Synchronization for Zandronum/GZDoom.
Intel SNA is useful on all Intel graphics, not just SandyBridge.
Create /etc/X11/xorg.conf.d directory:
Create 99-intel.conf file:
Move 99-intel.conf to /etc/X11/xorg.conf.d/:
and logout and login.
Disable Vertical Synchronization for Zandronum/GZDoom
Do the following step if you are using a GZDoom version prior to commit 4eb32a50e. The following step works for the open-source graphics drivers.
Create ~/.drirc file:
Run Zandronum/GZDoom, start a new game, open console and type vid_fps 1, see how many FPS are displayed, you should get more FPS than before.
Reverting changes
How To Install Gzdoom Steam
Remove ~/.drirc file:
Gzdoom Android Apk
Remove 99-intel.conf file:
and logout and login.
External links
How To Install Gzdoom For Doom 2
Retrieved from 'https://zdoom.org/w/index.php?title=Compile_GZDoom_on_Linux&oldid=48202'