Changed

• Every push is checked for leaked secrets, and the local test gate checks the commits being pushed. (DOOM-0471) A push that changes only documentation skips the test run, but only when GitHub's last run on that branch passed.

• Classic's software renderer does less redundant work per pixel, with an identical picture (DOOM-0445) The original 1993 renderer's inner loops looked up the screen width in a way that stops the compiler keeping it in a register, cleared more memory than it uses for each new floor or ceiling, and did a multiplication per pixel of the spectre effect. Each is now done once. The picture is checked byte for byte against the old renderer.

• Solid and Ultra spend far less time each frame updating moving floors, doors and animated textures (DOOM-0443) Every frame the game checks each corner of the level for doors, lifts and animated textures that changed. It was reading the level back from graphics memory to do so, which is slow. It now keeps a copy in ordinary memory and sends only what changed. Measured standing still at the start of E1M1 on the development machine in Solid, the frame rate roughly tripled. The picture is unchanged.

• Solid's full nearest-lights recalculation is faster (DOOM-0461) When a level loads, or a lit surface moves, Solid recalculates which fixed lights are nearest each part of the level. It now reads the lights from ordinary memory instead of graphics memory. The result is unchanged.

• Solid runs much faster in levels with many glowing objects (DOOM-0437) Each frame, Solid works out which lights are nearest each part of the level. It was reading the glowing objects' details back from graphics memory over and over, which is slow. It now keeps a copy in ordinary memory. Measured standing still at the start of E1M3 on the development machine, the frame rate nearly tripled. The lighting is unchanged.

• Animated nukage and lava no longer trigger a full lighting recalculation each time they change frame (DOOM-0436) In Solid, an animated floor changing frame used to redo the whole nearest-lights calculation, a regular spike in frame time. A changing floor moves no light, so now only the light colours are refreshed. The lighting result is identical.

• Levels resolve their wall textures by direct lookup instead of searching the texture list for every wall side (DOOM-0446) Loading a level used to compare each wall side's texture names against the whole texture list. It now goes straight to the entry. Every wall resolves to the same texture as before, including when a mod repeats a texture name.

• Finding a picture or sound in the game data is now a direct lookup instead of a search through the whole index (DOOM-0435) The game used to search its whole data index from one end every time it needed a picture or sound, and the Load, Save and volume menus did that inside their drawing loops. It now goes straight to the entry, and a mod file still overrides the original data exactly as before.

• Volumetric fog now defaults to Medium instead of Low The user's pick. A saved rt_fog setting in ~/.doomrc still wins. Part of DOOM-0011, which is still in progress.

• The game is now built with the compiler's optimiser switched on (DOOM-0434) It was shipping with the optimiser off — the setting used for debugging — which looks inherited from the 1997 source rather than chosen. Measured at about 5% less processor time on the original renderer. The classic renderer draws pixel-for-pixel the same frames as before, and the recorded demo fixtures are unchanged, so nothing about how the game plays or looks has moved.

• -rtview and -rippletime now say why a value was refused (DOOM-0405) Both refused a bad value in silence and carried on with the default. Both flags exist for repeatable headless captures, so the run looked like it worked and the picture was filed as evidence for a setting it never used. Neither flag stops the game; the message is the whole change.

• Saved games now record which build wrote them, and refuse to load into a different one (DOOM-0426) A saved game is a straight copy of the game's memory, so a different build can lay it out differently and read it as nonsense. It now says which layout it was written in and is politely refused if that does not match, instead of loading a broken game. Note: this makes saves from earlier versions unreadable. They were already being misread rather than refused.

Removed

• The config file no longer carries two serial-mouse settings nothing read. (DOOM-0450) mousedev and mousetype were 1997 settings for a serial mouse; SDL handles the mouse now. Old config files still load, and the two lines drop out the next time the game saves.

• Removed -statcopy, which wrote game data to an address given on the command line (DOOM-0401) A 1997 hook for an external statistics program that no longer exists. Passing it crashed the game at the end of a level.

Fixed

• Opening a door or riding a lift in a ray-traced view no longer writes past the end of the world's ray-tracing structure. (DOOM-0128) The structure was compacted to save about 90 KiB of video memory, and Vulkan cannot refresh a compacted structure in place. It now keeps its full size.

• Co-op games no longer quit at the first level exit, and multiplayer chat types what you press. (DOOM-0464) Three checks meant "is the game in French?" and always answered yes. Co-op asked for a French-only intermission graphic and quit when it was missing. Chat ran every key through the French keyboard layout.

• A lost graphics device now stops the game with a message instead of freezing it (DOOM-0412) If the graphics driver reset under the game, several checks threw the error away and the game carried on against a dead device. It now stops and says why. Also: on a screen that offers no ordinary 8-bit colour format the game says which one it fell back to.

• The ray-traced view now says when a crowded map has more monsters than it can draw (DOOM-0411) Past about 4,000 things it used to leave some out without a word. Also: a fog calculation at the far edge of a huge map no longer starts from a garbage position, and a debug message no longer floods the log during firefights.

• Ultra finds its HD textures wherever the game is started from (DOOM-0410) It used to look relative to the folder you launched from, and quietly fell back to the original artwork otherwise. It now looks beside the game itself and says which folder it used. The texture loader also reports every texture it shrinks or leaves out, and it no longer loads every texture into memory before deciding which ones fit.

• Ray-traced ghosting protection no longer switches off for good on very bright pixels (DOOM-0409) The denoiser stored a squared brightness in a format too small to hold it. Once it overflowed, that pixel could never reset its history again. Also: the bloom glow no longer smears thin lights at 67% and 75% render scale, and a single bad lighting sample can no longer spoil a room's baked light for the whole level.

• Solid's contact shadows no longer read the edge of a monster as a nearby wall (DOOM-0408) The shadow pass blended depth values across object edges, and a blend of a monster's marker value with a wall's depth looked like a close occluder. It now reads exact values. Also: a bad pixel can no longer reach the screen through the tone mapper, and the torch's shadow is only computed where the beam actually lands.

• The ray-traced view converts DOOM's colours with the exact sRGB curve (DOOM-0407) It used a rough approximation that was up to 59% off in the darkest colours. The sky, the HD art and the glow maths already used the exact curve. On screen, dark rooms brighten by about 1/255.

• Ray-tracer robustness fixes from the shader review (DOOM-0407) Zero-area lights no longer enter the light list, where they could produce infinite values. A missing GI table is no longer read. The -rtverify self-test now fails on any non-finite pixel instead of passing or reporting nothing.

• DOOM 1's animated intermission map now draws (DOOM-0391) The between-levels map was static. A check meant to skip the animation for DOOM 2 tested a constant that is always true, so the drawing step gave up on its first line while the artwork was still being loaded and advanced every frame. DOOM 2 is unaffected -- it never had the animation.

• The Windows build was missing a compiler safety flag the Linux build had by accident (DOOM-0434) This code deliberately reads the same memory as two different types, which the optimiser is allowed to assume never happens. The flag that disables that assumption was arriving on Linux only as a side effect of an unrelated sound library, and the Windows build was getting none of it. Both are now set deliberately, so switching the optimiser on could not quietly change behaviour on Windows alone.

• Fog now reaches rooms it was failing to light (DOOM-0406) The search that works out how far outdoor air seeps through a level ran on a fixed-size worklist. Once that filled, it recorded a shorter route to a room but never went back to tell that room's neighbours, so parts of a map were treated as further from the open air than they are. The worklist now grows instead.

• The lighting bake no longer scores cells outside the map (DOOM-0406) Every cell in the border ring around a level reported itself as breathable air, so the fog-lighting pass tested lights against points beyond the map's edge. Those tests could never light anything. Removing them cuts the work done each time a door finishes moving, and not one lit cell changed.

• A sprite could be freed while the texture atlas was still reading it (DOOM-0406) Building the atlas looked up the palette partway through copying a sprite. That lookup can evict cached data to make room — including the sprite being copied — and the copy carried on reading it. The palette is now looked up before the sprite is held.

• A crafted WAD can no longer push a sector's light level out of range (DOOM-0406) Wall and floor brightness was taken straight from the map file with no bounds check, while every other surface type already clamped it. The ray-traced view used the raw value, so an out-of-range level reached the lighting maths. Clamped at the source, which covers both views.

• An out-of-range -rtview value is no longer accepted on Windows (DOOM-0405) -rtview 9999999999 was refused on Linux and silently accepted as 2147483647 on Windows. The guard compared against the int limits but the type it compared is half as wide on Windows, so an overflowing value saturated to exactly the limit and passed. Measured on both toolchains before and after.

• -rippletime no longer accepts a value that is not a finite number (DOOM-0405) inf, nan and a number too large to represent were read as numbers and reached the renderer. No range check can catch one: inf compares as greater than zero, and every comparison against nan is false. A value that underflows is still accepted, because zero is its right answer.

• Keypad and Home/End keys no longer trigger unrelated actions (DOOM-0404) Keys the game has no name for were being folded onto letters that do have one. Tapping the keypad's full stop on the automap wiped your marks; keypad 9 acted as 'a', Caps Lock as '9', Home as 'J'. Those keys now do nothing, which is what they did in the original release.

• An add-on level pack with a damaged colour table can no longer read past its own data (DOOM-0404) The game read a fixed amount from the WAD's colour table without checking how much was actually there. A crafted or truncated file made it read past the end. The length is now checked once when the game loads, and a short table is refused with a clear message instead.

• Very long pauses in a music track no longer mistime everything after them (DOOM-0404) The MUS-to-MIDI converter could not write a gap longer than about 28 bits and produced a corrupt timestamp instead, throwing out the timing of every note that followed. Over-long gaps are now capped at the longest the format allows.

• Network errors on Windows now say what actually went wrong (DOOM-0404) Windows reports network failures separately from ordinary file errors, and the game was printing the wrong one -- a connection problem could appear as "No such file or directory", or as success.

• A failed clock read can no longer feed garbage into the game's timing (DOOM-0404) Two places read the system clock without checking whether the read worked, from a variable that starts with whatever was left in memory. The one that paces the game now stops with a clear error; the one behind the FPS counter reports zero and carries on.

• Saved games with an unusual character in the name no longer show as empty on Windows (DOOM-0403) The file was being opened in text mode, where Windows stops reading at certain bytes. A perfectly good save was then listed as an empty slot, with nothing said about why. Linux was never affected.

• The FPS counter no longer opens on a nonsense figure (DOOM-0403) It started by measuring across the level load, when nothing is being drawn, so the first reading was about 1 frame per second. It now waits for a period it was actually drawing in. This applies to every level change, not just the first.

