This is incredible. Probably the best example of the capability of ACE to wreck a category even with source requirement rules. I have a few questions out of curiosity: The description says that controllers 2, 3 and 4 write a chunk of assembly code into RAM while the ocarina is being played, is controller 1 doing the same with the notes being played? Also, do you have a rough estimate of how many inputs / notes were played with the ocarina and all controllers used? In the total control video you said that in that situation controllers 1 and 3 could write 1 byte of code per frame, so I assume this would be higher with all of them in use. Finally, are the inputs from controllers 2-4 always working in TAS only speeds during the run as well? Or maybe only in between item pick ups? Anyway, thanks for the effort you've put into this!
Hey I'm glad you enjoyed it :) Writing the code with srm actually breaks into two parts. At first I use controllers 1 and 3 to construct a small payload in a place that's reachable from the addresses currently in the registers (at that point I can't yet reach the place that I want the larger, final payload to go). That's what's happening at the start when you're actually hearing notes played. The job of the small payload is to write the large payload using the analog sticks of controllers 2, 3 and 4, so once it's completed controller 1 holds inputs that jump to the small payload (this is when the ocarina sound becomes a single note). Once that's all done there are a few more instructions in the small payload that set the hook, and we're off to the races. The large payload is 724 bytes. Each (visual) frame, the small payload writes a word formed from the controller 2 and 4 analog sticks to an offset given by the controller 3 analog stick, which means I was able to write the large payload at 4bytes/frame. If I were really going for efficiency I could have made fuller use of both the analog sticks and buttons on controllers 2-4 to get more data/frame, but writing a single instruction each frame was fast enough and less complicated than the alternatives. The other controllers aren't working full-time during the run. The typical setup is that upon arriving in a scene they will quickly arrange for Link to receive an item (this most often means changing an actor's running function + rearranging some other data in their instance). Then when Link has collected the item and is ready to leave, the other controllers will either send him to some entrance or write a set of voidout coordinates and void him. This left plenty of time in between those things for messing around.
uses SRM+filenames to tell the game to read controller inputs as code to execute, and then is constantly writing code with all 4 controllers telling the game what to do next (drastically oversimplified obvs)
@@jmarvins I just watched the video where fierce diety link rides the dog, so basically hes writing code to teleport him to all the chests and get all the stuff?
@@JoJo-ps8ik exactly, along with codes to do random shit for fun, and codes to speed up chest animations or skip cutscenes and so on. everything up to when he goes to the graveyard around 23 mins in is just getting to the point where he can trick the game into reading the file-names as code and executing it, code which says "look at the four controller ports and read what they say as code." from there the controllers are all writing instructions to the game that teleport him to instantly getting every item, along with silly stuff for fun.
the real Kaztalek was the friends we made along the way
28:07 i needed that 8 seconds of reality
24:35 the fun part begins
Saw this on ZFG's twitch and just want to say it was really cool, thanks for putting it together and sharing it.
run starts at 23:00
Kafei's Mask says "Dopefish lives!" but holy shit it is literally one frame of that.
Epilepsy at 37:00
absolutely nuts - fantastic work, and a great unintentional birthday present for me as I turn 24 today :)
This is genius and blloody funny !
very cool and fun to watch, thanks for making it
nice sonic highschool reference
30:15 thats one tall likelike
Thank you so much for Flat Deity Link
36:57 Unused triforce wipe transition
This is so entertaining ty for making it
31:58 2020 mood
uuuuUUUaaagh
this is nuts
Awesomeness
....I have no words-
Man, this is sick
Imagine if ACE was allowed in 100% and 100% became 4 player Zelda runs in both OoT and MM, that would be cool at first then quickly start to suck lol
speeed
Rip mrgrunz's tas
More than half of this run is first cycle
oof, we're sorry that your haunted copy of majora's mask is broken, that is NOT up to our standard of quality. DM us and we'll sort this out!
Nice
That's so crazy, man.
Can the fall damage in the grottos be avoided though?
This was insane
Not enough OoT items strimmer FrankerZ
30:21 Thursday was yesterday though.
This is incredible. Probably the best example of the capability of ACE to wreck a category even with source requirement rules.
I have a few questions out of curiosity:
The description says that controllers 2, 3 and 4 write a chunk of assembly code into RAM while the ocarina is being played, is controller 1 doing the same with the notes being played?
Also, do you have a rough estimate of how many inputs / notes were played with the ocarina and all controllers used? In the total control video you said that in that situation controllers 1 and 3 could write 1 byte of code per frame, so I assume this would be higher with all of them in use.
Finally, are the inputs from controllers 2-4 always working in TAS only speeds during the run as well? Or maybe only in between item pick ups?
Anyway, thanks for the effort you've put into this!
Hey I'm glad you enjoyed it :)
Writing the code with srm actually breaks into two parts. At first I use controllers 1 and 3 to construct a small payload in a place that's reachable from the addresses currently in the registers (at that point I can't yet reach the place that I want the larger, final payload to go). That's what's happening at the start when you're actually hearing notes played. The job of the small payload is to write the large payload using the analog sticks of controllers 2, 3 and 4, so once it's completed controller 1 holds inputs that jump to the small payload (this is when the ocarina sound becomes a single note). Once that's all done there are a few more instructions in the small payload that set the hook, and we're off to the races.
The large payload is 724 bytes. Each (visual) frame, the small payload writes a word formed from the controller 2 and 4 analog sticks to an offset given by the controller 3 analog stick, which means I was able to write the large payload at 4bytes/frame. If I were really going for efficiency I could have made fuller use of both the analog sticks and buttons on controllers 2-4 to get more data/frame, but writing a single instruction each frame was fast enough and less complicated than the alternatives.
The other controllers aren't working full-time during the run. The typical setup is that upon arriving in a scene they will quickly arrange for Link to receive an item (this most often means changing an actor's running function + rearranging some other data in their instance). Then when Link has collected the item and is ready to leave, the other controllers will either send him to some entrance or write a set of voidout coordinates and void him. This left plenty of time in between those things for messing around.
W U T
Can this be done without black screen transitioning.
i can't unhear the donkey kong 64 fade in sound each time the triforce fade in happens.
feels like at anytime there will be the monke doing moon jumping
ZFG sent me
widepeepoHappy
Is it thursday yet?
Great!
*Now make a ROM Hack using ACE*
Lowest Percent sent me
31:31 nice gold skulltulas
yo how the frick does this work?
uses SRM+filenames to tell the game to read controller inputs as code to execute, and then is constantly writing code with all 4 controllers telling the game what to do next (drastically oversimplified obvs)
@@jmarvins I just watched the video where fierce diety link rides the dog, so basically hes writing code to teleport him to all the chests and get all the stuff?
@@JoJo-ps8ik exactly, along with codes to do random shit for fun, and codes to speed up chest animations or skip cutscenes and so on. everything up to when he goes to the graveyard around 23 mins in is just getting to the point where he can trick the game into reading the file-names as code and executing it, code which says "look at the four controller ports and read what they say as code." from there the controllers are all writing instructions to the game that teleport him to instantly getting every item, along with silly stuff for fun.
Well, that was a fun montage. When does the actual run come out? /s
widepeepoHappy