History of the TTC upwarp: Difference between revisions

Jump to navigation Jump to search
m
More cleanup.
m (Fixed formatting, oops)
m (More cleanup.)
Line 6: Line 6:


== August 4, 2015 ==
== August 4, 2015 ==
pannenkoek2012 put a $1000 bounty on the glitch. It was thought to be an unknown hangable ceiling glitch. The hypothesis was later superceded by the random bit flip hypothesis. (See August 5, 2015)<br>
Pannenkoek2012 put a $1000 bounty on the glitch. It was thought to be an unknown hangable ceiling glitch. The hypothesis was later superceded by the random bit flip hypothesis. (See August 5, 2015)<br>
<br>
<br>
https://www.youtube.com/watch?v=X5cwuYFUUAY<br>
https://www.youtube.com/watch?v=X5cwuYFUUAY<br>
Line 15: Line 15:
https://www.youtube.com/watch?v=X5cwuYFUUAY (description)<br>
https://www.youtube.com/watch?v=X5cwuYFUUAY (description)<br>


pannenkoek2012: "The random bit flip hypothesis shown in this video is just the current leading hypothesis. Before that, it was the ceiling seams, and before that the bob-omb/explosion/coin, and before that landing on the platform/wall at the same frame. Frankly, a gamma ray happening to flip a particular bit seems a bit far-fetched to me. It's completely possible that some in-game mechanic treats the height float like an integer and decrements it, thus decreasing that bit from a 1 to a 0, in which case the glitch would be reproducible, and the bounty would be awarded to the person who submits that. The bounty is not rewarded for hypotheses as to what caused the upwarp, otherwise the bob-omb or ceiling hypotheses would have "solved" it long ago."<br>
Pannenkoek2012: "The random bit flip hypothesis shown in this video is just the current leading hypothesis. Before that, it was the ceiling seams, and before that the bob-omb/explosion/coin, and before that landing on the platform/wall at the same frame. Frankly, a gamma ray happening to flip a particular bit seems a bit far-fetched to me. It's completely possible that some in-game mechanic treats the height float like an integer and decrements it, thus decreasing that bit from a 1 to a 0, in which case the glitch would be reproducible, and the bounty would be awarded to the person who submits that. The bounty is not rewarded for hypotheses as to what caused the upwarp, otherwise the bob-omb or ceiling hypotheses would have "solved" it long ago."<br>


Following that was an ECC discussion.<br>
Following that, ECC was discussed. See: September 16, 2018<br>
See: September 16, 2018<br>


== August 8, 2016 ==
== August 8, 2016 ==
Dane creates a program that makes frame perfect TASing easier, by overlaying the video on top of the emulator to compare frame by frame.<br>
Dane created a program that made frame perfect TASing easier, by overlaying the video on top of the emulator to compare frame by frame.<br>


https://www.youtube.com/watch?v=TD1-b3-60xY<br>
https://www.youtube.com/watch?v=TD1-b3-60xY<br>
Line 30: Line 29:


"LilithFaery: It happened to me once when i was playing this game for the first time maybe. Well i was still very young and i couldn't understant what had just happened... and i think i died because i panicked."<br>
"LilithFaery: It happened to me once when i was playing this game for the first time maybe. Well i was still very young and i couldn't understant what had just happened... and i think i died because i panicked."<br>
https://media.discordapp.net/attachments/311313032108048395/372553117767565312/image.png?width=903&height=120<br>
<br>
<br>
https://www.reddit.com/r/gaming/comments/6uxwdj/til_theres_1000_on_the_line_for_anyone_who_can/<br>
https://www.reddit.com/r/gaming/comments/6uxwdj/til_theres_1000_on_the_line_for_anyone_who_can/<br>


== May 8, 2017 ==
== May 8, 2017 ==
upwarp_pole channel is created, and pannen puts 3 of his main videos regarding the topics there.<br>
The #upwarp_pole channel was created in the discord server "SM64 TASing and ABC", and Pannen put 3 of his main videos regarding the topics there.<br>


== May 12, 2017 ==
== May 12, 2017 ==
Notchmath talks of doing a full frame perfect TAS run of Dota_Teabag's speedrun.<br>
Notchmath talked of doing a full frame perfect TAS run of Dota_Teabag's speedrun.<br>


== October 1, 2017 ==
== October 1, 2017 ==
Sidney makes a synced audio version of the upwarp footage.<br>
Sidney made a synced audio version of the upwarp footage.<br>
<br>
<br>
https://www.youtube.com/watch?v=mLQQPKXPx94<br>
https://www.youtube.com/watch?v=mLQQPKXPx94<br>


