From The DarkMod Wiki
Revision as of 15:15, 13 April 2023 by Nbohr1more (talk | contribs) (→‎No Sound with Pipewire)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search


This FAQ relates to the full TDM release version only. For players of the pre-release demos such as Thief's Den and Tears of Saint Lucia please refer to the Demo FAQ.


This wiki page is an amalgam of various issues discovered by TDM players and team members.
Many of the issues documented here only affect a small percentage of players.
Also, many of the issues documented here are no longer applicable in either Standalone or the latest TDM releases.

What do I need to play The Dark Mod?

With the release of TDM 2.0, you no longer need Doom 3 installed. The Dark Mod is completely standalone (and free!).
You need only follow the installation instructions on the website to start playing the game.

We do recommend that you have at least 2GB of RAM, 30GB of free HDD space, and at least a OpenGL 3.2 capable GPU with 512MB of VRAM.
Here is an article with low-end hardware confirmed to work with TDM Known System Configurations

Supported Operating Systems

Which Operating Systems are supported?

Windows, Mac os and several Linux Distribtutions are supported.


Which Windows versions can I use? The following versions of windows have been tested and are known to work: Windows 2000, Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server 2008, Windows Server 2003 in both 32bit and 64bit flavours.

  • As of TDM 2.08, Windows XP is no longer supported

Windows 10

Many users (including myself) have reported that TDM runs well under Windows 10. Like Windows 8\8.1 there have been some problems with the darkmod folder preventing updates due to OS protections. Most users can bypass these problems by changing security settings on the folder.

A note about Windows 10 security

Windows 10 has added some granular security options to address CPU hardware vulnerabilities like Meltdown and Spectre.
These may negatively impact load times or otherwise interfere with The Dark Mod.

Please see this reference and white-list TheDarkMod.exe (and\or) TheDarkModx64.exe


Windows 8.1 Preview

Thus far, on Intel HD graphics, TDM will not start unless it is started in Windows 7 compatibility mode:
Right click "TheDarkMod.exe" choose "Properties", click the "Compatibility" tab and select Windows 7 from the dropdown list. This may not be representative of other graphic hardware and may be due to early Windows 8.1 driver support.

Windows XP 32-bit

  • Obsolete info. TDM v2.05 is compiled with the XP flag in MSVC 2013.

As of TDM 2.08 Windows XP is no longer supported

Windows 2000: freeaddrinfo cannot be found in WS2_32.DLL

Please refer to the main article TDM in Windows 2000 to work around this problem.

PAE Enabled

One user with Windows XP Pro SP3 and an AMD Phenom processor reported problems starting Doom 3 due to having PAE enabled. Thread


Does it run in Linux?

Yes, Linux is supported.

Does it run in 64 Bit Linux?

Yes, the darkmod.x64 is a native 64-bit executable.

  • Obsolete info below. As of TDM 2.06+ there are native x64 builds.

Yes, Linux 64 bit is supported. In addition to the steps above, you need 32 bit compatibility libraries.

Steps to install TDM on a 64 bit disto are described in Installer and Manual Installation

since Doom3 is 32 bit only:

  • On SuSE, they should be included.
  • On Ubuntu/Kubuntu, install the package ia32.

For TDM after 1.0, this step should be no longer neccessary:

  • Since you cannot install 32 bit libraries on a 64 bit system with the normal package manager, you should use getlibs to install libmng and the boost filesystem lib:
getlibs libmng.so.1
getlibs -l libboost-filesystem1.34.1

What about Gentoo?

Yes. It's not "officially" supported (the team doesn't test it specifically), however several users have reported success running TDM under Gentoo.

What about Ubuntu 8.10?

Yes, thedarkmod.x64 works on Ubuntu

* Obsolete info. As of TDM 2.06 Boost Libraries are no longer required.

Yes. As of this writing you will need to install the libboost-filesystem package.

GLIBCXX_3.4.9 errors

If you receive an error about GLIBCXX_3.4.9, delete or rename the files /usr/local/games/doom3/libstdc++.so.6 and /usr/local/games/doom3/libgcc_s.so.1.

