Doom 64 EX

From PCGamingWiki, the wiki about fixing PC games

This page is for the fan-made port from 2008. For the official port from 2020, see Doom 64.

Doom 64 EX
Doom 64 EX cover
Original game Midway Games
Windows Samuel "Kaiser" Villarreal
macOS (OS X) Samuel "Kaiser" Villarreal
Kex Engine
Release dates
Windows July 10, 2008[1]
macOS (OS X) February 9, 2014[2]
Linux TBA
Microtransactions None
Modes Singleplayer
Perspectives First-person
Controls Direct control
Genres Action, Shooter
Themes Horror, Sci-fi
Series Doom
Doom 64 EX guide on StrategyWiki
Doom 64 EX on MobyGames
Doom 64 EX on Wikipedia
Doom (1993) 1993
Doom II: Hell on Earth 1994
Final Doom 1996
Doom 3 2004
Doom 64 EX (unofficial port) 2008
Doom 3: BFG Edition 2012
Doom (2016) 2016
Doom VFR 2017
Doom Classic 2020
Doom II Classic 2020
Doom Eternal 2020
Doom 64 2020

Key points

Although this fan-made port is available for free, it requires data from the original Doom 64 ROM cartridge for Nintendo 64 or the official Doom 64 port in order to work.
Great port that includes widescreen support, higher frame-rate, mouse look, and controller support.
Users of Windows 10 v1709 and newer needs updated SDL DLL files to restore mouse aiming.

General information

Official Site
Sourceforge page
GitHub page
Game page on The Doom Wiki
Doom64 EX Forums


Source DRM Notes Keys OS
Official website
macOS (OS X)
Must be compiled manually to run on Linux. See the GitHub page for more information.

Game data[edit]

Configuration file(s) location[edit]

System Location
Windows <path-to-game>\config.cfg[Note 1]
macOS (OS X)
It's unknown whether this game follows the XDG Base Directory Specification on Linux. Please fill in this information.

Save game data location[edit]

System Location
Windows <path-to-game>\doomsav*.dsg[Note 1]
macOS (OS X)


Video settings
Video settings
Display settings
Display settings

Graphics feature State Notes
Widescreen resolution
See Ultra-widescreen.
4K Ultra HD
Field of view (FOV)
See Field of view (FOV).
Borderless fullscreen windowed
Use Borderless Gaming.[3]
Anisotropic filtering (AF)
On/Off toggle. Amount unknown.
Includes option to disable blurry bilinear texture filtering.[Note 2]
Anti-aliasing (AA)
Force in GPU control panel.
On Nvidia cards, forced Transparency SGSSAA is blurry on oblique angles. Use Nvidia Profile Inspector to force 8xS, 8xSQ, 16xS, or 32xS HSAA (Hybrid Sampled Antialiasing) in Antialiasing - Setting instead, leaving transparency supersampling disabled.[6]
Vertical sync (Vsync)
60 FPS
Set Framerate to Smooth under the Setup screen in the Options menu.
120+ FPS
Duplicated frames from 60 FPS.[7]
High dynamic range display (HDR)


Instructions[citation needed]
  1. Go to the configuration file(s) location.
  2. Open config.cfg.
  3. Set the seta "v_height" "xxx.000000" to you desired vertical resolution.
  4. Set the seta "v_width" "xxx.000000" to you desired horizontal resolution.
  5. Ensure that windowed/fullscreen mode is set to your desired mode in the seta "v_windowed" "x".
  6. Save and close.
  7. Launch the game directly from DOOM64.EXE.


Geometry outside the 16:9 dimensions is frequently culled out.

Field of view (FOV)[edit]

Instructions[citation needed]
  1. Go to the configuration file(s) location.
  2. Open config.cfg.
  3. Set the seta "r_fov" "xx.x" to your desired vertical field of view.
  4. Save and close.


Mouse settings
Mouse settings
Controller settings.
Controller settings.


Fluidsynth settings
Fluidsynth settings

Audio feature State Notes
Separate volume controls
Sound, Music and Gain Output
Surround sound
Uses stereo output with some 3D spatial effects.
Closed captions
Mute on focus lost


Language UI Audio Sub Notes

Issues unresolved[edit]

Mouse aiming not working on Windows 10[edit]

Mouse aiming is broken in versions of Windows 10 from v1709, the Fall Creators Update released in October 2017, and onward.
Use a newer version of the SDL DLL files[8]
  1. Download either the official Doom 64 EX SDL patch (bundles SDL 1.2.14) or this package from SDL (bundles SDL 1.2.15).
  2. Extract the archive to <path-to-game> and ensure that the outdated SDL DLL files of the game are replaced with the ones from the downloaded archive.
  3. Launch Doom 64 EX and see if the mouse functionality is restored.
  4. If there is still an issue ensure that Enhanced pointer precision in Windows is disabled as well as SDL might not properly disable mouse acceleration of Windows even though it is set to the lowest in the in-game mouse menu.

Other information[edit]


Technical specs Supported Notes
OpenGL 1.2
Executable 32-bit 64-bit Notes
macOS (OS X)


Middleware Notes
Audio FluidSynth for MIDI playback
Input SDL 1.2

System requirements[edit]

Operating system (OS) 98, 2000, XP, Vista
Processor (CPU) 600 MHz
System memory (RAM) 64 MB
Hard disk drive (HDD)
Video card (GPU) 32 MB of VRAM
OpenGL 1.2 compatible


  1. 1.0 1.1 When running this game without elevated privileges (Run as administrator option), write operations against a location below %PROGRAMFILES%, %PROGRAMDATA%, or %WINDIR% might be redirected to %LOCALAPPDATA%\VirtualStore on Windows Vista and later (more details).
  2. In-game “linear” texture filtering uses 4-point bilinear filtering, rather than the 3-point bilinear filtering used on the Nintendo 64.[4] This results in more increased texture aliasing.[5]


  1. Doom64 EX - The Doom Wiki at
  2. Doom64 EX 2.4 Mac OS Version Available - Doom64 EX - last accessed on August 28, 2016
  3. Verified by User:AmethystViper on December 10, 2017
  4. Doom 64 EX looks a lot better pixelated. - Doom General - Doomworld
    "I don't think the original filtering applied from the N64 matches the bilinear which the port uses, I feel the pc bilinear is making it look worse than the N64's own filtering."
  5. Filthy Pants: A Computer Blog: N64 3-Point Texture Filtering in mupen64plus-libretro
  6. Verified by User:SirYodaJedi on 2019-08-12
    The blurring is quite noticeable. I have not noticed any issues yet caused by the LOD bias adjustment that Nvidia HSAA (and D3D Supersampling) force.
    Comparison screenshots:
  7. Verified by User:ZellSF on 2020-04-03
    Framerate counters say 120 FPS, but I'm not seeing them (even in frame-by-frame analysis of a capture
  8. Verified by User:Aemony on 2020-04-27