Crispy Doom 6.0 (Update: Mar 31, 2023)

[fabian]

Crispy Doom 5.11.1 is released on Feb 10, 2022. It it a bug-fix release to fix Heretic and Hexen config keys getting lost in setup.

 

Binaries for Windows (x86) are available here:
https://github.com/fabiangreffrath/crispy-doom/releases/download/crispy-doom-5.11.1/crispy-doom-5.11.1-win32.zip

https://github.com/fabiangreffrath/crispy-doom/releases/download/crispy-doom-5.11.1/crispy-heretic-5.11.1-win32.zip

https://github.com/fabiangreffrath/crispy-doom/releases/download/crispy-doom-5.11.1/crispy-hexen-5.11.1-win32.zip

[fabian]

20 hours ago, galileo31dos01 said:

I've also had a crash in the first map of this wad, few seconds in while looking around, the message was this and it seems to be consistent. 

 

The texture pack contains some flats and patches with the same names. Flats will be restricted to their respective range in the next release.

[VoanHead]

I read the changelog and saw that "some snow as a X-mas easter egg". Is there a way to see this via parameter or am I gonna have to manually change my computer's clock to see it? (Kinda like how there was a parameter to flip the levels in game)

yes, I'm an impatient fellow who can't wait 10 months to see how it looks like, I've already seen GOOBERS and -flip, I fully deserve charcoal in my stocking this year.

[Never_Again]

