Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is dhewm3?
dhewm3 is a modern source port of the original 2004 Doom 3 — not Doom 3 BFG Edition, which needs a different port. It takes the released Doom 3 source code and rebuilds it into an engine that runs natively on current systems, while still requiring you to legally own the game and supply its data files. In practice, it is the way many people play classic Doom 3 on a modern PC without fighting the original executable's limitations.
What it actually changes
Compared with the original release, dhewm3 focuses on compatibility and quality-of-life rather than redesigning the game:
- Platform support: known to work on Windows, Linux, macOS, FreeBSD, OpenBSD and AROS, and it should be portable to any system with OpenGL 1.4 plus ARB shaders, SDL and OpenAL.
- Bug fixes: accumulated corrections to the original engine.
- 64-bit support: native 64-bit builds instead of the old 32-bit-only executable.
- Widescreen: much better handling of widescreen resolutions, and recent versions add widescreen GUI support through adjusted
.uifiles. - Sound: EAX-like effects on all operating systems and hardware via OpenAL Soft's EFX support, rather than being tied to specific audio hardware.
- Settings menu: a mod-independent menu, so common options no longer depend on a particular mod's own interface.
- Smoother frame pacing: version 1.5.5 removed several sources of microstutter, including the old 60 vs 62.5 fps mismatch, which matters most when VSync is on.
- Texture support: BC7/BPTC-compressed
.ddstextures are now supported, offering better quality than the older S3TC/DXT/BC1–3 formats at similar sizes — useful for high-resolution retexture packs.
Who it is for
It suits players who already own Doom 3 and want it to run cleanly on a modern machine, especially on Linux, macOS or BSD where the original binary is impractical. It also appeals to modders and texture-pack authors, since the engine is actively maintained and accepts newer asset formats.
The main trade-off is mod compatibility. dhewm3 only supports older mods if they either do not ship their own game DLL or have been ported to dhewm3. Mods that depend on an unported DLL will not work out of the box. If a mod is central to how you play, check its status before switching.
A practical next step
If you want to try it, the order matters: install dhewm3 first, then point it at game data from a legitimate copy of Doom 3. The project's own installation guidance covers where those files need to go. For macOS, signed and notarized builds are distributed through Mac Source Ports, while the main downloads and release notes live on the project's GitHub page. If you are specifically on Doom 3 BFG Edition, look at a BFG-focused port instead, such as the one the project points to as Chocolate DOOM-3-BFG.
How do I install dhewm3 and set it up with the Doom 3 game data?
You install dhewm3 by downloading its executables, then pointing the engine at a legally owned copy of Doom 3's game data. The engine itself is free; the game data is not included.
Two separate pieces
dhewm3 is a source port of the original Doom 3 (not Doom 3 BFG). The project states you still need to legally own the game and provide the game data for dhewm3 to play. So the setup has two independent parts:
| Piece | What it is | Where it comes from |
|---|---|---|
| dhewm3 executables | The engine binary you run | The dhewm3 project's releases |
| Doom 3 game data | The .pk4 archives and related assets |
Your own Doom 3 installation or media |
The dhewm3 page has a "Getting the Doom3 Game Data" section and a "Getting dhewm3 executables" section, which reflects that split. The page also links to a "How to Install" section for the details.
Practical order of operations
- Get the dhewm3 executables for your platform from the project's download page.
- Locate the Doom 3 game data from a copy you own.
- Place the game data where dhewm3 expects it, following the installation instructions.
- Launch dhewm3 and confirm it finds the data; the in-engine Settings Menu is mod-independent, so you can adjust options without a specific mod loaded.
Platform and data caveats
dhewm3 is known to work on Windows, Linux, macOS, FreeBSD, OpenBSD and AROS. More broadly, it should work on any system supporting OpenGL 1.4 with ARB shaders, SDL and OpenAL. A signed and notarized macOS build is distributed through Mac Source Ports.
Mods are a separate consideration: dhewm3 only supports old mods if they either don't require their own game DLL or have been ported to dhewm3. Check the project's Mods page before assuming a given mod will load.
What are the main improvements in dhewm3 compared to the original Doom 3?
dhewm3 is a source port of the original Doom 3, not the BFG Edition, and its main improvements fall into four areas: stability, audio, display support, and modern hardware compatibility.
What changes compared to the original
- Bugfixes. The project describes many bugfixes relative to the original release, which is the baseline reason to prefer it for a replay.
- Sound. EAX-like environmental audio works on all operating systems and hardware through OpenAL Soft's EFX support, rather than being tied to specific Windows sound hardware.
- Widescreen. Support for widescreen resolutions is much better, and version 1.5.5 added widescreen GUI support, which requires adjusted
.uifiles. Optional downloads provide versions for the base game, Resurrection of Evil and The Lost Mission. - 64-bit support. The engine runs as a 64-bit build, which the original did not.
- Smoother frame pacing. The 1.5.5 release removed several sources of microstutter, including the old 60 vs 62.5 fps mismatch, so gameplay is smoother, particularly with VSync enabled.
- Settings menu. A new mod-independent settings menu is included, so common options no longer depend on a specific mod's own menu.
- Texture compression. BC7 (BPTC)
.ddstextures are supported, offering better quality than the older S3TC/DXT/BC1-3 formats at the same size as DXT3-5, which matters for high-resolution retexturing packs. - Portability. It is known to run on Windows, Linux, macOS, FreeBSD, OpenBSD and AROS, and should be portable to any system with OpenGL 1.4 plus ARB shaders, SDL and OpenAL.
Trade-offs to know before switching
The main limitation is mod compatibility. dhewm3 only supports older mods that either do not require their own game DLL or have been ported to dhewm3. If your favourite mod ships its own binary, check the project's mods page before assuming it will load. You also still need to legally own Doom 3 and supply the game data; the engine alone is not playable.
A practical next step
If you are setting up a replay, install dhewm3 first, point it at your existing Doom 3 data, and test the base game before adding mods. Then add the widescreen GUI pack if you play on a modern monitor, and only after that try mods one at a time so you can tell whether a failure comes from the engine or the mod. Mac users can look for the signed and notarized build distributed via Mac Source Ports, and the engine itself is available from GitHub.
Which mods are compatible with dhewm3 and how can I get them to work?
dhewm3 runs old Doom 3 mods only if they don't ship their own game DLL, or if someone has ported that DLL to dhewm3. The project maintains a separate Mods page and a companion repository, dhewm3-mods, which supplies compatible DLLs for selected mods. So the practical rule is: check whether the mod contains a game DLL first, then check whether dhewm3-mods or the mod author offers a port.
How to tell whether a mod will work
- No custom game DLL: These mods generally load as-is. They are usually content-only — maps, textures, models, sounds, weapon or monster definitions, HUD changes — and rely on the base game logic.
- Custom game DLL: The original binary won't load under dhewm3. You need a dhewm3-compatible build of that DLL (a
.dllon Windows,.soon Linux), either from dhewm3-mods or built from source with the dhewm3 SDK. - Total conversions: Treat these as the hardest case. They tend to bundle a DLL plus their own game data, and often need a dedicated port.
Concrete examples from the project's news
dhewm3-mods lists DLLs for newer mods including ELDOOM, Grimm, HeXen: Edge Of Chaos Demo, Real Gibs and Blood Mod. Two details are worth knowing:
- Real Gibs ships a DLL that the mod page says works only with the 32-bit version of dhewm3. The recommended route is to use the mod's game data with the DLL or
.soprovided by dhewm3-mods, or build the library yourself. - Blood Mod was updated to v1.8 and now also supports Resurrection of Evil.
- LibreCoop is maintained as part of the dhewm3 SDK while upstream is inactive.
Getting a mod running
- Install dhewm3 and confirm the base game starts, since it needs the original Doom 3 game data that you legally own.
- Read the mod's own instructions for its folder layout and launch parameters.
- If the mod includes a game DLL, replace or supplement it with the dhewm3-compatible version from dhewm3-mods.
- If no port exists, check the dhewm3 SDK and build the DLL yourself, or ask on the project's community channels.
- Keep the mod's data files separate from the base game so you can switch back easily.
A note on scope
dhewm3 targets the original Doom 3, not Doom 3 BFG Edition. For BFG, look at Chocolate DOOM-3-BFG instead. If you only want to replay the base game with widescreen menus, the optional widescreen GUI files cover the base game, Resurrection of Evil and The Lost Mission without any mod work.
What is new in the latest dhewm3 version 1.5.5?
Version 1.5.5 of dhewm3 is mainly a smoothness and compatibility update: it removes several sources of microstutter (including the long-standing 60 vs 62.5 fps mismatch), so gameplay should feel steadier, particularly with VSync enabled. It also adds widescreen GUI support, BC7 (BPTC) compressed .dds texture support, and ships or links DLLs for several additional mods.
What changed in 1.5.5
- Smoother frame pacing. Stutter sources were addressed, including the old 60 vs 62.5 fps problem. If you previously avoided VSync because it felt uneven, this is the release to retest.
- Widescreen GUIs. HUD and menu layouts can now scale properly to widescreen aspect ratios, but this requires adjusted
.uifiles. Arl produced versions for the base game, Resurrection of Evil and The Lost Mission, offered as an optionaldhewm3-wide-guis-*.zipdownload. - BC7/BPTC .dds textures. Higher quality than the older S3TC/DXT/BC1-3 formats at the same size as DXT3-5, which matters for high-resolution retexturing packs. The first pack to use it is hidef2k by y2keeth.
- New mod DLLs. dhewm3-mods provides libraries for ELDOOM, Grimm, HeXen: Edge Of Chaos Demo and Real Gibs. For Real Gibs, the page notes a caveat: the mod's own page says 32-bit only, but that refers to the
realgibs.dllit ships — use their game data with the DLL/SO provided by dhewm3-mods, or build the library yourself. - Mod updates. Blood Mod reached v1.8 and now supports Resurrection of Evil. LibreCoop is now maintained as part of dhewm3-sdk while upstream is inactive.
Who should update, and what to check first
If you play on a widescreen monitor, use VSync, or run high-res texture packs, the update addresses exactly your pain points. Mod users should check compatibility before updating: dhewm3 only supports old mods that either don't need their own game DLL or have been ported to dhewm3, so a mod that worked under the original Doom3 executable may not load here.
Builds are available from the project's GitHub releases, with a signed and notarized macOS build from Mac Source Ports. You still need to legally own Doom3 and supply the game data yourself — the GPL covers the engine source, not the assets.
Practical next step: install 1.5.5, then enable VSync and walk through a busy area of the base campaign. If motion looks even, keep it on; if not, your bottleneck is likely elsewhere. Widescreen users should grab the optional GUI pack matching whichever campaign they play, and texture-pack users can confirm BC7 support by checking that a .dds pack loads without the washed-out look typical of older compression.
How can I contribute to the dhewm3 project or get help with issues?
Contributing to dhewm3 usually means one of three things: reporting a bug, helping with mod compatibility, or building from source. The project page itself is mostly a launch point — it explains what dhewm3 is, links to the game data you must supply, and points to where executables live — so treat it as the front door rather than the whole community.
Getting help with an issue
Start by narrowing down what kind of problem you have, because the right destination differs:
- Installation or "where do I get the game data" questions. The page's "Getting the Doom3 Game Data" and "How to Install" sections exist precisely for this. dhewm3 is a source port of the original Doom3, not Doom3 BFG, and you still need to legally own the game and point dhewm3 at its data files. If you are missing that step, no amount of troubleshooting will help.
- Crashes, graphical glitches, or performance problems. These are best reported where the code lives. The project distributes its releases through GitHub, and the issue tracker there is the normal place for reproducible bug reports. Include your OS, dhewm3 version, GPU/driver, and whether the problem also happens in the original Doom3.
- Mods that don't work. dhewm3 only supports old mods if they either don't ship their own game DLL or have been ported to dhewm3. The Mods page is the reference point, and the project maintains a separate dhewm3-mods repository with DLLs for some newer mods. If your mod isn't listed, that's a porting question, not a bug.
- macOS-specific builds. Signed and notarized macOS builds are published via Mac Source Ports, so check there before assuming a build problem is a dhewm3 bug.
Contributing
The most useful contributions tend to be concrete and reproducible:
- Reproduce and document bugs. A clear report with steps, logs, and version details is genuinely valuable, especially for platform-specific issues on Linux, FreeBSD, OpenBSD, or AROS.
- Port mods. Because mod DLL support is the main compatibility gap, porting a popular mod to the dhewm3 SDK is a high-impact task. The SDK repository is where that work happens.
- Test new features. Recent releases added widescreen GUI support (requiring adjusted
.uifiles) and BC7/BPTC.ddstexture compression for high-res retexturing packs. Testing those with real texture packs and reporting regressions helps. - Build and test on your platform. dhewm3 targets anything with OpenGL 1.4 plus ARB shaders, SDL, and OpenAL, so builds on less common systems are useful feedback.
A practical first step
If you're unsure where you fit, pick the smallest useful action: install dhewm3 with legally owned Doom3 data, play for an hour, and note anything that misbehaves. Then check whether it's already known before filing it. That single loop — reproduce, search, report — is how most people end up contributing, and it costs the maintainers far less time than a vague "it doesn't work" message.
User reviews (0)