Crispy Doom 6.0 (Update: Mar 31, 2023)

[liPillON]

vms might have its own volume levels set too high, check the mixer applet

 

it could also be the soundfont you're using: some sf creators don't balance them properly (or they do according to their taste)

 

Edited April 3, 2022 by Delfino Furioso

[Trar]

I'm using a Roland SC-55 soundfont, and I can lower the volume to a reasonable level in the mixer - the problem is then it's too low for every other sourceport that balances the sound properly on their end (and every other program that uses MIDI).

 

EDIT: I found a newer SC-55 soundfont that has proper balance. Turns out it was my old-ass soundfont version that was the problem, go figure.

Edited April 3, 2022 by Trar

[Tycitron]

On 3/16/2022 at 3:13 AM, NightFright said:

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

 

Ah very late response but this works very nicely! although is there a way for the Spectres to have "invisible" blood over the bullet puffs? if thats even possible.

[NightFright]

Not with dehacked, I'm afraid. There is no thing tag for that purpose. Bullet puffs for blood is as good as it's gonna get without the port itself going beyond that.

[Tycitron]

Ah shame, well still i appreciate it!

[PKr]

6 hours ago, Tycitron said:

Ah very late response but this works very nicely! although is there a way for the Spectres to have "invisible" blood over the bullet puffs? if thats even possible.

 

On 2/12/2022 at 1:19 AM, Rotwang said:

It looks like it was changed back with this commit.

Just reverse the changes made here. That's what I personally do.

[Tycitron]

8 hours ago, PKr said:

 

Just reverse the changes made here. That's what I personally do.

I would... if i knew how to.

[PKr]

1 hour ago, Tycitron said:

I would... if i knew how to.

What OS do you use?

[Tycitron]

3 minutes ago, PKr said:

What OS do you use?

I use Windows 10.

[Never_Again]

2 hours ago, Tycitron said:

I would... if i knew how to.

 

The how-to was posted two months ago in the same thread.

[Tycitron]

27 minutes ago, Never_Again said:

 

The how-to was posted two months ago in the same thread.

Ah crap i completely forgot that was posted. my bad.

[PKr]

1 hour ago, Tycitron said:

I use Windows 10.

1. Go to https://github.com/fabiangreffrath/crispy-doom press on green "Code" button, download ZIP with Crispy-Doom source code.

2. Go to https://visualstudio.microsoft.com/free-developer-offers/ and download Visual Studio Community.

3. Go to https://github.com/Microsoft/vcpkg and get the latest version of vcpkg (direct link to current version: https://github.com/microsoft/vcpkg/archive/refs/tags/2022.04.12.zip)

4. Go to https://cmake.org/ and download the latest version of cmake (direct link to the latest version: https://github.com/Kitware/CMake/releases/download/v3.23.1/cmake-3.23.1-windows-x86_64.msi).

5. Launch VisualStudioSetup.exe (you have downloaded it in step 2), press continue.

6. Select (tick) "Desktop development with C++". In the right list of components, for minimal install select "MSVC v143 - VS 2022 C++ x64/x86 build tools", "Windows 10 SDK (10.0.19041.0)". Untick everything else (unless you need other stuff of course). Press "Install while downloading" or "Download all, then install".

7. Create a folder called "vcpkg" on C: drive (or wherever you want really...), and extract vcpkg you have downloaded in step 3 there.

8. Go to C:\vcpkg\ and double click "bootstrap-vcpkg.bat". This will download "vcpkg.exe" to the same folder.

9. Install cmake you have downloaded in step 4. Add cmake to "path" once prompted.

10. Restart your pc.

 

11. Go to Start (or press Windows key on your keyboard) > type "cmd" > hit enter. This will open a command line.

12. In command line navigate to vcpkg folder: "cd ..\..\vcpkg".

13. In command line type: "vcpkg integrate install".

14. In command line type: "vcpkg install sdl2:x64-windows sdl2-net:x64-windows sdl2-image:x64-windows sdl2-mixer[dynamic-load,libvorbis,libflac,mpg123,libmodplug,opusfile]:x64-windows libsamplerate:x64-windows". Hit enter, wait. It will take some time...

 

