Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Teo Slayer

A weird bug I found in Doom II

Recommended Posts

Screenshot_Doom_20210605_184104.png.907cbd5e86de5237926fb5351c973f2d.pngScreenshot_Doom_20210605_184109.png.9555aa5f9c5ac25d6dab677c68b2adce.png

Is this a bug or it's just my version of GZDoom?

Btw, the map is MAP18 - The Courtyard

Share this post


Link to post

Very likely it must be the SourcePorts you are using, in the Steam version I believe it doesn't have this kind of bug

Share this post


Link to post
9 hours ago, Teo Slayer said:

Screenshot_Doom_20210605_184104.png.907cbd5e86de5237926fb5351c973f2d.pngScreenshot_Doom_20210605_184109.png.9555aa5f9c5ac25d6dab677c68b2adce.png

Is this a bug or it's just my version of GZDoom?

Btw, the map is MAP18 - The Courtyard

It's most likely your version of GZDoom, or just GZDoom in general. You can switch to any other sourceport and this will work correctly.

Share this post


Link to post
Posted (edited)

I think I remember seeing this ages ago when I was playing Doom 95 IIRC. This bug is definitely present in some Doom 2 IWADs.

Share this post


Link to post

I have never seen this before, so it probably has something to do with the port you're using. I still use the original Doom 2 .iwad that came with the CD that I got back in 1994, so it's as pretty close to pristine as you can get. I still have the CD as well, but I just copied the files onto a computer years ago and my Doom and Doom 2 folders get backed up whenever I transfer to a new computer or hard drive.

 

I just tried it using the latest version of GzDoom, and Chocolate Doom, and I didn't see any graphics issues like that in Map 18. And I don't recall them when I was playing it in DOS 27 years ago either. So something might be up on your end.

Share this post


Link to post

Doom2 1.666 has this, it’s fixed in 1.9 (how the heck did you get a copy of 1.666 in this day and age? Cool old relic)

Share this post


Link to post
6 minutes ago, Doomkid said:

Doom2 1.666 has this, it’s fixed in 1.9 (how the heck did you get a copy of 1.666 in this day and age? Cool old relic)

yeah, i was gonna say, i thought it looked like a node issue or something, but that'd mean it'd have to be a different version??

Share this post


Link to post
6 hours ago, Doomkid said:

Doom2 1.666 has this, it’s fixed in 1.9 (how the heck did you get a copy of 1.666 in this day and age? Cool old relic)

There's a ton of downgrade patches made by doomers floating around on the internet. AFAIK there's no one collection of them, so it'd be a matter of Google to find them all.

Share this post


Link to post
Posted (edited)

It is 100% a level bug. I grew up with it; didn't even notice they eventually patched it in 1.9.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×