[FEATURE] Parse flats and sprites from BRGHTMPS lump

[Invictus812]

This is what I'd always meant to ask for and I never realized this was the issue I was having :P

The BRGHTMPS lump in doomretro.wad only calls for textures, and scanning the code it seems that the engine is also only looking for textures. Was hoping you could allow adding brightmaps to at least flats, but hopefully also sprites.

[bradharding]

Ah, ok. Now I understand! Never liked brightmaps for sprites, but I will work on allowing it. It's unlikely to make the next release however.

[Invictus812]

Just happy to know it's something in progress. Thank you 🤘🏻

[DeathWishh]

I’m looking forward to this too! It’s one of the few ports I use to play Doom. In some of the larger WADs I’ve been working on lately, I’ve been trying to add custom brightmaps for custom textures. I’ve also been helping various people figure this out, since this lump format isn’t very standardized. So far, Nugget Doom is leading the pack; I use it as a general-purpose port with a bunch of near-vanilla features and brightmaps for pretty much everything, including weapons. I’d like the lump from Woof/Nugget to eventually become the standard for many ports, since it offers the most features and isn’t that difficult to implement. But, damn it, Doom Retro has its own aesthetic, visual effects, and atmospheric lighting that I really like, and I’ve even adapted some of my maps to a specific visual style that I think looks best in Doom Retro.

[Invictus812]

So far, Nugget Doom is leading the pack;
I’d like the lump from Woof/Nugget

As much as I appreciate the solidarity, could we avoid referencing other source ports as an argument for adding features? I don't want to speak for Brad but it feels like poor taste, and there's plenty of reasons that feature can stand on its own merits besides that.

[DeathWishh]

Oh, okay, I get it. I didn't mean to cause any trouble.