If this doesn't resolve the error and you have an old version of GCC, then you may have to upgrade. It has been confirmed that, at least under Gentoo, GCC 4.1 does not work with TDM but GCC 4.3 and GCC 4.4 are compatible.

Mac OS X

Does it run on Mac OS X?

Yes, but only for tdm 2.05.
But for newer versions of TDM, you can use several WINE-sollutions.
These and other solutions to run TDM on Mac OS.
can be found in article Installer and Manual Installation

Graphics and Drivers

Does TDM support widescreen resolutions?

See also Resolutions

Yes. Choose "16:9" or "16:10" in the in-game Settings menu, and select the appropriate resolution. Note that you need to restart the game to have the new setting in effect.

If the native resolution of your wide screen monitor is not listed, you can enter it into Darkmod.cfg by changing the following entries like so:

seta r_mode "-1"
seta r_customwidth "1280"
seta r_customheight "800"
seta r_aspectratio "2"            // means 16:10, "1" is 16:9, other ratios are not yet supporred
If you get performance problems, please consider using a lower resolution and taking a look at Performance Tweaks.

What about TV resolutions like 1360x768?

If you have a wide-screen TV which uses any non-standard resolution, like 1360x768 (instead of 1366x768), then please use the following:

seta r_customWidth "1360"
seta r_customHeight "768"
seta r_mode "-1"
seta r_aspectratio 2
seta g_fov "100"                  // or any other suitable value

Alternatively, see the manual of your TV on the possibility to switch it to a "1:1" pixel mapping, or "monitor mode" or "computer mode".

Here is some background information: http://hd.engadget.com/2006/04/21/whats-the-deal-with-1366-x-768/

If you get performance problems, please consider using a lower resolution and taking a look at Performance Tweaks.

Changing the screen resolution/aspect ratio does nothing!?

These changes require a restart of Doom to work. Alternatively the command vid_restart can be issued at the console.

It can take quite some time to execute this command, depending on whether or not you're already ingame.

It will still be a lot faster than restarting and reloading the game though.

2.07 FBO and Resolution

As of TDM 2.07, all rendering results happen in a "Frame Buffer Object" (FBO).
TDM automatically tries to automatically set the screen resolution to match your monitor
and generates a FBO of matching resolution.

There is now a resolution scale slider that you can use to decrease the FBO resolution for extra performance.

In 2.09 your resolution is locked to Desktop resolution when in fullscreen mode.
Lower Render Scale is the only way to reduce fillrate impact unless you are willing to change your Desktop resolution.

NEW : 2.10 restores the ability to change resolution and still offers render scale options to improve performance.

Screen is Oversized in Fullscreen Mode (Image is too large to fit the screen area available)

Windows 7 Aero desktop is known to make the screen too large in fullscreen mode. This can be remedied by setting Windows 7 Aero to Basic.

This issue is discussed in more detail HERE.

Disable Desktop effects on Windows 10

To begin the process, type sysdm.cpl in Run box (Windows + R) and hit Enter to open the System Properties.

Select the Advanced tab and under Performance, Click the left mouse button click on Settings.

In the Performance Options box, select the Visual Effects tab.

Check "Adjust for Best Performance" then click Apply.

(this will also improve performance in some cases)

High DPI

Some users have reported that High DPI causes the same problem. Use these steps to disable it.

Right Click Click the right mouse button on TheDarkMod.exe or your shortcut, go to the Compatibility Tab and check "Disable Display Scaling on High DPI settings"
Click Submit Click the left mouse button


Right Click Click the right mouse button on your Desktop and select: screen resolution > make text and other items larger or smaller > Set to Medium

Dark Mod Setting Issues

Textures are missing, screen mostly black

Black textures

Look into your darkmod.cfg inside your darkmod folder and check that the following settings are like shown below:

 seta image_usePrecompressedTextures "1"
 seta image_useNormalCompression "0"
 seta image_useAllFormats "1"
 seta image_useCompression "0"
 seta image_preload "1"

