DRD Team

Video is self explanatory, but I start up Ultimate Doom in GZDoom normally, and in E1M3 about 20% of the time, for some reason, I can walk through this wall. Rockets go through it too, and the first time it happened I found it because a demon was running around in the nothingness behind the wall. Hitscan attacks still collide with it. As far as I can tell all other walls are solid, but I haven't had too much time to test this out. I don't know how to reproduce this and I only seem to be able to do this in GZDoom. If I can replicate this in ZDoom I'll probably go post it over there and disregard this thread, but so far I haven't been able to do this.

In the future, please explain what happens in the video in your post anyway. Videos should be used as nothing more than a support to a report - NOT the main component. Not everyone can view videos and this makes it hard for them.

I agree that text descriptions are important. However, his video has the text descriptions embedded in it, and they are at exactly the points in the walk-through to which they apply. This, for me at least, made his description of the problem very clear.

Mmk, added a text description to my OP quick.
If it's relevant, here's my .ini file.
I don't think my system specs are relevant to this but I could post them if need be?

Hmm, I could not seem to reproduce it with both yours and my ini.

It looks like there's no official SVN build for r916 so I can't test this properly, plus I've been unable to reproduce it with r945.

Does it happen with r945? can you record a demo for this revision exemplifying the glitch?

Ok this is just extraordinarly bizzare. It refuses to happen in r945, with or without my .ini, and it will not happen in r916 without my .ini. If I do so much as start up GZDoom r916 (with my .ini) from a batch file (let alone with the -record parameter), the glitch doesn't happen, but I can still get it easily enough if I start it up normally.

I really don't know. I guess I wouldn't worry about this bug too much since it apparently needs a very specific environment for it to happen?

If it is a bug that does not occur in later versions, usually you can assume it was already fixed.