Superdavo0001 | [TAS] Super Mario 64 - Swingin' In The Breeze In 11"03 By Superdavo0001, Dargos & Snark122 @Superdavo0001 | Uploaded 5 years ago | Updated 2 hours ago
• 11"10 By Snark122 (also 11"17 from 2012): youtu.be/NamWHywBEBY?t=3m30s
↓
• 11"07 by Dargos: youtu.be/HY0Qte37G_I
↓
• 11"03 By Superdavo0001 & Dargos
* Dar Gos' Channel: youtube.com/channel/UCEgfodfjfo3J-bUAHrwl0Lw
* Snark122's Channel: youtube.com/channel/UCyoAdfPdT100F12BmXDUpbw
* TimeTravelPenguin's Channel: youtube.com/channel/UCUMWpmbkD0HvkgFC0BqrTFw
In this video, the star Swingin' In The Breeze (in Rainbow Ride) is collected 2 frames faster than the previous record by Snark, and 1 frame faster than a run created by Dargos earlier today. This was achieved by fully optimising the new movement strat used in the original 1f save.
As was the case for our recent BitFS save, this was done in collaboration with the legendary Dargos, and we both contributed important details that led to this save.
In fact, this save happened in a remarkably similar way to the BitFS improvement (at least if you in include Plush's initial 1f save as an equivalent to Dargos' initial 1f save).
It began with TimeTravelPenguin investigating the star. He asked Snark for his files, and tried to find a way to save time. Unfortunately, his searches didn't find anything improvable, but led me & Dargos to look at Snark's original run more closely. We found that he used some rather unusual movement, which didn't look like it should be optimal, shortly after the ledgegrab. TimeTravelPenguin gave us Snark's run to look at, and Dargos realised that it should be faster to grind continually instead of recovering (Snark's recovery had significantly less speed, costing a lot of distance). When he TASed the run, he found that it saved a frame, and put him quite close to saving an additional frame.
Once Dargos posted that run, I decided to look through it & see whether he did anything that could be improved, and I found a couple of things. The main one was that he took a dust-frame during the initial grind. While this was useful in BitFS, that was only because we couldn't do perfect qframe grinding otherwise. Dargos assumed the same to be true here, and so took the dust-frame to avoid having to take a 1/4 transition. However, I realised that this was actually not the case, and was able to achieve a perfect qf grind. Dargos also jumped for 1 frame before diving to reach the axle (there was probably a reason for this in his run), when it would be faster to dive immediately.
I then fixed all these details, and tried to save a frame with them. Unfortunately though, I was unable to land on the axle a frame earlier, which was needed to save the frame.
Dargos then looked into this, and found that I was just 0.6 units (subject to correct speed manipulation on the jumpdive) from saving the frame, and set to work trying to save them. As was the case in BitFS, he managed to save just enough distance to save the frame, though it's still within a unit or so.
It really is weird just how similar the progression of this star is to the progression of BitFS - in both cases, a slower movement was replaced with divegrinding, which saved a frame, then I found a way to save a qframe, then Dargos finished the save by finding tiny unit-level improvements.
Although this run improves Snark's TAS by 2 frames, it still contains his inputs up to the ledgegrab, and he is therefore still an author. Pretty much all of the inputs that follow (except the grind setup, which has a few frames of my inputs) were done by Dargos. However, as I found the bulk of the most recent frame save, we decided that I should upload the run. Massive thanks to Dargos for letting me upload this one :D
Special thanks to TimeTravelPenguin for , and to Snark122 for giving us TAS files to work from! Their channel links are at the top of this description, along with Dargos' channel. I'd recommend checking them all out, as they've all been responsible for some awesome TASes!
Total re-records: 62,946 (2,527 by me & Dargos, the rest by Snark)
• 11"10 By Snark122 (also 11"17 from 2012): youtu.be/NamWHywBEBY?t=3m30s
↓
• 11"07 by Dargos: youtu.be/HY0Qte37G_I
↓
• 11"03 By Superdavo0001 & Dargos
* Dar Gos' Channel: youtube.com/channel/UCEgfodfjfo3J-bUAHrwl0Lw
* Snark122's Channel: youtube.com/channel/UCyoAdfPdT100F12BmXDUpbw
* TimeTravelPenguin's Channel: youtube.com/channel/UCUMWpmbkD0HvkgFC0BqrTFw
In this video, the star Swingin' In The Breeze (in Rainbow Ride) is collected 2 frames faster than the previous record by Snark, and 1 frame faster than a run created by Dargos earlier today. This was achieved by fully optimising the new movement strat used in the original 1f save.
As was the case for our recent BitFS save, this was done in collaboration with the legendary Dargos, and we both contributed important details that led to this save.
In fact, this save happened in a remarkably similar way to the BitFS improvement (at least if you in include Plush's initial 1f save as an equivalent to Dargos' initial 1f save).
It began with TimeTravelPenguin investigating the star. He asked Snark for his files, and tried to find a way to save time. Unfortunately, his searches didn't find anything improvable, but led me & Dargos to look at Snark's original run more closely. We found that he used some rather unusual movement, which didn't look like it should be optimal, shortly after the ledgegrab. TimeTravelPenguin gave us Snark's run to look at, and Dargos realised that it should be faster to grind continually instead of recovering (Snark's recovery had significantly less speed, costing a lot of distance). When he TASed the run, he found that it saved a frame, and put him quite close to saving an additional frame.
Once Dargos posted that run, I decided to look through it & see whether he did anything that could be improved, and I found a couple of things. The main one was that he took a dust-frame during the initial grind. While this was useful in BitFS, that was only because we couldn't do perfect qframe grinding otherwise. Dargos assumed the same to be true here, and so took the dust-frame to avoid having to take a 1/4 transition. However, I realised that this was actually not the case, and was able to achieve a perfect qf grind. Dargos also jumped for 1 frame before diving to reach the axle (there was probably a reason for this in his run), when it would be faster to dive immediately.
I then fixed all these details, and tried to save a frame with them. Unfortunately though, I was unable to land on the axle a frame earlier, which was needed to save the frame.
Dargos then looked into this, and found that I was just 0.6 units (subject to correct speed manipulation on the jumpdive) from saving the frame, and set to work trying to save them. As was the case in BitFS, he managed to save just enough distance to save the frame, though it's still within a unit or so.
It really is weird just how similar the progression of this star is to the progression of BitFS - in both cases, a slower movement was replaced with divegrinding, which saved a frame, then I found a way to save a qframe, then Dargos finished the save by finding tiny unit-level improvements.
Although this run improves Snark's TAS by 2 frames, it still contains his inputs up to the ledgegrab, and he is therefore still an author. Pretty much all of the inputs that follow (except the grind setup, which has a few frames of my inputs) were done by Dargos. However, as I found the bulk of the most recent frame save, we decided that I should upload the run. Massive thanks to Dargos for letting me upload this one :D
Special thanks to TimeTravelPenguin for , and to Snark122 for giving us TAS files to work from! Their channel links are at the top of this description, along with Dargos' channel. I'd recommend checking them all out, as they've all been responsible for some awesome TASes!
Total re-records: 62,946 (2,527 by me & Dargos, the rest by Snark)
![[TAS] Super Mario 64 - Swingin In The Breeze In 1103 By Superdavo0001, Dargos & Snark122](https://i.ytimg.com/vi/f8xM5fbwUsU/hqdefault.jpg "[TAS] Super Mario 64 - Swingin In The Breeze In 1103 By Superdavo0001, Dargos & Snark122
• 1110 By Snark122 (also 1117 from 2012): https://youtu.be/NamWHywBEBY?t=3m30s
↓
• 1107 by Dargos: https://youtu.be/HY0Qte37G_I
↓
• 1103 By Superdavo0001 & Dargos
* Dar Gos Channel: https://www.youtube.com/channel/UCEgfodfjfo3J-bUAHrwl0Lw
* Snark122s Channel: https://www.youtube.com/channel/UCyoAdfPdT100F12BmXDUpbw
* TimeTravelPenguins Channel: https://www.youtube.com/channel/UCUMWpmbkD0HvkgFC0BqrTFw
In this video, the star Swingin In The Breeze (in Rainbow Ride) is collected 2 frames faster than the previous record by Snark, and 1 frame faster than a run created by Dargos earlier today. This was achieved by fully optimising the new movement strat used in the original 1f save.
As was the case for our recent BitFS save, this was done in collaboration with the legendary Dargos, and we both contributed important details that led to this save.
In fact, this save happened in a remarkably similar way to the BitFS improvement (at least if you in include Plushs initial 1f save as an equivalent to Dargos initial 1f save).
It began with TimeTravelPenguin investigating the star. He asked Snark for his files, and tried to find a way to save time. Unfortunately, his searches didnt find anything improvable, but led me & Dargos to look at Snarks original run more closely. We found that he used some rather unusual movement, which didnt look like it should be optimal, shortly after the ledgegrab. TimeTravelPenguin gave us Snarks run to look at, and Dargos realised that it should be faster to grind continually instead of recovering (Snarks recovery had significantly less speed, costing a lot of distance). When he TASed the run, he found that it saved a frame, and put him quite close to saving an additional frame.
Once Dargos posted that run, I decided to look through it & see whether he did anything that could be improved, and I found a couple of things. The main one was that he took a dust-frame during the initial grind. While this was useful in BitFS, that was only because we couldnt do perfect qframe grinding otherwise. Dargos assumed the same to be true here, and so took the dust-frame to avoid having to take a 1/4 transition. However, I realised that this was actually not the case, and was able to achieve a perfect qf grind. Dargos also jumped for 1 frame before diving to reach the axle (there was probably a reason for this in his run), when it would be faster to dive immediately.
I then fixed all these details, and tried to save a frame with them. Unfortunately though, I was unable to land on the axle a frame earlier, which was needed to save the frame.
Dargos then looked into this, and found that I was just 0.6 units (subject to correct speed manipulation on the jumpdive) from saving the frame, and set to work trying to save them. As was the case in BitFS, he managed to save just enough distance to save the frame, though its still within a unit or so.
It really is weird just how similar the progression of this star is to the progression of BitFS - in both cases, a slower movement was replaced with divegrinding, which saved a frame, then I found a way to save a qframe, then Dargos finished the save by finding tiny unit-level improvements.
Although this run improves Snarks TAS by 2 frames, it still contains his inputs up to the ledgegrab, and he is therefore still an author. Pretty much all of the inputs that follow (except the grind setup, which has a few frames of my inputs) were done by Dargos. However, as I found the bulk of the most recent frame save, we decided that I should upload the run. Massive thanks to Dargos for letting me upload this one :D
Special thanks to TimeTravelPenguin for , and to Snark122 for giving us TAS files to work from! Their channel links are at the top of this description, along with Dargos channel. Id recommend checking them all out, as theyve all been responsible for some awesome TASes!
Total re-records: 62,946 (2,527 by me & Dargos, the rest by Snark)")
![[TAS] Super Mario 64 - Community Freerun In Big Boos Haunt](https://i.ytimg.com/vi/gTXM8dOsmq0/hqdefault.jpg "[TAS] Super Mario 64 - Community Freerun In Big Boos Haunt
Welcome to the latest in a long line of SM64 community freeruns - this time, in the spooky depths of Big Boos Haunt!
Who did what:
• Dargos: 0:00 - 1:04 and 1:52 - 2:00
• Ethan White: 1:04 - 1:52
• CeeSZee: 2:00 - 2:23
• Superdavo0001 (myself): 2:23 - End
This freerun was pretty good imo, and consistently entertaining throughout. My part features my first ever OJ that I routed myself - something which wasnt easy to achieve!
This freerun was done using Peter Fedaks Visible PUs ROMHack, which (as the name implies) makes Parallel Universes visible. This was chosen as it allowed for some interesting tricks to be performed in a PU, which normally wouldnt be entertaining enough to be used due to the whole area being invisible.
Unlike most of my videos, Im not explaining what happened here, to avoid ruining the magic. If anyone is curious, ask me in the comments.
Our channels:
• Superdavo0001 (myself): http://bit.ly/2mgJfkn
• Dargos: http://bit.ly/2xPwAgF
• Ethan White: http://bit.ly/2x2IGE8
• CeeSZee (main host of community freeruns): http://bit.ly/2fxbp8R
Total re-records: 12,646
Also, thanks for 200 subs & 50,000 views!")
![[TAS] SM64: Ztar Attack 2 - DarkRoom% In 2052](https://i.ytimg.com/vi/iSuQVq4vWwM/hqdefault.jpg "[TAS] SM64: Ztar Attack 2 - DarkRoom% In 2052
In this video, I complete SM64 Ztar Attack 2: A Blast To The Past (a ROMHack created by TheGael95), by accessing the dark room and its warp early, in just over 20 seconds. This is achieved by abusing the rooms location to access it from the hubworld using two negative jumps.
This dark room is supposed to be accessed from a warp at the end of the bonus levels, and contains a warp which takes you back to the title screen. From there, you are supposed to re-enter the save & return to the hubworld to collect the final star (hence the warp isnt really the ending as such, so Im not sure whether this category truly counts as a kind of completion). Unfortunately, the warp from the bonus content uses a Mario Spawner object rather than another warp inside the dark-room, and is therefore not reversible.
Conveniently, to save having more separate levels, this room was placed out of reach in the Ztar Seal Temple (hubworld), underneath the central pathway through this area, and inside a grey box to make its location less obvious. I quickly realised this fact once I reached the dark room during my casual playthrough.
Before I found this out, I realised that it was possible to BLJ to extremely high speeds (Over 20,000!), by abusing the slope to the upper platform, and the ceiling of the long arch behind it (this ceiling keeps Mario stuck in place near the top of the stairs). I had also realised that it was possible to use a negative-jump to reach the grey box. After realising that the dark room was inside the grey box, I wondered if it would be possible to do another negative-jump to access the dark room. After a bit of testing, I found a way to make it work, and as a bonus I could even keep my speed once I was down there! Unfortunately, the second negative-jump only works if Mario is not in the squish state (as the vertical displacement is halved in that state), so I have to wait on the grey platform for Marios squish animation to end. I also have to wait a couple of frames before I can jumpkick at the very end, as Mario also cannot jumpkick while squished.
This TAS is probably improvable in a couple of places (though I tried quite hard to optimise the first section to the best of my ability). In particular, its possible that there might be a better hyperspeed route after the BLJ, which might save a considerable amount of time.
Note that at the very end, I cannot quick-crouch into the teleporter (a trick which is used in most TASes that enter teleporters), as its hitbox is too high up for Mario to reach when crouched. Instead, he just crouches underneath it.
So what is this Negative Jump (NJ) Im referring to? Its basically what happens when Mario jumps with a high negative speed. You see, Marios vertical speed is proportional to his horizontal speed. This means that when Mario is moving forwards, he jumps higher than when he is stationary. When he is moving backwards, his jump will be lower. If he has enough negative speed, his vertical speed will never be above zero, and so he will immediately move downwards (assuming he doesnt immediately touch a floor hitbox, which will simply move him back up to the top of the floor). Normally, his downward speed is capped at -75 (terminal velocity), but this does not apply for the first quarter-frame of Marios movement. Thus, with enough negative speed, Mario can be displaced arbitrarily far below his initial location, allowing him to clip into areas far below his initial position. He still moves horizontally though, and so his lateral displacement also needs to be accounted for when planning NJ routes.
Negative-Jumps used to be known as Downward-Jumps (DJs), but the name was changed as the acronym is the same as that for double-jumps, which could lead to confusion. I used this glitch in a previous video, in order to clone blue coins productively without visiting parallel universes (https://youtu.be/QdT27ZpQjR0). Performing this glitch with PU speed (i.e. being displaced into a PU below the main PU grid) causes an overflow jump - a versatile glitch which can allow Mario to reach areas which are higher than his initial location.
SM64 Ztar Attack 2: Blast To The Past is an amazing ROMHack made by TheGael95. Gaels channel (including download links) can be found at: https://www.youtube.com/channel/UCiD6DYZSuu7N2302h83pLeQ
Total rerecords: 2,501")
![[TAS] Super Mario 64: 1 Key in 4:20.77](https://i.ytimg.com/vi/iUt840BUOYA/hqdefault.jpg "[TAS] Super Mario 64: 1 Key in 4:20.77
This tool-assisted speedrun was created by Tyler Kehne, MKDasher, sonicpacker, Snark, SilentSlayers, Gaehne D, Eru, ToT, Plush, sm64expert, Superdavo0001, dar gos & IsaacA.
When played back on an N64 console it completes the game in a time of 4:20.77, 0.17 seconds (5 frames or 10 VIs) faster than the previous record of 4:20.93. This improvement was achieved by changing the camera in both Bowser fights to prevent the game from lagging by keeping particularly complex & CPU-intensive visuals off-screen or far away from the camera. Such complex visuals include:
• Exploding mines
• Bowser bouncing after being hit by a mine
• Bowser exploding & the key spawning in Bowser In The Fire Sea
• The Bowser In The Fire Sea key & associated particles (lags when too close to the camera)
• Falling platforms in Bowser In The Sky
• Bowser (lags when too close to the camera)
While this run is optimised for console playback, it is in fact 5 frames slower when played back on an emulator than the current best time of 4:21.13. These 5 frames are used to change the camera mode back to Mario-cam during the first Bowser fight. This change is required to achieve many of the console-lag saves in this run, but as the emulator does not lag in those areas, changing the camera results in a net time-loss. The current emulator record can be found here:
https://youtu.be/pA6TBsIsraI
The channels of all the authors who created this run can be found here:
• http://www.youtube.com/c/TylerKehne
• http://www.youtube.com/user/MKDasher
• http://www.youtube.com/user/sonicpacker
• http://www.youtube.com/user/snark122
• http://www.youtube.com/user/SilentSla...
• http://www.youtube.com/c/GaehneD
• http://www.youtube.com/user/AruaErueru
• https://www.youtube.com/user/Superdavo0001
• https://www.youtube.com/c/dargos
• https://www.youtube.com/channel/UC0xWE0e79jiWmZucFc_w7sw (IsaacA)
(ToTs channel unfortunately no longer exists)
This is a tool-assisted speedrun, created using slowdown, savestates, memory-watch and various other tools in order to make a sequence of inputs which completes the game as fast as possible with all known techniques. It is *not* a real-time speedrun performed by a human in one shot, and so for obvious reasons will not be counted on any speedrunning leaderboards. For more information on tool-assisted speedruns, what they are & why they exist, check out Bismuths video on the subject: https://youtu.be/Ietk1-Wb7oY
The 1 Key category requires only that the game be completed as fast as possible, with no restrictions. This is optimally achieved by accessing Bowser In The Fire Sea immediately & defeating Bowser there to collect the key to the upstairs area of the castle, before heading to Bowser In The Sky & defeating Bowser once more.
This strategy does not collect any power stars, and abuses multiple glitches to skip through massive chunks of the game. The current best TAS which collects every power star (the 120-star or 100% category) can be found here: https://youtu.be/xL6VE_5PddM
This run is much more intricate & complex than it may look to the untrained eye, and is a product of many years of glitch discoveries & optimisations. If you want to learn more about what is actually going on & how any of this is possible, here are a few places to look:
• Bismuths explanation video about the 1key TAS: https://youtu.be/wjge1bVobN0
• The original TASVideos submission text: http://tasvideos.org/5237S.html
• Tyler Kehnes initial explanation of moat-door skip: https://pastebin.com/uH5GhHbp
Additionally, Im planning to make an alternate version of this TAS with visual-aids to make it easier to see whats going on, so stay tuned for that!
The timesaves in this run were found by Isaac and executed by me. Finding good camera angles & downtime movements to keep the run smooth & entertaining while also avoiding every possible source of console-lag proved to be an interesting challenge, but I hope the result was worth the effort.
Although not a direct author of the run, rcombs deserves a large amount of credit for the latest saves. By using her TASbot to play back the run on an actual console, she was not only able to time the run, but could also determine where exactly in the run any lag occurred, allowing us to fix it more precisely. Her Twitch channel (where she often streams console-verifications) can be found at: https://www.twitch.tv/rcombs
If youre interested in seeing the real-time speedrun world records in Super Mario 64, they can be found here: https://www.speedrun.com/sm64
Finally, if you want to learn more about tool-assisted speedrunning in Mario 64 overall & the many glitches that go into it, Id recommend checking out Ukikipedia - the communitys wiki, at https://ukikipedia.net/wiki/Main_Page.")
![[TAS] SMSR: The Piano Playing Thwomps 933 *WR*](https://i.ytimg.com/vi/jIY2nMf1DbY/hqdefault.jpg "[TAS] SMSR: The Piano Playing Thwomps 933 *WR*
950 by Shredwot: http://youtu.be/lwruu2GZpn8?t=17m58s
↓
933 by me
In this (short) video, I collect the star The Piano Playing Thwomps in 933, beating the previous record by 5 frames. There isnt much to describe in detail really for this one.
The only thing I really need to explain is the main improvement, which is right at the start. Its faster to jump immediately, hold the jump, and dive/recover at the bottom than to kick+jump+roll (as jumping at a nonzero speed will reduce that speed unnecessarily).
I also use a dust-frame on the final thwomp. This is because when landing optimally on the corner, the geometry is too steep to recover on, until you reach a flatter triangle 1f later.
This isnt perfect, not even close. Ill probably work to improve it a bit in the near-future, but one of the more annoying things about this star is that it requires bouncing on two thwomps, both of which use RNG, which determines where they will be when I reach them. Thankfully, I got fairly lucky with little tedious manipulation here, but Im probably not going to optimise this part any time soon (especially when itll have to be re-done with different RNG in a final run anyway). This run was just a proof-of-concept if anything, but I might try to optimise the start a bit more.
Re-records: 1022")
![[TAS] SM64: Ztar Attack Rebooted - A Crezzie Fight+100-coins In 4540](https://i.ytimg.com/vi/jQqwGuWE9dI/hqdefault.jpg "[TAS] SM64: Ztar Attack Rebooted - A Crezzie Fight+100-coins In 4540
Hack created by Aglab2: https://www.youtube.com/channel/UC77uQeQh3PVdbI4usjFg1rA
This TAS collects the star A Crezzie Fight (typo is in-game), as well as the 100-coin star in Creezie Mountain.
I came up with the route for this while messing about with a couple of singlestars for real-time speedrunning. I quickly realised that the placement of a couple of coins near the bully were ideally set up for a star-collection cancel via the springs. As this would likely make a pretty cool TAS, I decided to route it fully, and this is the result!
Although I aimed to make a smooth run, this TAS is likely far from as optimised as most of my other uploads. This is just because fully testing all options takes up a lot of my time, and for such a long run which will have to be redone for any full-game TAS anyway (because of RNG), it didnt seem worth it.
Star-cancel is a glitch which can be caused by interacting with certain objects in ROMHacks after collecting a star. In many cases, these objects change Marios action without checking which action hes in first. This cancels the action (in this case, freefalling after star-collection), allowing Mario to resume normal movement. The objects known to be able to cause this glitch are springs (as in this run), noteblocks, and Fire Freezies (enemies in SM64: Last Impact which can set Mario on fire regardless of state).
One interesting thing about this TAS is that after collecting the star, I have to be pretty careful with the camera (and Marios own position), as moving Mario and/or the camera to the edge of the bully area can make the game very unstable & prone to crashing. I think this is because the music is supposed to change when you leave this area, but this is somehow interrupted by the star-spawn music. In some cases I could trigger a crash after collecting the star, and just before the level faded out!
Total re-records: 2,989")
![[TAS] SM64 Last Impact: Cut-Out Content, 0x A Presses In 4807 [Outdated]](https://i.ytimg.com/vi/jdaidK7lZkA/hqdefault.jpg "[TAS] SM64 Last Impact: Cut-Out Content, 0x A Presses In 4807 [Outdated]
1x A Press by Timestoppa: https://www.youtube.com/watch?v yN8FgvkFVw
↓
0x [untimed] by Craftyawesome: https://www.youtube.com/watch?v=YddgQl2e49A
↓
0x [untimed, faster] by Ethan White: https://www.youtube.com/watch?v=h7jO0NcKekw
↓
0x 5705 by SM64Vids: https://www.youtube.com/watch?v=B2uFA6Fe0sQ
↓
0x 5503 by SM64Vids: https://www.youtube.com/watch?v=yh6-nVCR0Tw
↓
0x 5315 by SM64Vids: https://www.youtube.com/watch?v=S394EB4J8lo
↓
0x 4807 by me
A few days ago I saw that there was a bit of a TAS-race thing happening, with a few people trying to set good times on this level, so I thought Id join in, and optimise it as much as I could manage...
Detailed Description Of The Run
• First, I head to the door, and trigger the cutscene. Not much to say about this part - I tried to optimise it as much as possible, but no special tricks were used. The goal was to hit the trigger ASAP, as that would trigger the rising lava (something I will need to wait for later in the run) as fast as possible, rather than to get fully through the door optimally.
• Next, I climb up to the top of the next part of the path. This wasnt optimised fully, as I had a lot of time to waste. I then do exactly that by front-flipping (can we call it that?), and messing around. I need to wait for the lava to rise to a sufficient height for the next part of the run. You may be thinking I wait longer than necessary for this, but theres a good reason for that...
• Once the lavas sufficiently high, I front-flip and perform a lava-bounce. I then collect the coins on the box, and do another lava-bounce, reaching the next platform, before frame-walking to the top (this method could be faster than the lava-bounce if done properly, but Id only have to wait for the lava again). The coins collected were particularly important, as they did more than just restore the 3 HP from the first bounce - because of the way HP works in SM64, it gives me a delayed health boost just after the second, just barely giving me 4HP, and allowing for one more lava bounce. This trick required me to be moving sufficiently fast after collecting the coins to hit the lava very quickly, so the bounce had to be higher - hence, I had to start it later, when the lava was higher. I do this frame-perfectly.
• Next, I frame-walk up, and activate the next door. It may be possible to clip through the wall to the left, then lava-bounce up, but I think that would be slower.
• After that, I ride the elevator. I mess around a bit to pass time, mainly doing front-flips and quick-turns. The elevator cycle is a huge bottleneck to the run, and would require perhaps 15-30 frames to be saved before the next cycle could be reached (I dont think its possible).
• The next part is crucial to the run. I quick-turn to face the correct direction, front-flip, instantly land, storing 26 vertical speed, punch, pop off the platform, restoring my VS, rise upward, and grab onto the ledge. Nice VSC at the end of the elevator :-)
• Finally, I cross the final part of the level, and collect the star. I couldve waited slightly, and done a DSG glitch to exit the level quicker, but I decided not to, as its technically slower in a single-star context. Maybe Ill do another version of it that way sometime - itd add 2-ish seconds to the run I think, but itd still be a WR.
To finish, I also showed a slow-motion version of the VSC trick - to make it clearer whats happening in those few frames.
Rerecords: 2316
I might take a short break from TASing for a few days or so, just to give me time to work on other hobbies and uni-stuff. I may post non-SM64 videos in the near-future as well.
If youre interested in photography, it may also be worth checking out my Instagram page here: https://www.instagram.com/overyourhead_photography/?hl=en
Thanks for watching, and dont forge to subscribe!")
