Duration: 0:16

281 views

11

Rocky's YouTube: https://www.youtube.com/channel/UCImjEmDqdOuPg_hRu9NBszw

RockyGaming4725's comments: I found it was possible to actually stay on the ground for an extra tic before leaping to the door if you didn’t wallrun - leaving you with more momentum (and a wallrun of course). This allowed us to reach the door 2 tics faster. I then tried to get into the void one tic earlier but failed… sent it to Matt so he could have a look and he worked some magic to get it to work. Then, I saved another tic in the void, meaning it wasn’t even needed to try to get into the void one tic faster for 13 anyway!

almostmatt1's comments: A little while ago, both Rocky and I tried but weren't quite able to get 13 seconds so I'm quite happy to see this done!
This demo obviously doesn't use the recently discovered intercepts overflow trick and it may seem as though that's a missed opportunity leading to an inadequate demo but I'm not convinced that's the case. Rocky and I have not been able to get the bug to happen in a worthwhile way. Replicating the position that Zero Master found or a similar enough position is simple enough, but the problem is that it requires a pinky to move into the correct spot to work. RNG seed manipulation is not possible with CL3 (Ultimate Doom) demos like this, and manipulating it to happen as fast as possible through simply manipulating RNG by firing is quite a difficult thing to, so it takes a little while to activate the bug in the first place. On top of that, we wouldn't have reduced health from the barrel explosion so if we got the bug to happen and then got to the final room it would take some time for our health to deplete, especially since we can only take melee damage and not hitscan. Considering this, I would be happy to be proven wrong but it's not really apparent to me that the trick is the optimal way to do this demo, at least in a TAS context.
I think theoretically the perfect thing to happen would be to trigger the bug between taking damage from the barrel explosion and reaching the first door but getting the bug to happen at all is really, really hard. Maybe it'll happen some day, who knows.
What this demo DOES do compared to previous demos is hit the first door faster thanks to Rockys improved movement, get into the void a tiny bit faster and do the void section a little bit faster. Turns out all that was needed for a 13 was to improve what we had already done rather than chuck in something new. Thanks to Rocky for deciding to revisit this one.

There's something pretty weird that happens in this demo that honestly I don't understand. We had the idea to try to close the first door after we ran through it to influence wallrunning in the void. After the void glide, there's a small section of eastern wallrunning before turning north and doing the large section of void wallrunning. Void geometry is weird and difficult to understand because you can't see anything and there's no blatantly existing structures in the void to exploit. Rather, basically when a wall right up against the edge of a map is impassable, that impassable wall effect will continue on into the void. I thought that if we closed the door, the impassable surface of the closed door would continue infinitely east into the void and we could exploit it to wallrun.
In this particular demo, closing the door does indeed have an effect. Closing it creates an impassable surface in the void and facilitates an eastern wallrun, and leaving it open removes this surface and desyncs the demo.
However, this is not true of any prior E1M8 demo that takes advantage of this wallrun, which was done before we thought of the door trick thing. That is to say that for our old demos closing the door or not does not have an effect on the demo syncing at all. Getting the wallrun to happen regardless of having closed the door seems to be a matter of how far east you are when you happen to be south enough to contact the solid surface, but having examined a few other E1M8 demos there appears to be some inconsistency with this and I haven't really worked it out. Either way, very strange behaviour... The important thing is that it works, but I hate not understanding exactly HOW it works!