Note: Disabling compression may lead to Malloc errors due to memory consumption. You may be able to compensate by setting image_downsize options. See Malloc Failure Errors

The briefing is very fuzzy

  • Obsolete info. TDM 2.05 no longer makes the menus fuzzy when using image_downSize.

Look into your Darkmod.cfg inside your darkmod folder and check that the following settings are like shown below:

seta image_roundDown "1"
seta image_forceDownSize "0"
seta image_downSize "0"

Note: Disabling image_downsize options may lead to memory related errors.

You may be able to compensate by enabling texture compression (see #The game is very slow! )

or only downsizing bump\normal maps. See also: Malloc Failure Errors

Driver Issues

Optimus Laptop wont use your Nvidia GPU

See also: [1]

Many Laptops now have the ability to use the GPU that is built into the CPU when not "gaming".
Unfortunately, sometimes the drivers for these Laptops don't detect TDM as a "game".

The easiest solution is to create a Driver Profile for TheDarkMod.exe or TheDarkModx64.exe in your driver settings.

  • Right click Click the right mouse button anywhere on your desktop where no icon is shown
  • Left Click Click the left mouse button Nvidia Control Panel
  • Then click on the Programs Tab
  • Click "Add" and browse for TheDarkMod.exe or TheDarkModx64.exe
  • Then scroll down the settings list and find "OpenGL Rendering GPU"
  • Then select your Nvidia GPU from the list of options

Nvidia Profiles.jpg

Disable Catalyst AI in recent AMD ATI drivers

NEW 2018:

For the new Radeon Crimson and Adrenalin drivers this is simply:

Surface Format Optimization = OFF


From (at least) Catalyst versions 10.12 and beyond, the ability to disable Catalyst AI properly has been changed or removed.

Rage3d and Guru3d have advised using "Radeon Pro" to address this.


  • 1) Remove Catalyst Control Center (removing all ATI drivers recommended then re-install just the Display driver)
  • 2) Download and install "Radeon Pro" Radeon Pro Thread at Guru3D
  • 3) Create a profile as follows:
If you're using RadeonPro, create a profile for the game you want to disable Catalyst AI. 
Right-click the newly created profile, keep left shift key pressed and choose 
Open Location on context-menu, this will open the profile's XML definition. 
Append a new line and add entry like this

<Property name="CatalystAI" value="0" />

Save the file and start the game. CatalystAI should be disabled.

I also recommend to open ___GlobalProfile.xml 
(found on same directory where your profile is saved) 
and look for "CatalystAI" entry, it must be equal to "1" 
otherwise CatalystAI will be kept disabled after you exit your game.

CFX disabled by setting CatalystAI to 0

Here's another alternate method for Windows users:

  • 1) Obtain a copy of the free "ATI Tray Tools" by Ray Adams from Guru3d.
  • 2) Install it into your Windows tray.
  • 3) Right-click it.
  • 4) Select Direct 3d -> Catalyst AI -> Off.
HDR-Lite Post-Processing problems

Some owners of ATI graphics cards reported various artifacts when HDR-Lite Post-Processing was enabled. Among these artifacts are a distorted or upside-down screen and spinning sky. These can usually be fixed by disabling Catalyst AI, which also gives better loading times.

To turn off Catalyst AI, open your Catalyst control panel, go to 'graphics' at the top left, select '3d' from the dropdown list and on the new menu below, select 'AI'. Now select the 'Disable Catalyst A.I.' checkbox.

(For more recent Catalyst versions see: Disable Catalyst AI in recent AMD ATI drivers )

* This is probably obsolete. The Bloom features in 2.08 and newer are completely different than the old ARB shader approach referenced here.

Upside-down screen

See HDR-Lite Post-Processing problems above.

It has also been suspected that HDR-Lite Post-Processing may lead to poor performance underwater

Disable Nvidia "Threaded Optimizations"

Many random crash behaviors seen by Nvidia users can be resolve by the following steps:

Open Nvidia Control Panel ->

Manage 3D Settings ->

