Talk:Startup lumps

NETNOTCH's file size

I've been alerted to some information that may or may not be worth noting in this article, specifically the dimensions and size of the NETNOTCH lump required for Hexen startup. This fellow on Twitter reports that NETNOTCH is not 4x16 pixels/32 bytes, but 8x16 and 64 bytes. A couple of us have looked into this, and it turns out that the wiki is at least true as far as NETNOTCH inside GZDoom.pk3 - it turns out the 8x16/64 byte dimensions reported by @Slipgate0 are, in fact, referencing the data in vanilla Hexen. Couldn't quite figure out how to add a footnote on this wiki, though, and I don't know of a way to cleanly indicate this in the page without missing the purpose of the page itself. --WildWeasel (talk) 22:10, 25 February 2018 (CST)

Well the wiki is about ZDoom stuff, not necessarily vanilla stuff. Here's the relevant file from before the netnotch was externalized: clicky. Note the following:

#define ST_NETNOTCH_WIDTH	4
#define ST_NETNOTCH_HEIGHT	16

and

static const BYTE NetNotchBits[] =
{
0x52, 0x20,
0x23, 0x25,
0x33, 0x25,
0x31, 0x35,
0x31, 0x35,
0x31, 0x35,
0x33, 0x35,
0x31, 0x35,
0x31, 0x35,
0x31, 0x25,
0x33, 0x35,
0x31, 0x20,
0x21, 0x35,
0x23, 0x25,
0x52, 0x20,
0x05, 0x50
};

4x16 pixels, 32 bytes. Now why this was changed from Hexen, I do not know and cannot tell. When I externalized that stuff eight years ago already I just looked at what was inside ZDoom. It doesn't help that the data was presented differently between Hexen and ZDoom. --Gez (talk) 17:29, 26 February 2018 (CST)