Closed ExGuestCJ closed 4 months ago
Works fine for me in Windows 8.1 (virtual machine). Can you share your crispy-doom.cfg
? Add it to a zip file and attach it to your comment. Also, please share the exact command line you use to launch the game and the wads you're using.
Also, a good first troubleshooting step is seeing if you can play a midi correctly with vanBasco MIDI player:
I should also comment that vms does work on chocolate doom. crispy doom config.zip extract the file, the cfg file is on it
Didnt work either
Also, please share the exact command line you use to launch the game and the wads you're using.
Forgot to say i dont use anny command lines afaik and i use the ultimate doom wad
Where did you download Chocolate Doom and Crispy Doom? If they are from here, then the midi implementation is identical: http://latest.chocolate-doom.org/
Yea, i remember downloading them there
Yea, i remember downloading them there
Again, the midi code is identical between Chocolate Doom and Crispy Doom so something else is going on here. There are two things you can try, otherwise this is something on your end:
winmm_complevel 0
in crispy-doom.cfg
.C:\Users\<NAME>\AppData\Roaming\crispy-doom
.It worked!
Background
Version of Crispy Doom: 6.0.0
Operating System and version: Windows 8.1
Game: Doom
Bug description
Observed behavior: When setting virtualmidisynth #1 as the native midi device the music plays with the default soundfont
Expected behavior: The music should play using the custom soundfont