Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
mlin

Fastest Possible Time: Classic Doom?

Recommended Posts

since this question is on tophic, I watched this speedrun (movie) and up to the point when he was playing map16, without getting the red key, he went to the exit and just squeezed through the red door (bar) and he also did the same in map22 with the bars


just wondering how the heck that was done..

Share this post


Link to post

http://ural2.hszk.bme.hu/~ha211/compet-n/index.cgi?action=nostalg&page=doom2trick
the trick has to do with the player being just one unit wider than the opening... but the opening is at a sharp angle... so since DOOM calculates collision as it happens, and it uses the polar coordinate system, sometimes you can just fit through.
pretty damn cool, if you ask me.
those two maps in that speedrun are definitely "don't blink or you'll miss it" maps. :)

Share this post


Link to post
Fredrik said:

In fact there is.

yeah, kind of like how quake has a plot. i just mean it would have been better off without one.

Share this post


Link to post

Anyway I see no fun in running through all the levels of this great game in 15 minutes. It may be done once, but on the second hand, the game lacks it's climate... It lacks everything, It's just a damned race.

Share this post


Link to post

Each to his own. I've watched 30uv1617.lmp hundreds of times, and it still retains its appeal. It's the sense of near-perfection that appeals. You know: "this is how it would look if God played Doom" (if He existed, of course).

Share this post


Link to post
Fredrik said:

All walls in Doom are infinitely thin :P

You seem to be really good with math, so why is your explanation here lacking? They can't be "thin" (with any adjective, "infinitely" or otherwise) because they have no thickness. The walls are actually closer to being (conceptually) planar, having no thickness. Technically, though, as far as the engine is concerned, they don't really have a height either, do they? I mean, the wall is just a line that determines blocking, with the sector determining how much of the image on that line you can see... right? (Probably not, but whatever.)

Share this post


Link to post
Ultraviolet said:

You seem to be really good with math, so why is your explanation here lacking? They can't be "thin" (with any adjective, "infinitely" or otherwise) because they have no thickness.

It's just a matter of word usage. The way I interpret it, "infinitely thin" translates to "having no thickness".

Technically, though, as far as the engine is concerned, they don't really have a height either, do they? I mean, the wall is just a line that determines blocking, with the sector determining how much of the image on that line you can see... right?

That's right.

Share this post


Link to post

Grimm said:
I don't think God plays Doom.


Heh, I'll keep that line in mind as a reply when someone asks me whether I believe in God.

Share this post


Link to post
Fredrik said:

That's right.

Yay for me!

But as far as "word usage" goes, I think you're just covering your ass now. :P

(If you were to say "infinitely thin" in a mathematical context, it would be like saying that it does have a thickness, although immeasurable. I'm only arguing about this because that terminology should NOT be used. I was confused for YEARS thinking that points actually have dimensions because it was explained to me with that kind of terminology and I don't think it should be explained to people that way because it leads to an incorrect understanding. I understand now, but an ounce of prevention is worth a pound of cure...)

Share this post


Link to post

Well, infinitely thin must logically define a thickness of 0 (what else would it define?), which is the same as no thickness at all.

Share this post


Link to post

That terminology, for a layman, isn't as clear as just saying "the object in question does not have that dimension." It fails to immediately make it clear. Something that is said to be "infinite" doesn't necessarily not have a size. Just think about maybe the distance from one end of "the universe" to the opposite end (I couldn't think of a better example, I know this ends-of-the-universe thing is dumb). It's immeasurable (as far as I know, tell me if they've made something up by now :P), but it still uh... has a size. It's just beyond human quantifiability.

I suppose maybe it just clashes with me. Everybody develops an understanding of the terminology with slightly different schema behind it. Maybe for you infinitely small is exactly the same as inexistant in terms of the dimension in question, but it isn't for me and I'm willing to bet that at least a few other people think the same way.

Share this post


Link to post

Yes, Fredrik's post has left me totally confused about the nature of infinity, and consequently I am now reassessing my entire system of values. :p

TBH, I think "infinitely thin" is a perfectly acceptable term in informal contexts, and certainly the best way to express the idea in what was a dig at my own horribly imprecise statement.

BTW (back on topic), a new 30uv by Radek Pecka appeared yesterday. While it doesn't break the record, it includes some tricks that haven't been executed before in an unassisted 30uv run.

Share this post


Link to post

One end of the universe to the other is approximately 15 Billion lightyears.

Now, say we're talking about sprites, right?Sprites have no
density whatsoever. More thin than paper. The walls are sprites that are skewed, scaled, and rotated according to the player's FOV, by pulling one block of pixels at a time, which is one reason SNES and 32x Doom have horrible resolutions under emulators. Since TV's have "Natural Anti-Aliasing," meaning the TV blurs it and blends it so much it appears almost half the image's actual width, the dev's can do this alot easier by pulling on bigger blocks and not having to worry about the image appearing too "thick." Cheap lazy-asses ;)

Just a hypothesis :P

Share this post


Link to post

Yeah but the collision detection code doesn't care about the pixel blocks used for rendering, it uses plain 2D geometry.

Share this post


Link to post

I know, I'm just talking about the pseudo-3D code they used.
I've gotta admit, though, that's pretty clever = Rotating+scaling sprites between 2D lines to make a semi-3D game. God, iD is so cool...

Share this post


Link to post
Darkhaven3 said:

More thin than paper.

THAT is what I'm talking about. It is not just more thin than paper. It is thinner than anything because it has no thickness -- that dimension does not exist for the object in question.

Share this post


Link to post

Grazza said:
TBH, I think "infinitely thin" is a perfectly acceptable term in informal contexts, and certainly the best way to express the idea in what was a dig at my own horribly imprecise statement.


Yet some walls in DOOM really can be considered to have a thickness, just like walls in real life. But of course a question about missile collision in DOOM shouldn't be talking about walls.

BTW (back on topic), a new 30uv by Radek Pecka appeared yesterday. While it doesn't break the record, it includes some tricks that haven't been executed before in an unassisted 30uv run.


Cool. He recently did a -fast max, now this.

Share this post


Link to post
mlin said:

I did not include Final Doom since they were not designed by id Software; only marketed by them. I'd like to stay on topic though.


You might as well exclude Thy Flesh Consumed, then.

Share this post


Link to post

I don't think it's the same deal, since Romero headed the episode's development and produced two maps as well.

Share this post


Link to post

Speaking of 30uv1617.lmp, which ports can be used to view this? I tried both prboom and glboom but they both lost sync during map02.

Share this post


Link to post
Optiks said:

Speaking of 30uv1617.lmp, which ports can be used to view this? I tried both prboom and glboom but they both lost sync during map02.

Make sure you're using the latest version and check that your doom2 IWAD is the right one (14604584 bytes).

Share this post


Link to post

I got it working now. I had the latest version and the right wad but for some reason, glboom lost sync with the demo because it wasn't in the prboom directory <shrugs>. Oh well, thanks Fredrik.

Share this post


Link to post

The location of the files shouldn't matter - I regularly use GLBoom with files from several different locations on my HD. Maybe you have more than one version of Doom2.wad, and the location of the files in one case caused the program to choose one that had had, e.g., the nodes rebuilt or the reject map altered (since you mention map02...).

If that was the problem, note that you can specify the iwad in the command line (e.g. -iwad c:\doom2\doom2.wad).

Other ports it plays back with: mbf, eternity (latest version). And tasmbf I imagine, though I haven't watched it with that.

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
Sign in to follow this  
×