What is this?
This is the official 1997 source code release of DOOM, the 1993 first-person shooter by id Software, published for non-profit use with a note from John Carmack.
This is the official 1997 source code release of DOOM, the 1993 first-person shooter by id Software, published for non-profit use with a note from John Carmack.Is this the full playable game or just the engine source?It's just the engine source code — you still need a real copy of DOOM's data files (the WAD) to actually play it.
It's just the engine source code — you still need a real copy of DOOM's data files (the WAD) to actually play it.How do I get it running?Compile the C/C++ source on a Linux machine; the DOS version couldn't be released due to a copyrighted sound library.
Compile the C/C++ source on a Linux machine; the DOS version couldn't be released due to a copyrighted sound library.Do I need the original DOOM data files to play it?Yes, you need a real copy of one of the DOOM releases for the game assets; the README suggests checking software stores if you don't own one.
Yes, you need a real copy of one of the DOOM releases for the game assets; the README suggests checking software stores if you don't own one.Does it run on Windows or just Linux?As released it only compiles and runs on Linux; the Windows port id's team did at the time isn't included, though the code is described as portable to other platforms with some effort.
As released it only compiles and runs on Linux; the Windows port id's team did at the time isn't included, though the code is described as portable to other platforms with some effort.Who is this source release meant for?Hobbyist and engine programmers who want to study, port, or extend the original DOOM renderer and game logic.
Hobbyist and engine programmers who want to study, port, or extend the original DOOM renderer and game logic.What rendering technique does the original DOOM engine use?It renders using a BSP tree walk with horizontal and vertical lines of constant Z and fixed per-band light shading, a technique Carmack calls fundamentally sound even in retrospect.
It renders using a BSP tree walk with horizontal and vertical lines of constant Z and fixed per-band light shading, a technique Carmack calls fundamentally sound even in retrospect.What project ideas does the README suggest for people exploring this code?Carmack suggests porting it to other OSes, adding rendering features like transparency or look up/down, adding gameplay features like jumping or ducking, building networked client/server play, or creating a 3D-accelerated version.
Carmack suggests porting it to other OSes, adding rendering features like transparency or look up/down, adding gameplay features like jumping or ducking, building networked client/server play, or creating a 3D-accelerated version.Why wasn't the DOS version of the source released?It relied on a copyrighted sound library id Software didn't have rights to redistribute, so only the Linux port could be published.
It relied on a copyrighted sound library id Software didn't have rights to redistribute, so only the Linux port could be published.What does Carmack call one of the biggest design mistakes in the original code?He singles out the movement and line-of-sight collision checking as messy and slower than it needed to be, since the BSP tree could have been reused for environment testing instead of a separate line clip.
He singles out the movement and line-of-sight collision checking as messy and slower than it needed to be, since the BSP tree could have been reused for environment testing instead of a separate line clip.What are similar projects?bgfx, raylib, Chisel, SFML, OpenDiablo2, assimp, DaVinciResolve-likeColorGradePanel4UE, Hazel
bgfx, raylib, Chisel, SFML, OpenDiablo2, assimp, DaVinciResolve-likeColorGradePanel4UE, HazelWhich topics is it in?legacy, games, retrogaming, computer-graphics, gpl, game-engine, gamedev, gplv2, rendering, game, 3d, c
legacy, games, retrogaming, computer-graphics, gpl, game-engine, gamedev, gplv2, rendering, game, 3d, c