• The Renderer setting now says when your machine cannot run the 3D tiers (DOOM-0403) With no suitable graphics device the setting would not change and gave no reason. It now reads "Classic (no 3D)".

• The end-of-level frags column goes away again when nobody has fragged anyone (DOOM-0403) Once any level in a network game had a frag, the column stayed for the rest of the session. Network games only.

• Three smaller fixes in the menus, the end-of-game text and the settings file (DOOM-0403) An unrecognised quoted setting leaked a small amount of memory each time the settings were read; an add-on ending a level the original game has no text for could crash instead of showing the first chapter's text; and the developer menu's scroll arrow overlapped the status bar.

• The decorative border around the view is drawn again on a widescreen display (DOOM-0402) At any Screen Size below full, the carved stone frame around the picture was measured against the old 4:3 canvas rather than the actual screen. The right-hand edge was dropped entirely and the other three were pushed into the picture, where nothing ever copies them to the screen -- so the border was simply missing. A 4:3 display was never affected.

• The PAUSE graphic is centred on the picture again on a widescreen display (DOOM-0402) It was drawn about three-quarters of its own width to the right of centre, at every Screen Size. Same cause as the missing border, found while fixing it. A 4:3 display was never affected.

• A broken wall texture no longer leaves the rest of its columns pointing at nothing (DOOM-0402) A texture with a gap in it stopped the engine part-way through preparing it, and every later column of that texture was left uninitialised.

• The field of view is now correct at smaller screen sizes on a widescreen display (DOOM-0402) Shrinking the view with Screen Size kept the wide field of view but not the extra width to draw it in, so the picture was squeezed horizontally. Only full-screen was right. Nothing changes on a 4:3 display.

• Bounded four more command-line options against bad input (DOOM-0401) -wart with a missing map crashed; -maxdemo 0 recorded into a zero-sized buffer; -warpto with a huge coordinate silently put the player somewhere else and said it had worked; an empty or unreadable @response file was read as garbage arguments.

• Ultimate Doom episode 4 no longer shows an invented par time (DOOM-0401) The par-time table only holds episodes 1 to 3, and episode 4 was reading past the end of it. There is no par time in the 1997 data for those levels, so none is shown.

• The byte-order swap helpers can be built, and are now tested (DOOM-0401) They were declared for big-endian machines and compiled only for little-endian ones, so a big-endian build could not link at all, and the types would have swapped the wrong width.

• A bad number in your settings file can no longer stop the game starting (DOOM-0383) The volume settings were passed straight through to a check that shut the game down, and the menu you would have used to fix them is behind the game that will not start. Out-of-range settings now quietly go back to their normal value instead.

• A misspelled value in the settings file is reported and skipped (DOOM-0383) It used to be silently replaced by whatever the line above it said, or by leftover nonsense if it was the first line.

Security

• The Windows build checks a fingerprint of every library it downloads (DOOM-0413) A swapped or tampered SDL or Vulkan download is now refused instead of built into the game. Also: the release script explains why it stopped instead of exiting silently, and the Windows packaging steps exist once instead of in two drifting copies.

• Refuse a WAD whose texture lumps claim more than they hold (DOOM-0402) A crafted WAD could make the engine read past the end of its texture list. It now says which lump is wrong and stops.

• Refuse a WAD with no flats, no sprite lumps or no wall textures (DOOM-0402) These counts come from the WAD and could go to zero or below, which the engine then used as an array size.

• Refuse a network game with more players than DOOM can represent (DOOM-0401) Joining with more than four hosts wrote past the end of the player list. The engine now says so and stops instead.

• The Linux download is now built with packaging tools that are checked before they run (DOOM-0259) The build used to fetch three helper programs from a moving link and run them unchecked. They are now pinned to fixed releases and verified against a recorded fingerprint on every build.

• Network games now check that packets arrived intact (DOOM-0256) The check existed but had been switched off since 1997, so it passed everything. It now catches a damaged packet, and a packet from a different build of the game, instead of playing them as movement. Note that this means a network game only works between two copies of this version or newer.

• Two overflows inherited from the 1993 renderer can no longer be reached (DOOM-0382) Both were in the original game and had been made larger by this project's widescreen and higher-resolution work, so a map could scribble over memory it did not own. One is now impossible by sizing; the other regained a guard the original already had a few lines away. A floor-drawing check that was one row too generous was corrected at the same time.

Changed

• Levels load faster, noticeably so on large custom maps (DOOM-0399) Building each room's wall list used to re-scan every wall in the map once per room. Verified to produce identical results on all 68 original maps.

Fixed

• Starting with a savegame the game cannot read now returns to the title screen instead of crashing (DOOM-0429) It was left with no level loaded at all and crashed a moment later.

• A power loss while saving settings can no longer leave them empty (DOOM-0400) The new settings are now flushed to the disk before replacing the old ones.

• A failed read from a WAD is reported instead of silently returning an untouched buffer (DOOM-0400)

• A WAD given on the command line with a very short name no longer reads past the start of it (DOOM-0400)

• Saving no longer destroys the previous save if the write is interrupted (DOOM-0399) The new save is written alongside the old one and swapped in only once it is safely on disk.

• Loading a save from a different build says so instead of doing nothing (DOOM-0399) The menu simply closed, with no way to tell a refused load from one that worked.

• Maps that the original game played but this build refused now load again (DOOM-0399) A wall marked as having two sides but supplying only one is treated as one-sided rather than rejected.

• A lift or floor that lowers and changes its surface no longer quits the game (DOOM-0398) The floor copied a leftover value into the sector when no neighbouring floor sat at the height it was moving to, and standing in that sector ended the session.

• A custom map's odd sector setting no longer quits the game (DOOM-0398) One unrecognised number in a downloaded map used to end the session as soon as a player stood on that floor. It is now ignored, as in every modern DOOM port. No original map contains one.

• A crushing lift caught on something no longer sinks to a random height or freezes (DOOM-0398)

• A room that runs out of ceiling slots is released instead of being left unusable for the rest of the level (DOOM-0398)

• A switch click is played from the switch rather than from an unrelated position (DOOM-0398)

• Switches keep working even if the internal switch table loses its end marker (DOOM-0398) Previously that would have left every switch in the game silently doing nothing.

• A map thing whose type is not positive no longer spawns a stray player or aborts the level load (DOOM-0397) A THINGS record of type -1 matched MT_PLAYER's doomednum and spawned a player-shaped monster with no player behind it; type 0 quit the game during level load. Both are now ignored.

• A map with no start position for a player is refused by name instead of crashing (DOOM-0397) On the first level the game crashed on a null pointer; on a level change it read memory it had just released. It now says which player's start is missing and stops.

• Telling monsters to forget you no longer crashes the game with a BFG shot in flight (DOOM-0397) Developer builds only. A missile stores its owner in the same field a monster stores its prey, and clearing it left the BFG's spray with nothing to aim from.

• Hostile sound data, network packets and a bare -net switch can no longer take the game down (DOOM-0386) A sound in an add-on file could claim an absurd recording speed, which made the game try to reserve about eleven gigabytes and get itself killed by the system. Sounds outside a sensible range now fall back to the standard one, and an oversized conversion is refused. A game packet from the network could claim to hold more player input than it actually did, and the extra was read out of leftover memory and treated as movement and button presses; a packet is now checked against its real size. And starting the game with -net and nothing after it crashed instead of explaining what was missing.

• A corrupted or hostile WAD or config file is now turned away instead of trusted (DOOM-0384) The WAD reader checked that a file's table of contents fitted inside the file, then believed every entry in it. An add-on file could claim a piece was enormous, or sat at a negative position, and the reader would try. Each piece is now checked against the real file, and a file too short to hold a header is refused rather than read as leftover memory. Separately, the settings file could change a setting's type -- putting text where a number belongs, or the reverse -- which wrote past the setting or left the game following a bad address. Such a line is now ignored with a message and the built-in default kept.

• Startup no longer reads past the end of the sprite-name table (DOOM-0423) Sprite setup counted the game's sprite names by scanning for an end marker the table did not have, so every launch read a little past it. Nothing visible went wrong, because the value just past the table happened to be the marker it wanted. The table now carries the marker itself.

• A malformed level no longer crashes the game as it loads (DOOM-0422) A level whose wall data omitted a required side made the engine follow a pointer that was never set, killing the game the moment the level loaded. Such a level is now turned away with a message naming the offending wall. No level in either shipped game is affected.

• Saving a game now checks it has room before each write, instead of reporting an overrun after it happened (DOOM-0374) Saving wrote into a fixed half-megabyte buffer with nothing stopping it running past the end; the check that was meant to catch this only ran once every byte had been written. On a large custom level that is ordinary play, not an attack. A save that will not fit is now refused with a message naming what did not fit, before anything is overwritten.

• A graphics card that can run Solid but not ray tracing now falls back to Solid (DOOM-0380) If your settings asked for Ultra on such a card, the game dropped all the way to the original 1993 renderer, with the Solid view sitting unused. It now steps down one tier at a time and stops at the best one your machine can actually run. A setting that names no tier at all still gives you Classic.

• The ray-tracing self-test no longer passes when it measured nothing (DOOM-0376) This test is the gate the project requires before any ray-tracing change ships. Both of its scores started at zero and stayed there when there was nothing to measure, and zero counted as a pass — so a run that tested nothing reported success twice. It now reports how much it actually measured, says INCONCLUSIVE when that is nothing, and its exit code matches its verdict, so a script or a build step can rely on it instead of a human reading the output.

• The pre-push check now says when it could not run a check (DOOM-0375) Before every push, a script runs the same checks the build server runs. If it could not run one — no game file to test against, no Windows compiler installed — it skipped it silently and still reported both jobs green, and the push went through. It now names each check that did not run, reports the run as partial, and refuses the push, telling you apart from a real failure.

• Asset and WAD tooling: a crash-on-typo path, a silent rm -rf, and dead code stage_hero.py dereferenced the result of importlib.util.spec_from_file_location and its .loader without a null check, turning a wrong path into an opaque AttributeError; it shelled out to rm -rf through subprocess with no error check, now shutil.rmtree; and it carried an unused LICENSES constant. wad_seg_probe.py gains an explicit strict= on a deliberately ragged zip() and loses an ambiguous l identifier.

• A failing rb_materials test read uninitialised memory instead of reporting tests/rb_materials_test.cpp read order[1] unconditionally, but rb_apply_budget writes only n_loaded entries and none at all on its out-of-memory path. Since check() deliberately does not abort, the array was read uninitialised exactly when an earlier assertion had already failed — undefined behaviour in the test precisely when it was diagnosing a regression.

