The scary thing is that there are people out there specifically saving underneath doors. Like who opens a door, stands in the doorway, and saves? Would make more sense to save in a cleared out room, before the enemies are triggered.

@AlexeiVoronin

5 ай бұрын

I know, right? And there are probably people who save under water in Quake :P

@Snufflegrunt

4 ай бұрын

@@AlexeiVoroninwhat kind of unnatural animal born from of the antichrist would do that?

2:28 As a kid, that kind of game crashes and notes suspended eternally was my worst nightmare of all time. Ghosts and zombies were no match for possessed machineries.

@teranokitty

4 ай бұрын

Same here, it's very unnerving. Much worse than if it crashed to the DOS prompt with a text error.

@Lyne_Taperz

4 ай бұрын

@@teranokitty Oh hell, older versions of Heretic always gave me that kind of crashes when there's too much object on screen. 6-year-old me was so frightened that I almost jumped out of my chair whenever it happened.

Thanks for sharing these weird bugs! In the case of the first bug, after it occurred and the screen was corrupted, because pressing enter caused what was on the screen to change, I had a suspicion that it might have been back in DOS but with the wrong video mode. I tried reproducing with DOOM 1.2 Shareware under DOSBox 0.74-3, and sure enough if I typed "CLS" I got a normal-looking screen, or if I typed "DOOM" it started the game back up again. I don't know if "CLS" would work the same with a real version of DOS - maybe it wouldn't change back to text mode - but I imagine "DOOM" would work because eventually it'd change back into graphics mode and redraw the screen like normal.

@AlexeiVoronin

5 ай бұрын

I just tried it out - you are right, "cls" does work. So I guess this situation isn't as hopeless, as I had previously thought. Good find! :)

@mcbpete

14 күн бұрын

@@AlexeiVoronin You could also try 'blindly' typing *mode co80* to revert the resolution to the default 80 column text mode

This video is amazing, exactly what I needed right now! You have gained a new subscriber today

@AlexeiVoronin

5 ай бұрын

I am very happy to have found other people interested in this ancient "Doom lore". Glad you enjoyed it :)

This is exactly the type of content I’ve needed lol

@AlexeiVoronin

5 ай бұрын

Glad you enjoy it :)

Love your little Doom videos! Btw, do you know what else has a bug? The thumb counter from YT. Gave you a thumbs up, still says 0. -.-

@AlexeiVoronin

5 ай бұрын

Wow, you're fast! A bug on YT? Noooo waaaaaay :D

I used to get that same garbled graphics crash screen when I had DOOM II and would play it from the CD. It would crash on the final level every time. Never figured out why. I could see it being a problem if the game needed to write to the disk at that point and couldn't because it was a CD, but what would it be writing? So I never figured it out. It stopped happening when I finally installed the game to the disk. I was just trying to save space back in those olden days when having a 5GB hard drive was a big deal.

@AlexeiVoronin

5 ай бұрын

The first time I ever played Doom II, our PC was poorly configured, so the game crashed often, and had all sorts of crazy glitches. One ofthe worst things was that the chaingunners' sprites didn't load, which made them completely invisible :D

@RogueCarrot

5 ай бұрын

@@AlexeiVoronin Ultra Nightmare lol

@teranokitty

4 ай бұрын

@@AlexeiVoronin Super-duper-hard-mode :D

im no expert but in doom 1 closing it like that while directly inside the door after freshly loading a save probably causes an illegal linedef interaction as doomguys inside when it closes that ends up bricking the engine

@AlexeiVoronin

5 ай бұрын

It's a possibility. I don't know the exact mechanism of this bug, and the Doom Wiki doesn't explain it either...

@misha5670

5 ай бұрын

Yes, you are pretty much right on. Basically, trying to 'close' the door there tricks the engine into thinking it should 'close' the entire level: i.e. reduce the ceilings all down & with the player in them too! lol At least that's what my 30 year old memory is bring up. I did a lot of editing and hacking of Doom back in the mid '90s because internet really wasn't a thing yet, and i had a free copy of the game and no money.

@AlexeiVoronin

5 ай бұрын

@@misha5670 - Wow, sounds crazy... but then again, the older Doom engine did have a number of crazy bugs in it.

Hahaha,. what an odd that second one! I tried Doom in DosBox, indeed it froze for long. But also happened again on the other side. And again on the first side (sometimes it does and sometimes not). DosBox debug window would throw a ton of "Illegal write at CS:IP at address blah blah". Interestingly enough I try it in FastDoom in DosBox. It's easier to see the fault there with the command line box. I don't get long freezes, but everytime I press I get only 8 lines of "illegal read/write at CS:IP". So I can repeat pressing on both wall segments with the grey bars and it does happen repeatidly, because every time I do I see more stuff like that are printed. Now I'll check those lines in editor.

@AlexeiVoronin

4 ай бұрын

You can see similar messages appearing when you do the "save under an opened door" crash ;)

The door bug would probably SIGSEGV on a modern OS

to this day I avoid saving under doors (or on moving bits of scenery in general) in any game because of this bug.