15. Extract crispy-doom source code to some folder, for example to "C:\source\crispy-doom-master".

16. Go to C:\source\crispy-doom-master\cmake\ and open FindSDL2.cmake with notepad (right click > open with > notepad).

17. Press ctrl+f and find the line HINTS "${SDL2_DIR}/include" change it to HINTS "${SDL2_DIR}/include/SDL2"

18. Find the line HINTS "${SDL2_DIR}/lib/x64" change it to HINTS "${SDL2_DIR}/lib"

19. Under the first HINTS "${SDL2_DIR}/lib/x64" there is another one for "SDL2main". Change that second HINTS "${SDL2_DIR}/lib/x64" line to HINTS "${SDL2_DIR}/lib/manual-link"

 

20. Open FindSDL2_net.cmake with notepad, change HINTS "${SDL2_NET_DIR}/include" to HINTS "${SDL2_NET_DIR}/include/SDL2" and HINTS "${SDL2_NET_DIR}/lib/x64" to HINTS "${SDL2_NET_DIR}/lib"

 

21. Open FindSDL2_mixer.cmake with notepad, change HINTS "${SDL2_MIXER_DIR}/include" to HINTS "${SDL2_MIXER_DIR}/include/SDL2" and HINTS "${SDL2_MIXER_DIR}/lib/x64" to HINTS "${SDL2_MIXER_DIR}/lib"

 

22. Open Findsamplerate.cmake with notepad, add to the beginning of the file two lines:

set(PC_SAMPLERATE_LIBRARY_DIRS "C:/vcpkg/installed/x64-windows/lib/samplerate.lib")

set(PC_SAMPLERATE_INCLUDE_DIRS "C:/vcpkg/installed/x64-windows/include/samplerate.h")

 

23. Go to C:\source\crispy-doom-master\ and create a new folder called "build".

24. Open cmd and navigate to the build folder: cd C:\source\crispy-doom-master\build

25. In command line type: cmake .. -G "Visual Studio 17 2022" -A x64 -Thost=x64 -DCMAKE_TOOLCHAIN_FILE="C:\vcpkg\scripts\buildsystems\vcpkg.cmake" -DVCPKG_TARGET_TRIPLET=x64-windows

 

24. Go to C:\source\crispy-doom-master\build and open Crispy Doom.sln with Visual Studio.

25. Now you can compile crispy-doom: change debug mode to release, press build > build solution.

26. You will find binaries in C:\source\crispy-doom-master\build\src\Release (if you have followed these instructions to the letter)

 

27. Now reverse these changes: https://github.com/fabiangreffrath/crispy-doom/commit/99ca74732d617e98893bb6d9294330889e57efef

For example, you can see that

if (crispy->coloredblood)

newmobj->flags |= MF_NOBLOOD;

 

was removed from src/doom/p_enemy.c

 

Put your cursor where the "3." is on my screenshot, and find "p_enemy.c". Open it, find newmobj->target = actor->target; line and add

if (crispy->coloredblood)

newmobj->flags |= MF_NOBLOOD; above that line.

 

You get the idea. :>

 

P.S. There are other methods, but that's how I do it. On a side note you can right click on "crispy-doom" in solution explorer (seen in the screenshot) > properties > C/C++ > Optimizations and play with these settings. You can get up to 3-5% increase in the performance with these settings.

 

P.P.S. Oh, and also, after compiling crispy-doom, you will need to manually copy a few .dll files to "build" folder. These are located in C:\vcpkg\installed\x64-windows\bin You will need: FLAC.dll libpng16.dll modplug.dll mpg123.dll ogg.dll opus.dll samplerate.dll SDL2.dll SDL2_mixer.dll SDL2_net.dll vorbis.dll vorbisfile.dll zlib1.dll

Edited May 1, 2022 by PKr

[T.Will]

Here's the latest Truecolor build of Crispy Doom. Based on commit 9bc5a8b6b26365b8373c367cb8dca69a40384b11

 

crispy-doom-5.11.1-win64_TRUECOLOR.zip

crispy-doom-5.11.1-win32_TRUECOLOR.zip

Edited May 12, 2022 by T.Will

[TOFM]

I cannot save setup of crispy doom/heretic/hexen(older version like 5.9.1 have no this problem).It seems that cfg file is not generated.How to fix it?

