forgive me if this bug has been fixed already, it's been a long-ass time since i ever played Doom.
so long story short, i had the urge to play some Doom again, after months of not playing games, and i experienced a number of crashes. this confuddled me, so i decided to go deeper into the issue, and see what was wrong.
what i found out was 2 issues with the latest svn version of GZDoom, r1351, which i downloaded in order to play a mod here which required an svn version.
so anyways, after a bit of back and forth with GZDoom, i found out that r1351 apparently doesn't like a Boom-map property, which was to make the light kinda, dunno how to describe it, but flicker around a fixed location in different points of the map. i tested this with Community Chest 2's maps 02 and 15, which both has this light action in them. both crashed with no extra mods loaded. degrading to the previous svn version, 1349, fixed this issue, and the next one, which i'm coming to now.
so i told my friend that Doom crashed, and he told me to update my GPU drivers. i had little idea why that would work on GZDoom, but i did it anyway. and took note of an interesting bug while loading Wildweasel's ww-nazis mod.
at the titlemap, the screen turned all into pink with the latest drivers, and i had to manually shut down the computer to fix it. downgrading to the previous svn solved the issue and i had not experienced this again.
this makes me to believe that r1351 doesn't seem to like Titlemaps that well, since it made the whole screen filled with pink garbage pixels. but strange thing is, this did not happen until i decided to update my GPU drivers to the newest version (i have a 768MB GeForce 8800 GTX (Leadtek), in case you're wondering).
i was able to get a crashreport of the Boommap property, but since the pink garbage pixels made me have to shut down my computer, i couldn't get anything of it.
here's the crashreport, btw.
i hope i didn't waste anyone's time with my crashing experiences here~