Bottom half of list locate "Threaded Optimization" <-- Set to NO / Off

Also set "Multi-display/Mixed GPU acceleration" to "Single display performance mode"

  • Note: Newer Nvidia drivers seem to have cured these issues, and now the reverse issue was found by one user.
    It has been found that disabling Threaded Optimizations has dropped FPS from 60 to 25FPS.

The game hangs at Dark Mod screen/ locks up while turning on vsynch

Catalyst Control Center above 10.8 for ATI cards has a performance slider for V-Synch.
Setting that slider to Quality (Always On) fixes this issue. If set lower than quality and it is set to on in game it will freeze. (tested specifically in CC 10-11)

Graphic Corruption

One report we had was for a Radeon ATI HD 4650, catalyst 10.9. This screen corruption as I understand it was heavy pixelation even on the menus. Closing down Xfire fixed it. "I fiddled with the xfire Doom 3 configuration through the xfire_games.ini, and determined it has to do with InGameFlags portion. For some reason the settings in that were interfering with doom 3, and after I removed some things from there, I was still able to run xfire, and doom 3 was still able to look proper."

(For more recent Catalyst versions see: Disable Catalyst AI in recent AMD ATI drivers )

Performance Issues

Please see the article about Performance Tweaks to significantly improve performance.
The suggestions below are just a quick summary of the basics.

The game is very slow!

If you get less than 10 FPS, or the game even stutters, please try this:

1) Try enabling "Frontend Acceleration" ( "r_useParallelAddModels 1" ) under Video Settings > Advanced > Experimental Options

2) Try setting tdm_lg_interleave to 3 or more while setting tdm_lg_interleave_min to 1

3) Disable or lower in-game AA settings. (Or use driver AA options such as FXAA instead.)

4) Disable Soft Shadows

5) Set Shadow mode to "MAPS" in the Advanced Video settings ( also set r_shadowMapSinglePass 1 )

6) Disable SSAO

7) Disable "Bloom"

( OBSOLETE in 2.09 ) Set Ambient rendering to "Faster"

( OBSOLETE in 2.09 ) Set Interaction rendering to "Standard"

8) Set Object Detail to "Lowest"

9) AF to lower values or off

10) Disable v-sync (if acceptable) or set to Adaptive

11) Lower your Render Scale

12) Lower your Resolution

Look into your Darkmod.cfg inside your darkmod folder and check that the following settings are like shown below:

 seta com_smp "1"
 seta image_usePrecompressedTextures "1"
 seta image_useNormalCompression "1"
 seta image_useAllFormats "1"
 seta image_useCompression "1"
 seta image_preload "1"

If that doesn't help, your system might not have enough memory.

Try the image_downsize changes referenced here Malloc Failure Errors

Beyond the above, you may need to kill background applications, increase your system RAM, or upgrade your GPU to one with 1GB or more of VRAM.

Note: Many of the above changes can be made independently of each other so you may, for example, keep some quality options higher whilst reducing others based on preference and experimentation.

Linux UEFI (Secure Boot)

Most Linux distros fallback to (slow) open drivers if you do not have proper Secure Boot keys setup.
For the best performance, disable Secure Boot.

Slow loading times

OBSOLETE! TDM 2.10 has very fast loading times!
The only setting that might improve loading times is "seta image_preload 0"
If you find an FM is very slow to load it may be an ATI graphics card problem. One report says this was cured by turning off Catalyst AI. Also cures HDR-Lite Post-Processing Problems.

Changing the following settings to 0 will also reduce loading time, but be warned: if you have a lower-end system, poor graphics card, or low ram, you will likely notice a performance hit ingame since you will now be using uncompressed textures.

 seta image_useNormalCompression "0" 
 seta image_useCompression "0"
 seta image_preload "0"

Note: Setting image_preload 0 can cause stuttering when moving from area to area while textures load in. Note: Most TDM textures are pre-compressed so "image_useCompression 0" generally wont help much... but "image_useNormalCompression" will. Note: Disabling (standard) compression may lead to Malloc errors due to memory consumption. You may be able to compensate by setting image_downsize options. See Malloc Failure Errors