• Dead code removed from the 1997 engine: eight defects, no behaviour change A redundant null check in p_doors.c after an identical early return; a duplicated viewactive = true in g_game.c; dead patch assignments in r_data.c (x2) and dead thinker assignments in p_enemy.c and p_telept.c, each immediately overwritten by the following for initialiser; unused numplaying in d_net.c and totalwidth in r_data.c; and the frac/fracstep pair in R_DrawFuzzColumn, which the fuzz effect never reads because it samples the framebuffer rather than the source column. The engine now builds with zero compiler warnings.

• r_vulkan.cpp no longer fails to compile under clang A block-scope extern int rb_profile; conflicted with the file-scope extern "C" definition of the same symbol in the same translation unit. GCC accepts this and clang rejects it outright, so the file was uncompilable on any clang-based toolchain while the normal build stayed green.

• A mistyped -rtview or -rippletime value no longer silently selects a different setting Both flags parsed their argument with atoi/atof, which report no error: -rtview hgh became view 0 and -rippletime fast pinned the ripple clock at zero, in each case overriding the default with nothing printed. r_backend.c's own comment already promised the opposite. A value that is not wholly a number is now refused and the default kept, per DOOM-0026 INV-3. New rb_argparse.h + tests/rb_argparse_test.cpp (28 assertions, proved red before the fix).

• A release with nothing written down about it is refused instead of published. (DOOM-0358) The release tool took its description straight from the changelog and never checked there was anything there, so cutting a release with an empty changelog section published it with a completely blank body. It now stops before tagging and says which section came back empty.

• A release can no longer ship a build older than the code it is tagged against. (DOOM-0356) The release tool used to treat any file with the right name as "already built", so it could publish a binary made before the fix the release was cut for -- which is how 0.7.1 first went out. Each build is now stamped with the commit it came from and only reused for that commit, and every published file is downloaded again afterwards and checked against what was built.

• The version now moves everywhere at once when a release is cut. (DOOM-0357) The changelog heading, its links and the README's "Latest release" line used to move only on one of the tool's two routes, so a changelog written by hand left the README advertising the previous version. All of them are now brought up to date on either route, the tool refuses to tag while any of them lags behind, and a preview build deliberately leaves the README pointing at the last full release.

Security

• Saving settings can no longer be tricked into overwriting another file (DOOM-0400) The temporary file the game wrote alongside your settings had a predictable name and followed a symbolic link, so anything else on the machine could aim that write at a file of its choosing.

• Reloading a WAD that has changed size is refused instead of corrupting memory (DOOM-0400) Only reachable through the developer-only "-file ~name.wad" option. A crafted file could crash the game outright.

• A crafted map or savegame can no longer trick the loader into an undersized allocation (DOOM-0399)

• A map naming something that is not a floor texture is now refused (DOOM-0381) A map could name any piece of data in the WAD as its floor, and the original renderer turned that name into a position in a list without checking it was a floor at all — then wrote to that position. The 3D renderer already guarded this; the original one now does too. Every map in both official WADs was booted to confirm real maps are unaffected.

• Loading a saved game now checks every number in it that picks an entry from a list (DOOM-0373) Some of those numbers were checked and some were not, which is the confusing kind of bug: the guard exists, so it looks finished. Two of the unchecked ones let a save file you were handed write outside its list — your current weapon and your floor and wall textures among them. All of them now go through the same check the file already used elsewhere.

• Doors, floors, switches and platforms no longer act on a wall that has no second side (DOOM-0372) The map loader deliberately records "no side here" as a marker value, and eight places used that marker as a position in a list without checking. The worst was a door: pressing use on a one-sided wall with a door action on it produced a bad pointer that the engine then wrote through every frame while the door moved. All eight are closed.

• The demo clips at the title screen can no longer pick a player slot that does not exist (DOOM-0371) Those clips come from the WAD file, and one byte of a clip chose which of the four player slots the game wrote to, unchecked. Loading a hostile WAD was enough to trigger it — the title screen plays them on its own. Demo playback also had no end marker check, so a clip missing its terminator was read past the end of its own data, four bytes per frame, until it happened to stop.

• Two parts of a map file are now checked against their real size (DOOM-0370) Both were trusted for more than they contained, so a crafted map could make the game read far outside its own memory and, in one case, write to it. The second of the two is not even an attack: many ordinary map editors produce a short or empty one, and the game now fills in the missing part with the safe answer rather than reading whatever sat next to it.

• Five fixed-size lists in the original game code are now bounded (DOOM-0369) Each added to a list without ever checking it was full, so a map downloaded from the internet could overflow one and write over memory it did not own — which rarely crashes outright, it just corrupts whatever sat next to it. One of the five needed no hostile map at all: large community levels routinely have more scrolling walls than the list could hold.

• CI workflow hardened: SHA-pinned action, least-privilege token, no persisted credentials actions/checkout was pinned to the mutable v7 tag, which can be repointed at any commit; it is now pinned to the commit v7.0.1 resolves to, with the version in a trailing comment. The workflow had no permissions: block, so it inherited the repository default — it now declares contents: read, which is all either job needs. Both checkouts set persist-credentials: false, since neither job pushes. zizmor goes from 7 findings to 0.

Fixed

• Windows no longer throws away your settings every time you quit (DOOM-0353) Changing the volume, the resolution, the render tier or a key binding on Windows worked until you quit, and was then silently lost — so the game started with the same settings every time. The save writes to a temporary file and moves it over the real one, which replaces the old file on Linux but is refused by Windows once that file exists. Windows now uses its own replace-in-one-step move, so the settings stick. Measured on real Windows: the config file goes from unchanged to fully rewritten. Linux was never affected and is unchanged.

• Windows launches no longer freeze on a black screen about one time in forty (DOOM-0350) The game clock's sub-second maths overflowed on Windows, where a long is half the size it is on Linux, so the clock stepped backwards several times a second. When that landed during the screen-melt transition at startup, the melt was handed a negative number of steps and spun forever. Measured on real Windows: 350 launches, no freezes, against a 2-3% rate before. Windows timing is steadier throughout as a result, not just at startup.

• Vulkan validation: make the Ultra RT overlay pass render-pass-compatible with the framebuffers and pipelines it is used with (DOOM-0134, DOOM-0198) The overlay pass that draws the weapon and HUD on top of the ray-traced image was set up with slightly different rules from the drawing surface it was actually used with, which made the graphics debug layer log 20 rule violations per run. The picture was always correct; the setup was not. Both passes now share one set of rules. A ray-traced run on an RX 6600 goes from 20 validation errors to none, with the lighting, geometry and HD textures unchanged.

• The Windows build no longer swallows its own diagnostic messages (DOOM-0348) On Windows every message the engine writes to its error stream was held in a buffer that nothing ever emptied, so all of them were lost — including the ones that say why sound or music is unavailable. A player reporting silent audio had nothing to send back. Both output streams are now unflushed-buffer-free from startup, so those messages appear as they already did on Linux. Verified on real Windows hardware.

• Publishing a release no longer waits on a duplicate pre-push check (DOOM-0344) The pre-push check added in 0.7.0 ran on tag pushes as well as branch pushes, but it always builds the current code rather than whatever ref is being pushed — so tagging a release re-ran the entire four-minute check on code it had verified seconds earlier. It now skips a tag whose commit is already on the upstream branch, and still runs in full for a tag carrying a commit that has never been pushed.

Added

• -nosound and -nomusic command-line switches (DOOM-0327) Start the game with no audio at all (-nosound, which never opens the audio device) or with effects but no music (-nomusic). Both are the switches every other DOOM port has; until now they were silently ignored. -nosound implies -nomusic. The shared audio device is now also released on quit in the runs where music never started.

• CI now compiles the whole tree against the Windows compiler on every push (DOOM-0324) The Windows build used to be compiled only when a release was cut, so it could sit broken for months — and it did: two Windows-only compile errors accumulated silently across the 193 commits between 0.5.0 and 0.6.0. A second CI job now syntax-checks every source file with the Windows compiler on every push, in parallel with the Linux job, in about eight seconds. New packaging/mingw-deps.sh stages the upstream SDL2 / SDL2_mixer / Vulkan headers it needs and is now the one place those version numbers are written down.

Fixed

• The local CI gate now mirrors both CI jobs, and a transient download failure no longer reds the build (DOOM-0343) packaging/ci-local.sh ran only the workflow's Linux job, so the Windows cross-compile job could go red on a tree the local gate called green — which is exactly what happened. It now runs both jobs, and skips instantly on a docs-only change just as the workflow's paths-ignore does. Separately, the Windows job's dependency downloads had no retry, so a single transient HTTP 503 from GitHub's release CDN failed the build with nothing wrong in the tree; they now retry. A new packaging/hooks/pre-push runs the gate before every push (install with git config core.hooksPath packaging/hooks).

• Sealed the thin bright diagonal seam on ceilings and ledges in the Solid and Ultra views (DOOM-0180) DOOM stores map vertices as whole numbers, so where the level's own geometry data splits a DIAGONAL wall in two, the split point gets rounded — and the two sides of that wall round to different places. The 3D views built the wall from one side's numbers and the floor and ceiling around it from the other's, so the two stopped just short of each other and left a real hairline hole you could see the sky through. Every seg is now snapped back onto its wall's exact line, so both sides agree and the hole closes. Only diagonal walls were ever affected, which is why the seam was always a diagonal line.

• Distant toxic pools now fade into the fog like every other surface (DOOM-0330) A nukage pool used to hold one flat green all the way to its far edge while the walls and mountains behind it greyed out correctly. The fog was reaching it the whole time — it was fading into green fog rather than grey, at a shade too close to the goo's own to look like fading at all. Pools now haze over with distance at the same rate as the ground beside them. The green glow in the air above the goo is still to come.

Security

• A truncated or hand-edited savegame is now refused instead of read past the end of the file (DOOM-0255) Loading a .dsg never knew how long the file was — the length was read and thrown away, and every part of the load walked forward on trust. A save that stopped early therefore kept reading whatever happened to sit after it in memory; an empty one crashed the game outright. Savegames get traded between players, so the engine now remembers where the file ends and checks every read against it, naming the part that came up short ("savegame ends 172 byte(s) before its players") instead of carrying on. Saves written by earlier builds still load exactly as before.

Added

• A Render Effects screen that shows what every graphics toggle is set to (DOOM-0205) Options -> Renderer -> Render Effects lists the flashlight, SSAO, de-tile, dirt/grime, wet liquid, volumetric fog and the profiler, each with its current setting beside it. The toggles were hidden behind hotkeys, so the only way to know what was on was to remember — which caused a false bug report when two effects were off in a saved config and the game looked wrong for no visible reason.