== February 21, 2018 ==
== February 21, 2018 ==
Dota_Teabag (TeabagSRL) comments on the bitflip video, and suggests it could've been a cartridge tilt.<br>
Dota_Teabag (TeabagSRL) commented on the bitflip video, and suggested it could've been a cartridge tilt.<br>
<br>
<br>
"For what its worth (This is Dota_Teabag), I often had to tilt my cartridge weird ways in order to get the game to start. It seemed if i had it all the way pressed down sometimes it wouldn't start, but if i pulled it up on one side ever so slightly, it would start just fine. So if you think that is a possible factor, it is worth considering that fact."<br>
"For what its worth (This is Dota_Teabag), I often had to tilt my cartridge weird ways in order to get the game to start. It seemed if i had it all the way pressed down sometimes it wouldn't start, but if i pulled it up on one side ever so slightly, it would start just fine. So if you think that is a possible factor, it is worth considering that fact."<br>
Line 53: Line 51:


== June 4, 2018 ==
== June 4, 2018 ==
Dane sucessfully gets Dota to deliver the N64 and Mario game for hardware testing.<br>
Dane sucessfully got Dota to deliver the N64 and Mario game for hardware testing.<br>
<br>
<br>
SM64 TASing and ABC discord - #upwarp_pole<br>
SM64 TASing and ABC discord - #upwarp_pole<br>
<br>


== July 29, 2018 ==
== July 29, 2018 ==
The tests take place. Dane can't recreate the upwarp on Dota's console. Basic mulmul tests were also performed.<br>
The tests on Dota's cartridge took place. Dane couldn't recreate the upwarp on Dota's console. Basic mulmul tests were also performed.<br>
<br>
<br>
Info on Mulmul here:
Info on Mulmul here:
Line 72: Line 69:


== September 16, 2018 ==
== September 16, 2018 ==
ECC is discussed as it would disprove the bitflip hypothesis. More info here: https://en.wikipedia.org/wiki/ECC_memory<br>
ECC was discussed as it would disprove the bitflip hypothesis. More info here: https://en.wikipedia.org/wiki/ECC_memory<br>
<br>
<br>
Some confusion occurred after users used the VR4400 manual to assume ECC exists in VR4300 too. (VR4300 is the processor used by the N64) It was later discovered that VR4300 didn't have ECC.<br>
Some confusion occurred after users used the VR4400 manual to assume ECC exists in VR4300 too. (VR4300 is the processor used by the N64) It was later discovered that VR4300 didn't have ECC.<br>
<br>
<br>
<br>
According to the [http://datasheets.chipdb.org/NEC/Vr-Series/Vr43xx/U10504EJ7V0UMJ1.pdf "VR4300, VR4305, VR4310 64-Bit Microprocessor User Manual"],<br>
~From the VR4300, VR4305, VR4310 64-Bit Microprocessor User Manual:<br>
 
<br>
"However, this is a function used by the VR4400 to
process an ECC error in an exception handler. This function is defined to maintain
the compatibility of the VR4300 with the VR4400 because the VR4300 does not
have an ECC and a parity function"<br>
<br>
"VR4300 does not have a parity check function, however, its parity error register
"VR4300 does not have a parity check function, however, its parity error register
(26) and cache error register (27) do not practically operate. These registers are
(26) and cache error register (27) do not practically operate. These registers are
Line 90: Line 81:
"Because the VR4300 does not check data by using a cache parity, a parity error
"Because the VR4300 does not check data by using a cache parity, a parity error
exception does not occur."<br>
exception does not occur."<br>
<br>
http://datasheets.chipdb.org/NEC/Vr-Series/Vr43xx/U10504EJ7V0UMJ1.pdf<br>


== September 29, 2018 ==
== September 29, 2018 ==
A bruteforcer was proven to work to find a glitch where the racing penguin slid off the slide. They tried the same thing for the TTC upwarp, but it wouldn't reproduce the glitch.<br>
A bruteforcer was proven to work to find a glitch where the racing penguin slid off the slide. They tried the same program for the TTC upwarp, but it wouldn't reproduce the glitch.<br>
<br>
<br>
"This situation is similar to that surrounding the TTC upwarp glitch in that we had footage of the glitch being done, but not a TAS recreation of it. But in this case, we actually were able to reproduce the glitch just from footage of it, whereas the TTC upwarp glitch still hasn't been reproduced. For the record, we've also tried brute forcing the TTC upwarp, but that didn't end up reproducing the glitch."<br>
"This situation is similar to that surrounding the TTC upwarp glitch in that we had footage of the glitch being done, but not a TAS recreation of it. But in this case, we actually were able to reproduce the glitch just from footage of it, whereas the TTC upwarp glitch still hasn't been reproduced. For the record, we've also tried brute forcing the TTC upwarp, but that didn't end up reproducing the glitch." - Pannen, description from [https://www.youtube.com/watch?v=kpnBKNZ2YUs CCM Racing Penguin Falling Off the Slide]<br>
<br>
<br>
https://github.com/danebou/Fuzzy64 (Bruteforcer source code)<br>
https://github.com/danebou/Fuzzy64 (Bruteforcer source code)<br>
https://clips.twitch.tv/AlertStrangeMetalRiPepperonis (original video)<br>
https://clips.twitch.tv/AlertStrangeMetalRiPepperonis (original video)<br>
https://www.youtube.com/watch?v=kpnBKNZ2YUs (description)<br>

Navigation menu