Uploaded August 2016 | Updated November 2026, 3 hours ago
Join the Metroid Prime Speedrunning Discord: discord.gg/VbuzwaShMA
& The Metroid Prime Tool-Assisted Speedrunning Discord: discord.gg/feRzYX3c9Z
This is a tool-assisted speedrun of Metroid Prime completed with an in-game time of 0:37:37.000. (The in-game timer does count milliseconds, I just so happened to end with .000).
Created using Dolphin 4.0-4222 and the original North American (0-00) release of Metroid Prime.
Rerecord count is supposedly 128,969. Dolphin's rerecord counter is a little weird though, using read-only in certain ways seems to sometimes undo rerecords from your movie.
The in-game timer counts upwards any time you have control of Samus. Cutscenes, item collection text, and elevators between areas are some examples of things that do not contribute to in-game time. An argument can be made that a TAS should have the goal of the lowest possible real-time, but the vast majority of people from the Metroid Prime community will agree that real-time strats make for a less interesting watch, as well as a considerably slower in-game time on the mission final screen.
I started this TAS back in March of 2015. Up until around that point, loading times were a huge issue for this game on emulator. Certain tricks just plain don't work if the game loads too fast, things that are consistently console viable weren't an option on older builds of Dolphin. Once I'd done some testing and confirming that this revision did in fact have console-like load time, I dedicated my Spring Break to TASing Frigate. It was about a 60 hour “work week”, streaming almost 10 hours a day for 7 days. (youtube.com/watch?v=UvTG7hy_Rzs)
Shortly after Frigate, RNG started to become an issue and I had dropped the TAS for quite a while. Upon playback, enemies occasionally acted different, sometimes getting in the way or causing a dash angle to be inconsistent, which lead to desyncs. I don't fully understand the what causes the RNG variation, but I found out it could be avoided by making savestates mid-movie and playing back from them, as opposed to playing the movie back from power-on. This recording method is the reason this video isn't in some crazy 1440p 60fps quality like most other major TASes I've done. Being unable to record everything all at once made it much more of a chore to dump in 1440p with all the enhancements on. It's also the reason for some sections being 30FPS and the audio levels being weird. I'm sorry about that.
Anywho, progress up until recently was quite slow and spaced out. I spent a lot of time thinking about route improvements and looking for new glitches instead of actually working on this. In the end, most of my theory routes had issues, some seem potentially solvable, but currently have yet to be. I personally don't believe this route will be optimal in a few years, assuming this game keeps evolving as rapidly as it has been lately. Maybe by then we'll have a Dolphin build with perfect-to-console emulation and no RNG or syncing issues and a more optimized TAS can be made. For now, this is more than good enough for me.
I'd like to thank:
Claris, for helping find addresses and making a user friendly address viewing script. The optimization level on some bosses and even general movement would never have been possible without her help.
Edzan, for sharing his 100% TAS timings and input on various bosses to give me something to compare to and try and improve on.
Venick, for willing to sit on Discord with me for hours on end while I complain and rant as I grind rooms and timed things.
The Onion Bros as a whole, for also letting me hang out with them while I worked on this project.
Kirbymastah, for giving Edzan a shoutout at SGDQ2016 for something that I did.
Aruki, for his amazing Prime World Editor which allowed me to view load triggers and collision and opened a whole new world of optimization and understanding of the inner workings of this game.
The Metroid Prime community as a whole for being there to bounce ideas of off and always be willing to help look for new strats and optimizations.
And df for being df.
Join the Metroid Prime Speedrunning Discord: discord.gg/VbuzwaShMA
& The Metroid Prime Tool-Assisted Speedrunning Discord: discord.gg/feRzYX3c9Z
This is a tool-assisted speedrun of Metroid Prime completed with an in-game time of 0:37:37.000. (The in-game timer does count milliseconds, I just so happened to end with .000).
Created using Dolphin 4.0-4222 and the original North American (0-00) release of Metroid Prime.
Rerecord count is supposedly 128,969. Dolphin's rerecord counter is a little weird though, using read-only in certain ways seems to sometimes undo rerecords from your movie.
The in-game timer counts upwards any time you have control of Samus. Cutscenes, item collection text, and elevators between areas are some examples of things that do not contribute to in-game time. An argument can be made that a TAS should have the goal of the lowest possible real-time, but the vast majority of people from the Metroid Prime community will agree that real-time strats make for a less interesting watch, as well as a considerably slower in-game time on the mission final screen.
I started this TAS back in March of 2015. Up until around that point, loading times were a huge issue for this game on emulator. Certain tricks just plain don't work if the game loads too fast, things that are consistently console viable weren't an option on older builds of Dolphin. Once I'd done some testing and confirming that this revision did in fact have console-like load time, I dedicated my Spring Break to TASing Frigate. It was about a 60 hour “work week”, streaming almost 10 hours a day for 7 days. (youtube.com/watch?v=UvTG7hy_Rzs)
Shortly after Frigate, RNG started to become an issue and I had dropped the TAS for quite a while. Upon playback, enemies occasionally acted different, sometimes getting in the way or causing a dash angle to be inconsistent, which lead to desyncs. I don't fully understand the what causes the RNG variation, but I found out it could be avoided by making savestates mid-movie and playing back from them, as opposed to playing the movie back from power-on. This recording method is the reason this video isn't in some crazy 1440p 60fps quality like most other major TASes I've done. Being unable to record everything all at once made it much more of a chore to dump in 1440p with all the enhancements on. It's also the reason for some sections being 30FPS and the audio levels being weird. I'm sorry about that.
Anywho, progress up until recently was quite slow and spaced out. I spent a lot of time thinking about route improvements and looking for new glitches instead of actually working on this. In the end, most of my theory routes had issues, some seem potentially solvable, but currently have yet to be. I personally don't believe this route will be optimal in a few years, assuming this game keeps evolving as rapidly as it has been lately. Maybe by then we'll have a Dolphin build with perfect-to-console emulation and no RNG or syncing issues and a more optimized TAS can be made. For now, this is more than good enough for me.
I'd like to thank:
Claris, for helping find addresses and making a user friendly address viewing script. The optimization level on some bosses and even general movement would never have been possible without her help.
Edzan, for sharing his 100% TAS timings and input on various bosses to give me something to compare to and try and improve on.
Venick, for willing to sit on Discord with me for hours on end while I complain and rant as I grind rooms and timed things.
The Onion Bros as a whole, for also letting me hang out with them while I worked on this project.
Kirbymastah, for giving Edzan a shoutout at SGDQ2016 for something that I did.
Aruki, for his amazing Prime World Editor which allowed me to view load triggers and collision and opened a whole new world of optimization and understanding of the inner workings of this game.
The Metroid Prime community as a whole for being there to bounce ideas of off and always be willing to help look for new strats and optimizations.
And df for being df.
![TAS: Battle for Bikini Bottom - Any% in 39:20.10 [Visualized]
Welcome to the Visualized version of the Spongebob Squarepants: Battle for Bikini Bottom Any% TAS! Please watch in 60FPS for a full experience 👀
This video was created using an external program to read and display controller inputs/memory addresses alongside the game. The gameplay is identical to the 2020 TAS of Battle for Bikini Bottom, no improvements have been made since its release.
RTA Standard Timing (File Select to Final Cutscene): 39:20.100
TAS Standard Timing (Power-on to “Last Input”): 39:43.750
This TAS was created using Dolphin Emulator. While Xbox is the fastest console to play Battle for Bikini Bottom, it has limited TAS tools. Compared to Xbox, approximately 5 minutes were lost due to GameCube’s slow load screens, deaths, and oob-respawns throughout this run. A perfect conversion of these inputs to Xbox would yield a 34:xx time. (The lack of lag-based tricks also loses some amount of time).
Original Encode (Without Input/Address Viewer):
https://www.youtube.com/watch?v EYZ7dMCRqU
Previous TAS Record - Any% in 1:04:37.066 (2014):
https://www.youtube.com/watch?v=dRtf15EbS9U
Early Game: 0:00
Robo-Sandy (Skip): 9:03
Mid Game: 12:22
Robo-Patrick (Skip): 22:22
Late Game: 26:35
Final Cutscene (End): 39:45
Credits: 42:13
There are a couple of issues with the input display, as the information used to map the display is taken from the games pressed and release events in memory. Because of how the B Button is handled when skipping textboxes, it unfortunately does not display on the input viewer when text boxes are skipped. There is also a bug relating to lag which can cause a button to not register as released, I believe this only happens twice in the video, during SBA the Start Button displays as held for a couple seconds when it shouldnt, and towards the end of Kelp Forest the Z Button does the same.
Thank you: P3BK4C, THC98, Yoshifan for building off each others work to create the tool used to visualize memory and controller inputs.
https://twitter.com/p3bk4c
https://twitter.com/Tales 98
https://twitter.com/yoshifan28
https://github.com/peb-adr/ram-watch-cheat-engine
Thumbnail art by Klyx - https://twitter.com/KlyxTwit
Feel free to stream this TAS on Twitch (or anywhere really) for viewing parties / reaction content :) TAS: Battle for Bikini Bottom - Any% in 39:20.10 [Visualized]](https://i.ytimg.com/vi/67JANjM_nDc/mqdefault.jpg)



![[Ex-WR] TAS: Radical Highway Mission 1 in 1:29:00
NEW World Record: 1:14:82 by myself and THC98 https://www.youtube.com/watch?v=rCDOBrTlJ5A
This is a tool assisted speedrun of Radical Highway mission 1, completed with an in-game time of 1:29.00.
Played on Dolphin version 3.0-735 using the NTSC-U version of Sonic Adventure 2 Battle.
Re-records: 15512
The old TAS world record was held by me - https://www.youtube.com/watch?v=heXL-Ywet2U
The non-TAS world record is held by Son1cgu1tar - http://www.youtube.com/watch?v=4bQmB34PAB0
A few new minor tricks have been found since my last TAS of this level, but most of the time save came from far more extreme optimization. Obviously sub 1:29 is possible, but I wasnt able to achieve such a goal.
If you have any questions please ask them in a comment. Level requests count as questions by the way :) [Ex-WR] TAS: Radical Highway Mission 1 in 1:29:00](https://i.ytimg.com/vi/6zEInPVGvFs/mqdefault.jpg)

![[TAS] Sonic Adventure 2: Battle - Dark Story in 15:30.170 (Visualized)
This is a Tool-Assisted Speedrun (TAS). This was made with savestates, frame advance, RAM watching and Lua scripting to create a theoretically perfect speedrun out of pure love for the game.
Inputs by: FusionVaria, THC98, Brian_pso, and Laze
https://www.youtube.com/@itsPersonnal
https://www.youtube.com/@Tales98
https://www.youtube.com/@brianpso
https://www.youtube.com/@lazeHD
Sonic Adventure Series TAS Discord server: https://discord.gg/awG8CcjQqY
This TAS completes Sonic Adventure 2s Dark Story with a time of 15:30.170. We optimized the TAS for fastest stage completion in real time. Our timing formula ticks when the in-stage timer is moving, it also includes in-stage pauses. (A pause is only used in this TAS if the amount of frames it saves is at least equal to the amount of frames we pause the game for). Our timing does not include menuing from the main menu, load screens, results screens, cutscenes, etc.
Our timing method was inspired by the standard non-TAS timing “LRT” (Load Removed Time). Although LRT typically includes using the main menu, TASing on the Gamecube version means that we can save RTA with a soft reset at the end of each stage. As a result, soft resets enter the next stage sooner, but have to use the menu to select Dark Story after each reset. We decided that counting this menuing towards the final time would create a scenario where soft resetting to save RTA would be penalized for no real benefit. Thus we exclude the main menu from our timing, treating it identically to a cutscene or load screen.
The memory viewer on the left of the video has been reworked for this TAS. This now includes not only the LRT timing as described above, but also visual representations of speed, rotation and status variables. The relative speeds on the left represent the forward, vertical and side speed values relative to the character’s axes, while the global speeds on the right represent the character’s speed values relative to the global X, Y and Z axes. Note that while the relative speeds are uncapped, the global speeds are capped between -16 and +16 in most stages, and between -20 and +20 in Route 280, which are represented by their visuals. The facing angle viewer represents the raw Y rotation variable, where up points to +X, matching the global speed viewer. Gravity angle and tilt are calculated based on the X and Z rotation variables. Gravity tilt represents the angle between global down and the character’s down vector, and gravity angle shows the character’s down vector direction in a top-down view. Lastly, the status matrix viewer, as explained in the video intro, represents the bits in the character’s status bitfield variable, where the main ones were highlighted in the video. All the values in the matrix represent these flags, in order they are shown on screen:
[ Unknown, DisableControl, OnPath/LoopSpeed, DoNextAction ]
[ HoldObject, Attack, LightDash, BallForm ]
[ unused, unused, unused, unused ]
[ ObjectInteract, Hurt, OnObjectCollision, Grounded ]
Huge thank you to Onvar and Tales for working so hard to code this visualizer in such a short timespan. It is simply a thing of beauty. Amazing.
(I highly recommend watching your favorite stages at 0.25x speed, and paying attention to the different watches. You can learn so much from them. Plus theyre just so dang satisfying).
Huge thanks to Laze for helping polish up and add the extra flare to this video. They also worked super tirelessly to get this video put together and rendered out asap once the visualizer was finalized.
Enjoy!!
Stage list:
1:04 Iron Gate
2:45 Dry Lagoon
3:15 Sand Ocean
4:35 Radical Highway
6:12 Egg Quarters
7:02 Lost Colony
9:40 Weapons Bed
11:27 Security Hall
13:00 White Jungle
15:16 Route 280
18:15 Sky Rail
19:49 Mad Space
21:09 Cosmic Wall
25:06 Final Chase [TAS] Sonic Adventure 2: Battle - Dark Story in 15:30.170 (Visualized)](https://i.ytimg.com/vi/7Fza1BZVOs4/mqdefault.jpg)



