TASBot: Difference between revisions
No edit summary |
|||
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 | 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, Eddio made a [[ROMhack]] that allows the game to play back a TAS within itself. This ROM can be injected into [[Virtual Console|Wii VC]] and used to console verify. | ||
===Other consoles=== | ===Other consoles=== | ||
Although Super Mario 64 also can be played on the [[Super Mario 64#iQue (Chinese)|iQue]] console and [[Super Mario 64 DD Version|64DD]] extension, no TASing software exists for these, let alone TASBots. Thus, it is impossible and unnecessary to console verify TASes for these, as none exist anyway. | Although Super Mario 64 also can be played on the [[Super Mario 64#iQue (Chinese)|iQue]] console and [[Super Mario 64 DD Version|64DD]] extension, no TASing software exists for these, let alone TASBots. Thus, it is impossible and unnecessary to console verify TASes for these, as none exist anyway. |
Revision as of 00:49, 1 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, Eddio made a ROMhack that allows the game to play back a TAS within itself. This ROM can be injected into Wii VC and used to console verify.
Other consoles
Although Super Mario 64 also can be played on the iQue console and 64DD extension, no TASing software exists for these, let alone TASBots. Thus, it is impossible and unnecessary to console verify TASes for these, as none exist anyway.