• Menus can now be opened from the command line in developer builds, so they can be screenshotted (DOOM-0318) -devmenu <name> opens a named settings screen as the level loads — main, options, renderer, effects, video, sound or developer. Automated screenshots could already reach any view of the world but never a menu, because opening one needs a keypress and the desktop will not let a script press keys inside the game. Two long-open menu items had been waiting on someone checking them by hand for that reason.

• -inspect and -freeze command-line flags for the developer view (DOOM-0294) The Inspect preset (monsters ignore you, nothing can hurt you) and the freeze-monsters switch were reachable only through the developer menu, so an automated capture run could not use them. A capture taken in a live level is not a measurement: an A/B of the wet-liquid layer reported 15% of pixels moved where the real signal was 13.8%, the rest being a monster walking through frame and the health counter ticking down.

• Volumetric fog now takes its colour from the room: green over nukage, a red haze through Hell (DOOM-0011 L4) Two area profiles feed the fog march. A nukage pool fogs green, and a Hell level (Inferno, or DOOM II from map 20) gains a thin red haze over everything. They stack — a goo room on a Hell level reads green through red. Torch shafts keep their own warm colour rather than taking the room's tint. Ultra's ray-traced view only; measured at under 0.02 ms.

• Add a make compile_commands.json target for the static analysers cppcheck and clang-tidy take a file's language from its extension, so a whole-tree sweep was parsing the 10k-line Vulkan back-end as C and analysing none of it. A compilation database gives each file the compiler, standard and include paths the real build used.

• Drifting fog now rolls through a torch's glow and cuts it, instead of sliding behind a still patch of light (DOOM-0300) Light reaching the fog is attenuated along its own path from the lamp, so billows passing in front of a torch actually dim it. Before this the glow was a fixed shape painted over moving fog; now the two move together.

• Torches and lava now light the fog around them (ray-traced views) (DOOM-0011) A lamp, a light panel or a pool of nukage now glows into the air near it instead of only lighting the walls. Which lights can reach which patch of air is worked out once when the level loads, using the game's own line-of-sight test, so a torch never shines through a wall and the effect costs no extra ray tracing while you play. Indoors, where there is no sky to light the mist, a nearby light is now the thing you see by.

• Developer screenshot: F12 saves the frame you are looking at (DOOM-0294) F12 (or Developer → Capture Screenshot) writes exactly what is on screen, HUD and all, to dev-shots/shot-NNNN.png — full display resolution, in any 3D view, raster or ray-traced. The Classic tier saves DOOM's own .pcx instead, since the software renderer never builds an image for the GPU to present. Developer builds only (make DEV=1).

• Developer view: a testing menu for jumping to any level and looking at it (DOOM-0294) An Options → Developer menu that jumps straight to any level in either game at any skill, switches the monsters' attention off (or freezes them) so a map can be walked and looked at rather than fought through, opens locked doors, picks a path-tracer diagnostic view by name, and prints where you are standing as the -warpto line that reproduces the spot. A Play/Inspect switch flips the whole set at once, so the same jump can also be used to test a level as a player meets it. Developer builds only (make DEV=1): a released binary is compiled without any of it.

• Fog now billows: a near-white base with banks of visibly varying thickness drifting past (Ultra/Solid ray-traced view) (DOOM-0011) The haze is no longer even. Two layers of slowly drifting 3-D noise thicken and thin the air, so mist pools in one part of a room and clears in another, and a bank passes in front of and behind a pillar as you turn. Costs about 6% of frame time on an RX 6600; the ; key still dials it Off / Low / Medium / High.

• Fog now drifts indoors through doorways and windows (DOOM-0011) Indoor fog used to stop dead at a roofline. It now fades in near an opening onto the outdoors and thins as you walk deeper in, while a sealed room that merely shares a wall with the outside stays clear — the game works out the route through doorways, not the straight line through the wall.

• Floor fog outdoors — mist that pools around your feet (DOOM-0272) A second fog layer that fades with distance from the camera as well as with height, so the air at your feet can be genuinely misty without the far end of a courtyard turning white. Outdoors only for now; indoor rooms follow once the engine can tell a room with a window from a room buried three doors deep.

• Test coverage for the mus2mid happy path, font metrics, asset-path resolution and degenerate emitter input mus2mid_test asserted only rejection paths; it now checks three hand-built scores byte for byte, covering note on/off encoding, the track-length back-patch, percussion-channel mapping, the DMX 0x80 clamp quirk and the MIDI-channel allocator's skip of channel 9. Also new: rb_text vertical metrics and the atlas-doubling retry, rb_materials' rb_asset_root/rb_asset_path joining, and emissive_derive's null/zero-area guard.

• Headless boot-smoke CI gate that actually runs the engine (DOOM-0203) A new -bootsmoke [N] engine flag boots the game on the GPU-free software renderer, simulates N tics (default ~3 s) through the real game loop, and exits cleanly. CI now runs it after the build + unit tests (under SDL dummy drivers against a free Freedoom IWAD), so a boot or per-frame render regression is caught automatically instead of only on a manual play-test.

Changed

• Say how to fix it when the HD art is missing (DOOM-0042) Ultra falling back to the 1997 art looks like a lighting regression in a screenshot rather than a missing asset directory, so the message now names DOOMASSETDIR as the thing to set.

• Fog wisps churn at Silent Hill 2's rate, and each map gets its own drift heading (DOOM-0300) The fog's glow read as a painted patch because the wisp pattern needed 24 seconds to cross one noise cell, where Silent Hill 2's fog fully restructures in under 2.2. Both octaves now drift 15x faster and are exactly opposed, so the fog dissipates and reforms in place instead of blowing past -- measured at 0.4% of the change explained by translation, against SH2's own 0-1%. Each level also draws its own heading, seeded from the map so captures stay reproducible.

• Bake the sun's fixed direction into a load-time clearance field and delete L2's per-sample ray. (DOOM-0289) The volumetric fog's sun visibility is now baked into a load-time field instead of a shadow ray fired from every fog sample, so the fog costs 3.2% of a frame instead of 44% -- 28 fps back up to 42 on the test machine, with the picture unchanged.

• The play area is never framed by a border -- a fresh install fills the screen (DOOM-0285) The old default drew the 1993 decorative frame around a shrunken picture. The status bar stays; only the border goes.

• Ultra's ray-traced view is about 17% faster — 41 to 48 FPS on the test machine (DOOM-0197) The processor and the graphics card were taking turns instead of working at the same time: each frame spent 3.6ms preparing moving doors and lifts and only then started waiting on the card. That preparation now happens while the card is still drawing the previous frame, which is time the frame no longer spends. Nothing about the picture changes.

• Indoor mist now reaches further in from an opening, and no longer halves at the threshold (DOOM-0281) Fog standing in a doorway was capped at half the density of the air just outside it, so it visibly halved the moment it crossed the opening; and it faded out within about two door-widths, so anyone standing back in a room saw none of it. Mist now carries most of the outdoor strength at an opening and reaches roughly twice as far inside. A sealed room stays clear, which is guaranteed by how the two dials are defined rather than by the values chosen.

• Ultra's ray-traced fog is ~7.5 ms/frame cheaper — 31 to 41 FPS with fog on (DOOM-0276) The fog used to fire a test ray straight up from every one of its 24 samples per pixel, just to ask "is there sky above here?". DOOM is flat-mapped — one ceiling per spot on the floor — so that answer was already in the small per-level map the fog builds for its doorway seep. It now reads it from there instead. Measured on an RX 6600 in E1M1 at 50% render scale: fog costs +35% of frame time before and +4% after. The one visible cost is that the line between misty outdoor air and clear indoor air now follows that map's 64-unit grid, so it can sit up to half a cell from the wall.

• nee_sampling_test's unbiasedness bound is derived from the sample count instead of a flat 0.5% The old fixed tolerance sat only ~3.9 sigma from the estimator's true standard error on two of the five weight sets, well short of the 6 sigma the neighbouring frequency check uses. The bound is now computed from the exact estimator variance, so it scales with N and the weights; all five sets currently land within 1.6 sigma.

Fixed

• The Windows build no longer fails to compile Two faults, both from the developer-capture work and both invisible on Linux. -warpto used a 64-bit whole number without asking for the header that defines one — Linux picked it up by accident from a neighbouring header, the Windows cross-compiler did not. The F12 screenshot folder was then created with a two-argument call that Windows spells with one, the way -cdrom already does elsewhere in the engine. Every Windows build since those flags landed stopped with an error. Caught by the release build, which makes both versions before it publishes anything.

• The lighting self-test now covers the glowing-sprite light path it was skipping (DOOM-0122) -rtverify proves the renderer's lighting maths is unbiased by comparing two estimators that should agree. Both were being handed a light list that stopped short of the sprite lights — fireballs, glowing pickups — so the newer half of the lighting code was never actually checked. Both estimators now receive the real split, and the verify run reports how many lights of each kind it covered, so a future gap is visible rather than silent.

• -devshot N now captures the Classic tier as well as Solid and Ultra (DOOM-0294) Classic never builds a Vulkan swapchain image, so the flag was a silent no-op there -- and a harness that finds no new file will happily read a stale one. All three tiers now write dev-shots/shot-NNNN.png under one shared naming helper.

• Bound the scaled patch blitter and the Classic menu's text rows (DOOM-0230) The scaled patch draw added for the menu work never got the on-screen bounds check its two siblings have, and the menu text helper that calls it clipped sideways but not vertically. Off-screen text is now dropped with a one-off note instead of writing outside the frame.

• Skip the frame when the video texture cannot be locked A failed SDL_LockTexture leaves the pixel pointer untouched, and the Classic renderer wrote the whole frame through it anyway.

• Ordinary walls no longer glow like lights, and DOOM's own light fixtures now do (DOOM-0307) A curated list of light-source wall textures replaces the brightness test that decided this before. That test rated a texel by its strongest colour channel, and DOOM's palette ramps nearly all end at 255 in some channel, so the palest cement highlight scored exactly as pure fire did — 82 of DOOM II's 428 wall textures cast light, including all nine CEMENTs and every Wolfenstein wall. It was wrong in the other direction too: the game's own light panels (LITE3, LITE5, LITEBLU, COMPSTA) sat below the threshold and emitted nothing, so the lamps were dark while the walls glowed. Both are fixed; sprites, flats and liquids are unchanged.

