Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content count

  • Joined

  • Last visited

About fabian

  • Rank
    Senior Member

Recent Profile Visitors

3116 profile views
  1. fabian

    Doom Unity(rerelease) VS GZDoom

    Ah, ok, thanks! So the vertical misplacement of the Cacos is due to the rockets' explosion thrust. At first I believed they would "intelligently" change their vertical position to get out of the rocket launcher's line of aim.
  2. fabian

    Doom Unity(rerelease) VS GZDoom

    I couldn't find anything related in the changelog. Could anyone please point me to the commit that fixed this?
  3. The tall texture bug will be fixed in the next release.
  4. fabian

    Crispy Doom 5.9.2 (Update: Sep 22, 2020)

    No dumb questions. Sorry if my reaction appeared a bit harsh, it wasn't meant to be.
  5. fabian

    Crispy Doom 5.9.2 (Update: Sep 22, 2020)

    He, if course not. Doom 2 will behave as Vanilla Doom 2 even if nerve.wad got auto-loaded and NRFTL will behave as expected whether started from the New Game menu or loaded as a PWAD.
  6. fabian

    Crispy Doom 5.9.2 (Update: Sep 22, 2020)

    Mostly level transitions and placement of intermission screens.
  7. fabian

    Why is Eternity not so popular?

    |: Why isn't Eternity as feature-rich as GZDoom? Because it is focused on compatibility. Why isn't Eternity as compatible as PrBoom+? Because it is focused on features. :|
  8. SO, did you also provide a SWITCHES lump which adds the SW1GOTH and SW2GOTH pair and assigns it to "episode 3" (i.e. Doom 2)?
  9. fabian

    Crispy Doom 5.9.2 (Update: Sep 22, 2020)

    Bummer! Apparently this has been introduced by this commit from nearly 4 years ago (!) which changed non-bleeding monsters to not leave a blood pool behind after being crushed. And with the coloredblood feature enabled, Lost Souls are not bleeding anymore. https://github.com/fabiangreffrath/crispy-doom/commit/6bccb76114d5d2917c0931609d4c28bf366526d6#diff-a69b6dbe48f9c404ad2c5eab38e74645b2c16da9bc7d9eed20e000d7800ae0bd Edit: Fixed and replaced by a more careful approach. Thanks for the report!
  10. Nope. Not sure about Doom Retro, but neither Crispy nor Woof! do currently support UMAPINFO.
  11. This is the "texture not power of 2 wide" problem. I think I am on it, at least I found a working solution for Crispy which I will have to port over. What I don't understand, though, are these little slime trails in the top right corner, I don't have them in Crispy, for example. This is all the same spot when walking from the bridge to the grass, right? I guess this is because the floorlevel for the sector at the gap is at -20480, which makes the engine go nuts.
  12. In general, there is no reason against it. Though I remember integration of MUSINFO as rather non-trivial from its impementation in Crispy, including extending savegame formats, etc. Thank you for this! Unfortunately, there is no way I can fix this in Woof! without breaking strict MBF compatibility, because the highest "complevel" I have in Woof! happens to be MBF. ;-)
  13. fabian

    What is the most loved doom demon

    Why is this in the Source Ports forum?
  14. Even PrBoom+ has this with the software renderer.
  15. Which map is this? Could you post a screenshot of the automap at that place?