Nugget Doom 3.1.0 (updated May 16th, '24)

[CacoKnight]

1 minute ago, Alaux said:

Read this, from the third paragraph onward; maybe that's what happened.

Interesting, weird also it happens every once in a while?

[Alaux]

Just now, CacoKnight said:

Interesting, weird also it happens every once in a while?

If that bug really is what you encountered, then it happens when the conditions described in the article are met, and well, you may just be unlucky enough to accidentally trigger it every once in a while.

[CacoKnight]

I wanted to ask this for a while but I keep forgetting, why is that soundfont included in the build? It doesn't sound good at all and it's the first thing I remove every time I download Nugget/Woof. It's almost 50% of the total size of the archived .zip, it seems like useless waste of space. Why not let people download/decide on their own instead of having them play with something that doesn't sound like the original Doom at all?

 

Also, isn't the OS Midi system the default config anyway? Most people won't even use that soundfont in the first place.

 

Just some thoughts.

Edited March 26 by CacoKnight

[dasho]

45 minutes ago, CacoKnight said:

I wanted to ask this for a while but I keep forgetting, why is that soundfont included in the build? It doesn't sound good at all and it's the first thing I remove every time I download Nugget/Woof. It's almost 50% of the total size of the archived .zip, it seems like useless waste of space. Why not let people download/decide on their own instead of having them play with something that doesn't sound like the original Doom at all?

 

Also, isn't the OS Midi system the default config anyway? Most people won't even use that soundfont in the first place.

 

Just some thoughts.

 

It's better than the inevitable "Music doesn't work" issues that would be brought up instead.

[plums]

1 hour ago, CacoKnight said:

I wanted to ask this for a while but I keep forgetting, why is that soundfont included in the build? It doesn't sound good at all and it's the first thing I remove every time I download Nugget/Woof. It's almost 50% of the total size of the archived .zip, it seems like useless waste of space. Why not let people download/decide on their own instead of having them play with something that doesn't sound like the original Doom at all?

 

Also, isn't the OS Midi system the default config anyway? Most people won't even use that soundfont in the first place.

 

Just some thoughts.

On Linux you need a soundfont to get any music at all, unless you use OPL playback. IIRC the included soundfont is free of any copyrighted material and OK to distribute with GPL software, and 6 megs is an OK balance between quality and size.

Edited March 26 by plums

[CacoKnight]

Maybe better this one? But anyway, fair enough, it takes one second to disable/change/remove.

[plums]

18 minutes ago, CacoKnight said:

Maybe better this one? But anyway, fair enough, it takes one second to disable/change/remove.

See further down that page where ceski shows that that one is full of samples directly from Windows' gm.dls, except with the copyright hacked out.

 

Just getting a soundfont that is completely (legally, verifiably) free and GPL compatible, and small, is hard enough, let alone one that sounds good.

Edited March 27 by plums

[CacoKnight]

But but but, last msg on the subject I promise, what about the Trevor one? Forgot about this one, it's a little bigger but it sounds very good.

 

..or the GZDoom one? Isn't that open source?

[dasho]

17 minutes ago, CacoKnight said:

But but but, last msg on the subject I promise, what about the Trevor one? Forgot about this one, it's a little bigger but it sounds very good.

 

..or the GZDoom one? Isn't that open source?

 

The GZDoom one uses the Deemster preset, which still has Roland copyright statements. The Trevor soundfont is derived from decrypted SC55 ROMs. 

[S3M_XM]

Is it possible to add "Show Alive Monsters" in the automap?

[Alaux]

30 minutes ago, S3M_XM said:

Is it possible to add "Show Alive Monsters" in the automap?

What exactly would that do? How would it differ from iddt?

Edited March 27 by Alaux

[S3M_XM]

10 minutes ago, Alaux said:

What exactly would that do? How would it differ from iddt?

To show just only the alive monster markers that don't get mixed up with the other thing markers.

[Alaux]

9 minutes ago, S3M_XM said:

To show just only the alive monster markers that don't get mixed up with the other thing markers.

It's doable, but I'm not fully convinced.

 

FWIW, there's also iddkt, and I think you can change the colors used for each thing marker and maybe even hide some of them by modifying the config file.

Edited March 27 by Alaux

[CacoKnight]

1 hour ago, S3M_XM said:

To show just only the alive monster markers that don't get mixed up with the other thing markers.

That'd be a cool automap feature, is there a port that can do that?

[Deil]

@Alaux 

Nice nuggets, that was a pleasant surprise.

[CacoKnight]

I was checking Cherry Doom last night because I noticed that he finally merged with the latest Nugget and I saw that and I thought he messed up something on the code while he was merging, didn't even think of checking Nugget but I just did, funny stuff.

Edited April 1 by CacoKnight

[No-Man Baugh]

I am currently under an NDA regarding Nugget-Doom, so I can neither confirm nor deny anything funky going on that people may or may not encounter when playing Nugget-Doom today

[Siglev_]

I didn't know that nugget doom turned health bonuses into cheese on April 1st, Very funny.

[Xemonix]

14 hours ago, CacoKnight said:

I was checking Cherry Doom last night because I noticed that he finally merged with the latest Nugget and I saw that and I thought he messed up something on the code while he was merging, didn't even think of checking Nugget but I just did, funny stuff.

I actually did mess up a whole bunch of things, but I'm working on it.

When I saw the cheese I thought using certain cheats made it appear (as in cheesing the map), only realized it's an April 1st joke after checking the source code. Made me chuckle, nice job, Alaux.

[Shepardus]

I thought the cheese was part of the WAD I was playing until I switched to a different WAD and the cheese was still there.

[No-Man Baugh]

I honest to god thought I broke something when I was testing out my NUGHUD like it was a placeholder or something
 

Spoiler

My honest reaction

 

[plums]

I was mainly surprised it was cheese, and not nuggets of some kind.

[UUN4]

I've been playing Valiant recently, and the cheese being there never hit me; I kinda just assumed it was a part of Valiant for some reason.

[Shepardus]

I'm encountering some unintuitive behavior from the rewind feature. FWIW I have my rewind interval set to 5 seconds, it might be less of an issue with lower intervals like 1 second.

 

The first is that the rewind keyframes don't line up with the 5-second intervals of in-game time. I think it might be because the interval doesn't reset when reloading a map or switching to a different map? i.e. if I IDCLEV to a different map in the middle of an interval, rewinding later might take me back to 0:02 instead of 0:00 or 0:05. This isn't that much of a problem, I can get used to it, but dsda-doom in comparison saves a keyframe at the beginning of the level which makes it easier to remember what times the keyframes are at.

 

What's more of a problem for me is that rewinding to a keyframe seems to make the port forget about that keyframe. I guess that's a measure to prevent getting stuck rewinding to the same keyframe over and over, but it prevents me from using a keyframe more than once, for example when repeatedly trying and failing to make a jump in a platforming map. Each time I rewind it goes further and further back, unless I wait for another keyframe to be saved, and even if I do wait, there ends up being a gap between keyframes, which can lead to surprising results when I rewind and jump 30 seconds between two keyframes.

 

I think dsda-doom handles this by making the rewind key jump to the second most recent keyframe instead of the most recent one (so rewinding at 0:17 goes to 0:10 instead of 0:15). It's not perfect since if I mess up in less than 5 seconds I have to wait for the next interval before I can rewind (which is why I care to know when exactly the keyframes are, bringing me back to the first point), but I think it's still better than the current behavior in Nugget Doom.

 

Overall though I'm loving the feature and the rest of the source port! It's been my most-used port recently, and it's great to see how far it's come.

[Raith138]

I wish I had found this source port sooner. Perfect source port for me.

[Alaux]

18 hours ago, Shepardus said:

I'm encountering some unintuitive behavior from the rewind feature.

I agree with your suggestions, so I've made an experimental branch to try some tweaks (Windows autobuilds here -- I forgot what OS you're on, though).

 