• A torch revealed by a door that opens now lights the fog in front of it, instead of waiting for a level reload (DOOM-0296) (DOOM-0296) Which torches can light which patches of air was worked out once, when the level loaded — so a torch behind a shut door stayed unknown to the fog even after you opened the door. The answer is now recalculated whenever a door or lift finishes moving.

  Honest note on what you will see: on the stock maps, very little. This was measured rather than assumed — opening every door in DOOM 2's MAP01 changes the picture by about a five-hundredth of the threshold the project uses to decide a look has changed at all. Vanilla DOOM rarely puts a torch behind a shut door and close enough to matter. It is a correctness fix that stops a wrong answer being possible, and any map or texture set that does place a bright light behind a door gets it for free.

• The renderer's -rtverify self-test failed on DOOM 2 and passed on DOOM 1, on the same build (DOOM-0297) The check was under-sampled, not the renderer wrong. DOOM 2's lights are fewer and more clustered, so the estimator needs more samples there to settle; the test now takes them (262144 vs 16384) and both games pass the same unchanged 0.50% bar. Raising the sample count can only make the test stricter, so nothing was loosened to get there.

• A nukage pool glowed only in patches, because the per-texel emissive mask was applied to liquids too. (DOOM-0302) Nukage pools looked like they had random glowing spots in them. Now the whole pool glows evenly.

• The -shotverify capture is not tic-deterministic, so a cold-cache run blesses a different golden. (DOOM-0287) Adds a -noinput flag so an automated test or profiling run ignores the keyboard, mouse and gamepad and leaves the pointer to whoever is using the desktop. The -shotverify / -shotcompare capture modes imply it, which also makes their golden-image comparison trustworthy: a stray mouse movement during a capture used to turn the camera and change the image.

• Screenshot captures are no longer time-dependent, so the visual-regression gate compares like with like (DOOM-0011) The drifting fog and the liquid ripples both ride a wall clock, which made every capture a slightly different image.

• Fog now rolls into a room whose wall opens during play (DOOM-0281) The seep field that decides how far fog reaches indoors was flooded once at level load from the doors' spawn state, so a wall that opened in play left the room behind it permanently clear. It is now re-flooded when an opening actually appears or vanishes, and the fog eases across to the new answer over about a second so the mist drifts in through the opening instead of popping into place. A door that shuts eases it back out. Ultra's ray-traced view; costs nothing on a map where nothing has moved.

• Fog and seep no longer read the empty-space sentinel along a level's far edges (DOOM-0276) The seep map's grid was sized with a rounding-down divide, which left its outer "nothing here" ring overlapping real air at the top and right edges of a level. E1M1's grid was one column short. Found by the review of the change above, and it had to be fixed for that change to be correct.

• Fix the correctness and doc-drift findings from the 2026-07-26 audit + indie-review sweep. (DOOM-0263) The baked global-illumination pass was reading the sky as if it were a wall; several smaller bugs and six stale documentation claims are fixed too.

• game_select_test drives the real IWAD selection loop rather than a copy of it (DOOM-0244) (DOOM-0244) The preference scan moved from D_DetectIwads into iwad_select_reps() in iwad_detect.h, parameterised by an "is it installed?" predicate — access() for the engine, an in-memory set for the test. Changing the real selection order now fails the test, which it could not do before.

• rb_text_test bakes the bundled Oxanium instead of skipping itself when no system font is installed (DOOM-0243) (DOOM-0243) It used to look for DejaVu at three distro paths and, finding none, print "skipped" and exit 0 — a green result that ran none of its assertions. It now bakes the embedded assets/Oxanium-SemiBold.ttf the engine itself ships, so a missing font is impossible; fonts-dejavu-core is no longer a CI dependency.

• Test suite no longer passes vacuously — assert() retired for a check() helper (DOOM-0242) (DOOM-0242) assert() is deleted by -DNDEBUG along with any call inside it, so the four tests that wrote assert(function_under_test(...) == x) would have printed "all passed" while running nothing. Reproduced, then fixed by moving the whole suite onto tests/check_util.h, whose check() is an ordinary function that also records a failure and keeps going instead of aborting and hiding every later case.

• Corrected mold from a required to an optional dependency in the README. The README listed the mold linker among the required Linux dependencies. The Makefile detects it and falls back to the default linker when it's absent, so a first-time builder was being sent after a package they don't need.

• The local CI mirror now runs the same boot smoke as GitHub Actions. packaging/ci-local.sh announced itself as "exactly what GitHub Actions runs", but its container mode ran only build + unit tests and skipped the DOOM-0203 headless boot smoke. A boot regression could pass locally and still turn CI red. The container path now installs Freedoom and runs the smoke, as the workflow does.

• release.sh now updates README's "Latest release" line (DOOM-0202 debt sweep). The release standard says the version lives in three places in lockstep — the git tag, the CHANGELOG heading, and README's "Latest release" line — all moved by the release tool. The tool only ever moved two of them, so every release shipped with a stale README. It now rewrites the README line too, and fails loudly if it can't find it.

• Golden-image gate no longer inherits your fog setting (DOOM-0202). The -shotverify / -shotcompare capture pins a canonical render configuration so a screenshot comparison can't be poisoned by a play-test tweak left in ~/.doomrc. Volumetric fog (rt_fog) shipped after that pin was written and was never added to it, so the fog level leaked back in — exactly the config-dependence the pin exists to prevent. It is now pinned with the rest.

• Golden-image visual-regression gate is now config-independent (DOOM-0208). The -shotverify / -shotcompare modes rendered the normal path, which inherited the live ~/.doomrc — so a play-test tweak (a brighter rt_brightness, a stuck-on flashlight, a flipped effect toggle) silently poisoned the golden and made the gate fail on an unchanged render. They now pin a canonical, config-independent RT configuration (the shipped defaults) whenever armed, so a capture is reproducible regardless of the user's live config. Re-blessed the E1M1 Ultra-RT golden under the canonical config (fresh compare is bit-exact, mae=0.000).

• Fix three low-severity bounds nits: donut NULL-deref, sfx off-by-one, basedefault snprintf. (DOOM-0220) Three small safety tidy-ups: a malformed WAD donut, a sound-index edge, and a long $HOME path can no longer misbehave.

• Fix -warp E/M bounds so -warp 3 on a non-commercial IWAD can't NULL-deref. (DOOM-0219) Typing doom -warp 3 on DOOM 1 crashed at startup; now it's handled gracefully.

• Guard RB_BuildPSprites against a negative sprite lump index. (DOOM-0218) A missing weapon-sprite frame could read out of bounds; now it's skipped, matching the world-sprite path.

• Drain the GPU before RB_Vulkan_BuildLevel frees/recreates live buffers. (DOOM-0217) Loading a new level could, in rare timing, free graphics memory the GPU was still using; now the GPU is drained first.

• Clamp menu value-name indices (showMessages/fpsCorner) against a hand-edited config. (DOOM-0216) Editing ~/.doomrc to an out-of-range value could crash the game when opening the menu; the value is now clamped.

Security

• Validate the REJECT lump against the map's sector count (DOOM-0119) The light cull indexed the REJECT visibility table by sector pair without checking the lump was big enough to hold that many sectors, so a map shipping a short REJECT read past the end of it on both the CPU and the GPU. Too small now simply turns the cull off, and says so.

• Bound the last unguarded WAD and savegame indices (DOOM-0254) P_LoadLineDefs dereferenced its two vertex indices straight out of the PWAD while the nine sibling indices around it were already guarded, and savegame loading cast stored state, type and player indices back into array subscripts unchecked -- a saved player index of 0 read players[-1]. Both now go through the same refuse-the-file guard the rest of the level loader uses.

• Harden every untrusted-input boundary the 2026-07-26 audit + indie-review sweep found. (DOOM-0254) A hostile or broken WAD, savegame, config file or command line can no longer make the game read or write memory it does not own.

• Clamp netconsole (packet player field) to MAXPLAYERS in d_net GetPackets. (DOOM-0215) A malformed network packet could write out of bounds using a bogus player number; now such packets are skipped.

• Clamp netgame packet numtics against BACKUPTICS in i_net PacketGet. (DOOM-0214) A malformed network packet could overflow an internal array before any validation; now oversized packets are dropped.

• Bound mus2mid MUS->MIDI reads by the real lump length, not the header's own claim. (DOOM-0213) A crafted in-WAD music track could make DOOM read up to ~64KB past the end of the lump; now reads are capped at the true lump size.

• Harden W_AddFile/W_Reload: validate the WAD directory against the real file size. (DOOM-0212) A hand-made/corrupt WAD could previously make DOOM read random memory while loading; now a bad directory is rejected cleanly.

Added

• A cleaner, sharper in-game menu for the 3D modes, plus a consistent Classic main menu. (DOOM-0206) In the Solid and Ultra 3D modes, every menu now uses a crisp modern font drawn at full display resolution over a dimmed backdrop, with a layout that no longer overlaps the bottom status bar. The menu cursor is the real DOOM skull and the main-menu title shows the real DOOM logo, both sharpened and brightened. In the original Classic (1997 software) mode, the main-menu items now all share one consistent size and font, instead of mixing large graphic words with a tiny "Game Select" row.

• De-tiled, grimy surfaces in the Ultra ray-traced view (DOOM-0181, DOOM-0179) (DOOM-0181) HD walls and floors no longer read as the same tile pasted over and over: each repeat is stochastically offset/mirrored and keyed to its world position (Inigo-Quilez 4-corner blend), breaking both within-surface and between-surface tiling. Toggle/quality via the ] key (off / 2-tap / 4-tap). On top, a filth layer makes a monster-overrun base look filthy: distinct, hard-edged, multi-coloured dirt stains (sampling a real first-party CC0 dirt texture) with crevice pooling and green-goo puddles on floors — applied to every non-sprite world surface, never on sprites or on the flowing green liquid itself. Ultra RT view only; Classic and Solid are byte-identical.

Changed

• Solid (raster) 3D view now overlaps CPU frame-build with GPU rendering, roughly doubling its frame rate (DOOM-0074). The per-frame CPU work (moving-sector re-height, point-light cull, sprite billboards) now runs ahead of the GPU fence in steady-state raster, so the CPU prepares the next frame while the graphics card finishes the current one instead of waiting for it. On the RX 6600 (E1M1) this took the Solid view from ~70 to ~161 fps. The ray-traced Ultra view is unchanged (it stays single-frame-in-flight; extending the overlap there is tracked separately).

Fixed

• Fixed a long-standing operator-precedence bug in the "donut" sector effect that could misbehave (or crash) on hand-crafted donut sectors (DOOM-0138).