Edited May 14, 2022 by TOFM

[mikeday]

1 hour ago, TOFM said:

I cannot save setup of crispy doom/heretic/hexen(older version like 5.9.1 have no this problem).It seems that cfg file is not generated.How to fix it?

I'm assuming you're on Windows. My first guess is that crispy is trying to save the cfg file in location that's write-protected and therefore the file never gets created. Is your crispy-doom folder located in "Program Files (x86)" perhaps?

[xX_Lol6_Xx]

1 hour ago, TOFM said:

I cannot save setup of crispy doom/heretic/hexen(older version like 5.9.1 have no this problem).It seems that cfg file is not generated.How to fix it?

Try turning off your antivirus if you're using Windows.

[TOFM]

27 minutes ago, Lol 6 said:

Try turning off your antivirus if you're using Windows.

I have no antivirus.Even windows defender was turn off long ago

[TOFM]

37 minutes ago, mikeday said:

I'm assuming you're on Windows. My first guess is that crispy is trying to save the cfg file in location that's write-protected and therefore the file never gets created. Is your crispy-doom folder located in "Program Files (x86)" perhaps?

No,i put those in D disc

Solved......file path must all english.Thx

Edited May 14, 2022 by TOFM

[mikeday]

7 minutes ago, TOFM said:

No,i put those in D disc

If you right click on the crispy-doom folder and go to Properties, is "Read-only" checked?

[MauryMyers]

Does Crispy specifically detect the complevel through the IWAD? Or does it have to be entered manually?

[fabian]

Complevel is always Vanilla. It does differentiate between 1.9, Ultimate and Final by IWAD, and you can additionally set this on the command line. 

[NightFright]

^ That. You can't run Boom or any MBF pwads with this port, anyway. You have Woof for that, for example. ;)

[Frost-Core]

I'am getting creepy vibes with my old thy flesh consumed save, first i start with a rocket launcher, or so i thought, after shooting it turns into a shotgun? and i also see the pistol sprite here, im using an old git build of crispy doom :

 

[maxmanium]

Is there any way to requantize the background in the Crispness menu for a new color palette? In other words, is it available somewhere as a lump?

[Alaux]

14 minutes ago, maxmanium said:

Is there any way to requantize the background in the Crispness menu for a new color palette? In other words, is it available somewhere as a lump?

The graphic is baked into the binary. It's a flat called CRISPYBG which, based on some testing I just did, can be replaced by PWADs just fine.

I managed to extract the flat and convert it to PNG, it seems to be alright. Here it is:

Edited May 31, 2022 by Alaux

[maxmanium]

4 minutes ago, Alaux said:

The graphic is baked into the binary. It's a flat called CRISPYBG which, based on some testing I just did, can be replaced by PWADs just fine.

I managed to extract the flat and convert it to PNG, it seems to be alright. Here it is:

 

Thank you!

[NightFright]

I know it's a very picky request, but is there any chance to only have the new on-top statusbar stats with two colors (optionally) without including multi-color names on the automap?

Also for some reason I think it'd look better to actually make the K/I/S letters white instead of the numbers. Yeah, I am crazy...

 

But just to be on the safe side: It's a great feature and I am glad it has been added.

Edited June 11, 2022 by NightFright

[maxmanium]

I think it might be a better idea to use the CR* Boom lumps for color translation as opposed to the current hardcoded values, as it appears different with custom palettes (e.g. mistaking teal for green, not using the full hue-shifted gold range).

[fabian]

On 6/22/2022 at 6:47 AM, maxmanium said:

I think it might be a better idea to use the CR* Boom lumps for color translation as opposed to the current hardcoded values, as it appears different with custom palettes (e.g. mistaking teal for green, not using the full hue-shifted gold range).

 

I have code for this ready, but you will lose e.g. colored status bar widgets in BTSX:

 

 

as opposed to the current state

 

Edited June 23, 2022 by fabian

[maxmanium]

9 minutes ago, fabian said:

-snip-

 

It's up to you, but I think this change would be fine since the first picture is how it appears everywhere else, precisely because the STTNUM lumps don't use the red range + it's not remapped as such in the CR* lumps.