So far, I've made it so that key frames are only deleted if less than 0.6 seconds pass between rewinds; I can't be bothered to figure out how to properly store key frames upon loading levels right now. Anyways, feel free to try that branch and let me know how it goes.

[Zaratul]

16 hours ago, Raith138 said:

I wish I had found this source port sooner. Perfect source port for me.

 

Same for me. Now that Woof and Nugget Doom supports native resolutions these are my source ports of choice. DSDA is great but i like QoL of Woof\Nugget and last but and not least: blockmap bug fix!

[PH0B0Z5]

Hello, excuse my ignorance

Are there any plans on including hardware renderer?

[Alaux]

7 hours ago, PH0B0Z5 said:

Are there any plans on including hardware renderer?

I wouldn't mind including one, but I think it's safe to say that I won't be the one coding it. To be clear: as of writing this, I don't have any hardware-renderer implementations in sight.

Edited April 7 by Alaux

[Shepardus]

On 4/5/2024 at 11:39 PM, Alaux said:

I agree with your suggestions, so I've made an experimental branch to try some tweaks (Windows autobuilds here -- I forgot what OS you're on, though).

 

So far, I've made it so that key frames are only deleted if less than 0.6 seconds pass between rewinds; I can't be bothered to figure out how to properly store key frames upon loading levels right now. Anyways, feel free to try that branch and let me know how it goes.

Cool, thanks for working on this! The keyframe deletion is more of a problem to me than not keyframing the start of the level, so the change you made sounds great already. I don't have a lot of time right now but will check it out when I can. (I'm on Linux, usually build from source)