• Ultimate Doom now shows the correct per-episode sky (SKY1-SKY4) instead of always the E1 sky (DOOM-0139). The sky picker compared mission-pack values against the game-mode field; because they overlap numerically, retail (Ultimate Doom) was wrongly forced onto the Doom II map-range sky (always SKY1). Fixed to test the mission field, so E2/E3/E4 get SKY2/SKY3/SKY4 as intended.

• Silenced the flood of "V_DrawPatch: bad patch (ignored)" warnings at startup and on 4K/widescreen HUD compositing (DOOM-0137, DOOM-0171). The view-border bezel and widescreen status-bar fill legitimately draw UI art past the 320-wide low-res framebuffer; those patches were already ignored (the frame renders correctly), but each printed two warning lines — dozens at startup, hundreds at 4K. The diagnostic is now capped at the first few occurrences with a suppression note. Log-hygiene only.

Added

• Activated switches/buttons emit a faint coloured glow (red buttons glow red). (DOOM-0082) When you press a lit button or switch, it gives off a soft glow in its own colour — a red button casts a faint red light — instead of staying flat.

• Armour pickups' green glowing eyes emit a faint green glow in the path tracer. (DOOM-0157) The armour pickups have little green glowing eyes; those should cast a soft green glow when you are near them, instead of looking flat — they do not glow right now.

• Game-select boot menu: choose DOOM 1 or DOOM 2, switch back without relaunching by hand. (DOOM-0060) When both DOOM 1 and DOOM 2 are installed, a startup chooser lets you pick which to play, and you can switch games mid-session from the main menu without relaunching by hand. The app remembers the last game you played and defaults to it next launch. If only one game is installed it boots straight in.

• Name the gamepad confirm button in the Quit prompt, per controller family. (DOOM-0161) The "quit?" box now tells controller players which button to press to confirm, and shows the right name for their pad — "A" on an Xbox pad, "X" on a PlayStation pad.

• Answer the Quit (and other yes/no) confirmation prompts with the gamepad. (DOOM-0160) You can now confirm "Quit Game" with the controller instead of having to reach for the keyboard's Y key — the same button you use to pick the menu item confirms the prompt.

• Announce a found secret with an on-screen message + a distinct sound (all renderers). (DOOM-0158) Stepping into a secret area now shows "A secret is revealed!" centred on screen in bright yellow and plays a distinct chime, in all three renderers (Classic, Solid, Ultra) — previously secrets were only revealed in the end-of-level tally.

Changed

• Render tier drives the ray-tracing default so Solid is the fast raster original view. (DOOM-0169) Picking the "Solid" graphics mode now gives the fast, classic-looking view instead of secretly running the heavy ray-traced renderer — so it's smooth. "Ultra" is the ray-traced one. You can still flip ray-tracing on/off within a mode with the ~ key.

• 3D renderer defensive-hardening bundle (indie-review deferred items). (DOOM-0073) Defensive hardening of the 3D renderer against corrupt or pathological (non-stock) level data — cap-carve buffer-overflow guard, per-frame texture-index bounds, sprite-rotation int overflow fix at the far map edge, a mid-session overlay-resize guard, and checked results on the load-bearing Vulkan setup calls. No change to normal play.

• 3D renderer tiers are now gated on descriptor-indexing support at probe time (DOOM-0059) On a GPU that lacks the Vulkan 1.2 descriptor-indexing features the bindless material path needs, the menu now stays on Classic instead of erroring out when a 3D mode is selected. The probe checks the same four features device creation requires, so an unsupported GPU is never offered Solid/Ultra.

Fixed

• Render the DOOM sky in the ray-traced view (no more see-through floating geometry). (DOOM-0141) In the Ultra/Solid ray-traced view the sky was a hole, so distant buildings floated in mid-air and the sky showed as flat blue instead of the mountains you see in Classic. This makes the sky a solid backdrop again.

• Alpha-test two-sided masked mid-walls (grates/fences) in the ray-traced view so you can see through them. (DOOM-0163) In the ray-traced view, see-through grates and fences look like solid walls; make them see-through like they are in the classic and raster views.

• Title-screen music sometimes silent on the very first launch, plays on the next. (DOOM-0165) Sometimes when you first open the game there's no menu music, but if you quit and open it again the music plays fine. Track down why the first launch occasionally starts silent.

• Fix the DOOM-0060 game-select Windows cross-build (windows.h boolean clash). (DOOM-0166) The DOOM 1 / DOOM 2 chooser could not be compiled for Windows at all — this fixes that so it can be tested on Windows.

• Draw the DOOM-0141 sky occluder in the raster view too, so distant geometry stops floating there. (DOOM-0162) The raster 3D view (Solid tier / ~ toggle) now hides distant geometry behind the sky the same way the ray-traced view does, so far-off buildings no longer appear to float. The DOOM-0141 sky occluder mesh is drawn depth-tested in the raster pass via a new world-space sky-dome flag, and the DOOM-0143 below-horizon fog fade is mirrored into the raster sky shader.

• Seam (black line + white sliver) where the RT sky cap meets a wall top. (DOOM-0143) With the new ray-traced sky, a thin dark line and a small bright sliver can show right where a wall meets the sky.

Added

• Restored the subtle pitch variation on repeated sound effects (DOOM-0156) Repeated sounds (gunshots, etc.) again vary slightly in pitch like classic DOOM, instead of sounding identical every time. Built on demand so it costs little memory.

