|SLADE||3||It's a Doom editor|
SLADE v3.1.8 Released
Fri, Nov 22 2019
Time for another minor bugfix release - 3.1.8 (at this rate we really will get to 3.1.10 before 3.2.0 is ready :P). The full list of changes is below:
v3.1.7 was Released
Wed, Oct 30 2019
A bit late due to issues with the website around the time it was released, but anyway, 3.1.7 is (was) released!
It's mostly to fix the text editor issues with 3.1.6 on Windows. The changes are below:
v3.1.6 now with More Bits (tm)
Thu, Aug 22 2019
SLADE v3.1.6 is now available for download, including a few changes to Windows builds - it should no longer require the MSVC runtimes to be installed separately, and there is now an 'experimental' 64bit build available.
The 64bit build currently doesn't support MIDI playback via fluidsynth (you'll have to set up and use timidity instead for now). Otherwise, the 64bit build should run a bit faster on modern hardware and allow opening much larger files than the 32bit version can.
Apart from that, this release is mostly a minor bugfix release, including a fix for the long-standing issue where playing most ogg files would cause a crash. See the full list of changes below:
UPDATE 5-Sep-2019: A macOS build of 3.1.6 is (finally) available over at the downloads page.
SLADE v3.1.5 and Linux Flatpak
Tue, May 07 2019
A new release of SLADE is up, with a bunch of fixes and minor improvements:
As per usual it can be downloaded from the downloads page.
Also, linux users may notice another link added to the downloads page - SLADE now has an official flatpak release for linux, which should make installing and keeping it up to date much simpler.
SLADE v3.1.4 Released
Wed, Dec 26 2018
Another minor bugfix-focused release, with the following changes:
Also, I'd like to remind anyone using SLADE and having issues - please report the issue. If I don't know about it it's very unlikely to be fixed unless I happen to come across it randomly or someone else reports it.
There are many options to do this, you can:
The best place to report it is on GitHub - it is much easier to keep track of it there and even if I don't get around to fixing it right away someone else may pick it up and fix it via a pull request.