This topic is for the purpose of discussing #882: spezzafer's N64 Super Mario 64 in 16:27.00

Hey look, the auto time calculating thing is still buggy.

Hey look, the auto time calculating thing is still buggy.

The correct numbers should be: 16 minutes and 27 seconds, which is 59220 frames. It got the re-record count right, but I'm not sure where it got 3:07 from. Anyway... whoa! you did that impossible jump after all. The rest was great, too. There's only 1 big problem: maybe it was just something I did, but it looks like you don't pick up the big star at the end to actually end the game...

Yeah, that's the only thing I'm noticing, too... I had to pick up the controller and finish it off myself ^^ Other than that it's gorgeous. I get all excited thinking about the possibility of a 120 star run... hint, hint... Anyway, I've been watching the progress the whole time. This movie was incredibly enjoyable to watch and I look forward for it to become the first published N64 TAS on the site.

Maybe the upload script cut off the last few frames of the movie.

the movie uploaded fine and it does the same thing with the movie on my HD, so I think the emulator may be at fault for some reason it stops at 59190 instead of 59220 and doesn't play the last 30 frames

Well, that could be. I had problems with it throwing out seconds of a Bomberman 64 movie I started.

Hey look, the auto time calculating thing is still buggy.

It got the re-record count right, but I'm not sure where it got 3:07 from.

00C 4-byte little-endian unsigned int: number of frames (vertical interrupts)

I think whoever made the auto-calculate script read the first 2 bytes as big-endian. 3:07 ~11220 frames ~2BD4 in base 16 reverse the bytes: D42B (plus maybe a few 16^2's) 54450 frames ~16 minutes Edit: No, doesn't work out. The file clearly says 54 E7 at 0x00C and reversing it would give 6 minutes.

for some reason it stops at 59190 instead of 59220 and doesn't play the last 30 frames

It's because the frames aren't what matter to it, it's the number of input samples (the count in parentheses). It says your movie only has 28536 input samples, did it go higher than this while recording and then it got cut down to a lower number on playback?

If it didn't, then maybe the game took longer for the same amount of input on playback for some reason.

I've watched it and were amazed, both by the fact that playing N64-movies works so good and how well you performed. As mentioned earlier, you'll have to make sure you take the last big star, anyways, this is well worth a yes vote. I'm also looking forward to seeing more N64 runs, just a question: Is there a place here (with the criterias set for this site) for both 16, 70 and 120 stars run?

If it didn't, then maybe the game took longer for the same amount of input on playback for some reason.

It looks like it simply saved the wrong count of input samples into the final movie. If you change the byte at 0x018 in the movie file from 78 to 7E, (adding 6 to the number of input samples), then it reaches the end correctly, so the input is still there. The procedure the script should be following to get the time is: read the 32-bit integer at 0x0C, which here is 0x54E7 = 59220, and read the 8-bit integer at 0x20, which here is 0x3C = 60, and divide them (59220/60 = 987 seconds = 16 minutes + 27 seconds).

OH MY GOD!! If Jesus played Mario 64 while smoking meth, the result would look something like this.

Yes it's very good, but if anything this made me realize how incredibly impressive the console run of this is.

For the record, the error (in movie length calculation) was that the script read the FPS as 32-bit int, even though it's a 8-bit int.