I used the Hacx 1.2 IWAD I once downloaded, dated 10/10/2010 10:00pm, size 19.199.268 bytes (is that dating coincidence? There's a lot of tens in there...)
If yours is different, please extract the map and attach it here so I can compare.
Moderator: GZDoom Developers
If Xaser was involved at that point, I really doubt it was a coincidence. But I could be wrong.Graf Zahl wrote:(is that dating coincidence? There's a lot of tens in there...)
I downloaded my copy from the Hacx website, the date of it is 21/10/2010, size 19,321,722 bytes. Seems like the V1.2 IWAD was updated some time after release, and this updated IWAD is on /idgames as well. The mapchecksum of MAP05 in the IWAD is '9BC9E12781903D7C2D5697A5E0AEFD6F'.Graf Zahl wrote: I used the Hacx 1.2 IWAD I once downloaded, dated 10/10/2010 10:00pm, size 19.199.268 bytes (is that dating coincidence? There's a lot of tens in there...)
If yours is different, please extract the map and attach it here so I can compare.
Code: Select all
-iwad doom2 -file pg-raw.wad -nomonsters +map map32 +god +warp 8800 0
Spoiler:The problem happens in prboom-plus too, so I'm not sure if it is fixable on engine side.
Code: Select all
920F8D876ECD96D8C2A978FF1AB2B401 // Darken2.wad map01 - Nodes go out of bounds/beyond normal sector boundaries
CFEDB7FA89885E24856CAC9A2FB3CE58 // Darken2.wad map03 - GZDoomBuilder crashes when displaying Nodes
8E961FA7029761D5FAB3932C40F10CD2 // Darken2.wad map04 - Nodes go out of bounds/beyond normal sector boundaries
DEA5E9C6253FFF8FDB2D5E5BADE13A9D // Darken2.wad map06 - Nodes go out of bounds/beyond normal sector boundaries
0E72254C0C26F721333A1C56E3648D68 // Darken2.wad map07 - Nodes go out of bounds/beyond normal sector boundaries
1437B40F2D56DF82346366814E9729D9 // Darken2.wad map08 - Nodes go out of bounds/beyond normal sector boundaries
8B15F89E47E422780FBF2D6CDE3AA050 // Darken2.wad map09 - GZDoomBuilder crashes when displaying Nodes
5A2FD43D23B45191229E5C74E9398D36 // Darken2.wad map10 - Nodes go out of bounds/beyond normal sector boundaries
FA25A78B3DFD7CC44E9B10C7B78EADAE // Darken2.wad map11 - Nodes go out beyond normal sector boundaries
01592ACF001C534076556D9E1B5D85E7 // Darken2.wad map12 - Nodes go out of bounds/beyond normal sector boundaries
16A2ED2917A68B2FD8D264BE4D64EA09 // Darken2.wad map13 - Nodes go out of bounds/beyond normal sector boundaries
F5DA2AA0C7112E090167A6B2F6D4A079 // Darken2.wad map15 - Nodes go out beyond normal sector boundaries
A40A4472AB0FDBE2D55ADADA7D9005C8 // Darken2.wad map16 - Nodes go out of bounds/beyond normal sector boundaries
244701904E6B754A02842415AB183EBE // Darken2.wad map17 - Nodes go out beyond normal sector boundaries
661D3C9221114A1CD16674CBFF239DDF // Darken2.wad map19 - Nodes go out of bounds/beyond normal sector boundaries
1FB559C4C37CCE8C3883057C963952A8 // Darken2.wad map20 - Nodes go out beyond normal sector boundaries
D36E7D121F28F77A3780A5BD88425FB4 // Darken2.wad map21 - Nodes go out beyond normal sector boundaries
3253B280FB7A4A04284FE08A6D9F222D // Darken2.wad map22 - Nodes go out beyond normal sector boundaries
E0E5517B7928E88B88F6A5B77AC449DF // Darken2.wad map23 - Nodes go out of bounds/beyond normal sector boundaries
6DD76422593381E3234FA703C155C493 // Darken2.wad map24 - Nodes go out of bounds/beyond normal sector boundaries
{
rebuildnodes
}