117 lines
7.9 KiB
HTML
117 lines
7.9 KiB
HTML
<html>
|
|
|
|
<head>
|
|
<title>Tool Assisted Speedruns</title>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
|
<meta name="generator" content="HelpNDoc Personal Edition 3.6.0.345">
|
|
<link type="text/css" rel="stylesheet" media="all" href="css/reset.css" />
|
|
<link type="text/css" rel="stylesheet" media="all" href="css/base.css" />
|
|
<link type="text/css" rel="stylesheet" media="all" href="css/hnd.css" />
|
|
<!--[if lte IE 8]>
|
|
<link type="text/css" rel="stylesheet" media="all" href="css/ielte8.css" />
|
|
<![endif]-->
|
|
<style type="text/css">
|
|
#topic_header
|
|
{
|
|
background-color: #EFEFEF;
|
|
}
|
|
</style>
|
|
<script type="text/javascript" src="js/jquery.min.js"></script>
|
|
<script type="text/javascript" src="js/hnd.js"></script>
|
|
<script type="text/javascript">
|
|
if (top.frames.length == 0)
|
|
{
|
|
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
|
top.location.href = "fceux.html?" + sTopicUrl;
|
|
}
|
|
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
|
{
|
|
top.FrameTOC.SelectTocItem("ToolAssistedSpeedruns");
|
|
}
|
|
</script>
|
|
</head>
|
|
|
|
<body>
|
|
|
|
<div id="topic_header">
|
|
<div id="topic_header_content">
|
|
<h1>Tool Assisted Speedruns</h1>
|
|
|
|
<div id="topic_breadcrumb">
|
|
<a href="FAQGuides.html">FAQ / Guides</a> ›› </div>
|
|
</div>
|
|
<div id="topic_header_nav">
|
|
<a href="FAQGuides.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
|
|
|
<a href="Troubleshooting.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
|
|
|
<a href="ROMHacking.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
|
|
|
</div>
|
|
<div class="clear"></div>
|
|
</div>
|
|
<div id="topic_content">
|
|
|
|
<p><span class="rvts17">Tool Assisted Speedruns</span></p>
|
|
<p><br/></p>
|
|
<p><span class="rvts16">What is Tool Assisted Speedrunning?</span></p>
|
|
<p><br/></p>
|
|
<p>A tool-assisted speedrun (commonly abbreviated TAS) is a speedrun movie or performance produced with the use of tools such as slow motion and re-recording. The basic premise of these runs is that a "tool" (such as an emulator that provides the author with features that are unavailable in regular playing) is used in order to overcome human limitations such as skill and reflex.</p>
|
|
<p><br/></p>
|
|
<p>Creating a tool-assisted speed run is the process of finding the ideal set of inputs to complete a given criterion - usually completing a game as fast as possible. No limits are imposed on the tools used for this search, but the result has to be a set of timed key-presses that, when played back on the actual console, achieves the target criterion. Traditionally, the only available tool for this was an emulator with re-recording - the ability to use savestate while recording key-presses. However, due to advances in the field, it is now often expected that frame-advance, stepping through emulation one frame at a time, is used. A tool-assisted speed run done without this technique may be criticised as "sloppy play". Before frame-advance became common, playing in slow motion was a common technique, but frame-advance has displaced this.</p>
|
|
<p><br/></p>
|
|
<p>In essence, Tool Assistance allows one to overcome human limitations of skill and reflex in order push a game to its limits. One important thing to remember is that TAS movies are not competing in terms of playing skill, nor do they claim to. </p>
|
|
<p><br/></p>
|
|
<p>For more info on Tool Assisted Speedruns:</p>
|
|
<p><a class="rvts18" href="http://tasvideos.org/">http://tasvideos.org/</a></p>
|
|
<p><a class="rvts18" href="http://tasvideos.org/WhyAndHow.html">http://tasvideos.org/WhyAndHow.html</a></p>
|
|
<p><a class="rvts18" href="http://en.wikipedia.org/wiki/Tool-assisted_speedrun">http://en.wikipedia.org/wiki/Tool-assisted_speedrun</a></p>
|
|
<p><br/></p>
|
|
<p><span class="rvts16">FCEUX TAS features</span></p>
|
|
<p><br/></p>
|
|
<p>FCEUX provides a wealth of tools and resources for creating TAS Movies for NES & FDS games. It features the most current and cutting edge tools for optimizing movies and making the process of movie making quicker an easier.</p>
|
|
<p><br/></p>
|
|
<p><span class="rvts10">Basic Recording features:</span></p>
|
|
<p><a class="rvts18" href="MovieRecording.html">Frame advance, Slow-downs, "bullet-proof" rerecording</a>, <a class="rvts18" href="TASEditor.html">TAS Editor</a></p>
|
|
<p><br/></p>
|
|
<p><span class="rvts10">Advanced Recording features </span></p>
|
|
<p><a class="rvts18" href="Input.html">Input presets</a>, <a class="rvts18" href="AutoFireConfigurations.html">Auto Hold & Auto-Fire</a></p>
|
|
<p><br/></p>
|
|
<p><span class="rvts10">Automated Movie Making Processes</span></p>
|
|
<p><span class="rvts18">Macros & Multi-tracking</span>, <span class="rvts18">Lua scripting</span>, <span class="rvts18">Basic Bot</span>, </p>
|
|
<p><br/></p>
|
|
<p><span class="rvts10">Finding Ram values:</span></p>
|
|
<p><a class="rvts18" href="CheatSearch.html">Cheat Search</a>, <span class="rvts18">RAM Filter</span>, <a class="rvts18" href="HexEditor.html">Hex Editor</a>, <a class="rvts18" href="Debugger.html">Debugger</a>, <a class="rvts18" href="NESRAMMappingFindingValues.html">NES RAM Guide</a></p>
|
|
<p><br/></p>
|
|
<p><span class="rvts10">RAM Monitoring:</span></p>
|
|
<p><a class="rvts18" href="MemoryWatch.html">Memory Watch</a>, <a class="rvts18" href="HexEditor.html">Hex Editor</a></p>
|
|
<p><br/></p>
|
|
<p><span class="rvts10">Movie Splicing Editing</span></p>
|
|
<p><a class="rvts18" href="fm2.html">Text based file format</a></p>
|
|
<p><br/></p>
|
|
<p><span class="rvts16">Movie making</span></p>
|
|
<p><span class="rvts16"><br/></span></p>
|
|
<p>To get started making a Tool Assisted Movie, simply begin recording a movie (see <a class="rvts18" href="MovieRecording.html">Movie Recording</a>). The basic premise of TASing, however, is to use re-records to optimize the execution of a decided upon goal (usually to complete the game as fast as possible). Re-recording is the act of replacing an already recorded part (of a movie) with something else; also called undo.</p>
|
|
<p><br/></p>
|
|
<p>In the making of emulator movies, re-recording is done by loading a savestate of earlier event in the movie and continuing playing from that point. The emulator will update the movie file to undo everything that was cancelled by the savestate loading, and continue recording from that point. The makers of tool-assisted speedruns use re-recording very extensively to reach perfection and to avoid mistakes.</p>
|
|
<p> * In single-segment non-assisted speedruns, re-recording is starting over from beginning. The recording of the failed playing is usually not preserved. </p>
|
|
<p> * In multi-segment non-assisted speedruns, re-recording is starting over from the beginning of current segment. The recording of the failed segment is not preserved. </p>
|
|
<p> * In tool-assisted speedruns, re-recording only undoes a small part of playing. The undone part will not be seen in the resulting movie. A tool-assisted movie may have been re-recorded anything between 50 and 200000 times, depending on the precision of the movie and the difficulty of the game. Often, the same small passage of the game (could be as small as fractions of second long) is attempted tens of times before continuing. </p>
|
|
<p><br/></p>
|
|
<p>For more info on making TAS movies:</p>
|
|
<p><a class="rvts18" href="http://tasvideos.org/CommonTricks.html">http://tasvideos.org/CommonTricks.html</a></p>
|
|
<p><a class="rvts18" href="http://tasvideos.org/GenericTips.html">http://tasvideos.org/GenericTips.html</a></p>
|
|
<p><br/></p>
|
|
<p class="rvps2"><span class="rvts13">Created with the Personal Edition of HelpNDoc: </span><a class="rvts14" href="http://www.helpndoc.com">Free HTML Help documentation generator</a></p>
|
|
</div>
|
|
|
|
<div id="topic_footer">
|
|
|
|
<div id="topic_footer_content">
|
|
2012</div>
|
|
</div>
|
|
</body>
|
|
|
|
</html>
|
|
|