Requirements

• A working version of Doomsday, PrBoom, and/or Chocolate Doom with the Doom/Ultimate Doom, Doom II, Final Doom, and/or Doom Shareware WAD file (Doomsday can also use Heretic and Hexen's WADs).

• A recent version of GTK+2 installed, including development packages (package ending in -dev or -devel in most distro repositories), GCC, pkg-config, and GNU make to compile from source. GTK+3 is currently not supported. (NOTE: For testing release 0.7.4 and future releases, GTK+3 is now supported, and GTK+2 version 2.24 or later is required. Please use Enyo 0.6.x if you cannot meet these requirements.)

Download

Download the latest version from the Downloads tab above. Extract with a suitable GUI tool or with tar zxfv enyo-(version).tar.gz. (As of 0.7, the package is named enyo-doom-(version).tar.gz.) Due to the small size of the package and it not needing many dependencies, I will not make binary releases of the GNU/Linux version -- ask your distribution's package maintainers if you want a package made for your distribution.

Use any enyo-doom package at your own risk. I cannot claim any responsibility for any damage to your computer, your health, your pets, your plants, the environment, or to the fabric of reality. Enyo is released under the GPL version 2, which means you can do what you wish with it as long as you keep the source free. For the legally-binding description, please take a look at the GPL itself to see what you can and can't do.

Compiling and installing

By default, enyo-doom will be installed in /usr/bin and its data files in /usr/share/enyo (/usr/share/enyo-doom as of 0.7). To change this, edit the first few lines of the Makefile in the extracted source tarball.

Simply type make to begin compiling enyo-doom. Since it is a small program I do not use the normal configure step to generate a makefile. If it complains that it cannot find gtk+-2.0, you need to install the development packages as instructed above, or the pkg-config tool is not installed or cannot find the GTK development files. Check the documentation for your distribution to find out how to properly set up pkg-config for GTK+-2.0.

When the build is finished, type make install as root to install enyo-doom. If you are using Ubuntu or a derivative, you will need to use sudo make install; most other systems you will need to do something like su -c 'make install'. The install should create a shortcut in the default menu structure for most desktops under Games; you can manually create a shortcut or run it from the commandline using the command enyo. (As of 0.7, the command is now enyo-doom.)

Configuration

You will need to point enyo-doom to a game WAD (the data file that contain Doom level, sound, graphic, music, etc data). Change the dropdown under the logo to the type of Doom WAD you have and use Find beside the Main WAD File entry to locate the proper WAD for that game type.

* Only on engines that support Heretic/Hexen

By default, enyo-doom will look in your system's PATH to find the binaries for Doomsday (doomsday) or Chocolate Doom (chocolate-doom). If these binaries are not in your PATH, you will need to set their location from the Global Options tab under "Path to engine binary", with the proper engine selected at the top.

Extra patch WADs (pwads) or any other file type (for example, Doomsday's pk3 files) that add levels, sounds, music, etc., can be enabled by enyo-doom by using the Add... button beside the Add-ons box in the Launcher tab. To return to having no extra WADs load, click Remove All; saving the WAD paths will then have no WADs load for that game type when enyo-doom starts. Each WAD set is specific to the game type you choose; also, selecting the shareware version of DOOM will disable adding pwads since it does not support them.

Under Global Options, there is a box to set how much RAM the Doom engine may use called "Memory to allocate". By default, this is set to 128. This sets the maximum memory the Doom engine will use. This setting is mostly used for the older versions of Doomsday, which by default sets the maximum memory used very low; if you get a message about maxzone needing to be increased, this is the setting to do so. Chocolate Doom seems to not be affected by this at all; in either case, leaving this set at 128 is generally the best choice. NOTE: This option is depreciated starting with the 1.9.0 versions of Doomsday, which means you may leave this option at its default if you are running this version or a later one (the option will be ignored by Doomsday).

The Advanced Options expander at the bottom of the Game tab hold two options. The first one is the ability to add extra commandline options to the game (this is saved per-game, so if you switch engines and the other engine does not support the extra option(s), you will need to change it). Secondly, you may save your current Game configuration under a new selectable entry with a new name that you specify -- this is useful if, for example, you want to save a certain PWAD combination (like Hell Revealed for Doom 2). You must have a basic game type selected to create a customized entry.

Everything else should be pretty self-explanatory; just click the Run Game button at the bottom to start the game. If you have any problems running, make sure the output window is enabled (under Global Options) and view the output of the engine; it may provide a clue about what is not configured correctly. For Chocolate Doom, it is recommended that you run the chocolate-setup before you use enyo-doom to run it, since the majority of that engine's configuration is done there. To eliminate the information screen that pops up after you exit Chocolate Doom, untick Show ENDOOM screen in Display Configuration in chocolate-setup. There is unfortunately no way I have found to eliminate the ENDOOM screen in prBoom; this will show up as a jumble of control characters and text at the end of the output. You can just safely ignore this.

Windows version

The Windows version was quickly written using C# (2010) in under an hour to fill my need for a Chocolate Doom/ZDOOM launcher under Windows, and is probably very, very buggy. The current version is a rewrite of a version I did earlier using Visual BASIC.NET, which is a horrible, horrible language. It is still, however, experimental since it is a straight rewrite into C#. Therefore, I am not supporting this version at all; if it doesn't work, it doesn't work.

You will need the latest version of the .NET runtime (2010) available from Microsoft to run it. The latest version uses the .NET application publisher.

It currently supports Chocolate DOOM and ZDoom; either place it in the directory with the Chocolate Doom and/or ZDoom executables (it expects chocolate-doom.exe and zdoom.exe) or select the executable from the Settings tab for the proper executable. Besides choosing the main WAD and PWADs, there are no other configurable options at this time.

I dumped whatever I thought was appropriate to build this under Visual C# 2010 into the source ZIP. If it's not everything Visual C# 2010 needs to compile it, you might have to cobble it together. However, from what I can tell, the entire source and support files are there.

Enyo?

Enyo (ih-NAI-oh) is the Greek goddess of war, known as Bellona in Roman mythology. She is the companion to Ares, the god of war (known as Mars in Roman mythology), and his two sons Phobos and Deimos, linking Enyo to the setting of Doom (the Martian moons of Phobos and Deimos and occasionally Mars itself). (Information from the Wikipedia article on Enyo.)