- Where to download
- Installation Instructions
- game modding and server administration documentation
- Third party installers
- Corrupted doom3.png
- AMD 64
- Alsa and multichannel sound
- SNDCTL_DSP_SPEED failed to get the requested frequency 44100, got 48000
- Unable to initalize OpenGL / Couldn't get a visual
- Unable to initialize OpenGL / fails right after dlopen on gentoo
- How can I get Linux players on my 1.1 Windows server?
- Should I replace libgcc and libstdc++ with the ones from my distro?
- Doom III is hitching on 2.6.9 kernel
- Known issues
- Reporting Bugs
Sun Jun 17 14:28:22 CDT 2007
DOOM III 1.3.1, build 1304
This was actually released back in February, but I'm only getting around to update this page now. This is a bugfix release for 1.3, with a number of things specifically fixed/added for mods. See below for the links to our ftp and BitTorrent tracker.
6325f0936f59420d33668754032141cb doom3-linux-220.127.116.114.x86.run 48330b83d08298826992da9a348c1620 DOOM3-1.3.1.exe fa8a444186359384a0acdcafb91dff88 Doom3Mac1.3.1RevA.dmg
Where to download
GNU/Linux system, Pentium III, 1Ghz 256Mb RAM Kernel 2.4, 2.6 is recommended glibc 2.2.4 and up 3D card: NV10 or R200 minimum hardware OpenGL hardware acceleration 64 MB VRAM sound card, OSS or Alsa, stereo sound and 5.1 are supported with both APIs Alsa version 1.0.6 or above is required A licensed copy of Doom III retail for Windows In order to play the additional Resurrection of Evil Expansion Pack, a licensed copy of the Expansion Pack for Windows
Sound card and 3D card are not needed for the dedicated server
Demo installation instructions
By default, the setup will install the files to /usr/local/games/doom3-demo Start the demo with the command: doom3-demo You don't need to copy any files
Patch installation instructions
The following files need to be copied from the win32 install CDs to your base/ directory ( md5 sums provided below as reference ) by default, /usr/local/games/doom3/base 71b8d37b2444d3d86a36fd61783844fe base/pak000.pk4 4bc4f3ba04ec2b4f4837be40e840a3c1 base/pak001.pk4 fa84069e9642ad9aa4b49624150cc345 base/pak002.pk4 f22d8464997924e4913e467e7d62d5fe base/pak003.pk4 38561a3c73f93f2e6fd31abf1d4e9102 base/pak004.pk4 If you are also installing the Resurrection of Evil Expansion Pack, you need to copy the following file to your d3xp/ directory by default, /usr/local/games/doom3/d3xp a883fef0fd10aadeb73d34c462ff865d d3xp/pak000.pk4 Localization is not supported on Linux ( only english ), you should not copy over any of the zpak files. Start the game with the command: doom3 Start the dedicated server with the command: doom3-dedicated If installed, you can start the Expansion Pack directly from the command line with the command: doom3 +set fs_game d3xp Or you can select it in the mods menu of the base game.
game modding and server administration documentation
The official website for DOOM III modding is http://www.iddevnet.com/ However, some documentation about the new features in DOOM III 1.3 is available here:
AutoDownload - how to run custom maps on your server and have players autodownload them when connecting
AddonPaks - improved control over what your players have to download when connecting to a server
fs_game_base - run mods based off the base game and another mod ( RoE for instance )
Third party installers
Some individuals and distributions are repackaging id software releases for Linux into their own installers. We need to insist here again that this is not legal. You can not tamper with id software's intellectual property by redistributing the games under a modified form. The only distribution format for id games on GNU/Linux is the installer we provide. In particular, it is essential that all users acknowledge the End User License Agreement prompt before any installation. DOOM III on GNU/Linux is a proprietary product, and it cannot be handled in the same way as free software products would.
As a user, you should refrain from using any such third-party installer. Please do not report any setup or runtime bugs if you are not using the official installers.
Some installations carry a corrupted doom3.png icon file. You can get a correct one here.
ATI's Proprietary Linux Drivers (fglrx) version 3.14.6 and up will run DOOM3. Download fglrx from http://www.ati.com/support/drivers/linux/radeon-linux.html.
The DRI drivers for ATI cards may run the game with some tweaking ( you need to apply the S3TC patch for instance ). But the rendering quality will be sub-optimal, as a number of important graphic features are not available in the DRI drivers.
There are no amd64 builds planned at this time. However the 32 bit binaries will run in a native amd64 environement.
Localization is untested in the Linux builds at this point. More localization features are possible in future release. Until then you should not copy over the zpak000.pk4 file at all.
Alsa and multichannel sound
Starting with build 1286, DOOM III on Linux now supports both Alsa and OSS sound backends, as well as multichannel sound.
If you are having trouble with Alsa, here are a few things you can try:
instead of the default device, try using plughw:0, and surround51 for multichannel. A lot of Alsa installations have a misconfigured default device. You do that by passing +set s_alsa_pcm <alsa_device_name> on the command line.
if you are trying to get multichannel sound, make sure stereo works already. You switch between stereo and multichannel with +set s_numberOfSpeakers 2 and +set s_numberOfSpeakers 6
on amd64 systems you may need to get the snd-ioctl32 module loaded in
Then, if Alsa doesn't work, try using the OSS emulation ( +set s_driver oss ) .. and after that, just use plain OSS ( the OSS/Free implementation, or even better the OSS/Linux one from OpenSound ). OSS is not an outdated and deprecated sound API. It turns out to be much easier to setup and operate than Alsa for a lot of people.
SNDCTL_DSP_SPEED failed to get the requested frequency 44100, got 48000
Deprecated: this issue should only happen if you use one of the old 1282 builds
The sound engine will only output 44.1KHz. This indicates that your sound processing cannot do this and suggests 48KHz instead. Depending on your setup, try to find a configuration that allows 44.1KHz. If you are running artsd for resampling/multiplexing, you can try to reconfigure with the following command: artsd -s 44100 -F 6 -S 256
Unable to initalize OpenGL / Couldn't get a visual
You need to be running a 24bpp desktop. If you use the glxinfo commands, you will see 24bpp modes in the visuals list:
$ glxinfo [..] visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat ---------------------------------------------------------------------- 0x21 24 tc 0 32 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None [..]
Unable to initialize OpenGL / fails right after dlopen on gentoo
Deprecated: this issue should only happen if you use one of the old 1282 builds
This appears to be a specific issue on gentoo with nvidia card. Even with a valid /usr/lib/libGL.so.1, dlopen would fail. One hack around it is to run like that:
$ LD_PRELOAD=/usr/lib/libGL.so.1 doom3
Recompiling glibc and the nvidia drivers with NPTL support should fix the problem:
$ USE="nptl" emerge glibc
You will need to emerge the nvidia drivers configured with NPTL as well.
How can I get Linux players on my 1.1 Windows server?
The Linux paks were not included in the Win32 1.1 release. But you can drop the Linux game pak file in your base/ directory: Linux 1.1 game file for win32 servers
Should I replace libgcc and libstdc++ with the ones from my distro?
While we haven't seen that replacing them will noticeably improve performance, on some distribution (gentoo for instance) this is known to cause crashes. At your own risks.
Doom III is hitching on 2.6.9 kernel
There is a bug in 2.6.9 kernel causing kswapd to stall the system. See http://www.ussg.iu.edu/hypermail/linux/kernel/0410.3/0086.html. Thanks to roothorick for pointing this out.
Doom III would hang during starting if you redirect the output. Pass +set in_tty 0 on the command line to fix: $ doom3 +set in_tty 0 > output.txt
If you want to report an issue with the game, you should make sure that your report includes all information useful to characterize and reproduce the bug.
check the Linux Gamers' FAQ for any issue not covered here
search on Google
include the computer's hardware and software description ( CPU, RAM, 3D Card, distribution, kernel etc. )
include the output of glxinfo
if appropriate, send a console log, a link to a save game, a screenshot, an strace ..
Note that we can't help you with OS-specific issues like configuring OpenGL correctly, configuring ALSA or configuring the network.
If you are sending a console log, make sure to enable developer output:
$ doom3 +set developer 1 +set logfile 1
If you have a complete and precise bug report, email it to me: ttimo at idsoftware dot com