Doomsday version 1.9.10
|Release date:||December 21, 2012|
In version 1.9.10 we are taking concrete steps forward in pursuit of several long-term objectives. A guiding principle has been to bring a new level of clarity into the internal structure of the engine while also preparing the next-generation incarnations of key subsystems: file system, resource management, and scripting. This means, though, that the number of visible changes is still significantly smaller than the number of internal changes. We hope that this is soon changing as the pieces are now falling into place for us to start addressing UI and graphics related issues.
The work we've done in this release illustrates our strategy for realizing Doomsday 2: instead of attempting to rewrite everything at once — and getting hopelessly bogged down with the massive workload — we are upgrading subsystems gradually, during many small iterations.
End of jDoom/jHeretic/jHexen. We've made a fundamental change regarding game plugins. We are now using the main Doomsday version number (1.9.10) for all of the "official" game plugins (libdoom, libheretic, libhexen). This effectively marks the end of jDoom and the other j-ports — they have been finally fully demoted from individual ports to mere plugins for Doomsday. However, we will continue supporting the j-prefixed names inside resource packages for backwards compatibility.
- The longstanding gameplay bug that prevented a column from lowering on Doom E1M7 has now been fixed. 
- On Linux, the FluidSynth audio plugin no longer requires FMOD to play music; it can send music directly to the audio output.
- Command-line tools for creating and editing data files (md2tool, wadtool, texc) are now included as part of the distribution packages. (Note: wadtool is only available for Windows in this release.)
- Bug fixes and stability improvements.
Progress on roadmap
If you are upgrading an existing installation of Doomsday, note the following:
- Your automatic update preferences, main window position, and display mode will be reset to the default settings. This information is no longer stored in the system registry (on Windows) or other system-provided configuration files. Instead, it is saved in persist.pack in your runtime folder.
- The default display mode is now your desktop resolution. (Previously it has been 640 x 480.)