hex11
Senior Member
Posts: 1989
Registered: 09-09 |
It's the doom2.wad from v0.7:
MD5 (freedoom-iwad-0.7/doom2.wad) = 21ea277fa5612267eb7985493b33150e
But you're right, those aren't even in the IWAD. They only show up when I also load the slige.out PWAD into Yadex, or run the resulting output from bsp with chocolate-doom (or prboom). Chocolate Doom also shows some warnings on startup:
R_Init: Init DOOM refresh daemon - [...........R_GenerateLookup: column without
a patch (GRIDRED)
R_GenerateLookup: column without a patch (GRIDBLUE@)
R_GenerateLookup: column without a patch (GRIDYLW)
R_GenerateLookup: column without a patch (GRIDPURP@)
R_GenerateLookup: column without a patch (GRIDWHT2@)
R_GenerateLookup: column without a patch (EXITSWIT@)
R_GenerateLookup: column without a patch (WOODLITE)
So I maybe slige is doing something wrong...
Okay, after RTFM, it looks like slige inserts some new (custom) textures into the generated PWAD, unless you use the -nocustom option. But the weird thing is, those new textures don't cause any problems when using the real Doom II IWAD (no warnings at startup, no tutti fruti, etc.) In fact, here's what the same MAP02 looks like in this case:
http://img14.imageshack.us/img14/7240/grayalt.png
This is with the same exact PWAD that I loaded before with the Freedoom IWAD. But in this case, none of the four patches in that GREYALT texture are transparent, and the EXITSWIW also looks sane.
|