Underwater performance poor

Some people suffer from very low framerates underwater with HDR-Lite Post-Processing enabled. Currently, the only known fix to this problem is to set g_doubleVision to 0 in the console. This however disables the doubleVision effect completely, so that there is no underwater-blur any more. The murkiness still remains though.

Note: This workaround will cause many fogged water types to become opaque. Disabling Post Processing is a better option at this time.


It is hard to answer questions on why something fails, because wildly different systems cause wildly different symptoms. If the following section does not help you, please ask at our forums.

For any solutions below that refer to "disabling Catalyst AI", if you discover you can not use ATI's tools to do so, alternate methods are discussed in Disable Catalyst AI in recent AMD ATI drivers below.

General Troubleshooting Basics

Please see: Reporting a Problem

The game crashes on load

Make sure that:

  • Your system meets at least the minimum system specs.
  • You have enough free main memory. Try closing a few running programs like Outlook, Anti-Virus or torrent clients.
  • Nvidia "Threaded Optimizations" are causing Doom 3 Mod stability issues (see: Disable Nvidia "Threaded Optimizations" )
  • Backup then delete your Darkmod.cfg to see if a fresh configuration will resolve your issue
  • 2.06 Try the 32-bit executable. Some systems (primarily 32-bit ones...) may not launch the 64-bit one.
  • The new Multi-Core optimization is unstable on some systems. Set com_smp 0 in your Darkmod.cfg to force this off prior to start.
  • 2.07 try disabling "Fence Sync" (r_useFenceSync = 0)

If that doesn't fix it, you probably receive an error message referencing an "Unknown event" at startup, like the screenshot below illustrates.


Here are a couple of known problems and their solutions:

  • Sometimes, the procedure fails due to spaces in the installation path. Try extracting the gamex86.dll manually using Winzip or similar or install Doom 3 in a different directory.
  • You have a firewall installed that prevents the copy procedure, because since version 1.03, TDM has a built-in mission downloader. This misbehavior has been reported for the COMODO Firewall.
  • It is also possible that an old version of gamex86.dll (or gamex86.so) is lying around in your Doom 3 folder. Delete it and try again.

TDM Updater

OBSOLETE! Please use tdm_installer which you can download here:


See also TDM installer and zipsync

Updater (tdm_update.exe) closes almost as soon as it's started

See the main article on tdm_update.

Updater (tdm_update.exe) crashes at some point during the update

The Windows update will crash at the "Applying Update" stage if the Darkmod folder is set to "read only". You fix it by right clicking on the folder, going to folder properties, and unchecking the box that says "read only" under folder attributes.

Can't load saved games -- TDM gives error about "can't load .script" file

Make sure your folder is called "darkmod". If it isn't, rename it. That should make the problem go away. I've heard reports that having spaces in the names of any folders in the path can cause problems, but haven't confirmed it. Something to try if it still happens and your folder is already called "darkmod". This is fixed as of TDM 2.02

FM won't install manually

If you are running Dark Mod under Linux and have edited the file darkmod/currentfm.txt this might prevent the FM from installing. This may be fixed in an update but apparently editing using notepad under Wine works OK.

FMs downloaded but don't show in menu list