Hello, Alexei. In the first example, the computer (or DOSBox in this case) didn't crash or get stuck. What happens here is there's an abnormal termination with the game, which causes the screen's framebuffer not to be cleared up on exit, so the last frame of the game is still displayed because it's still stuck in the video memory. Think of it as your screen being left with a stain. The reason pressing escape was moving the screen a bit is because you were at the command prompt, and pressing escape at the command prompt prints the escape character (\). To fix this, you don't have to terminate DOSBox (or MS-DOS in the case of real hardware). You can just type "doom" and hit enter, and it will clean up the screen and start the game up again normally. From there, you can just quit the game from the main menu, and the screen will be fixed. In the second example, that's the first time I see that freezing effect. I think this is something DOSBox does, for some reason. For me back in Windows 98, it would just crash the game, because it reads invalid memory. In Chocolate Doom, it crashes the game (intentionally, since that's the aim of Choco). Both Crispy Doom and GZDoom make it so you can't trigger door specials if they're placed on 1-sided linedefs, therefore the game acts like the lines have no special assigned. In the case of Crispy Doom, however, the game does internally print a warning: "EV_VerticalDoor: DR special type on 1-sided linedef" (doom/p_doors.c line 426). This is not seen by the player, however. In any case, the game just continues as normal (although the special is triggered, but it's immediately terminated, so nothing happens). Some cool trivia in the case of GZDoom with this map: when GZDoom launches, it checks what levels are present in the IWADs and PWADs that you loaded and it runs a hash check on these maps to see if they are known for having issues. If those maps' hashes fit what is defined in the internal database, it goes and applies those fixes by modifying the maps during runtime (it doesn't edit your WADs, just modifies the maps loaded into your RAM). These fixes can be anything from removing specials from lines with inappropriate actions to adding missing textures to fix HOMs, etc. In the case of MAP06, however, it's one of the few Doom 2 levels not listed in the database as requiring fixes. The other ones are MAP01, MAP09, MAP11, MAP20, MAP23, MAP24, MAP30, MAP31 and MAP32.

@AlexeiVoronin

29 күн бұрын

Yeah, at some point after making the video I realized that the "Venetian blind" crash can be easily recovered from. This will be useful the next time I show such a crash (there is one bug I will probably demonstrate in the future, which causes such a crash) ;) I think I've seen GZDoom compatibility database. IIRC, it also quietly fixes the inaccessible secrets of E4M3 (and maybe E4M7).

What version of Doom is this on? Steam, GZDOOM, Boom...?

@AlexeiVoronin

5 ай бұрын

It's the original vanilla Doom (for DOS). Тhe exact version number can be seen at the top fo the screen during the startup sequence (at 1:49 and 5:29), though you'd have to pause the video because it zooms by pretty fast. Pretty much all of the old bugs I demonstrate were fixed, one way or another, in modern source ports, so vanilla remains the only way to experience them.

@youmukonpaku3168

4 ай бұрын

@@AlexeiVoroninthe crash on the Crusher door is actually still present in Chocolate Doom, except worse; it doesn't self-heal. I believe this is intentional, however, since Chocolate Doom aims to replicate even negative behaviors.

@AlexeiVoronin

4 ай бұрын

@@youmukonpaku3168 Chocolate Doom si doing its job well, in this case :P I wonder if the self-fixing is due to DOSBox (which, although very accurate, still isn't a 100% perfect emulation of DOS). I'm thinking of running a few tests in a virtual machine that runs actual DOS 5.00.

Hmmm the Doom2 iwad I use today is one I bought off Steam years ago, before Doom3 BFG and before Unity and Bethesda; but still loooooooooooooong after the old days. I wonder if my version still has it. But I run it through GZDoom and that might "fix" it so maybe it wouldn't be an accurate test. I wish I never misplaced my Doom2 3.5s. For Doom 1 I had the shareware, and I had Ultimate Doom on CD (Doom 1 + Thy Flesh Consumed, installed like and ran similar to Doom95).

@AlexeiVoronin

4 ай бұрын

Yeah, GZDoom quietly fixes the majority of the old engine bugs, so the best way to see them nowadays is in vanilla. If your IWAD still has medikits with red crosses, it's most likely the 90's original ;)

@johnroscoe2406

4 ай бұрын

@@AlexeiVoroninyup I have the classic red crosses. Wouldn't have it any other way! lol

Doom engine vs build engine cursed doors

who are you?

@AlexeiVoronin

5 ай бұрын

Just a guy trying out a new hobby. And a Doom fan, obviously ;)

8 minute video that shows the exact same thing as a 30 second video from 2008 thats also on the doom wiki page for this error

@AlexeiVoronin

4 ай бұрын

(shrug) I apologize for forcing you to watch my video against your will. I promise I won't do so again. Jokes aside, that's just my style of doing things - I like to imagine that I'm engaging the viewer in a conversation, that we are moving along together.

@johnroscoe2406

4 ай бұрын

Grow up "Chief." This is fun watching for those of us who aren't Gen Z newbie "fans." Go back to Decino or something. Or go do your stupid speedrunning.

@kellymountain

4 ай бұрын

@@johnroscoe2406 dawg it's just a comment did you have to get so elitist over me saying there's a better example of this glitch? I don't speedrun and I'm not even part of gen z