DOOM Universe logo
    • Register
    • Login
    • Search
    • Recent
    • Popular
    • Users
    • Groups

    Sprinkled Doom and RZDoom + Tools

    Source Ports and Tools
    3
    10
    96
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      Gibbon last edited by Gibbon

      So, to avoid having such a giant list, I've opted to have updates for my 2 main ports, Sprinkled Doom and RZDoom plus some useful tools. A ton of other stuff remains on my github as usual. Releases are on the github links in the Release tab.

      Ports!

      • Sprinkled Doom - Latest release is 3.4.1

      Sprinkled Doom is a fork of Chocolate Doom with widescreen capability (plus Unity statbar) with full Choco / Vanilla compatibility but without any of the fixes or additions that Crispy Doom has. It is a middle-ground between Choco and Crispy. It was kept in-sync with Choco but I have since broken that as they were doing changes and fixes I had already made, and things got very messy.

      • RZDoom - Latest release is 3.2.0

      RZDoom is a fork of ZDoom 2.8.1 which retains full compatibility for it. But with updated libraries, optimisations, performance improvements and FMOD Studio implementation.

      Tools!

      • idManager

      This is a TurboC update of the old DeathManager tool shipped with Doom/Doom2/Heretic etc.. I received the source and added features to it for a better experience for those who use DOS for vanilla play.

      The changes:

      1. DeHackEd and DeuSF support (for Doom)
      2. HeHacked and DeuSF support (for Heretic)
      3. SeHacked and DeuSF support (for Strife)
      4. Ability to use many different executables
      5. Upgrading the GUI's and fixing some bugs in the code
      6. Making separate versions for Heretic and Strife.
      7. Ability to record a demo

      The binaries:
      IDMANAGER.zip

      I also reactivated the Funky Blue colour via Assembler:
      IDMANAGER_FUNKY_BLUE.zip

      I have uploaded them here as the source code is still closed and I am unable to release it due to Romero himself asking for it to be so. Apparently, Bethesda wasn't happy with all the code releases he did in the past.

      1 Reply Last reply Reply Quote 4
      • G
        Gibbon last edited by

        RZDoom has had a major update and now is at version 3.1.0.

        Release (binaries for Linux and Windows): https://github.com/atsb/rzdoom/releases/tag/3.1.0

        Change log:

        1. Optimising Windows Inputs
        2. UMAPINFO rev1.4 support (with a deviation on intermusic functionality)
        3. Removal of all JPEG support
        4. Replacing BYTE with uint8_t modern equivalent for intermission code (ongoing for other areas)
        5. FIXED: Barrel explosion timing
        6. FIXED: Hexen stair crushers
        7. ADDED: Pistol Start ability
        8. FIXED: VSync support
        9. Fully supports Brutal Doom Community Expansion project
        1 Reply Last reply Reply Quote 3
        • Dusk-Iv
          Dusk-Iv last edited by

          I've been loving rzdoom but it seems to output console messages after quitting the game and on longer play sessions it takes a strangely long time, is this a bug?
          Otherwhise I haven't had issues with it, still the smoothest zdoom port I've played on.

          G 1 Reply Last reply Reply Quote 1
          • G
            Gibbon @Dusk-Iv last edited by

            @Dusk-Iv said in Sprinkled Doom and RZDoom + Tools:

            I've been loving rzdoom but it seems to output console messages after quitting the game and on longer play sessions it takes a strangely long time, is this a bug?
            Otherwhise I haven't had issues with it, still the smoothest zdoom port I've played on.

            Not a bug, but how would you like it to work? I could do something if it is annoying?

            Glad you like it 🙂

            1 Reply Last reply Reply Quote 0
            • Dusk-Iv
              Dusk-Iv last edited by

              When ENDOOM screens are on it seems like the console also waits for the ENDOOM to quit, but when quitting it the program freezes on it for a while before actually exiting too, so maybe it should skip the console output when ENDOOM is on.

              G 1 Reply Last reply Reply Quote 0
              • G
                Gibbon @Dusk-Iv last edited by

                @Dusk-Iv said in Sprinkled Doom and RZDoom + Tools:

                When ENDOOM screens are on it seems like the console also waits for the ENDOOM to quit, but when quitting it the program freezes on it for a while before actually exiting too, so maybe it should skip the console output when ENDOOM is on.

                Windows? Because on Windows it has a little 'click anywhere to quit' and that works fine. I tried it on Red Hat too and it was ok.

                Dusk-Iv 1 Reply Last reply Reply Quote 0
                • Dusk-Iv
                  Dusk-Iv @Gibbon last edited by

                  @Gibbon yeah it's happening on windows and also persisted through the update, maybe if I wipe it first it may get fixed. Will try later.

                  1 Reply Last reply Reply Quote 1
                  • dasho
                    dasho last edited by

                    I grabbed a clean MSVC release and didn't seem to encounter the same issue.

                    1 Reply Last reply Reply Quote 1
                    • G
                      Gibbon last edited by

                      I’ll give the endoom and console code a glance, maybe I can optimise things there a bit and make it snappier

                      1 Reply Last reply Reply Quote 1
                      • G
                        Gibbon last edited by

                        A new release of RZDoom (3.2.0)

                        This is a rather small update.

                        • Reverted to FMODEX for audio from FMOD Studio due to Studio's lack of support of various audio backends and channels that were causing issues.
                        1 Reply Last reply Reply Quote 1
                        • 1 / 1
                        • First post
                          Last post