TASBot: Difference between revisions
No edit summary |
m (→Wii (U) VC) |
||
| Line 13: | Line 13: | ||
TASBots are used for a phenomenon called console verification. The N64 has [[Super Mario 64#Wii VC|some properties]] that make it crash more often than emulators like Mupen. This means that a TAS that plays back fine on Mupen may actually crash on console. This is not desired, and so many important TASes, especially those utilizing [[PU]] movement, have been console verified, such as [[Watch for Rolling Rocks#A Button Challenge|Watch for Rolling Rocks 0.5x A presses]]<ref>https://www.youtube.com/watch?v=kI8iC_WL-Bw</ref> and the [[1 Key]] TAS<ref>https://www.youtube.com/watch?v=-rTBD3eTK8s</ref>. | TASBots are used for a phenomenon called console verification. The N64 has [[Super Mario 64#Wii VC|some properties]] that make it crash more often than emulators like Mupen. This means that a TAS that plays back fine on Mupen may actually crash on console. This is not desired, and so many important TASes, especially those utilizing [[PU]] movement, have been console verified, such as [[Watch for Rolling Rocks#A Button Challenge|Watch for Rolling Rocks 0.5x A presses]]<ref>https://www.youtube.com/watch?v=kI8iC_WL-Bw</ref> and the [[1 Key]] TAS<ref>https://www.youtube.com/watch?v=-rTBD3eTK8s</ref>. | ||
===Wii (U) VC=== | ===Wii (U) VC=== | ||
There is no known way to make a TASBot for the Wii or Wii U, due to inconsistent input polling. Thus, TASes made using Dolphin or a [[Mupen64#Mupen64-WiiVC-RTZ|hacked version of Mupen]] cannot be console verified using a TASBot. However, | There is no known way to make a TASBot for the Wii or Wii U, due to inconsistent input polling. Thus, TASes made using Dolphin or a [[Mupen64#Mupen64-WiiVC-RTZ|hacked version of Mupen]] cannot be console verified using a TASBot. However, a [[ROMhack]] by Eddio allows the game to play back a TAS within itself. It is possible to inject this into a Wii WAD, which makes TASes made for Wii VC console-verifiable. This method does not work for Wii U VC. | ||
===Other consoles=== | ===Other consoles=== | ||
Revision as of 15:03, 22 October 2018
|
A TASBot is a replay device that can play back the common *.m64 (TAS) files that Mupen64 creates on a physical Nintendo 64 (N64). TASbots work by imitating the inputs of a real controller, but they are not identical to normal N64 controllers.
TASBots in the Discord Server
There are currently four people who own TASBots in the SM64 TASing and ABC server.
Those members are:
Uses of TASBots
Console Verification
TASBots are used for a phenomenon called console verification. The N64 has some properties that make it crash more often than emulators like Mupen. This means that a TAS that plays back fine on Mupen may actually crash on console. This is not desired, and so many important TASes, especially those utilizing PU movement, have been console verified, such as Watch for Rolling Rocks 0.5x A presses[1] and the 1 Key TAS[2].
Wii (U) VC
There is no known way to make a TASBot for the Wii or Wii U, due to inconsistent input polling. Thus, TASes made using Dolphin or a hacked version of Mupen cannot be console verified using a TASBot. However, a ROMhack by Eddio allows the game to play back a TAS within itself. It is possible to inject this into a Wii WAD, which makes TASes made for Wii VC console-verifiable. This method does not work for Wii U VC.
Other consoles
Super Mario 64 can also be played on the iQue console, but since the iQue is a handheld console it is impossible to make a TASBot for it without modifying the console.
A rare development version of Super Mario 64 exists for the 64DD extension, though only 1 such copy of the game exists. Though no TASing software exists for the 64DD, a regular N64 TASBot could theoretically be used to play back movies on it.