1.15 Release Candidate 2
We discovered a couple of issues with 1.15 RC1, so here is a new release candidate: 1.15 RC2 (build 1606)
Changes in RC2:
Please report bugs in the Tracker. When reporting bugs, don't forget to mention "1.15 RC2" in the description. Depending on the urgency of discovered issues, we'll evaluate if they will get fixed in new RCs or later patch builds.
You can read more about Doomsday 1.15 (and RC1) in the previous news post.
Changes in RC2:
- Fixed a possible (rare) crash when exiting a map.
- Fixed a possible crash in the 64-bit version (OS X and Linux) when binding input controls in the game menu.
- Hexen: Death Wyvern no longer gets stuck in the central pillar of its cave.
- Hexen: Death Wyvern's fire now appears more glowing and less solid.
- Hexen: Added a subtle light source on an important secret door.
- No longer shut down the engine when an XG plane mover related error occurs.
- Windows: The obsolete wadmapconverter.dll is removed by the installer.
Please report bugs in the Tracker. When reporting bugs, don't forget to mention "1.15 RC2" in the description. Depending on the urgency of discovered issues, we'll evaluate if they will get fixed in new RCs or later patch builds.
You can read more about Doomsday 1.15 (and RC1) in the previous news post.
Comments
EDIT: This is what I get when launching Doomsday from the command-line:
I hope you know how much we appreciate the immense work that it must take to work on such a large project as the Doomsday Engine in one's spare time. Real life can be very challenging in eating up all of ones energy and time.
Thanks again!
http://pastebin.com/VKTuvJPx
In the mean time, disabling FluidSynth should be a sufficient workaround. (FMOD has basic music support for DLS sound fonts.)
Let me know if this one works better.
http://pastebin.com/zYF4tByS
Any change?
What is weird is that RC1 was working just fine. Are there any old settings files I need to purge to make sure there is nothing the new build is choking on?
On an unrelated note, is there a particular reason why you are providing Doomsday as a PKG rather than the usual "drag app into Applications" distribution method? Suspicious Package does not show any installation script.
EDIT: Checked the latest FluidSynth, but apparently they haven't yet replaced the use of the deprecated APIs in question. Oh well...
This is the last release with a .pkg installer. We're switching to CMake produced .dmg images with regular draggable applications on them.
The .pkg installer was used so that both Doomsday and the Doomsday Shell applications are installed together side by side, so the Shell can find the engine.
Fingers crossed that this took care of all the deprecated calls. Third time's the charm, right?