You have downloaded some FMs but they don't show on Dark Mod's New Missions list. Possible causes:

  • You must not extract the pk4s or zip files but put them into the darkmod/fms folder (or alternatively you can create the FM folder in there eg, darkmod/fms/chalice for chalice.pk4 or chalice.zip.
  • Early versions of Dark Mod cannot handle zip suffixes. Solution: rename to .pk4 or run tdm_update to get the latest version of Dark Mod.

FM downloaded but won't play

If you have downloaded an FM you might see it in the New Missions List but can't get it to play. These are almost always an install problem. These are some of the causes and cures:

FMs (fan missions) are archives and in early versions of Dark Mod MUST be suffixed .pk4 not zip. Apparently Internet Explorer 8 may change it from pk4 to zip during download without telling you. You need to rename it back if running an early version of Dark Mod else run tdm_update to update and then zip files are OK.

You do NOT need to extract the pk4 archives to install or play. Just download into or move the pk4 into the darkmod\fms folder. Optionally you can create a folder of the same name as the map and put it in there, eg, darkmod\fms\chalice but there is no need because Dark Mod will create that automatically. Just make sure your pk4 goes, unopened, into the fms folder, then run TheDarkMod.exe

If you have done the above but see for example, a blank objectives screen and no briefing then it is still almost certainly an install error. I recommend you do a clean sweep if in doubt:

  • Exit Dark Mod
  • Delete darkmod\currentfm.txt (this just uninstalls any FM)
  • Move the pk4 into the darkmod\fms folder if it is not already there.
  • Delete the darkmod\fms\FMname folder if any, eg, darkmod\fms\chalice. Don't worry if there isn't one; it will be created automatically later.

So all that is left is the pk4 in the fms folder. Now run TheDarkMod.exe. The FM should be in the list in the New Missions menu. Re-install it and you should now be able to play it.

AI are tread-milling into easily avoided obstacles or having pathing issues

While this can be the fault of poor map design or monsterclip placement,
one thing that can cause this is the performance cvar:

seta cm_backFaceCull "1"

This cvar does improve performance but it is not worth the hassle in most cases.
We recommend disabling it (cm_backFaceCull "0" ) unless you know the mission you're playing has been tested with it enabled.

Textures are missing, shadows are pitch black

Try disabling the AGP surface accelerator in DXDIAG.

The sky is corrupted

You either see black sky, or fragments of other textures. This seems only to happen on Geforce 6800 cards.

There are two fixes for this:

As a quick fix you can rename the following folder:


to a different name. That will result in black sky.

Alternatively, edit the file materials/tdm_sky.mtr with notepad or a different editor and find the sky material named textures/darkmod/nature/skybox/skybox_darkland_NE:

 //Author: Dram
 //skybox_ocean with ocean replaced with dark land
 //Moon moved to north east by Fidcal
    qer_editorimage env/skyboxes/skybox_ocean/ocean_ed
        blend add
        cameraCubeMap env/skyboxes/skybox_darkland_ne/darkland_NE
        texgen skybox
        texgen wobblesky .0 .0 .0

In this declaration, comment out the line that reads forceHighQuality by adding // in front of it:

 // forceHighQuality

That should fix the sky and make it render correctly.

The Sky rotates

This problem only affects FMs with a dynamic sky (eg, moving clouds etc.).

If you see the sky spinning it may be an ATI graphics card problem. One report says this was cured by turning off Catalyst AI. Also gives better loading times and cures HDR-Lite Post-Processing Problems.

If that doesn't fix it then try this. Note that it replaces dynamic sky with a static clear one so it might look odd in a stormy FM for example, but better than a spinning sky:

* Create a new folder in your darkmod folder called materials.
* Within it create a plain text file named no_skybox.mtr.
* Paste in the following:

 	qer_editorimage env/skyboxes/skybox_ocean/ocean_ed
 		blend add
 		cameraCubeMap env/skyboxes/skybox_darkland_ne/darkland_NE
 		texgen skybox
 		texgen wobblesky .0 .0 .0

(For more recent Catalyst versions see: Disable Catalyst AI in recent AMD ATI drivers )

Sound Issues

Game freezes for several seconds when opening doors

  • Note: This may be obsolete as of TDM 2.06 as the EAX code has been replaced by EFX.

The following problems :

A) "game freezes and loads some data from hard drive while opening doors"

B) "while loading mission you are returned to the menu and need to restart loading"

are often resolved by disabling EAX 4.0 HD in the Audio Settings menu.

The sound lags behind the picture

  • This may be obsolete as of TDM 2.06 as the audio sub-system has be revised to use the OpenAL framework from Dhewm3

This seems to happen on some Linux Distributions with PulseAudio. Doom's sound engine defaults to ALSA, you can try to use OSS instead:

