Tag: stable

Doomsday 2.3.1 released

Doomsday 2.3.1 has been released (build 3685). This is a patch that fixes the following issues:

  • Incorrect placement of sky textures in Heretic and Hexen.
  • Alignment of floor/ceiling textures whose size is not 64×64.
  • macOS: Missing and flickering textures on M1 Macs.
  • macOS: Bullets firing in the wrong direction on M1 Macs.
  • macOS: 3D camera mode does not allow flying downwards, only upwards on M1 Macs.

Release notes (→ Manual)

The new release is available to download from:

Doomsday 2.2.1 released

Doomsday 2.2.1 has been released (build 3299). This is a patch that fixes the following issues:

  • In Hexen, some of the player character colors were not loaded and thus some player colors were not available.
  • On macOS, package information text was sometimes displayed incorrectly in the UI.
  • On Linux, music was always at full volume if FluidSynth was being used for playing back music directly to system audio.
  • In the game library, a custom profile would forget its “No monsters” setting after restarting Doomsday.
  • 3D weapon models would sometimes get near-clipped, so the near clip distance was reduced when rendering them.

Release notes (in the Manual)

The new release is available to download from:

Doomsday 2.2 released

Doomsday 2.2 has been released (build 3272). The highlights of this version are:

  • Improved Doomsday Script integration
  • Heretic modding enhancements
  • Separate FOV for rendering player weapons
  • Flatpak for Linux
  • Renderer bug fixes

Download 2.2

Release notes

Another milestone

Exactly 20 years ago — December 18th, 1999 — I first announced that work had started on a project called “Doomsday Engine”:
Continue reading Doomsday 2.2 released

Focus adjustments

I took a good look at the project roadmap in the Tracker and decided it was time to do some spring cleaning.

I’ve now updated the plan for the 2.x releases so that each version has a specific focus. For instance, the 2.0 release will focus on the Home UI and basic package management, and the 2.1 release will focus on multiplayer improvements.

While the roadmap is just a plan and plans may always change, defining a clear focus area for each version will help in pushing things forward. Not doing this would mean that each release has the risk of ballooning feature creep and features would likely not be fully baked.

Another topical issue to note is that due to the autobuilder upgrade, the stable 1.15 builds have been suspended until the stable build environment is updated to work with the new builder setup. However, I’m placing my focus on finishing features for the 2.0 stable release, so I don’t expect many fixes for 1.15 in the near future.