wololo.net/talk

Thanks for this release, has been excellent so far. especially the digital music which I have working in Doom I/II. My only issue is getting Hexen's digital music pack to work and that is with the linked Hexen music pack. Is the problem possibly related to the SHA1 values in the config?

Al Capwn wrote: ↑

Wed Apr 18, 2018 10:49 am

Thanks for this release, has been excellent so far. especially the digital music which I have working in Doom I/II. My only issue is getting Hexen's digital music pack to work and that is with the linked Hexen music pack. Is the problem possibly related to the SHA1 values in the config?

I haven't personally tested the Hexen config from the pack provided by MysticalLiete, but I know that this worked fine when I tested it in Release 1.

Concerning the digital music packs, I would recommend the boosted packs. The raw packs seem to be missing some music tracks.

rsn8887 wrote: ↑

Wed Apr 18, 2018 9:52 pm

Concerning the digital music packs, I would recommend the boosted packs. The raw packs seem to be missing some music tracks.

some things are named incorrectly such as intermission music

fgsfds wrote: ↑

Wed Apr 18, 2018 3:09 pm

Al Capwn wrote: ↑

Wed Apr 18, 2018 10:49 am

Thanks for this release, has been excellent so far. especially the digital music which I have working in Doom I/II. My only issue is getting Hexen's digital music pack to work and that is with the linked Hexen music pack. Is the problem possibly related to the SHA1 values in the config?

I haven't personally tested the Hexen config from the pack provided by MysticalLiete, but I know that this worked fine when I tested it in Release 1.

Thanks! That worked perfectly. The really confusing thing is that I can't tell any difference between the config files but I re-copied both and my original definitely doesn't play for some reason.

fgsfds wrote: ↑

Wed Apr 18, 2018 3:09 pm

Al Capwn wrote: ↑

Wed Apr 18, 2018 10:49 am

Thanks for this release, has been excellent so far. especially the digital music which I have working in Doom I/II. My only issue is getting Hexen's digital music pack to work and that is with the linked Hexen music pack. Is the problem possibly related to the SHA1 values in the config?

I haven't personally tested the Hexen config from the pack provided by MysticalLiete, but I know that this worked fine when I tested it in Release 1.

Thanks for confirming this, I've edited the post to advise people to use the .cfg in the link instead.

By the way, there’s a few issues with saving separate settings for each game. For example, Hexen, Heretic and Strife will all keep their own individual settings. However, Chex Quest, Freedoom etc. will always use the same settings as Doom II. Because the sound in these games needs to be set to OPL3 (whereas the Doom games will be using Digital), that means manually adjusting the settings each time. I assume this is because they need their own .cfg files in /chocolate/?

MysticalLiete wrote: ↑

Sun Apr 22, 2018 4:27 pm

By the way, there’s a few issues with saving separate settings for each game. For example, Hexen, Heretic and Strife will all keep their own individual settings. However, Chex Quest, Freedoom etc. will always use the same settings as Doom II. Because the sound in these games needs to be set to OPL3 (whereas the Doom games will be using Digital), that means manually adjusting the settings each time. I assume this is because they need their own .cfg files in /chocolate/?

This is sort of the way Chocolate Doom works. There's actually four different binaries in the VPK, each represents a "sub-engine" capable of running its own set of games. Each binary uses its own set of config files:

• Chocolate Doom (doom.bin) runs all Doom and Doom 2 based games and uses default.cfg and chocolate-doom.cfg;
• Chocolate Heretic (heretic.bin) runs Heretic and uses heretic.cfg and chocolate-heretic.cfg;
• Chocolate Hexen (hexen.bin) runs Hexen and uses hexen.cfg and chocolate-hexen.cfg;
• Chocolate Strife (strife.bin) runs Strife and uses strife.cfg and chocolate-strife.cfg.

As you've probably noticed, there's a fuсkton of games that run on the Doom "sub-engine" and they all use the same two configs. The launcher keeps separate settings for each set of configs or "sub-engine", but not for each game. So your assumption is correct, however you can't have Chocolate Doom load any additional configs automatically. You can do it using response files (by specifying the -config and -extraconfig command line args), but that's kind of a pain in the аss either way. I'll probably fix this in some way for the next release.

fgsfds wrote: ↑

Sat Apr 07, 2018 1:43 am

It turns out Chocolate Doom does not fully support FreeDoom, so be wary of savegame overflows and other limit-related bugs when playing it.

You can always go into chocolate-doom.cfg and set vanilla_savegame_limits and vanilla_demo_limits to 0 to at the very least lessen the chance of savegame and demo recording overflows. Not sure about other limit-related bugs, however.

Does anybody know if it’s actually possible to load the No Rest for the Living (nerve.wad) Doom 2 expansion that came with BFG Edition through Chocolate Doom?

It’s not officially supported, but apparently it can be forcibly loaded with Vanilla Doom (albeit with some glitches, incorrect music and level names etc.) using parameters. This implies that it should be possible with Chocolate Doom too.

MysticalLiete wrote: ↑

Sun May 06, 2018 3:08 pm

Does anybody know if it’s actually possible to load the No Rest for the Living (nerve.wad) Doom 2 expansion that came with BFG Edition through Chocolate Doom?

It’s not officially supported, but apparently it can be forcibly loaded with Vanilla Doom (albeit with some glitches, incorrect music and level names etc.) using parameters. This implies that it should be possible with Chocolate Doom too.

just load it as a pwad