fabian

Members
  • Content count

    876
  • Joined

  • Last visited

4 Followers

About fabian

  • Rank
    Forum Regular
  1. Reportedly, this issue will be fixed in the SDL 2.0.7 release.
  2. Here's a new one: crispy-heretic_4.3.zip
  3. Update September 19, 2017: Crispy Doom 4.3 is released! Crispy Doom is a friendly fork of Chocolate Doom that provides a higher display resolution, removes the static limits of the Doom engine and offers further optional visual, tactical and physical enhancements while remaining entirely config file, savegame, netplay and demo compatibile with the original. Crispy Doom 4.3 has been released on September 19, 2017. It is based on Chocolate Doom 2.3.0. This quick fix release introduces improvements requested by ZeroMaster010 and is supposed to be the last release based on SDL1. Please visit the Crispy Doom homepage for more information: https://www.chocolate-doom.org/wiki/index.php/Crispy_Doom#History_of_changes The Crispy Doom source code is available at GitHub: https://github.com/fabiangreffrath/crispy-doom Binaries for Windows (x86) are available here: http://www.greffrath.com/~fabian/crispy-doom_4.3.zip http://www.greffrath.com/~fabian/crispy-doom-music-pack_2.zip Have a lot of fun! - Fabian
  4. Update September 15, 2017: Crispy Doom 4.2 is released! Crispy Doom is a friendly fork of Chocolate Doom that provides a higher display resolution, removes the static limits of the Doom engine and offers further optional visual, tactical and physical enhancements while remaining entirely config file, savegame, netplay and demo compatibile with the original. Crispy Doom 4.2 has been released on September 15, 2017. It is based on Chocolate Doom 2.3.0. The changes since 4.1 are mostly polish of previously introduced features. This is supposed to be the last released based on SDL1. Please visit the Crispy Doom homepage for more information: https://www.chocolate-doom.org/wiki/index.php/Crispy_Doom#History_of_changes The Crispy Doom source code is available at GitHub: https://github.com/fabiangreffrath/crispy-doom Binaries for Windows (x86) are available here: http://www.greffrath.com/~fabian/crispy-doom_4.2.zip http://www.greffrath.com/~fabian/crispy-doom-music-pack_2.zip Have a lot of fun! - Fabian
  5. I see. I wondered about your post especially in the light of our recent email conversation, but know I understand what you meant. ;)
  6. Erm, sorry?
  7. What happens is that Crispy realizes that the PWAD that was loaded when you saved the game has a different filename than the one that is loaded now that you want to restore that savegame, so it asks for confirmation first. However, if you confirm this message, everything should work as expected and you could even re-save the game to update the filename check to the new spelling.
  8. This has to do with the game being restored at a different gametic than it was saved (the relevant part is gametic & 3): https://tracker.dengine.net/issues/1868#note-12
  9. This is exactly how I implemented it in Crispy. o_O
  10. Erm, yes, I meant "if you are already in a compiled Crispy Doom source tree". ;) Also, for builds targetting Windows, you might have to call make crispy-heretic.exe Note the ".exe"!
  11. Today's snapshot of Crispy Heretic (completely unsupported!): crispy-heretic_gitb38b48c6.zip
  12. They are, but it is (still) easy to re-enable them again. I am just looking for someone to step up as a reliable maintainer.
  13. Hey guys, I am just here to tell you that Crispy Heretic (and Hexen and Strife) is still there and regularly synced with the (admittedly, sparse) commits to the Choco code base. It is just that Crispy Heretic/Hexen/Strife are not built and released anymore, because I haven't done any changes to them since the initial release (though, I have turned Heretic limit-removing at one point). I have recently pushed a commit to GIT that makes it easier to build the three non-Doom games. In the Crispy source directory do cd src make -C heretic make crispy-heretic and you are done!
  14. Using *leveltime* will cause multi-level demos to desync across map boundaries. This is how I have fixed this in Crispy: https://github.com/fabiangreffrath/crispy-doom/commit/b9ccc9d9696648ee6b02983b385ab4e557fd5e11
  15. Crispy counts respawned monsters in their own variable that's separated by a '+' sign from the "regular" kills in the map statistics in the Automap.