The new 'snow' feature is a cheat code: LETITSNOW (like the other cheats it's not case-sensitive). IMO, it's not really an Easter egg as commonly known in computing, though if one were so inclined he could argue the semantics here all day.

[PKr]

What was the issue with spectre and lost souls blood?

 

"All "blood fixes" have been removed from the "colored blood" feature. That is, spectres don't bleed spectre blood anymore and Lost Souls don't bleed puffs anymore, but bloodless objects still don't bleed or leave gibs when crushed."

 

That is unfortunate. :(

[rzh]

1 hour ago, PKr said:

What was the issue with spectre and lost souls blood?

 

"All "blood fixes" have been removed from the "colored blood" feature. That is, spectres don't bleed spectre blood anymore and Lost Souls don't bleed puffs anymore, but bloodless objects still don't bleed or leave gibs when crushed."

 

That is unfortunate. :(

Many people stated that it makes it harder to notice if you hit Spectres and Lost Souls at a glance.

[PKr]

3 hours ago, rzh said:

Many people stated that it makes it harder to notice if you hit Spectres and Lost Souls at a glance.

That is VERY unfortunate... :(((

 

Could you please point me to where that change was made, and I'll recompile 5.11.1 with reversed blood changes? I will probably never find the code on my own. 🙏

Edited February 11, 2022 by PKr

[xvertigox]

@fabian Apologizes if this is an oft repeated issue but Windows Defender flags midiproc as a virus in 5.11.1

 

 

Spoiler

 

Edited February 11, 2022 by xvertigox

[Rotwang]

33 minutes ago, PKr said:

Could you please point me to where that change was made, and I'll recompile 5.11.1 with reversed blood changes? I will probably never find the code on my own. 🙏

It looks like it was changed back with this commit.

[PKr]

17 hours ago, Rotwang said:

It looks like it was changed back with this commit.

Thank you, it's absolutely working now!

Edited February 12, 2022 by PKr

[Tycitron]

Yeah definitely not a fan of the change to the Lost Soul and Spectre blood back to being red at all. i liked it being accurate because it was always a small thing that bothered me in the OG games (the blood or lack thereof being red no matter what enemy it is) that was fixed with that option. its a small thing but a huge shame IMO

[Never_Again]

Well, that's the beauty of open source: you don't like something in the master branch? FucFork it!

Here are the instructions for building Crispy on Windows. They are somewhat out of date and not complete, so add the following steps to the five already listed:

 

6. Install MinGW Cmake (from the MSYS2 terminal)

pacman -S mingw-w64-i686-cmake

7. Install the TortoiseSVN client (from Windows, not the MSYS2 terminal) to manage your local copy of the Crispy repo. Once it's installed you'll be able to do such management from Windows Explorer.

8. Check out a copy of the Crispy repo to a new dir/folder in your MSYS2 installation, the new folder should be under /msys64/home/<your_username>, e.g.

   c:\msys64\home\johnsmith\crispy-blood

Right-click on that new folder and pick SVN checkout...

The URL to check out is https://github.com/fabiangreffrath/crispy-doom.git/trunk.

9. Right-click on the new Crispy folder again and pick SVN Show log. A list of commits will be displayed, with the latest at the top. Scroll down until you find the commit you want to revert (it's dated 2021-08-30). Right-click on it and pick Revert changes from this commit.

10. In the MSYS2 terminal go to the new Crispy folder, e.g.

cd /crispy-blood

11. Run Cmake with the following parameters:

cmake -S . -B ./build -Wno-dev -G"MSYS Makefiles" -DCMAKE_BUILD_TYPE=Release

12. Change to the build dir and build with make:

cd build
make

To speed up the process you can change the make command to make -j x to build using x threads instead of the default one.

13. The newly built execs will be in crispy-blood/build/src. You may want to run strip on them to make them smaller

strip src/*.exe

 

From then on whenever you want to catch up with the official Crispy repo right-click on your crispy-blood folder and pick SVN Update. Then repeat steps 12 and 13.

 

[Never_Again]

On 2/11/2022 at 6:10 PM, xvertigox said:

Apologies if this is an oft repeated issue but Windows Defender flags midiproc as a virus in 5.11.1

 

1. It's a false positive.

2. Crispy does not use midiproc since Oct 2021.

[fabian]

8 hours ago, Tycitron said:

Yeah definitely not a fan of the change to the Lost Soul and Spectre blood back to being red at all. i liked it being accurate because it was always a small thing that bothered me in the OG games (the blood or lack thereof being red no matter what enemy it is) that was fixed with that option. its a small thing but a huge shame IMO

 

I know it's a controversial change and I'm sorry for those who miss the feature. But I have been asked several times in the past to remove it again - or at least make it optional. And my general stance is that if a feature is too minor to deserve its own switch in the menu (and there are more than enough already) then the right thing to do is to preserve Vanilla behavior. 

[PKr]

2 hours ago, fabian said:

 

I know it's a controversial change and I'm sorry for those who miss the feature. But I have been asked several times in the past to remove it again - or at least make it optional. And my general stance is that if a feature is too minor to deserve its own switch in the menu (and there are more than enough already) then the right thing to do is to preserve Vanilla behavior. 

What's your take on a switch that is not present in the menu, but is a variable that exists only in .cfg files? I guess it wouldn't bother anyone nor clutter menus, etc.

Edited February 13, 2022 by PKr

[Tycitron]

7 hours ago, PKr said:

What's your take on a switch that is not present in the menu, but is a variable that exists only in .cfg files? I guess it wouldn't bother anyone nor clutter menus, etc.

This would be nice it probably wont happen but i would love this.

[rzh]

This happens sometimes when the player gets gibbed. Is it normal behaviour?

Tested in Doom 2, with no additional wads loaded and confirmed it happens there as well.

[xX_Lol6_Xx]

On 2/13/2022 at 3:41 AM, fabian said:

 

I know it's a controversial change and I'm sorry for those who miss the feature. But I have been asked several times in the past to remove it again - or at least make it optional. And my general stance is that if a feature is too minor to deserve its own switch in the menu (and there are more than enough already) then the right thing to do is to preserve Vanilla behavior. 

If you ask me, I would have made it like the crosshair switch, with the option of "None", "On" and "On+Fuzzy". Or something like that.

[fabian]

1 hour ago, rzh said:

This happens sometimes when the player gets gibbed. Is it normal behaviour?

Tested in Doom 2, with no additional wads loaded and confirmed it happens there as well.

 

That's the current player sprite in the health widget's place. It shows whether you are gibbed or crushed - or just dead. :D

[fabian]

1 hour ago, Lol 6 said:

If you ask me, I would have made it like the crosshair switch, with the option of "None", "On" and "On+Fuzzy". Or something like that.

 

No, sorry, I am fed up with options. I need facts. ;)

[rzh]

5 hours ago, fabian said:

 

That's the current player sprite in the health widget's place. It shows whether you are gibbed or crushed - or just dead. :D

I figured as much and I'd rather not clutter the Github issues tracker so I used this forum instead :P

Thank you!

[liPillON]

hi fabian, I'm looking for a clarification about fluidsynth support in crispy on windows

 

I have virtualmidisynth installed and I'm noticing that its midi mixer applet shows up whenever I play crispy

this indicates that the program is playing midis through the windows midi soundsystem

 

I was under the impression that fluidsynth support was embedded into the engine and it would work like in gzdoom (where virtualmidisynth does not come into play) 

am I wrong? what should I do to ensure that no external midi drivers are used?

 

my crispy cfg has both the timidity e fluidsynth variables set

should I remove the timidity one?

is there some other variable that act as a switch between the different music outputs?

 

thank you!

 

 

[NightFright]

Are there new truecolor builds for latest v5.11.1?

Edited March 14, 2022 by NightFright

[T.Will]

1 hour ago, NightFright said:

Are there new truecolor builds for latest v5.11.1?

Thank you for reminding me.

 

32bit/64bit Truecolor builds from commit 400de1870954c762172901 294fd9b218db480de5

crispy-doom-5.11.1_Truecolor-win64.zip

crispy-doom-5.11.1_Truecolor-win32.zip

[rzh]

Speaking of truecolor, is it also an option for Heretic/ Hexen?

[NightFright]

If nothing changed about what was written on Github back in 2015, any non-Doom game is broken in truecolor. Do custom palettes in Doom mods still cause issues as indicated in that old feature request?

 

Otherwise: Would be great if this found its way into the official release at some point. Even better would be an ingame option to switch between 8-bit and 32-bit rendering like in DelphiDoom, but I dunno if it's technically possible here.

 

UPDATE:
There is one bug I noticed in the truecolor builds. Cutscenes (like the one at the end of ep.3) seem to be broken - they all have a blue tint. Maybe it's worth looking into that? So far it's been the only issue I have encountered.

Edited March 15, 2022 by NightFright

[NightFright]

@T.Will

Care to do another truecolor compilation of latest dev snapshot (commit ca4e704e1ee8e9114e8f73aa73ef9d5ebfadb079 or newer)? Looks like there's a fix for the blue tint in the ep.3 scroller and I'd like to see if it works.

Edited March 16, 2022 by NightFright

[Noiser]

On 2/11/2022 at 2:13 PM, PKr said:

"All "blood fixes" have been removed from the "colored blood" feature. That is, spectres don't bleed spectre blood anymore and Lost Souls don't bleed puffs anymore, but bloodless objects still don't bleed or leave gibs when crushed."

On 2/12/2022 at 10:01 PM, Tycitron said:

Yeah definitely not a fan of the change to the Lost Soul and Spectre blood back to being red at all. i liked it being accurate because it was always a small thing that bothered me in the OG games 

A bit late to the party, but you can actually use a Dehacked patch to remove the blood from Lost Souls and Spectres. Just enable the NOBLOOD flag on them (aka "Puffs vs. bleeds" on WhackEd4) and that's it. No blood whatsoever.

Edited March 16, 2022 by Noiser

[NightFright]

Drop a file named "bloodfix.deh" (or anything else you prefer) with following code into the doom-all subdir of your Crispy Doom autoload if you want non-bleeding Spectres and Lost Souls:

Patch File for DeHackEd v3.0
# Created with WhackEd4 1.2.4 BETA
# Note: Use the pound sign ('#') to start comment lines.

Doom version = 21
Patch format = 6


Thing 14 (Spectre)
Bits = 4980742

Thing 19 (Lost Soul)
Bits = 541190

In the meantime, I have confirmed that only the ep.3 sidescroller has the blue tint bug in truecolor, so the next build should fix it (hoping for T.Will).

Edited March 16, 2022 by NightFright

[forgettable pyromaniac]

Alrighty-o, so-

I've been messing with my settings to get everything just right, and I almost have, with one exception: the menu button. I set it to Tilda instead since I was just messing with options to see what felt right, but now I can't set it back to esc since pressing esc when it says "hit a key" actually stops the hit a key prompt, so I dunno what to do in this situation.

 

does anyone know how I'd fix it without just resetting my config (cuz I wanna try and keep everything the way it is now while only changing that...)