Submission Text Full Submission Page
  • hourglass-r90 used.
  • SHA1: 72b04284e3e8a4af9fa9fb6a0c85c2718e2f2db5
  • BIOS: American Megatrends International, LLC. 1.I0, 2024/12/27
  • IWBTG any%(JP Ruleset) 12:10


TASVideoAgent
They/Them
Moderator
Joined: 8/3/2004
Posts: 15979
Location: 127.0.0.1
Spikestuff
They/Them
Expert player (2776)
Joined: 10/12/2011
Posts: 6514
Location: The land down under.
Loud game is loud. Amplify(0.25) is used in the temp encode below. Input overshoots by a lot as pointed out by the author, should be a 12:10.54 (maybe sooner if a jump can hold momentum). Link to video And I believe the site grabbed the framerate wrong as Hourglass reports it being 50fps.
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account. Something better for yourself and also others.
Player (74)
Joined: 4/1/2016
Posts: 304
Location: Cornelia Castle
I think the time is correct for the submission, since you need to move out of the way to avoid the final fruit.
DJ Incendration Believe in Michael Girard and every speedrunner and TASer!
Editor, Experienced player (530)
Joined: 11/8/2010
Posts: 4055
Thanks Spikestuff for verifying and making an encode. I verified it as well, on the standard .exe available on the author's site. I don't know why our site parser detected 51 FPS as Hourglass does show 50. The site calls this "NTSC 50 (Obsolete)", but it can't be obsolete as we have a current publication using this framerate (also marked 50 "Obsolete").
Editor, Skilled player (1392)
Joined: 3/31/2010
Posts: 2125
Thanks for the encode, Spikestuff! Ooh, this is neat. Some missed shots at the bosses look a bit unclean, but overall this run was highly entertaining. I also don't have any reason to assume the run loses time because of that. I didn't realize just how much of this game can be skipped. Very nice work, yes vote.
Editor, Active player (472)
Joined: 2/11/2018
Posts: 248
2012 TAS with (I think) the same ruleset, for possible comparison. Link to video In the IWBTG thread there's mention of a way to glitch the credits to get the final input sooner. Is that done in the submission?
CoolKirby wrote:
I don't know why our site parser detected 51 FPS as Hourglass does show 50.
The 4 bytes at 0x014 in the movie file = 51. Haven't checked inside Hourglass. Edit: Site parser has been fixed now

1743262470