Skip to content
Daniel Gibson edited this page Oct 10, 2015 · 37 revisions

Which game data files are required?

Data files for the original Doom 3, including the MD5 hash:

MD5 (base/pak000.pk4) = 71b8d37b2444d3d86a36fd61783844fe
MD5 (base/pak001.pk4) = 4bc4f3ba04ec2b4f4837be40e840a3c1
MD5 (base/pak002.pk4) = fa84069e9642ad9aa4b49624150cc345
MD5 (base/pak003.pk4) = f22d8464997924e4913e467e7d62d5fe
MD5 (base/pak004.pk4) = 38561a3c73f93f2e6fd31abf1d4e9102
MD5 (base/pak005.pk4) = 2afd4ece27d36393b7538d55a345b90d
MD5 (base/pak006.pk4) = a6e7003fa9dcc75073dc02b56399b370
MD5 (base/pak007.pk4) = 6319f086f930ec1618ab09b4c20c268c
MD5 (base/pak008.pk4) = 28750b7841de9453eb335bad6841a2a5

And if you own the expansion pack Resurrection of Evil:

MD5 (d3xp/pak000.pk4) = a883fef0fd10aadeb73d34c462ff865d
MD5 (d3xp/pak001.pk4) = 06fc9be965e345587064056bf22236d2

Note that you have to patch your game to version v1.3.1 to obtain all files.

If you bought the game on CDs/DVD, base/pak000.pk4 - pak004.pk4 and d3xp/pak000.pk4 can be found on the disks, the other files are from the patch. If you bought it on Steam it should already be fully patched.

On Linux (and probably other Unix-like systems and maybe even Windows with a mingw shell) you can extract the needed files from the official 1.3.1 patch for Linux with:
sh /path/to/doom3-linux-1.3.1.1304.x86.run --tar xvf --wildcards base/pak* d3xp/pak*

How do I get the files using Steam?

First you need to buy the game (and the Resurrection of Evil Addon, if you want that too), of course.

On Windows, just install it and copy the game data from there (see above for what files are needed).

UPDATE: Unfortunately, downloading it with download_depot doesn't seem to work, maybe the data files are still encrypted or something. Things are downloaded that look right at first sight, but the .pk4 files are not actually zip files and have the wrong md5sum. See https://github.com/dhewm/dhewm3/issues/123
So you'll have to download with the Windows version of Steam (either on Windows or using Wine) :-/
Sorry for the inconvenience and I'd be grateful for fixes (if there's any way to decode the files or something).

On Linux/OSX unfortunately you can't just install the game, it's Windows-only on Steam.
However, you can open the Steam Console (launch steam with steam -console or try steam://open/console in a web browser) and enter the following:
download_depot <appid> <depotid>

This will download the base game files to a path similar to (the path cannot be configured):
~/.steam/root/ubuntu12_32/steamapps/content/app_<appid>/depot_<depotid>/

For Doom3 the AppID is 9050 and the DepotID is 9051.
For Resurrection of Evil the AppID is 9070 and the DepotID is 9071.

So in the Steam Console you'd enter:
download_depot 9050 9051
for Doom3 and
download_depot 9070 9071
for Resurrection of Evil.

It'll tell you when it's done, it'll look like:

] download_depot 9050 9051
Downloading 1491 MB ... 
Depot download complete : /path/to/Steam/ubuntu12_32\steamapps\content\app_9050\depot_9051

Can I use the Doom 3 BFG data files with dhewm 3?

No. Doom 3 BFG uses different formats for the archives and the game data itself.
Try RBDoom3BFG.

Where do I need to put the game data files?

Each mod keeps its data files in its own sub directory relative to the so called BASEPATH. For the original game the sub directory is named base and the expansion is named d3xp.

dhewm 3 tries to find the BASEDIR in the following order:

For Windows:

  • Next to the binary dhewm3.exe
  • The original Doom 3 installation directory (if you have installed the game from CD)
  • The steam Doom 3 installation directory

For *nix:

  • The data directory which was configured at compile time ($CMAKE_INSTALL_PREFIX/share/dhewm3; the default is /usr/local/share/dhewm3)
  • The default Doom 3 installation directory /usr/local/games/doom3 (if you have installed the game from CD)
  • Next to the binary dhewm3

For OSX:

  • The directory the bundle is in

Data files can also be placed in the savegame folder (see below). These will always take precedence over the paths listed above on all platforms.

Where do I find the config files and savegames?

For Windows:

  • My Games\dhewm3 in your localized My Documents

For *nix:

  • config files: $XDG_CONFIG_HOME/dhewm3 (default: $HOME/.config/dhewm3)
  • savegames: $XDG_DATA_HOME/dhewm3 (default: $HOME/.local/share/dhewm3)

For OSX:

  • Library/Application Support/dhewm3 in your home directory

The console key does not open the console. How to fix?

This is a side effect of the move to SDL.

You can just open it by pressing Shift and Escape at the same time.

Or you start the game once with the command line parameter: +set in_kbd german and open it with the key below Escape (^ on German layout, ~ on US layout, etc)

Current supported layouts are: english french german italian spanish turkish

If your layout is not supported, file a bug. You need to mention the symbol codes of the console key for your keyboard layout. These can be taken from this codepage. We need the codes (the bold ones) for the symbol you get when pressing that key, once without and once with shift.

How do I enable the OpenAL EFX sound effects?

Just enable EAX 4.0 HD in the system options.

Is the Demo Version of Doom3 supported?

No.

The game freezes on startup

This problem so far has only be observed with Chromebooks, I could imagine it happening on other ARM based devices as well, even though I couldn't figure out why exactly it happens (see https://github.com/dhewm/dhewm3/issues/102). It seems to hang while showing "loading menu".

Anyway, the workaround is to start the game with ./dhewm3 +set in_tty 0

It crashes in the first level, near an info terminal showing a video

... and the backtrace shows something about libogg/libvorbis.
This is a bug in libvorbisfile3 1.3.4-2 and earlier in debian (and possibly derived Distros like Ubuntu), caused by a patch that debian applied.
See https://github.com/dhewm/dhewm3/issues/104 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782831
Try updating libvorbisfile or building your own and enforce its usage with LD_LIBRARY_PATH or something.

Clone this wiki locally