Add the following to your dmargs.txt (it is in ~/.doom/darkmod/):

+set s_driver oss

If your system does not provide OSS or a working OSS-emulation (try padsp ./tmdlauncher-linux), reset this to best which means ALSA.

While OSS or ALSA deal directly with the sound hardware, PulseAudio is a soundserver that puts itself between the application (doom3) and ALSA. Your goal is to bypass the PA-part while playing TDM.

You can either disable the PulseAudio daemon temporarily or connect Doom directly to ALSA.

To disable PA, create a file named client.conf in ~/.pulse which contains:


Then open a terminal and type:

pulseaudio -k

When sound playback fails, make sure you have s_driver set to best, and s_alsa_pcm to default. When it works, you propably want to adjust volume settings outside TDM. Try alsamixer (in a terminal).

When you're finished playing, turn PA back on:

pulseaudio -D

starts the daemon. Changing autospawn to yes should prevent you from doing this manually after every reboot.  :)

The other way, just bypassing PA, requires some knowledge about your sound hardware. Type

aplay -L

This gives you a long list of your ALSA playback devices, three lines for each, first line is <name>. Choose the one with PCM Playback that your speakers are connected to and add

+set s_alsa_pcm <name>

to dmargs.txt. If <name> is not convenient for you just try something like hw:1,0 if you know what you are doing, but be aware abstract designations like default will get "hijacked" by PA.

No Sound with Pipewire

Many modern Linux distributions are adopting a new "pipewire" audio framework.
TDM does not have a native pipewire interface but you can install pipewire-alsa to allow TDM to use alsa calls for sound.

Some modern Linux distributions with pipewire will still render audio via Alsa Default
For these distributions, applications must run as a user. No audio will render when running as root or sudo.

Getting "Malloc Failure for #######" crash-to-desktop

Note: As of The Dark Mod 2.06, 64-bit binaries are available. That said, it is still possible to exceed your available RAM or VRAM

so the downsize changes can still be beneficial for larger missions on systems with less available memory.

Because Doom 3 is a 32-bit game, it can only utilize a certain amount of RAM. When TheDarkMod.exe needs more memory, but cannot allocate anymore, it crashes with an error saying something like

Shutdown event system
malloc failure for 3145781

If you run into malloc failures, it is suggested to try the following:

1) Make sure you've enabled compression per the settings HERE

2) Edit your darkmod.cfg and use the following:

seta image_downSizeBump "1"
seta image_downSizeBumpLimit "256"

These will reduce the bumpmap size. Memory impact will be few hundred megabytes lower, at the expense of very minor blurring of texture quality.

3) If the above does not help you it is recommended you try

seta image_downSize "1" 
seta image_downSizeLimit "256"
seta com_videoRam "512" (or however much video RAM you have).

These will reduce all texture sizes. Memory impact will be much lower, but the graphics are visually pixelated, depending on the com_videoRam number. But at least the mission will be more likely run with systems with low RAM.

4) If step 3 resolves your issue, you can also try

seta image_downSizeLimit "512" 

...to see if it still loads with better quality.

Note: Image_downsize can make menus blurry, see The briefing is very fuzzy (Obsolete info. TDM 2.05 no longer makes menus blurry with image_downSize enabled.)

(Mostly deprecated info as of TDM 2.02 and higher below.)

A possible solution is to patch Doom3.exe with a 4GB Patcher to allow the game to allocate more memory, but the TheDarkMod.exe should already be using large memory space.

Stop Head-bob animations

  • Obsolete info. In 2.11 these values are saved when entered in the console.
    You no longer need an autoexec.cfg ( Using an autoexec.cfg will still work though. )

Some players get motion sickness or are otherwise uncomfortable with head bob.

Add these values to an autoexec.cfg

seta pm_runbob "0"
seta pm_runpitch "0"
seta pm_runroll "0"
seta pm_walkbob "0"
seta pm_bobpitch "0"
seta pm_bobroll "0"
seta pm_bobup "0"
seta pm_crouchbob "0" 

to disable head-bob.

See also:


See also