• Switch weapons with the mouse wheel and the gamepad D-pad (DOOM-0153) Scroll the mouse wheel up/down, or press the controller D-pad left/right, to cycle to the next/previous weapon you own. Works like tapping the number keys (so it's safe in demos and multiplayer).

• Widescreen and Fill Screen display toggles in the Renderer menu (DOOM-0147 Part C) (DOOM-0147) Two persisted options (Options -> Renderer): "Widescreen" turns the authentic Hor+ widescreen on or off (Off forces classic 4:3 even on a wide monitor; takes effect on restart), and "Fill Screen" stretches the picture to fill the whole monitor, removing the black bars on displays whose shape isn't 4:3 (applies instantly). Both are saved to ~/.doomrc. Defaults reproduce the prior behaviour exactly.

• Authentic widescreen (Hor+) for the Classic software renderer (DOOM-0147 Part B) (DOOM-0147) On a display wider than 4:3 the Classic renderer now shows MORE of the level to the left and right instead of stretching the 4:3 picture. The view width is chosen at startup from the real display aspect; the projection keeps DOOM's vanilla vertical proportions and per-column angle, so it still feels like the original. UI art and the status bar stay centred. Displays at 4:3 or narrower (e.g. 5:4 1280x1024) render authentic 4:3 unchanged — a provable no-op there. Internally SCREENWIDTH became a runtime value (view-width arrays now sized at the MAXWIDTH cap). Builds clean on Linux and Windows; awaiting visual confirmation on a 16:9 display. Part C (a 4:3<->Widescreen menu toggle) follows.

Changed

• Sound effects are much louder / the SFX slider now spans its full range (DOOM-0047) Effects were far too quiet relative to music (the old mixer capped them at ~12%). The SFX volume slider now scales effects from silent to full, and centred sounds (including all menu blips) play at full volume, so effects balance the music properly. Adjust the two sliders to taste.

• Mouse now turns only — it no longer moves the player forward/back (DOOM-0154) Moving the mouse up/down no longer walks the player; the mouse only turns left/right. Use the arrow keys or WASD to move.

• Gamepad remap: flashlight on D-pad Up, L1 is Run again (DOOM-0153) The controller D-pad is now the weapon/flashlight pad in-game (left/right change weapons, up toggles the flashlight), and L1 goes back to being a Run button. The D-pad still navigates menus.

• Widescreen now auto-detects the display and defaults off on non-widescreen screens (DOOM-0147) On a 4:3 or 5:4 monitor (where widescreen has no effect), the Widescreen option now correctly reads Off instead of a misleading On. Displays wider than 4:3 keep the saved preference (on by default).

• Widescreen intermission (level-end) screens fill the sides instead of showing stale pixels (DOOM-0151) The "level finished" and "entering" map screens now extend their background to the edges on a widescreen display, matching the title and HUD. No change at 4:3.

• Widescreen HUD sides now continue the grey status bar instead of black bars (DOOM-0151) The strips either side of the centred status bar are filled by extending the bar's own edge, matching the title-screen treatment. No change at 4:3.

• Widescreen title/menu screens fill the sides instead of showing black bars (DOOM-0151) On a display wider than 4:3, the title, credits, help and menu-background screens now extend their own edges outward to fill the black side strips, so they look intentional rather than pillar-boxed. Uses only the game's own on-screen pixels (no added art). No change at 4:3. Intermission and finale screens still to follow.

• The menu now shows the plain DOOM title behind it, not the attract-loop credits Opening the menu while the credits/help screen was showing put red menu text over red credit text and was hard to read. The menu now always draws the plain TITLEPIC behind it and pauses the title/demo cycle until you close the menu.

• Rebalanced audio so sound effects are no longer drowned out by music: the music volume ceiling is lowered (quieter at every slider position) and new installs default to full sound-effects volume. (DOOM-0047)

Fixed

• Sound effects on Windows: play them through SDL2_mixer like the music (DOOM-0047) Rewrote the effects engine to play each sound as an SDL2_mixer chunk on the same audio device as the music (the approach Chocolate Doom uses), replacing a hand-rolled mixer that was near-silent on Windows. Effects loudness is calibrated to match the previous Linux behaviour. No change expected on Linux.

• Sound effects silent on Windows (take 2): mix effects into the music device (DOOM-0047) The game opened two separate audio devices — one for effects, one for music — and on Windows the effects device barely produced output. Effects now play through the same (working) device as the music, so they're audible on Windows. Music and Linux behaviour are unchanged.

• Sound effects nearly silent on Windows (DOOM-0047) The effects mixer ran at 11025 Hz, which SDL's Windows (WASAPI) audio backend resamples badly to near-silence. The mixer now outputs at 44100 Hz (the common native rate, matching the music), so effects play at full volume on Windows. Pitch and Linux behaviour are unchanged.

• Music played at full volume until the volume slider was touched (and drowned the SFX on Windows) (DOOM-0047) The saved music volume wasn't re-applied when a track actually started, so SDL2_mixer's MIDI backend (on Windows) played it at maximum until you nudged the slider -- which also made the sound effects seem far too quiet. The volume is now applied every time music starts.

• Grey squares covered parts of the HUD in widescreen (DOOM-0147) Status-bar numbers/icons were drawn shifted for widescreen but their background was cleared at the old position, leaving grey rectangles over adjacent readouts (ammo, arms). The clear now follows the shifted position.

• Floor and ceiling textures swam relative to walls in widescreen (Classic renderer) (DOOM-0147) On a widescreen display the flat (floor/ceiling) texture scale didn't match the widened field of view, so floors appeared to slide as you moved. Now locked to the same 4:3 reference the rest of the view uses. No change at 4:3.

• Crash ("Bad V_CopyRect") when starting a level in widescreen with the HUD on (DOOM-0147) The status-bar draw copied to a shifted position on a widescreen screen, which tripped an over-strict internal bounds check and aborted the game the moment a level loaded. The check now measures against the real (wider) screen, so widescreen play works with the HUD visible. No effect at 4:3.

• The Screen Size slider can no longer be raised high enough to hide the in-game HUD; the status bar now always stays on during play. (DOOM-0148)

• Classic renderer now presents at authentic 4:3 instead of a stretched 16:10, so the picture has correct proportions and fills a 4:3 monitor (title and menu screens too). (DOOM-0147)

Added

• Player flashlight (headlamp), toggled by F or gamepad L1 (DOOM-0044) A camera-mounted spotlight aimed along the view, toggled with F or gamepad L1 and persisted in the config. In Ultra (path-traced) it casts real ray-traced shadows; in Solid (raster 3D) it lights a cone with distance falloff. Same session: the path tracer's dynamic lights gained a near-field softening so they no longer blow out at point-blank range, the SVGF temporal denoiser's anti-ghosting was fixed so a light switching off no longer lingers, and the muzzle flash was brightened to light the surrounding room.

• Ultra ambient floor: path-traced rooms marked bright by the level designer no longer go pitch black (DOOM-0043) The path tracer now adds a gentle ambient term scaled by each surface's DOOM sector lightlevel, so a sector the mapper lit brightly reads as lit even when it holds no emissive lamp texture, while dark sectors stay dark. Applied as a floor under the baked GI (max, not add) so already-lit rooms are unchanged. Ultra-only (Solid keeps its pitch-black rooms — the flashlight is its answer). Brightness is an inline tunable pending playtest.

• User-adjustable brightness slider for the path-traced (Ultra/denoiser) view. (DOOM-0096) The ray-traced view looked a little dark. Add a Brightness slider to the Renderer settings menu so you can dial it to taste; it now defaults a touch brighter.

• Temporal upscaler (TAAU) for the Ultra path tracer — DOOM-0009 build step 6-d phase 1 (DOOM-0009) The denoised path-tracer view can now render below display resolution and reconstruct a full-resolution image by accumulating sub-pixel-jittered frames (a custom temporal anti-aliasing upsampler). Adds the jitter, motion-vector, and menu plumbing the later FSR 2 / FSR 3.1 backends will share. New Options -> Renderer sub-menu: Renderer, Upscaler (Off / TAAU), Render Scale (100/75/67/50%); defaults to Off, so the existing image is unchanged until enabled.

• Add a 3D wireframe debug view, toggled by the gamepad Share button. (DOOM-0077) Draws the world and sprites as wireframe over a filled sky in Solid/Ultra to show what the renderer builds; no effect in Classic. Start alone now opens the menu.

• Reflect runtime wall/flat texture changes in the 3D mesh (switches, animated textures). (DOOM-0066) In the 3D renderers a pressed switch doesn't light up and animated surfaces (screens, slime) don't animate, because the 3D world bakes each surface's picture in once.

• Map the controller Triangle (Y) button to toggle the automap. (DOOM-0063) Press Triangle on the PS4 pad to open the map; press it again to close it.

• Let the controller Circle (B) button close an open menu. (DOOM-0056) Circle on the controller now backs out / closes the menu, like Start does.

• Convert the renderer to true 3D. (DOOM-0008) Replace DOOM's fake-3D trick with a real 3D engine.

• Optional on-screen FPS counter with selectable corner placement (DOOM-0046) An Options "FPS:" item cycles Off / Top-Left / Top-Centre / Top-Right, persisted in the config. Drawn with the small HUD font into the 320x200 screen buffer, so it appears under every renderer (Classic, Solid, Ultra). Measured as a half-second rolling average via a new wall-clock millisecond timer.

• Add game controller (gamepad) support. (DOOM-0038) Plug in a controller and play: left stick moves and strafes, right stick turns, the triggers and face buttons fire, open doors and run, and Start opens the menu. Reuses DOOM's original joystick handling so the menus and controls just work; controllers can be plugged in and out while playing.

• Add a Windows build target. (DOOM-0006) Produce a version that runs on Windows so friends can play it.

• Keep the classic 2.5D renderer selectable alongside the 3D renderer. (DOOM-0026) When the new 3D renderer arrives, you'll still be able to switch back to the original DOOM look from the main menu - both renderers ship in the same build.

• Render the classic view at 640x400 (hi-res). (DOOM-0027) The picture is now drawn at double the internal detail (640x400 instead of 320x200), so walls, floors and monsters look crisp instead of blocky when the window is enlarged - the classic DOOM look is unchanged, just sharper. Built from a design spec hardened through 6 cold-eyes review loops; the 320x200 UI art (status bar, menus, HUD, intermission, finale) is integer-doubled to match. (Code-complete and building clean; pending an in-game play-test.)

Changed

• Resample omnidirectional sprite lights with RIS so the path tracer casts one shadow ray instead of one per light. (DOOM-0120) The Ultra path tracer's sprite-light loop now uses Resampled Importance Sampling (the cheap end of the ReSTIR family): it weighs every surviving candidate light, keeps one by weighted-reservoir, and casts a single shadow ray on the survivor — instead of a shadow ray per light. Frame time is now effectively independent of how many glowing props are on screen (measured ~flat from 22 to 40 sprites), and the worst-case is faster than before. No cross-frame reservoir is kept, so it stays light on AMD RDNA2 registers; the temporal upscaler and denoiser absorb the single ray's noise. The estimator is provably unbiased against the previous per-light sum, and the old dim-sprite cull (with its small one-sided bias) is removed.

• REJECT-lump light culling for NEE (cheap-ladder step 1). (DOOM-0119) Ultra path tracer skips glowing-sprite lights in rooms a surface can't see (via the WAD REJECT visibility lump), before casting their shadow rays. At 50% render scale in a light-heavy multi-room scene the megakernel now dips to ~9 ms (51 fps spikes) where cross-room lights are culled, up from the ~37-46 fps DOOM-0090 baseline.

• Smooth camera between game tics in the 3D renderers — render rate is no longer capped at the 35 Hz game tick (DOOM-0048) DOOM's world updates 35 times a second; the 3D view now interpolates the camera between those updates so walking and turning look smooth at any frame rate above 35 FPS, instead of stepping at 35. The simulation itself is untouched (so demos and multiplayer stay identical), and Classic mode still renders locked to the tick.

• Ultra now boots playable by default (TAAU upscaler at 50% render scale) instead of at native resolution (DOOM-0090) Fresh installs start Ultra the way it's actually playable (~35-42 FPS on a mid GPU) rather than ~8 FPS at native; existing saved settings are untouched and the scale is still adjustable in Options -> Renderer. Also trimmed the denoiser's coarsest filter pass (5->4) to shave its cost with minimal visual change.

• Ultra path tracer runs markedly faster in light-heavy rooms (~20s → 35-42 FPS on an RX 6600 at the same 50% render scale) (DOOM-0090) Skips shadow rays for sprite lights too far or dim to add visible light, instead of tracing one per glowing prop per pixel. The win grows with how many glowing props are in view. Plus a new on-screen per-pass GPU profiler (the \ key) used to find the hotspot.

• Ultra now boots into the denoised path-traced view and remembers your view choice between sessions (DOOM-0116)

• Compact the static world BLAS to reclaim ray-tracing acceleration-structure memory (DOOM-0091) The per-level world BLAS is now built with ALLOW_COMPACTION and copy-compacted into a right-sized acceleration structure at load, reclaiming the worst-case build padding (a 20-50% VRAM win that scales with large WADs). ALLOW_UPDATE is kept so moving doors/lifts still refit on the compacted structure.

• Smooth (pixel-art-aware) upscaling of the 2D title/HUD/menu overlay in the 3D renderers. (DOOM-0089) The menus and title screens now look smooth instead of blocky when shown over the 3D view.

• Print clear WAD-placement guidance when no IWAD is found. (DOOM-0040) If no game data file is found, the game now tells you exactly where to put a WAD instead of a cryptic error.

• Launch in fullscreen by default, with -windowed to opt out. (DOOM-0039) The game now opens fullscreen straight away; pass -windowed if you'd rather have a window.

• Replace obsolete alloca() in r_data.c and w_wad.c with C99 VLAs (bounded buffers) and checked heap allocations (untrusted WAD-driven sizes), so a hostile lump count fails gracefully instead of overflowing the stack (DOOM-0034)

• Mark I_Error as _Noreturn. (DOOM-0023) Tells the compiler that the fatal-error function never returns, so it can optimise better and reason correctly about the code that runs after a fatal-error guard.

Fixed

• M_QuickLoad sprintf can overflow tempstring[80] (-Wformat-overflow). (DOOM-0097) A harmless-looking quick-load confirmation message could, with a long savegame name, write past the end of a fixed text buffer — a latent crash/corruption risk flagged by the compiler.

• Draw the 2D presentation layer (HUD, menu, FPS, weapon) over the path-traced view. (DOOM-0094) In the ray-traced view you currently see only the world — no menu, HUD, FPS counter or your gun. Bring those back so it's a real playable view, not a bare diagnostic.

• 3D renderer: use a per-swapchain-image present semaphore (DOOM-0079) The Vulkan present-completion signal (renderFinished semaphore) was shared across frames, so a queue submit could re-signal it while a prior present still held it (a validation error caught once the Khronos validation layer was installed). Now one semaphore per swapchain image, indexed by the acquired image — no behaviour change on screen, but technically correct.

• Fix the sky rendering a black band across distant outdoor views in the 3D back-ends. (DOOM-0076) The sky shader squashed the panorama into the top half of the screen and clamped everything below centre to the texture's dark bottom row; it now maps the sky at DOOM's fixed scale with the horizon at screen centre and wraps instead of clamping, matching Classic.

• Guard the Vulkan surface-format query against a zero count / dropped result. (DOOM-0071) On an unusual graphics driver the renderer could read invalid memory while picking a display format at startup; now it checks properly and fails loudly instead.

• Faithful 3D lighting — ceilings no longer render black in Solid/Ultra (DOOM-0069) Removed a non-canonical directional key light from the mesh fragment shader. Classic DOOM shades by sector light + distance only, so floors and ceilings at the same light/distance now match; previously down-facing ceilings were darkened ~40% and went black in dim sectors (the courtyard-overhang band).

• Stray distant floor/ceiling planes in the 3D outdoor view. (DOOM-0065) In the 3D renderers a dark slab appears across the distance outdoors where Classic shows open sky.

• Build flush lift/step shaft walls in the 3D mesh so they appear when the lift travels. (DOOM-0068) In the 3D renderers a lift shaft wall was missing (you could see through it) until the lift moved; now it's there like Classic.

• Stop door/lift textures stretching and squashing as they move in the 3D mesh. (DOOM-0067) In the 3D renderers a moving door/lift stretched its texture open and squashed it closed; now the texture stays put as the surface slides, like Classic.

• Automap renders blank/frozen in the 3D back-ends (Solid/Ultra). (DOOM-0064) The in-game map is blank in the 3D renderers and only updates in Classic; needs a runtime probe to finish diagnosing.

• Draw the upper wall above an outdoor doorway in the 3D mesh (sky-ceiling guard fix). (DOOM-0062) In the 3D renderers the wall above DOOM's outdoor exit door was see-through; now the lintel renders like Classic.

• Port DOOM wall texture pegging into the 3D mesh (fixes vertically-misaligned uppers and switches). (DOOM-0061) In the 3D renderers a wall switch's button graphic was sliding out of view; now textures line up vertically like Classic.

• Fix in-game menu text ghosting in the Classic renderer (hi-res). (DOOM-0053) In Classic mode, menu pages smear over each other as you navigate.

• Close black gaps in floor/wall geometry near doorways in the 3D view. (DOOM-0052) Some doorways show black wedges where floor/wall should be.

• Fix mid-game renderer switching (blank 3D world, Classic ghosting). (DOOM-0051) Switching renderers during play broke the view; now rebuilt cleanly.

• Animate moving sectors (doors, lifts, floors, crushers) in the 3D view. (DOOM-0049) Doors and lifts don't visually move in 3D mode yet.

• Classic hi-res floors no longer smear or crash (DOOM-0055) At the sharper 640x400 resolution the floor and ceiling could smear during movement or close the game; the renderer's floor/ceiling row tracking is now widened to handle the taller picture (the classic 1997 limitation it warned about). Fixes the floor rendering and the windowed-mode crash.

• Menu now shows when booting straight into a 3D renderer (DOOM-0045) Launching directly into the Solid/Ultra 3D renderer previously showed a blank screen with no title or menu until a level loaded; the 2D menu now composites over the 3D view from the first frame.

• Sound effects no longer drowned out by the music (DOOM-0047) Music plays on a separate, louder audio device than the sound effects; its volume is now capped so effects stay audible underneath it.

• Fix DOOM-0027 hi-res scaling regressions: small view window and mispositioned weapon sprite. (DOOM-0041) In the new sharper (640x400) mode the 3D view was a small square in the middle of the screen and the gun drifted up to the centre; both now sit and scale correctly.

• Initialise VulkanState::viewProj in the 3D renderer back-end. (DOOM-0037) Make sure a camera matrix in the new 3D renderer always starts with a known value.

• Fix the standalone sndserv build by adding the missing <string.h> include to soundsrv.c (DOOM-0036)

• Fix signed/unsigned printf/scanf format-specifier mismatches in the serial/IPX multiplayer drivers (flatadr, uart) (DOOM-0035)

• Pass a literal format string to printf for the dev/CD-ROM banners. (DOOM-0033) Tidies up two startup messages so they print safely.

• Guard unchecked heap allocations against out-of-memory null-deref. (DOOM-0032) If the game can't get memory it now exits with a clear message instead of crashing.

• Loading a savegame written by a different DOOM version no longer leaks the file buffer on the rejected-version path. (DOOM-0031)

• Playing back a demo recorded by a different DOOM version no longer crashes — it skips the demo and returns to the title screen (or exits cleanly for an explicit -playdemo/-timedemo). (DOOM-0030)

• Fix undefined order-of-evaluation in sndserv's strupr. (DOOM-0029) Tidied a tiny string-uppercasing routine in the standalone sound server that relied on undefined C behaviour, so it now works reliably on any compiler.

• Fix an off-by-one out-of-bounds read in the menu/finale font renderer. (DOOM-0028) A stray character in on-screen text could make the game read one slot past the end of the font table; now it's skipped cleanly like any other non-font character.

• Stop leaking the candidate IWAD path strings in IdentifyVersion. (DOOM-0025) Tidies up the data-file search at startup so the small scratch strings it builds while hunting for your DOOM .wad are no longer left dangling in memory.

• Harden the config-file parser against an over-long line. (DOOM-0024) A corrupt or hand-edited config file with a very long line can no longer overflow an internal buffer and crash the game.

• Print pointers with %p instead of %lx in s_sound debug output. (DOOM-0022) A cosmetic fix to the debug logging so memory addresses print correctly on 64-bit builds.

• Fix off-by-one ammo-type bounds check in P_GiveAmmo. (DOOM-0021) Corrects a boundary test on ammo types so an edge value can't read past the end of the ammo array.

• Add the missing mobjinfo bounds guard in P_RespawnSpecials. (DOOM-0020) Hardens the item-respawn code against an out-of-bounds read if a queued item has an unrecognised type.

• Fix level-load reset clearing pointer size instead of the mouse/joy button arrays. (DOOM-0019) On each new level the game tried to wipe the mouse and joystick button state but only cleared a sliver of it, so a button could appear stuck for a moment after a level loads.

• Fix undefined behaviour in the event-queue ring increment. (DOOM-0018) Fixes a hidden flaw where the input-event counter was updated in a way modern compilers are allowed to mishandle - it could silently drop or scramble keypresses on a new compiler.

Security

• Clamp atlas tile width so a crafted-WAD wide texture can't overrun the atlas. (DOOM-0072) A specially-crafted level file with an unusually wide texture could corrupt memory while building the 3D texture sheet; the width is now capped so it crops instead.

• Bound the -record demo-name to prevent a buffer overflow (DOOM-0070) A -record command-line name longer than 27 characters overflowed the fixed 32-byte demoname buffer (strcpy+strcat). G_RecordDemo now uses snprintf to bound and NUL-terminate the name.

DOOM_Ants 0.2.0-pre.2 — Windows build (preview)

A refreshed 64-bit Windows cross-build, rebuilt from the current master so it includes all the renderer work since the first Windows preview (v0.2.0-pre.1).

⚠️ Preview — untested on real Windows hardware

This .exe is cross-compiled on Linux. It compiles cleanly and boots, but it has not yet been run on an actual Windows machine — the 3D modes (Solid / Ultra, which use Vulkan), sound, music, and gamepad support are unverified on Windows. Please treat this as an early preview and report anything broken in Issues.

What's new since the last Windows preview

• 3D sky fixed — the black band across distant outdoor views is gone; the sky now meets the horizon like the original (DOOM-0076).
• 3D wireframe debug view — toggle with the gamepad Share button in Solid/Ultra (DOOM-0077).
• Moving floors/ceilings animate in 3D — doors and lifts now open/close in the 3D renderers (DOOM-0049).
• Live texture changes in 3D — switches light up and animated surfaces (screens, slime) animate (DOOM-0066).
• Controller mapping — Triangle toggles the automap (DOOM-0063), Circle closes a menu (DOOM-0056).
• Assorted 3D fixes: door-area gaps (DOOM-0052), classic hi-res menu/visplane fixes (DOOM-0053, DOOM-0055), dark-ceiling shading (DOOM-0069).

How to run

1. Download and unzip DOOM_Ants-0.2.0-pre.2-windows-x64.zip.
2. Put a DOOM .wad (the free shareware doom1.wad works) next to doom_ants.exe.
3. Run doom_ants.exe. See the included README.txt for details and controls.

No game data is bundled (licensing) — you supply the .wad.

GPL v2. Full source: https://github.com/milnet01/DOOM_Ants

The first Windows build of DOOM_Ants — plus a self-contained Linux build. 🪟🐧

A preview / development snapshot (pre-release): the classic renderer is complete and playable on both platforms; the Phase-2 3D renderer is still in progress. Published as a pre-release so it doesn't imply the in-progress features are finished.

Downloads — both are one-download-and-done (just add a WAD)

• Windows (x86-64): doom_ants-0.2.0-pre.1-windows-x86_64.zip Unzip, drop a .wad next to doom_ants.exe, run. All needed DLLs are bundled.
• Linux (x86-64): doom_ants-0.2.0-pre.1-x86_64.AppImage One file. chmod +x it (or right-click → Allow executing), then run: ./doom_ants-0.2.0-pre.1-x86_64.AppImage -iwad doom1.wad Every library is bundled (SDL2, SDL2_mixer, FluidSynth) and a compact General-MIDI soundfont is baked in, so music works out of the box — no apt/zypper/dnf install needed. Targets reasonably current distros (built on a recent glibc).

A DOOM .wad is required and not included (licensing). The free shareware doom1.wad works, as do retail doom.wad / doom2.wad.

What's new

• First-ever Windows build via a new mingw-w64 cross-build target (DOOM-0006).
• Self-contained Linux AppImage — no dependency install, music included.
• Both built from master @ 5859307.

Notes

• A console/terminal window accompanies the game and shows startup messages.
• 3D acceleration uses the system Vulkan loader (GPU driver / system package); the game runs fine without it on the classic renderer.
• The older v0.1.0 tarball remains for systems where you'd rather use your distro's own SDL2/FluidSynth packages.

The first playable build of DOOM_Ants — id Software's 1997 DOOM engine, modernised to build and run on today's 64-bit Linux through SDL2.

What's in it

• 🎵 Music is back — the in-WAD soundtrack plays as clean General MIDI (FluidSynth), with sound effects untouched.
• 💾 Saving fixed — save/load no longer corrupts memory or crashes.
• ⌨️ WASD movement alongside the arrow keys.
• 🖥️ Bigger, resizable, fullscreen-capable window (-fullscreen).
• 🎮 -iwad switch to pick DOOM 1 / DOOM 2 / Ultimate Doom from one folder.

Download & run (Linux x86-64)

Grab doom_ants-0.1.0-linux-x86_64.tar.gz below, then:

tar xzf doom_ants-0.1.0-linux-x86_64.tar.gz
cd doom_ants-0.1.0
./linuxxdoom -iwad /path/to/doom1.wad

You'll need a DOOM .wad (not included — the free shareware doom1.wad works) and a few runtime libraries. See the bundled README.txt for the one-line install command for your distro (SDL2, SDL2_mixer, FluidSynth, a GM soundfont).

A Windows build and a fully self-contained package are planned for later.

GPL v2, derived from id Software's DOOM source.