initial upload of English version of TAS Editor Manual
[[Split portion of a mixed commit.]]
This commit is contained in:
ansstuff
parent
4a98f4339e
commit
fe45494191
|
|
@ -0,0 +1,226 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>6. Advanced Features</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("AdvancedFeatures");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>6. Advanced Features</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="BeginnersGuide.html">Beginner's Guide</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="BeginnersGuide.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="ProgramCustomization.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="Reference.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Advanced Features</span></p>
|
||||
<p class="rvps2"><span class="rvts36"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts36"><br/></span></p>
|
||||
<p class="rvps14"><a class="rvts27" href="AdvancedFeatures.html#ProjectsSharing">1. How to share projects.</a></p>
|
||||
<p class="rvps14"><a class="rvts27" href="AdvancedFeatures.html#UsingPatterns">2. Patterns usage.</a></p>
|
||||
<p class="rvps14"><a class="rvts27" href="AdvancedFeatures.html#UsingMarkers">3. Effective usage of Markers.</a></p>
|
||||
<p class="rvps14"><a class="rvts27" href="AdvancedFeatures.html#UsingLua">4. Lua usage.</a></p>
|
||||
<p class="rvps10"><span class="rvts22"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="ProjectsSharing"></a>
|
||||
<span class="rvts48"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">1. How to share projects.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">A Taseditor project is saved to disk as an .fm3 file. All essential aspects of the work process are saved into this file, making it possible to restore the postponed work in its exact state. The size of such "instant snapshot" may be pretty huge (depending on the Greenzone size, it may take hundreds of megabytes).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you want to publish your project in the Internet (for example, as a TASVideos submission), it's better to share only the most important information, but not the whole snapshot of your working process. To do that, choose </span><span class="rvts25">File -> Save Compact</span><span class="rvts21"> in Taseditor's main menu. The "Save Compact" window will appear, prompting you to select which aspects you want to save to the new FM3 file.</span></p>
|
||||
<p class="rvps10"><img align="left" alt="" style="padding : 6px;" src="lib/save-compact.png"/></p>
|
||||
<p class="rvps10"><span class="rvts25">Binary format of Input</span><span class="rvts21"> – save movie Input in binary form. This option is related to fm2 format, which is the base of the fm3 format. If you uncheck it, Input will be saved to the fm3 file in text format, which will increase file size but leave the possibility to edit it in any text editor. However, Taseditor is much better suited for editing movies, so it's recommended to keep that checkbox set, and avoid changing FM3 projects outside Taseditor. Anyway, in non-compact fm3 projects (saved regular way) Input is always stored in binary.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Markers</span><span class="rvts21"> – save Markers to the file. The movie Input is always saved to fm3 file, because without it emulator won't be able to open fm3 files. But without Markers the movie replay is still possible, so you can uncheck the checkbox if you don't want to share them. Although this way your fm3 won't differ much from an fm2 movie, so it's recommended to leave that checkbox checked, to share all current Markers and their Notes in the compact project. The file size will increase insignificantly.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Bookmarks</span><span class="rvts21"> – save all Bookmarks and their branches data to the file. It's recommended to leave this option checked. The file size will increase insignificantly.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Greenzone</span><span class="rvts21"> – save Greenzone to the file, including all savestates and the Lag Log. The file size will increase dramatically! Greenzone is the main factor causing huge project file size. It's recommended to keep this option unchecked. If during the compact saving the Playback cursor is at the very first frame of the movie, there will be no single Greenzone savestate in the fm3 project. But if the cursor was left at some frame in the middle of the movie, the compact fm3 will contain one Greenzone savestate, allowing to restore the emulator state on the Playback cursor frame when you open the project. Since one savestate uses very little disk space, the file is still compact.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">History</span><span class="rvts21"> – save History Log to the file. The file size will increase by several megabytes. Usually there's no need to publish the data. So it's recommended to uncheck this option. When you open an fm3 project with no History Log, Taseditor creates a new History automatically.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Piano Roll</span><span class="rvts21"> – save current position of vertical scrolling of the Piano Roll, in order to see the exact segment of the movie after loading the compact fm3 file. The file size will increase insignificantly, so you may keep that option checked.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Selection</span><span class="rvts21"> – save all Selection data to the file. Both current Selection and whole Selection History is saved. The file size will increase insignificantly, but usually there's no need to publish the data. So it's recommended to uncheck this option.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Using compact saving you can get an fm3 project being less than 500KB in size, while still sharing all essential data the recipient may need. For example, if you are working in co-authorship with another TASer(s), you will need to share not only Input, but also Markers and Bookmarks. As for the Greenzone, the recipient can recreate it by replaying the project movie in Taseditor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">On compact saving, your project name receives the "-compact" suffix. Compact saving doesn't replace normal project saving, so if you have any unsaved changes in the project, the asterisk in the window caption will not disappear after Save Compact.</span></p>
|
||||
<p class="rvps10"><img align="left" alt="" style="padding : 6px;" src="lib/export-to-fm2.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">Besides saving a compact fm3 you can also export movie data to fm2 format, accepted at TASVideos before Taseditor even existed. But in such files you will share only Input. To do that, choose </span><span class="rvts25">File -> Export to FM2</span><span class="rvts21"> in Taseditor's main menu. The "Export to FM2" window will appear, prompting you to choose target movie type (1P, 2P, Fourscore).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Since FM2 format also supports text subtitles, you can use existing Marker Notes as a source for generating movie subtitles. For that, enable the "Convert Marker Notes to Movie Subtitles" checkbox. Then while watching the fm2 file the viewers will see text messages appearing when passing certain frames (the frames where your project had Markers at). If necessary, you can then convert those fm2 subtitles into the commonly used .srt format to post the TAS on Youtube. To do that, right-click the FCEUX window while replaying the subtitled movie and choose "Dump Subtitles to SRT file" command.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">FM2 files can be opened in Taseditor similarly to loading fm3 projects. In the "Open TAS Editor Project" window (</span><span class="rvts25">File -> Open</span><span class="rvts21">) switch to the filter "All Files (*.*)" and then choose your fm2 movie file. Taseditor will bring the message box saying that this is not a project file, and will ask confirmation. After you click "Yes" it will create new project using Input and settings from the fm2 file.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Also, you can import Input from any fm2 or fm3 file using </span><span class="rvts25">File -> Import Input</span><span class="rvts21">. This time no new project will be created, but Input of current project will be replaced with Input from the file. This operation is very similar to pasting Input from the Clipboard, it is registered in History Log and can be undone by </span><span class="rvts30">Ctrl + Z</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="UsingPatterns"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">2. Patterns usage.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When editing Input, TASer actually creates a unique sequence of presses and releases for every button of joypad. But, despite the uniqueness, this large sequence still contains many typical segments, which are are short sequences of presses and releases that repeat many times in succession, or appear many times in different places of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To speed up the work, you can remember the most typical or frequent sequences as </span><span class="rvts37">patterns</span><span class="rvts21">, to be able to put them with a couple of clicks, not drawing every single buttonpress manually each time.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Patterns are useful in several cases:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">when one sequence is frequently used in the movie (for example, an accurate alternation of pressing and releasing the </span><span class="rvts29">B</span><span class="rvts21"> button)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when you need the same sequence for several buttons (for example, alternating </span><span class="rvts29">L</span><span class="rvts21"> and </span><span class="rvts29">R</span><span class="rvts21">)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when a certain sequence needs to be drawn (or redrawn) many times (for example, making a running start by tapping </span><span class="rvts29">R</span><span class="rvts21"> twice)</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21">Some of the most obvious patterns are already added by author. To add your own pattern you need to edit the </span><span class="rvts20">taseditor_patterns.txt</span><span class="rvts21"> file in any text editor (like Notepad), this file is stored in </span><span class="rvts20">/tools</span><span class="rvts21"> subfolder of FCEUX main folder. Every second line in this file constitutes an encoded sequence of button states. The code is straightforward: "button pressed" is encoded by 1, "button released" – by 0.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Every pattern is looped, which means, when a long sequence of Input is created using a short pattern, the pattern is repeated the necessary amount of times to fill the whole given interval.</span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/patterns-menu.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">After adding or editing the patterns file, restart Taseditor to reread the file changes. The list of all available patterns is always in the upper right corner of the TAS Editor window. To change the current pattern, enter that menu and click the needed pattern name. For easy orientation in patterns it's recommended to call each pattern by a distinct name that reflects its in-game meaning.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To apply current pattern, Taseditor needs to know the beginning and the end of the interval where the chosen button is going to be pressed and released according to the rule. There are 3 different ways to apply a pattern:</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Example 1. </span><span class="rvts21">Point and click the start frame (click in any Piano Roll column except the icons column), thus selecting that frame. Then hold the </span><span class="rvts30">Alt</span><span class="rvts21"> key and left-click the end frame in the column of the button you are editing. In the interval between those two frames you will get the needed sequence of the chosen button presses. This method is rather handy when the start frame is already selected by previous clicks in Piano Roll, and you only need to to hold down </span><span class="rvts30">Alt</span><span class="rvts21"> and click the end frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Example 2. </span><span class="rvts21">Left-click the start frame in the column of the button you are editing, and hold the mouse button to start drawing. Hold </span><span class="rvts30">Alt</span><span class="rvts21"> and move the mouse cursor up or down. This way you will be </span><span class="rvts37">drawing</span><span class="rvts21"> the pattern sequence of buttonpresses.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Example 3. </span><span class="rvts21">Select a range of frames, then hold </span><span class="rvts30">Alt</span><span class="rvts21"> and left-click on the edited button symbol in the Piano Roll Header. The pattern will be applied to the selected area.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When using traditional method of TASing you are also able to apply patterns to recorded sequences, although in a less convenient manner. To do that you should set the "</span><a class="rvts27" href="Toolbox.html#UsePattern">Use pattern</a><span class="rvts21">" checkbox on Recorder panel. Before that you may want to record the buttons you don't need to alternate (record them without using patterns), and then record the needed button(s) with pattern, using the "Superimpose" function for the segment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">For example, you need to record a burst of fire while jumping over the pit. At first, record that jump without shooting, then return the Playback cursor to the beginning of the segment (by jumping to the Bookmark left here), check "Superimpose" and "Use pattern", hold the </span><span class="rvts29">B</span><span class="rvts21"> button and unpause the emulation. You'll see how the shooting Input superimposes over jump Input.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Before Taseditor there was the "Autofire" concept similar to patterns. But due to inconveniences of the Recording method that feature was rarely used, because when you are typing Input it's usually easier to press and release the needed buttons manually. So if you stick to traditional method of TASing, you won't likely use patterns. But in the non-linear or semi-automatic TASing, patterns are drawn as quickly as regular buttonpresses, so that's where they can really speed up the work.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Patterns are used when creating sequences for a single button. But when you want to use a typical macro involving several buttons, use Copy/Paste.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="UsingMarkers"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">3. Effective usage of Markers.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Markers exist to simplify complicated situations by structurizing the problem. When the game requires you to perform (or think over) several complex actions, you should break the large segment into separate intervals, in order to understand clearly where one action stops and another one starts. Even if the initial subdividing appears to be wrong, it still helps you to get thoughts in order.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Obviously, you are not expected to set Markers on commonplace segments, most of which aren't even polished (e.g. where it's enough to hold </span><span class="rvts29">R</span><span class="rvts21"> to win). But key moments and memorable situations of the movie should be marked and commented with Notes. It will help you to keep the whole picture of the project in mind and navigate the movie by text.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">No need to write works of literature inside the Notes. You may just confine yourself with simple label words, numbers, tags. Invent the words on the fly, but try to keep systematic approach. As in, if at the beginning of the first level (on the transition screen) you've set a Marker with the Note "level 1 start", you should also write "level 2 start" at the beginning of the second level, and not "act II begin" or something. During the creation of TAS you naturally form a unique glossary in your mind using various terms that are topical for that specific game. And the more systematic approach you apply to writing the Notes, the easier it will be to describe another (similar) segment and understand its task. The easier it'll be to find similar Input segments, recalling only their vague in-game appearance.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The tasks you meet in video games are often repeatable. Details and environment may be different, but player actions remain more or less the same. In some cases you can just copy the Input (solution of the similar task) from the previous level, and it will successfully sync with the new in-game situation (probably after a little adjustment). Though, after the copy/paste it's recommended to diversify the Input to prevent the TAS viewers from noticing the repetition and getting bored.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">For example, at the beginning of many levels in Super Mario Bros you need to use the same button sequence to accelerate to maximum speed optimally. Let's imagine, you are honestly commenting Input during TASing. Then in World 1-1 in the acceleration section you probably left a Note with words like "acceleration" or similar. Now, when you start creating Input for a segment with that task again, in a new level you put a Marker at the beginning of the segment and write a Note, describing your current task. Obviously enough, you are going to use the word "acceleration" there as well, because you need to accelerate.</span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-selection.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">And that's where you can use Taseditor's function of automatic searching for similar Notes. Leave the Playback cursor inside the current segment and press the "</span><span class="rvts29">Similar</span><span class="rvts21">" button at the bottom of the Toolbox. The Selection cursor will instantly jump to the Marker that contains the most resembling Note, in Taseditor's opinion. Most likely, it will be the Marker left at the beginning of the acceleration segment in the World 1-1. Therefore you can instantly select all Input in that segment by pressing </span><span class="rvts30">Ctrl + A</span><span class="rvts21">, then copy the Input to the Clipboard (</span><span class="rvts30">Ctrl + C</span><span class="rvts21">), return to the current segment (press </span><span class="rvts30">Shift</span><span class="rvts21"> twice) and paste from the Clipboard (</span><span class="rvts30">Ctrl + V</span><span class="rvts21">).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If the first search result doesn't bring you to the intended segment, you can press the "</span><span class="rvts29">More</span><span class="rvts21">" button to try next result of the search. Usually the right segment is among the first offered finds, granted that you marked the segment with a sensible Note.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Interesting fact: while writing the Note for the second appearance of the acceleration segment, you use the word "acceleration" without an intent to correlate to previous cases, but only according to the in-game situation. So you are not expected to actually remember the text of old Notes. The right words will come to your mind in the right time.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This way, right during the TASing process you form a </span><span class="rvts25">library of useful Input combinations</span><span class="rvts21">, not unlike the pattern list described above, except that you don't have to purposely prepare the button sequences – they appear natural way during the segments shaping and optimization, and they are stored inside the movie, not in an external file. And when you improve a combination for some segment (e.g. find a faster way to accelerate), you can easily find and fix all related segments with similar button sequence. Also, here you don't have to remember the exact description or the name of the needed sequence, because, if you use systematic approach to describe tasks, the words will partially match (and a perfect match is not required, since the searching algorithm is rather smart).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The auto-search is also useful when you need to jump between two (or more) related segments, located far from each other in the movie. Scrolling the Piano Roll with the mouse wheel or jumping through dozens of Markers from one segment to another is not as handy as clicking the "</span><span class="rvts29">Similar</span><span class="rvts21">" or "</span><span class="rvts29">More</span><span class="rvts21">" button. To let the algorithm instantly find the twin segment (or the</span><span class="rvts37"> source</span><span class="rvts21"> segment and the </span><span class="rvts37">destination</span><span class="rvts21"> segment), consider using some unique word in their Notes, one that isn't used in other places of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">For example, in the "Megaman" game each robot master must be beaten twice (second time it's in the end of the game). It's logical to suppose that both battles will be entitled by Marker Notes containing the name of the robot and the word "boss" or "fight", or something like that. As a result, when the Playback cursor is in one of those 2 places, pressing the "</span><span class="rvts29">Similar</span><span class="rvts21">" button will get you to another one.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In this example the proper words for the Notes text are no-brainer, yet they are unique enough not to repeat in other places (at least not in that combination), so the auto-search will work perfectly. In a different case you may have to invent a unique label, but usually the first description you think of is enough.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/find-note.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">You can also use standard search for Note text. For example, it's common to leave a Note beginning with the "TODO" word at some places where you are not sure the best solution is found (the segment Input is optimal). So, when you have mood to make fixes, you could skim through all Markers with that tag by bringing the "Find Note" window (</span><span class="rvts30">Ctrl + F</span><span class="rvts21">) and typing the word "TODO" to search for.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you don't like all these big ideas with Markers, you can TAS without them. After all, many games provide rather simple tasks for a TASer, they don't require a highly organized approach to the solving process. If the problem can be solved on impulse, don't spend time on preparation and fortification. Markers provide advantages only in long-term goals.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">So, just like in programming, in most cases you can successfully write the so-called "dirty code" (here it would be a project without Markers and Notes) that is fast to create, but hard to maintain and extend. Or you can make a lovingly formatted project which is nice to watch and modify. Since TASers have to modify their movies very often (in order to beat previous records), the today's time costs for the project formatting are likely to be repaid by the fact that the looks of the project motivate to continue the work on it.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="UsingLua"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">4. Lua usage.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">With the Lua language you can write scripts that can be executed by FCEUX along with game emulation. Writing scripts requires minimal programming skill, while the range of possibilities is pretty huge. You can create your own TAS tools, modify the game at the time of execution, have access to images and sound on the fly, send data via network or record it to disk, etc. And you can make custom extensions for TAS Editor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To master the Lua language completely you would need to read its documentation and gain actual experience, but for making simple scripts it should be enough to read this Manual and the </span><a class="rvts27" href="http://www.fceux.com/web/help/fceux.html?LuaScripting.html" target="_blank">Lua chapter in FCEUX docs</a><span class="rvts21">. At first, try to run scripts created for FCEUX by various people. They are stored in the </span><span class="rvts20">/luaScripts</span><span class="rvts21"> subfolder. Each script is a text file with </span><span class="rvts20">.lua</span><span class="rvts21"> extension, such file may be created and modified in any text editor. Before running scripts you need to open some game ROM in FCEUX. To run a script, open the Lua console (</span><span class="rvts25">File -> Lua -> New Lua Script Window</span><span class="rvts21">), in this window press the "</span><span class="rvts29">Browse</span><span class="rvts21">" button and load the script file, then press "</span><span class="rvts29">Run</span><span class="rvts21">". If emulator is paused, either unpause it or advance a frame to activate the script. As for the Lua console, the window may be hidden or minimized.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Program code in Lua scripts for FCEUX usually consists of 2 parts: the first part is executed once the script is activated, another part runs on certain emulation events, such as the end of a frame emulation, loading a savestate and so on.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The first part, which runs on script activation, is usually executed only once (unless you made an infinite loop in it). The code is executed line by line, from top to down. Usually the task of that part is to initialize global variables and register functions to be launched by FCEUX when certain events occur.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In most of cases the main code of the script is contained in the single function that is automatically executed at the end of every frame. For example, this is how Mario hitbox drawing code for SMB may look:</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps10"><table width="98%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid;"><p class="rvps2"><span class="rvts50">marioWidth = 16</span></p>
|
||||
<p class="rvps2"><span class="rvts50">marioHeight = 32</span></p>
|
||||
<p class="rvps2"><span class="rvts50"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts50">function everyframe()</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50">marioX = memory.readbyte(0x3AD)</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50">marioY = memory.readbyte(0xCE)</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50">gui.drawbox(marioX, marioY, marioX + marioWidth, marioY + marioHeight)</span></p>
|
||||
<p class="rvps2"><span class="rvts50">end</span></p>
|
||||
<p class="rvps2"><span class="rvts50"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts50">emu.registerafter(everyframe)</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When activating this script, FCEUX creates and initializes two variables ("marioWidth" and "marioHeight"), then registers the function called everyframe() to the "frame end" event (registerafter). After that the text ends and the script finishes its execution, but the registered function remains in emulator memory, and if you unpause it or press </span><span class="rvts26">Frame Advance</span><span class="rvts21">, after every frame it will run the code stored within the everyframe() function. That code consists of 3 lines. The first two create variables for the hitbox position and initialize them with current values from RAM of the emulated console. The third line draws graphics over the game picture output.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Actual RAM addresses can be found in public resources (like </span><a class="rvts27" href="http://tasvideos.org/GameResources/NES/SuperMarioBros.html" target="_blank">http://tasvideos.org/GameResources/NES/SuperMarioBros.html</a><span class="rvts21">) or found on your own using the Cheat Search tool or the RAM Search tool built in FCEUX. In this case we know that Mario's X position is stored in memory address 0x3AD, and his Y position is in 0xCE. So, the script just takes their current values and draws the rectangle in the corresponding screen position. Sometimes there's need to recalculate the values to translate the in-game world coordinates into on-screen coordinates, but in this case they match.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The standard functions readbyte(), drawbox() and other useful functions are described in the </span><a class="rvts27" href="http://www.fceux.com/web/help/fceux.html?LuaFunctionsList.html" target="_blank">FCEUX documentation</a><span class="rvts21">. It also describes how to use mathematical expressions and make loops and conditions.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The standard functions available only when Taseditor is engaged are listed in the </span><a class="rvts27" href="LuaAPI.html">Reference</a><span class="rvts21">. Using all this knowledge you can not only draw and write messages over the emulator screen, but also control Playback and Selection, and most importantly, modify the movie Input and Markers.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">For example, this code copies one joypad Input to the second one's place:</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps10"><table width="98%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid;"><p class="rvps2"><span class="rvts50">function doCopy()</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50">selection_table = taseditor.getselection()</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50">if (selection_table ~= nil) then</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50"> </span><span class="rvts50">for i = 1, #selection_table do</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50"> </span><span class="rvts50"> </span><span class="rvts50">selected_frame = selection_table[i]</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50"> </span><span class="rvts50"> </span><span class="rvts50">joypad1data = taseditor.getinput(selected_frame, 1)</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50"> </span><span class="rvts50"> </span><span class="rvts50">taseditor.submitinputchange(selected_frame, 2, joypad1data)</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50"> </span><span class="rvts50">end</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50"> </span><span class="rvts50">taseditor.applyinputchanges("Copy 1P->2P")</span></p>
|
||||
<p class="rvps2"><span class="rvts50"></span><span class="rvts50"> </span><span class="rvts50">end</span></p>
|
||||
<p class="rvps2"><span class="rvts50">end</span></p>
|
||||
<p class="rvps2"><span class="rvts50"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts50">taseditor.registermanual(doCopy, "Copy 1P to 2P")</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When launching this script, FCEUX registers the doCopy() function to the event of pressing the "</span><span class="rvts29">Run function</span><span class="rvts21">" button (registermanual). Now any click on the button will run the code of that function, consisting of 9 lines. At first, the function gets information about Selection from Taseditor, and if it's not blank (i.e. at least one frame is selected in the Piano Roll) it runs the FOR loop, going through all the selected frames from the first to the last. For each selected frame the function requests the Input of the first player from Taseditor (and stores this data to the "joypad1data" variable), then it submits the claim to change the second player Input for that frame. All these submissions are accumulated in Taseditor memory until the FOR loop ends, after that they all are applied by calling the applyinputchanges(). As a result, the second joypad in the selected range of frames contains the same Input as the first joypad.</span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/lua-run-manual.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">This simple script is already a useful mini-tool that may be needed when making a TAS for 2 or more players. Launch it, and while TASing you will be able to select a range of frames in the Piano Roll and click the "</span><span class="rvts29">Copy 1P to 2P</span><span class="rvts21">" button (or press the "</span><span class="rvts25">Run Manual Lua function</span><span class="rvts21">" hotkey) to synchronize both players. Every time the script work results in an Input change, the Greenzone is automatically truncated, and a new item is added to the History Log, allowing you to undo the changes done by the script. This way you've got a feature completely integrated into Taseditor, and you've programmed the behavior of the feature yourself.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Even though you can successfully TAS without Lua knowledge, its support can save you much time and even hint on a less obvious solutions during the Input optimization (or more exactly, during the game Output analysis).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Videogames often hide important details of the situation, and TASer has to watch memory state directly in order to know for sure what's going on and to precisely perceive the optimality factors while polishing segments.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">For example, many games don't show boss HP on screen. So, to know exactly the damage you inflict, you need to watch the numeric value of the corresponding RAM address in the Memory Watch window. And when there is a plenty of hidden factors (for example, several timers of invulnerability and boss attack, and some special counters of the player character), TASer needs to watch and analyze many memory addresses as they change according to different rules. In this case an on-screen visualization of some data would be huge helper. For example, boss HP can be displayed as a bar or a number above his head, and a red color can indicate the damage frames or other events. As a result, your mind is relieved by moving from deciphering an abstract data format to the format that instantly delivers the main idea (e.g. "the boss was damaged", "good/bad").</span></p>
|
||||
<p class="rvps10"><span class="rvts21">So it's recommended to learn Lua at least to the level of being able to sensibly modify others' scripts. For the long time FCEUX existed, people wrote and published a lot of scripts serving for various purposes, and you'll probably only need to change some RAM addresses to adjust a script to your game. Oftentimes it also makes sense to ask for help at </span><a class="rvts27" href="http://tasvideos.org/forum/viewforum.php?f=25" target="_blank">TASVideos forums</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Taseditor guide is over. If you were reading carefully, you should now know everything necessary to make a TAS up to the high standards of TASVideos. The only thing left is to gain an experience in real work, master some actions to automatism in order to feel no trace of routine and have fun from the process of armed playthrough and investigation of games.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/help-authoring-tool">Single source CHM, PDF, DOC and HTML Help creation</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,97 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Beginner's Guide</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("BeginnersGuide");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Beginner's Guide</h1>
|
||||
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="Title.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="Introduction.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Beginner's Guide</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">This part of the documentation is presented in the form of a textbook on TASing.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It explains the practice of using Taseditor and describes the mechanism of conventional TASing methods.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The course will be useful both to people who wish to learn TASing and to already experienced TASers who are open to new trends and wish to improve their knowledge.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Introduction.html">Introduction</a></p>
|
||||
<p class="rvps12"><span class="rvts24">General overview of TAS Editor's goals and features</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="ProgramInterface.html">Program Interface</a></p>
|
||||
<p class="rvps12"><span class="rvts24">Learning the fundamentals of the program usage</span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Navigation.html"><br/></a></p>
|
||||
<p class="rvps10"><a class="rvts23" href="TASingProcess.html">TASing Process</a></p>
|
||||
<p class="rvps12"><span class="rvts24">The author's vision of the competent working process</span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Operations.html"><br/></a></p>
|
||||
<p class="rvps10"><a class="rvts23" href="TASingMethodology.html">TASing Methodology</a></p>
|
||||
<p class="rvps12"><span class="rvts24">Dissection of the Input improvement methods</span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="LuaAPI.html"><br/></a></p>
|
||||
<p class="rvps10"><a class="rvts23" href="ProgramCustomization.html">Program customization</a></p>
|
||||
<p class="rvps12"><span class="rvts24">Detailed review of all settings</span></p>
|
||||
<p class="rvps10"><span class="rvts23"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="AdvancedFeatures.html">Advanced Features</a></p>
|
||||
<p class="rvps12"><span class="rvts24">Describing the additional possibilities</span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour/create-ebooks-for-amazon-kindle">Full-featured Kindle eBooks generator</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,499 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Controls</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("Controls");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Controls</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="Reference.html">Reference</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="Reference.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="Glossary.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="Navigation.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Controls</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Taseditor is controlled by </span><a class="rvts27" href="Controls.html#mouse">mouse</a><span class="rvts21"> and </span><a class="rvts27" href="Controls.html#keyboard">keyboard</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Every operation can be done in several alternative ways (via menu, hotkey or GUI element).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Any action can be done using mouse, but some are faster to do with keyboard. The Manual assumes that one hand of user is holding the mouse and other hand is placed on a side of the keyboard, occasionally holding </span><span class="rvts30">Shift</span><span class="rvts21">/</span><span class="rvts30">Ctrl</span><span class="rvts21">/</span><span class="rvts30">Alt</span><span class="rvts21"> or pressing a key combination.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Some actions (e.g. switching </span><span class="rvts21">"Follow cursor")</span><span class="rvts21"> can be done by mouse only.</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="mouse"></a>
|
||||
<span class="rvts6"><br/></span></p>
|
||||
<p><span class="rvts53">Mouse controls</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps25" style="text-indent: 30px"><a class="rvts51" href="Controls.html#mouseover">pointing with mouse</a></li>
|
||||
<li class="rvps25" style="text-indent: 30px"><a class="rvts51" href="Controls.html#leftbutton">left mouse button</a></li>
|
||||
<li class="rvps25" style="text-indent: 30px"><a class="rvts51" href="Controls.html#rightbutton">right mouse button</a></li>
|
||||
<li class="rvps25" style="text-indent: 30px"><a class="rvts51" href="Controls.html#middlebutton">middle mouse button</a></li>
|
||||
<li class="rvps25" style="text-indent: 30px"><a class="rvts51" href="Controls.html#wheel">mouse wheel</a></li>
|
||||
</ul>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><a name="mouseover"></a>
|
||||
<span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">Pointing with mouse</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">A. </span><span class="rvts34">Displaying Bookmarks screenshots and descriptions</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Hover mouse cursor over the right half of Bookmarks List to see the game screenshot of the bookmarked frame in the movie branch you're pointing at. Optionally there can be a description of the branch under the screenshot.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">B. </span><span class="rvts34">Displaying information of the Bookmark</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Hover mouse cursor over an icon of any Bookmark in the Branches Tree to see the information about the Bookmark (real time of creation, bookmarked frame, full timeline, screenshot and description). When you point at a Bookmark that doesn't belong to the timeline of current movie branch, mouse cursor changes to arrow with question mark.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">C. </span><span class="rvts34">Illuminating button symbols in the Piano Roll Header</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Hover mouse cursor over a button symbol in the Piano Roll Header to see if you can change the movie by clicking this symbol. When some rows of Piano Roll are selected, symbols in the Header will illuminate on mouse hover.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="leftbutton"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">Left mouse button</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The main button.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">A. </span><span class="rvts34">Standard Windows actions</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Most of GUI elements of TAS Editor window are controlled the same way as in other Windows applications.</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">press a button by left-click (also works with progressbar, "Bookmarks/Branches" caption and "Marker #" labels)</span><span class="rvts21"> – fires on button press</span></li>
|
||||
<li class="rvps10"><span class="rvts21">check/uncheck checkboxes and radiobuttons</span><span class="rvts21"> – fires on button release</span></li>
|
||||
<li class="rvps10"><span class="rvts21">open the window menu, choose menu item, set/remove ticks from menu items</span></li>
|
||||
<li class="rvps10"><span class="rvts21">scroll Piano Roll or History Log using progressbars</span></li>
|
||||
<li class="rvps10"><span class="rvts21">move or resize TAS Editor window</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">B. </span><span class="rvts34">Moving Playback cursor</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on any row in the "Icons" column of Piano Roll to send Playback cursor to the frame pointed. If you hold the left mouse button, you can drag the Playback cursor up and down. This way you can even move Playback cursor into frames outside currently visible area of the movie. Just try dragging the cursor below or above Piano Roll – the farther you lead the mouse, the faster will be scrolling and Playback rewinding.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">C. </span><span class="rvts34">Selecting rows in Piano Roll</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on a frame number in the "Frame#" column of Piano Roll to select this frame and remove selection from other frames (if there was any selection before). </span><span class="rvts21">If you hold the left mouse button, you can stretch the selection by moving mouse up or down.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you need to append new selection to an already existing selection, hold </span><span class="rvts30">Ctrl</span><span class="rvts21"> while clicking on a frame number. This way you can select several non-overlapping segments. Also this way you can remove some parts of existing Selection, just hold </span><span class="rvts30">Ctrl</span><span class="rvts21"> while clicking on a selected frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you hold </span><span class="rvts30">Shift</span><span class="rvts21"> instead of </span><span class="rvts30">Ctrl</span><span class="rvts21">, the click will select a region of frames starting from the beginning of previous Selection.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you hold </span><span class="rvts30">Alt</span><span class="rvts21">, the click will select rows using current Pattern.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">D. </span><span class="rvts34">Setting/unsetting Input in Piano Roll</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Point mouse cursor at needed cell of Input (find crossing point of needed frame row and needed button column) and press left mouse button. The Input in this cell changes at the moment you press the button. Empty cell will become occupied and vice versa.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The row containing this cell will become selected, and other Piano Roll rows will become unselected. This feature ensures that Selection cursor always appears in the context of Input editing.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you hold the left mouse button, you can draw or erase Input in other cells of Piano Roll by moving mouse cursor over them. Drawing starts when you click on an empty cell, erasing starts by clicking on an occupied cell.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you hold </span><span class="rvts30">Shift</span><span class="rvts21"> while clicking on a cell, the Input change will apply to all frames from Selection cursor to the row containing the cell. Selection cursor won't move this time.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you hold </span><span class="rvts30">Alt</span><span class="rvts21"> instead of </span><span class="rvts30">Shift</span><span class="rvts21">. the click will set Input (</span><span class="rvts21">from Selection cursor to the row containing the cell) </span><span class="rvts21">as on current Pattern. </span><span class="rvts21">Selection cursor won't move this time.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">E. </span><span class="rvts34">Setting/unsetting Input using the Header of Piano Roll</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on a button symbol </span><span class="rvts21">in the Piano Roll Header to change the Input of this button in selected frames. If no frames are selected, nothing will happen. If in some of the selected frames the button in not set, the click will set the button in all selected frames. If the button is set in all selected frames, the click will unset the button in all selected frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you hold </span><span class="rvts30">Alt </span><span class="rvts21">while clicking on a button symbol, </span><span class="rvts21">the click will the button Input in selected frames </span><span class="rvts21">as on current Pattern</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you click on the </span><span class="rvts21">"Frame#" label, the click will apply to Markers instead of Input.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">F. </span><span class="rvts34">Creating and moving Markers</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Double-click on a frame number in Piano Roll to set Marker to this frame. </span><span class="rvts21">If you hold the left mouse button, you can drag the Marker freely. Release the button to leave the Marker at the frame number it was held over. This way you can move Markers from place to place. If you release the Marker over Input columns, the dragging will be cancelled, and the Marker will return to the frame it was picked from. If you release the Marker over another Marker, those two Markers will switch places.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you release the Marker outside Piano Roll, this Marker will be dumped. Thus, to remove a Marker, double-click on it and drag it somewhere outside TAS Editor window.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">G. </span><span class="rvts34">Entering/exiting Note editing mode</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on the upper or the lower edit field to start editing Note text displayed in this field at the moment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To finish editing (and save changes) click on anything outside the edit field.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">H. </span><span class="rvts34">Controlling the Bookmarks List</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on a frame number in Bookmarks List (on the left side of the list) to send Playback cursor to the frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on a time indicator in Bookmarks List (on the right side of the list) to restore movie state saved into the Bookmark and send Playback cursor to the bookmarked frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Those operations fire on the left button release.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">I. </span><span class="rvts34">Controlling the Branches Tree</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on icon of a Bookmark to send Playback cursor to the bookmarked frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Double-click on icon of a Bookmark to restore movie state saved into the Bookmark and send Playback cursor to the bookmarked frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Those operations fire on the left button press.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">J. </span><span class="rvts34">Controlling the History Log</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on any row of the History Log to </span><span class="rvts21">restore movie state to the point of time when the Log record was created.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="rightbutton"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">Right mouse button</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">A. </span><span class="rvts34">Moving Playback cursor with mouse wheel</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Hold right button and roll the mouse wheel up or down to move Playback cursor respectively.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Mouse cursor can be anywhere over the TAS Editor window or emulator main window.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">B. </span><span class="rvts34">Scrolling the Piano Roll</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Place mouse cursor over the Piano Roll, hold right button and move mouse cursor anywhere outside the Piano Roll to scroll visible area to the side. This is especially useful for horizontal scrolling, because using scrollbar would be too slow.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">C. </span><span class="rvts34">Setting a Bookmark</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Right-click on a row of the Bookmarks List to set the Bookmark to the frame where Playback cursor currently is.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Alternatively, right-click on icon of a Bookmark in the Branches Tree to set the Bookmark to the frame where Playback cursor currently is.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Those operations fire on the right button release.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">D. </span><span class="rvts34">Context menu</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Right-click on a frame number of any selected frame in the Piano Roll to bring the context menu containing the following items:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps26" style="margin-left: 0; text-indent: 30px"><span class="rvts39">Set Markers</span></li>
|
||||
<li class="rvps26" style="margin-left: 0; text-indent: 30px"><span class="rvts39">Remove Markers</span></li>
|
||||
<li class="rvps26" style="margin-left: 0; text-indent: 30px"><span class="rvts39">Deselect</span></li>
|
||||
<li class="rvps26" style="margin-left: 0; text-indent: 30px"><span class="rvts39">Select between Markers</span></li>
|
||||
<li class="rvps26" style="margin-left: 0; text-indent: 30px"><span class="rvts39">Ungreenzone</span></li>
|
||||
<li class="rvps26" style="margin-left: 0; text-indent: 30px"><span class="rvts39">Clear</span></li>
|
||||
<li class="rvps26" style="margin-left: 0; text-indent: 30px"><span class="rvts39">Delete</span></li>
|
||||
<li class="rvps26" style="margin-left: 0; text-indent: 30px"><span class="rvts39">Insert</span></li>
|
||||
<li class="rvps26" style="margin-left: 0; text-indent: 30px"><span class="rvts39">Insert # of Frames</span></li>
|
||||
<li class="rvps26" style="margin-left: 0; text-indent: 30px"><span class="rvts39">Clone</span></li>
|
||||
<li class="rvps26" style="margin-left: 0; text-indent: 30px"><span class="rvts39">Truncate movie</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Scrollbars and Note editing fields also have their own context menus.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="middlebutton"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">Middle mouse button</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The middle mouse button serves one major role – to pause and unpause emulator, no matter where mouse cursor is The button</span><span class="rvts21"> fires on button press.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When emulator is paused, pressing the middle mouse button will unpause it (same as pressing </span><span class="rvts26">Pause</span><span class="rvts21"> hotkey). Moreover, if there is the green arrow outside Greenzone in Piano Roll, the middle-click will launch seeking to the frame with the green arrow (same as pressing </span><span class="rvts26">Restore Playback</span><span class="rvts21"> hotkey).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you hold </span><span class="rvts30">Shift </span><span class="rvts21">while mid-clicking, this will launch seeking to the nearest Marker.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you hold </span><span class="rvts30">Ctrl </span><span class="rvts21">while mid-clicking, this will either launch seeking to Selection cursor (if it's below Playback cursor) or re-watch the movie segment starting from Selection cursor (if it's above Playback cursor).</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When emulator is unpaused, </span><span class="rvts21">pressing the middle mouse button will pause it (same as pressing </span><span class="rvts26">Pause</span><span class="rvts21"> hotkey).</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Usually the middle mouse button is the mouse wheel.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="wheel"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">Mouse wheel</span></p>
|
||||
<p class="rvps10"><span class="rvts46"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The wheel can be rolled up and down with different speed. When you need precision, roll the wheel slowly. When you need speed, roll the wheel quickly.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">A. </span><span class="rvts34">Scrolling the Piano Roll or History Log</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When mouse cursor is over the History Log, roll the mouse wheel to scroll visible area of the History Log.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When mouse cursor is anywhere else, roll the mouse wheel to scroll visible area of the Piano Roll.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">B. </span><span class="rvts34">Moving Playback cursor</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Hold right mouse button and roll the mouse wheel up or down to move Playback cursor respectively.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you want to always see the Playback cursor position in Piano Roll, check the "Follow cursor" checkbox in the Playback section of TAS Editor window.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">C. </span><span class="rvts34">Jumping on Markers</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This is similar to pressing </span><span class="rvts29"><<</span><span class="rvts21"> and </span><span class="rvts29">>></span><span class="rvts21"> buttons or using </span><span class="rvts30">Ctrl</span><span class="rvts21">/</span><span class="rvts30">Shift</span><span class="rvts21"> + </span><span class="rvts30">Page Up</span><span class="rvts21">/</span><span class="rvts30">Page Down </span><span class="rvts21">hotkeys.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Hold the </span><span class="rvts30">Shift</span><span class="rvts21"> key and roll the wheel to make jumps with Playback cursor. The Piano Roll will follow it if </span><span class="rvts21">the "Follow cursor" checkbox</span><span class="rvts21"> is checked.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Hold the </span><span class="rvts30">Ctrl</span><span class="rvts21"> key and roll the wheel to make jumps with Selection cursor. The Piano Roll will follow it automatically.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">D. </span><span class="rvts34">Crossing gaps</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Point mouse cursor to any member of a long column of buttonpresses or to an empty cell among other empty cells in its neighborhood, then hold the </span><span class="rvts30">Alt</span><span class="rvts21"> key and roll the wheel up or down to scroll the Piano Roll in such a manner that mouse cursor immediately appears before the upper end or after the lower end of the column / emptiness.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This allows you to quickly navigate among long sequences of Input.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The same approach can be used to find previous/next Markers (when mouse cursor is over the column with frame numbers) and Bookmarks (when it's over the icons column).</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="keyboard"></a>
|
||||
<span class="rvts6"><br/></span></p>
|
||||
<p><span class="rvts53">Keyboard controls</span></p>
|
||||
<p class="rvps2"><span class="rvts36"><br/></span></p>
|
||||
<p class="rvps5"><img alt="" style="padding : 1px;" src="lib/keyboard-all-keys.png"/></p>
|
||||
<p class="rvps5"><span class="rvts36"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps25" style="text-indent: 30px"><a class="rvts56" href="Controls.html#modifiers">modifiers (Shift, Ctrl, Alt)</a></li>
|
||||
<li class="rvps25" style="text-indent: 30px"><a class="rvts56" href="Controls.html#accelerators">accelerator hotkeys</a></li>
|
||||
<li class="rvps25" style="text-indent: 30px"><a class="rvts56" href="Controls.html#hotkeys">FCEUX hotkeys</a></li>
|
||||
<li class="rvps25" style="text-indent: 30px"><a class="rvts56" href="Controls.html#virtual_joypad">virtual gamepad</a></li>
|
||||
</ul>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><a name="modifiers"></a>
|
||||
<span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">Modifiers (Shift, Ctrl, Alt)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you hold one of these keys the functions of left mouse button and mouse wheel change.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts30">Shift</span><span class="rvts21"> is responsible for Playback cursor navigation and for selecting whole region of frames.</span></li>
|
||||
<li class="rvps10"><span class="rvts30">Ctrl</span><span class="rvts21"> </span><span class="rvts21">is responsible for Selection cursor navigation and for appending frames to current Selection</span><span class="rvts21">.</span></li>
|
||||
<li class="rvps10"><span class="rvts30">Alt</span><span class="rvts21"> </span><span class="rvts21">is responsible for Patterns and for crossing gaps using mouse wheel.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you tap the </span><span class="rvts30">Shift </span><span class="rvts21">key twice in a row, the Piano Roll will automatically scroll to Playback cursor</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you tap the </span><span class="rvts30">Ctrl </span><span class="rvts21">key twice in a row, the Piano Roll will automatically scroll to Selection cursor</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you're drawing/erasing Input, hold </span><span class="rvts30">Shift</span><span class="rvts21"> key to remove the "single-column" confinement.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="accelerators"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">Accelerator hotkeys</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">These are key combinations typical for many Windows applications. You cannot redefine those combinations. In this documentation they are highlighted with red color.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps18"><img alt="" style="padding : 1px;" src="lib/keyboard-accelerator-keys.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + S</span><span class="rvts21"> = save project to disk</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + Z</span><span class="rvts21"> = undo (step back in History Log)</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + Y</span><span class="rvts21"> = re</span><span class="rvts21">do (step forward in History Log)</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + Q</span><span class="rvts21"> = restore previous Selection (Selection undo)</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + W</span><span class="rvts21"> = </span><span class="rvts21">restore next Selection</span><span class="rvts21"> (Selection redo)</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + A</span><span class="rvts21"> = select all frames between two Markers surrounding Selection cursor</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + B</span><span class="rvts21"> = reselect frames that contain Input that was copied to the Clipboard</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + C</span><span class="rvts21"> = copy selected Input to the Clipboard (Copy)</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + X</span><span class="rvts21"> = </span><span class="rvts21">copy selected Input to the Clipboard and then clear selected frames (Cut)</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + V</span><span class="rvts21"> = paste Input from the Clipboard to Selection cursor (Paste)</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + </span><span class="rvts30">Shift + V</span><span class="rvts21"> = insert</span><span class="rvts21"> Input from the Clipboard to Selection cursor (PasteInsert)</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts30">Delete</span><span class="rvts21"> = clear selected frames</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + Delete</span><span class="rvts21"> = remove selected frames from the movie</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Insert</span><span class="rvts21"> = insert given number of blank frames before Selection cursor</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + Insert</span><span class="rvts21"> = clone selected frames</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + </span><span class="rvts30">Shift + Insert</span><span class="rvts21"> = insert blank frames before selected frames</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + F</span><span class="rvts21"> = bring Find Note dialog</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + PageUp</span><span class="rvts21"> / </span><span class="rvts30">Ctrl + </span><span class="rvts30">Page</span><span class="rvts30">Down</span><span class="rvts21"> = jump on Markers with Selection cursor</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + Home</span><span class="rvts21"> / </span><span class="rvts30">Ctrl + </span><span class="rvts30">End</span><span class="rvts21"> </span><span class="rvts21">=</span><span class="rvts21"> move Selection to the beginning / to the end of the movie</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + Up</span><span class="rvts21"> / </span><span class="rvts30">Ctrl + Down</span><span class="rvts21"> = transpose Selection 1 frame up / down</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + Right</span><span class="rvts21"> / </span><span class="rvts30">Ctrl + Left</span><span class="rvts21"> = scroll Piano Roll right / left</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts30">Shift + </span><span class="rvts30">Page</span><span class="rvts30">Up</span><span class="rvts21"> / </span><span class="rvts30">Shift + </span><span class="rvts30">PageD</span><span class="rvts30">own</span><span class="rvts21"> </span><span class="rvts21">=</span><span class="rvts21"> </span><span class="rvts21">jump on Markers with Playback cursor</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Shift + Home</span><span class="rvts21"> / </span><span class="rvts30">Shift + </span><span class="rvts30">End</span><span class="rvts21"> </span><span class="rvts21">=</span><span class="rvts21"> send</span><span class="rvts21"> Playback cursor </span><span class="rvts21">to the beginning / to the end of the movie</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Shift + Up</span><span class="rvts21"> / </span><span class="rvts30">Shift</span><span class="rvts30"> + Down</span><span class="rvts21"> = move Playback cursor 1 frame up / down</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Shift + Right</span><span class="rvts21"> / </span><span class="rvts30">Shift</span><span class="rvts30"> + Left</span><span class="rvts21"> = scroll Piano Roll right / left</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts30">PageUp</span><span class="rvts21"> / </span><span class="rvts30">Page</span><span class="rvts30">Down</span><span class="rvts21"> = scroll Piano Roll up / down</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Home</span><span class="rvts21"> / </span><span class="rvts30">End</span><span class="rvts21"> = scroll Piano Roll </span><span class="rvts21">to the beginning / to the end of the movie</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="hotkeys"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">FCEUX hotkeys</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Emulator allows to map keyboard keys to different functions, see the </span><a class="rvts27" href="ProgramCustomization.html#fceux-config">Program Customization</a><span class="rvts21"> chapter. Keys that are already mapped by default are highlighted by light-blue color in this documentation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps18"><img alt="" style="padding : 1px;" src="lib/keyboard-hotkeys.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts26">Ctrl + F1</span><span class="rvts21"> = reload last project</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts26">Pause</span><span class="rvts21"> = pause/unpause emulator</span></p>
|
||||
<p class="rvps10"><span class="rvts26">Esc</span><span class="rvts21"> = cancel seeking</span></p>
|
||||
<p class="rvps10"><span class="rvts26">Spacebar</span><span class="rvts21"> = restore Playback cursor position (launch seeking to the green arrow)</span></p>
|
||||
<p class="rvps10"><span class="rvts26">Ctrl + </span><span class="rvts26">Spacebar</span><span class="rvts21"> = toggle "Auto-restore last position" checkbox</span></p>
|
||||
<p class="rvps10"><span class="rvts26">\</span><span class="rvts21"> (backslash) = </span><span class="rvts26">Frame Advance</span><span class="rvts21"> (emulate 1 frame)</span></p>
|
||||
<p class="rvps10"><span class="rvts26">Backspace </span><span class="rvts21">= </span><span class="rvts26">Frame Rewind</span><span class="rvts21"> (move Playback cursor 1 frame up)</span></p>
|
||||
<p class="rvps10"><span class="rvts26">Shift + R</span><span class="rvts21"> = play movie from the beginning</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts26">-</span><span class="rvts21"> (white "minus") = decrease emulation speed</span></p>
|
||||
<p class="rvps10"><span class="rvts26">=</span><span class="rvts21"> (white "plus") = increase emulation speed</span></p>
|
||||
<p class="rvps10"><span class="rvts26">Tab</span><span class="rvts21"> = Turbo speed (applies as long as the key is being held)</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts26">F1</span><span class="rvts26">-</span><span class="rvts26">F10</span><span class="rvts21"> = load movie branch from respective Bookmark slot (1-10)</span></p>
|
||||
<p class="rvps10"><span class="rvts26">1-0</span><span class="rvts21"> = </span><span class="rvts21">jump to the frame of the Bookmark (1-10)</span></p>
|
||||
<p class="rvps10"><span class="rvts26">Shift + F1-F10</span><span class="rvts21"> = set Bookmark (1-10)</span></p>
|
||||
<p class="rvps10"><span class="rvts26">I </span><span class="rvts21">= set currently selected Bookmark (deprecated)</span></p>
|
||||
<p class="rvps10"><span class="rvts26">P</span><span class="rvts21"> = </span><span class="rvts21">load movie branch from </span><span class="rvts21">currently selected Bookmark (deprecated)</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts26">M</span><span class="rvts21"> = show/hide rerecord counter</span></p>
|
||||
<p class="rvps10"><span class="rvts26">, </span><span class="rvts21">(comma) = switch Input display</span></p>
|
||||
<p class="rvps10"><span class="rvts26">. </span><span class="rvts21">(dot) = show/hide frame counter</span></p>
|
||||
<p class="rvps10"><span class="rvts26">/ </span><span class="rvts21">(slash) = show/hide lag counter</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts26">Shift + L</span><span class="rvts21"> = reload current Lua script</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts26">Q</span><span class="rvts21"> = toggle Recording mode</span></p>
|
||||
<p class="rvps10"><span class="rvts26">W</span><span class="rvts21"> = switch current multitracking mode</span></p>
|
||||
<p class="rvps10"><span class="rvts26">Ctrl + R</span><span class="rvts21"> = invoke Reset command</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Full list of FCEUX hotkeys that can be used when Taseditor is engaged:</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts42">Power</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Reset</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Pause</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Frame Advance</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Screenshot</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Exit</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Slowest Speed</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Speed Down</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Normal Speed</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Speed Up</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Turbo</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Turbo Toggle</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Savestate Slot 0</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Savestate Slot 1</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Savestate Slot 2</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Savestate Slot 3</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Savestate Slot 4</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Savestate Slot 5</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Savestate Slot 6</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Savestate Slot 7</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Savestate Slot 8</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Savestate Slot 9</span></li>
|
||||
<li class="rvps10"><span class="rvts54">Next Savestate Slot</span></li>
|
||||
<li class="rvps10"><span class="rvts54">Previous Savestate Slot</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State to Slot 0</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State to Slot 1</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State to Slot 2</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State to Slot 3</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State to Slot 4</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State to Slot 5</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State to Slot 6</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State to Slot 7</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State to Slot 8</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State to Slot 9</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State from Slot 0</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State from Slot 1</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State from Slot 2</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State from Slot 3</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State from Slot 4</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State from Slot 5</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State from Slot 6</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State from Slot 7</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State from Slot 8</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State from Slot 9</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Play Movie From Beginning</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Toggle Read-Only</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Toggle Frame Display</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Toggle Input Display</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Toggle Status Icon</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Reload current Lua script</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Sound Mute Toggle</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Sound Volume Up</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Sound Volume Down</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Sound Volume Normal</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Record AVI As...</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Stop AVI</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Eject or Insert FDS Disk</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Switch FDS Disk Side</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Use Input Preset 1</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Use Input Preset 2</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Use Input Preset 3</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Toggle Background Display</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Toggle Object Display</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Lag Counter Toggle</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Open TAS Editor</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Open Memory Watch</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Open Cheats</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Open Debugger</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Open Hex Editor</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Open PPU Viewer</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Open Name Table Viewer</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Open Trace Logger</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Open Code/Data Logger</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Frame Adv.-Skip Lag</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Reload ROM or TAS Editor Project</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Toggle Movie Subtitles</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Open Ram Watch</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Open Ram Search</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Toggle Rerecord Display</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Frame Rewind</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Restore Playback</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Cancel Seeking</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Switch Auto-restore last position</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Switch current Multitracking mode</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Run Manual Lua function</span></li>
|
||||
<li class="rvps10"><span class="rvts42">Toggle FPS Display</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Other FCEUX hotkeys will not work when Taseditor is running, for more details see </span><a class="rvts27" href="MistakeProofing.html">Mistake-proofing</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="virtual_joypad"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">Virtual gamepad</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Emulator also allows to map keyboard keys to buttons of emulated console. You can use these keys for Input Recording and for changing Input in Selection, see the </span><a class="rvts27" href="ProgramCustomization.html#fceux-config">Program Customization</a><span class="rvts21"> chapter.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">By default these keys are mapped to Player 1 buttons:</span></p>
|
||||
<p class="rvps10"><span class="rvts25">D</span><span class="rvts21"> – </span><span class="rvts29">B</span></p>
|
||||
<p class="rvps10"><span class="rvts25">F</span><span class="rvts21"> – </span><span class="rvts29">A</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Enter</span><span class="rvts21"> – </span><span class="rvts29">Start</span></p>
|
||||
<p class="rvps10"><span class="rvts25">S</span><span class="rvts21"> – </span><span class="rvts29">Select</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Keypad up</span><span class="rvts21"> – </span><span class="rvts29">Up</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Keypad left</span><span class="rvts21"> – </span><span class="rvts29">Left</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Keypad down</span><span class="rvts21"> – </span><span class="rvts29">Down</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Keypad right</span><span class="rvts21"> – </span><span class="rvts29">Right</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you need to input hardware commands, use FCEUX menu or hotkeys:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts34">NES -> Reset</span><span class="rvts21"> or "</span><span class="rvts26">Reset</span><span class="rvts21">" hotkey (</span><span class="rvts26">Ctrl + R </span><span class="rvts21">by default) – to invoke the "Reset" command</span></li>
|
||||
<li class="rvps10"><span class="rvts34">NES -> Power</span><span class="rvts21"> or "</span><span class="rvts55">Power</span><span class="rvts21">" </span><span class="rvts21">hotkey</span><span class="rvts21"> – to invoke the "Power switch" command (not used in practical TASing)</span></li>
|
||||
<li class="rvps10"><span class="rvts34">NES -> Eject/Insert Disk</span><span class="rvts21"> or "</span><span class="rvts55">Eject or Insert FDS Disk</span><span class="rvts21">" hotkey – to invoke the disk command (only useful for an Famicom Disk System game)</span></li>
|
||||
<li class="rvps10"><span class="rvts34">NES -> Switch Disk Side</span><span class="rvts21"> or "</span><span class="rvts55">Switch FDS Disk Side</span><span class="rvts21">"</span><span class="rvts21"> hotkey – to invoke the disk command (only useful for an Famicom Disk System game)</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">These commands work only when Recording mode is on. And after invoking a command you need to advance at least 1 frame to actually activate the command and insert it into the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Since in </span><span class="rvts21">TAS Editor 1.0 Piano Roll doesn't have columns for displaying hardware commands (they are rarely used), it's recommended to set Markers to frames where a command was inserted.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="notes"></a>
|
||||
<span class="rvts6"><br/></span></p>
|
||||
<p><span class="rvts53">Controls in Note editing mode</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you enter Note editing mode, the keyboard is used for typing the text.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">1. The following accelerator hotkeys change their meaning:</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + A</span><span class="rvts21"> – select all text of the Note</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + Z</span><span class="rvts21"> – undo/redo the last change in the text</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Ctrl + X</span><span class="rvts21">, </span><span class="rvts30">Ctrl + C</span><span class="rvts21">, </span><span class="rvts30">Ctrl + V</span><span class="rvts21"> – text copy/cut/paste</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Delete</span><span class="rvts21"> – delete one symbol or all selected symbols</span></p>
|
||||
<p class="rvps10"><span class="rvts30">Home</span><span class="rvts21">/</span><span class="rvts30">End</span><span class="rvts21"> – move typing position to the beginning/to the end of the text</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">2. FCEUX hotkeys do not work.</span></p>
|
||||
<p class="rvps10"><span class="rvts26">Backspace</span><span class="rvts21"> – </span><span class="rvts21">delete previous symbol</span></p>
|
||||
<p class="rvps10"><span class="rvts26">Esc</span><span class="rvts21"> – exit Note editing mode without saving any changes</span></p>
|
||||
<p class="rvps10"><span class="rvts26">Tab</span><span class="rvts21"> – toggle between upper and lower Note editing field</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">3. Virtual gamepad keys do not work. Note: they will work if you check the </span><span class="rvts21">Config -> Enable -> Background Input in FCEUX menu, so it's not recommended to enable the feature.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">4. Mouse controls are the same as usual. Any click outside the text edit field (except for mid-clicks) will exit Note editing mode and save text changes. Also, if the Playback cursor or Selection cursor move away from the Marker while you're editing its Note, the text changes will be saved and you'll begin editing another Marker's Note.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour/create-ebooks-for-amazon-kindle">Full-featured Kindle eBooks generator</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,140 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>FAQ</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("FAQ");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>FAQ</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="Reference.html">Reference</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="Reference.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="LuaAPI.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="SpeedrunningSynopsis.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">FAQ</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">If after reading the Manual you still have any questions on the topic, feel free to ask them at </span><a class="rvts27" href="http://tasvideos.org/forum/index.php" target="_blank">TASVideos</a><span class="rvts21"> forum.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">I think I've found a bug in the program, what should I do?</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Post a message in the </span><a class="rvts27" href="http://tasvideos.org/forum/viewforum.php?f=15" target="_blank">FCEUX</a><span class="rvts21"> subforum of TASVideos. Try to explain the issue precisely, to help author reproduce the situation. Attach a screenshot if you think it reflects the essence of the problem.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Is it possible to use Taseditor with other emulators?</span></p>
|
||||
<p class="rvps10"><span class="rvts21">No. Even though the program code of Taseditor is isolated from the emulator code, it is by no means a plug-in. So it's necessary to manually port its source code and modify it according to specifications of target platform.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">How can I TAS the traditional way, yet with Taseditor interface?</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Basically, you can start traditional TASing right away, no additional settings are required. But if you must keep some old habits intact, you can fine-tune the program. Try the following options:</span></p>
|
||||
<ul style="text-indent: 25px; margin-left: 5px; list-style-position: inside;">
|
||||
<li class="rvps10" style="text-indent: 25px"><span class="rvts21">switch on the </span><a class="rvts27" href="ProgramCustomization.html#OldcontrolschemeforBranching">Config -> Old control scheme for Branching</a><span class="rvts21"> option</span></li>
|
||||
<li class="rvps10" style="text-indent: 25px"><span class="rvts21">switch off the </span><a class="rvts27" href="ProgramCustomization.html#BranchesrestoreentireMovie">Config -> Branches restore entire Movie</a><span class="rvts21"> option</span></li>
|
||||
<li class="rvps10" style="text-indent: 25px"><span class="rvts21">switch on the </span><a class="rvts27" href="ProgramCustomization.html#CombineconsecutiveRecordings">Config -> Combine consecutive Recordings/Draws</a><span class="rvts21"> option</span></li>
|
||||
<li class="rvps10" style="text-indent: 25px"><span class="rvts21">switch off the </span><a class="rvts27" href="ProgramCustomization.html#UseInputkeysforColumnSet">Config -> Use Input keys for Column Set</a><span class="rvts21"> option</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21">Also, it's recommended to switch the Bookmarks List to the "Branches Tree" view.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Why the right-click on the FCEUX window doesn't prompt the usual context menu?</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's done to facilitate the </span><a class="rvts27" href="Navigation.html#rewinding-by-wheel">Playback cursor navigation with mouse wheel</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Usually users move the mouse cursor in such a manner that it's in sight. Thus when TASer is watching the game events the cursor will often be inside the FCEUX window. Context menus would obstruct the view when you want to rewind the Playback by holding right mouse button and rolling the mouse wheel. Since there's no important items in the menu while TAS Editor is engaged, the menu was removed.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Why the right-click on the Piano Roll sometimes prompts a context menu and sometimes doesn't?</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Taseditor's context menu only appears when you right-click on the number of a selected frame. If you right-click on a frame that is not selected, or you right-click on the Input of a selected frame, the menu won't appear.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's done to facilitate the Piano Roll scrolling by right-clicking and dragging.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Generally, it's recommended to use keyboard shortcuts and other means of accessing Taseditor features instead of using context menu.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">How do I insert a Reset command into the movie?</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You should use Input Recording here. Place the Playback cursor to the target frame, switch on Recording, then choose </span><span class="rvts25">NES -> Reset</span><span class="rvts21"> in FCEUX main menu and press </span><span class="rvts26">Frame Advance</span><span class="rvts21">. Also, it's recommended to set a Marker to this frame, since there's no other way to mark a Reset/Power switch in the Piano Roll (there's no columns for commands, only for joypad buttons).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Then you can switch Recording off and continue usual movie editing. The frame with the Reset command can be transposed up or down by inserting or deleting frames above it.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Other hardware commands are invoked the same way, see </span><a class="rvts27" href="Controls.html#virtual_joypad">Controls</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">How do I change the order of columns in the Piano Roll?</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Unfortunately, this feature is not supported in TAS Editor 1.0. This will be </span><a class="rvts27" href="Ideas.html#BetterColumns">fixed</a><span class="rvts21"> in next versions.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">How do I change the number of players (joypads) in my movie?</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You should create a new project, copying the Input and Markers from current one.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Choose </span><span class="rvts25">File -> New</span><span class="rvts21"> in TAS Editor main menu. In the "Create New Project" window: choose the needed Input type, check "Copy current Input" and "Copy current Markers" checkboxes and click "OK".</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Old project's Bookmarks won't be copied to the new project this way. You can recreate them using export/import Input features.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">How can I quickly compare two movies?</span></p>
|
||||
<ol style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Make sure that </span><a class="rvts27" href="ProgramCustomization.html#EnableHotChanges">Hot Changes</a><span class="rvts21"> are enabled and </span><a class="rvts27" href="ProgramCustomization.html#AutoAdjustInputAccordingtoLag">Auto-adjustment of Input</a><span class="rvts21"> is disabled.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Create an empty project, import the first movie into it (using </span><span class="rvts25">File -> Import Input</span><span class="rvts21">), replay the movie to the end and save it to Bookmark 1.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Import the second movie over the existing Input and save the result to Bookmark 2.</span></li>
|
||||
</ol>
|
||||
<p class="rvps10"><span class="rvts21">The import operation will truncate the Greenzone after the frame where the first difference between Input of the two movies was found. Other places of discrepancy can be detected by observing the Input in the Piano Roll:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">buttonpresses that match in both movies are colored black</span></li>
|
||||
<li class="rvps10"><span class="rvts21">new buttonpresses (added by the 2nd movie) are colored bright-red</span></li>
|
||||
<li class="rvps10"><span class="rvts21">deleted buttonpresses are marked by dash</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21">For extra convenience it's recommended to name both Bookmarks, e.g. copy/paste the filename of the imported movie into the upper Marker Note just before creating a Bookmark.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Why are those fm3 files so large?</span></p>
|
||||
<p class="rvps10"><span class="rvts21">An FM3 file usually contains full snapshot of the working process, including the Greenzone data (which takes the most part of the file). See </span><a class="rvts27" href="AdvancedFeatures.html#ProjectsSharing">Advanced Features</a><span class="rvts21"> for details.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Why is the Manual so long?</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Because besides the program specifications the Manual contains comprehensive tutorial (the </span><a class="rvts27" href="BeginnersGuide.html">Beginner's Guide</a><span class="rvts21">) which systematizes known principles of effective TASing. Since there was no similar endeavours before, the author decided that lengthy explanations are the lesser evil than possible inexactitude.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour">Full-featured Help generator</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,392 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>FM3 format</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("FM3format");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>FM3 format</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="TASEditorInside.html">TAS Editor Inside</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="TASEditorInside.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="MistakeProofing.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">FM3 format</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The FM3 format is a simple extension of the FM2 format. FM2 files contain data which is needed for replaying the movie, and FM3 just adds Taseditor's working data to the end of FM2 file.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can read full specifications of FM2 format in the FCEUX Help and on </span><a class="rvts27" href="http://www.fceux.com/web/FM2.html" target="_blank">official site</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Every FM3 consists of 3 parts:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><a class="rvts27" href="FM3format.html#Header">Header</a><span class="rvts21"> (as in fm2)</span></li>
|
||||
<li class="rvps10"><a class="rvts27" href="FM3format.html#InputLog">Input Log</a><span class="rvts21"> (as in fm2)</span></li>
|
||||
<li class="rvps10"><a class="rvts27" href="FM3format.html#TaseditorData">Taseditor data</a></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="Header"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Header</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Header is always in ASCII plain text format.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It consists of several key-value pairs (lines of text where all symbols before the first space separator are considered to be the keyword and all symbols after this separator are considered to be the text representation of the value).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Newlines may be </span><span class="rvts70">\r\n</span><span class="rvts21"> or </span><span class="rvts70">\n</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If a line starts from "|" (pipe), it means the end of Header and the beginning of Input Log.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The key-value pairs may be in any order, except that the first key must be </span><span class="rvts25">version</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Value text is always terminated by a newline, which the value text does not include.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The value text is parsed differently depending on the keyword, it can be either integer or string.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts34">Keys with integer value:</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">(also used for booleans, with a 1 for </span><span class="rvts70">true</span><span class="rvts21"> and 0 for </span><span class="rvts70">false</span><span class="rvts21">)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">(the value can be stored as </span><span class="rvts70">int32</span><span class="rvts21">)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts25">version</span><span class="rvts21"> (required) – the version of the movie file format; for now it is always </span><span class="rvts25">3</span></li>
|
||||
<li class="rvps10"><span class="rvts25">emuVersion</span><span class="rvts21"> (required) – the version of the emulator used to produce the file (e.g. </span><span class="rvts25">21060</span><span class="rvts21">)</span></li>
|
||||
<li class="rvps10"><span class="rvts25">rerecordCount</span><span class="rvts21"> (optional) – the rerecord count</span></li>
|
||||
<li class="rvps10"><span class="rvts25">palFlag</span><span class="rvts21"> (</span><span class="rvts70">bool</span><span class="rvts21">) (optional) – </span><span class="rvts70">true </span><span class="rvts21">if the movie uses PAL timing</span></li>
|
||||
<li class="rvps10"><span class="rvts25">NewPPU</span><span class="rvts21"> (</span><span class="rvts70">bool</span><span class="rvts21">) (optional) – </span><span class="rvts70">true </span><span class="rvts21">if the movie uses New PPU</span></li>
|
||||
<li class="rvps10"><span class="rvts25">FDS</span><span class="rvts21"> (</span><span class="rvts70">bool</span><span class="rvts21">) (optional) – </span><span class="rvts70">true </span><span class="rvts21">if the movie was recorded on a Famicom Disk System (FDS) game</span></li>
|
||||
<li class="rvps10"><span class="rvts25">fourscore</span><span class="rvts21"> (</span><span class="rvts70">bool</span><span class="rvts21">) – </span><span class="rvts70">true</span><span class="rvts21"> if a fourscore was used. If fourscore is not used, then </span><span class="rvts25">port0</span><span class="rvts21"> and </span><span class="rvts25">port1</span><span class="rvts21"> are required</span></li>
|
||||
<li class="rvps10"><span class="rvts25">port0</span><span class="rvts21"> – the type of input device attached to the port 0. Supported values are:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 60px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">SI_NONE = 0</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">SI_GAMEPAD = 1</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">SI_ZAPPER = 2</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts25">port1</span><span class="rvts21"> – the type of input device attached to the port 1. Supported values are:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 60px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">SI_NONE = 0</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">SI_GAMEPAD = 1</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">SI_ZAPPER = 2</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts25">port2</span><span class="rvts21"> (required) – the type of the FCExp port device which was attached. Supported values are:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 60px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">SIFC_NONE = 0</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts25">binary</span><span class="rvts21"> (</span><span class="rvts70">bool</span><span class="rvts21">) (optional) – </span><span class="rvts70">true </span><span class="rvts21">if Input Log is stored in binary format. FM2 files usually contain Input in text format, for easy editing and splicing. FM3 files usually contain Input in binary format, to save disk space</span></li>
|
||||
<li class="rvps10"><span class="rvts25">length</span><span class="rvts21"> (required in FM3) – movie size (number of frames in the input log). If this key is specified and the number is >= 0, the Input Log ends after specified number of records, and any remaining data should not be parsed (because it's Taseditor data). The Header of FM3s always has this keyword, the Header of FM2s doesn't have it.</span></li>
|
||||
</ul>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts34">Keys with string value:</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">(their values cannot contain newlines)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">romFilename</span><span class="rvts21"> (required) – the name of the file used to record the movie</span></p>
|
||||
<p class="rvps10"><span class="rvts25">romChecksum</span><span class="rvts21"> (required) – the base64 of the hexified MD5 hash of the ROM which was used to record the movie</span></p>
|
||||
<p class="rvps10"><span class="rvts25">comment</span><span class="rvts21"> (optional) – simply a memo. By convention, the author of the movie should be stored in a comment with the subject "author". Example: "comment author AnS"</span></p>
|
||||
<p class="rvps10"><span class="rvts25">subtitle</span><span class="rvts21"> (optional) – a message that will be displayed on screen when movie is played back (unless Subtitles are turned off). Right after the word "subtitle" and following space separator there must be an integer value indicating the frame that the subtitle will be displayed. Any remaining text after the integer and following space separator is considered to be the string displayed. Example: "subtitle 100 Level Two" – at frame 100 the words "Level Two" will be displayed on the screen</span></p>
|
||||
<p class="rvps10"><span class="rvts25">guid</span><span class="rvts21"> (required) – a unique identifier for a movie, generated when the movie is created. Meaningless in FM3, because all there's no external savestates associated with the project file.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="InputLog"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Input Log</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Input Log section consists of movie records either in the form of text lines or in the form of binary data.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts34">Text format:</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Every frame of the movie is represented by line of text beginning and ending with a "|" (pipe).</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">If fourscore is not used, the fields in the line are as follows:</span></p>
|
||||
<p class="rvps10"><span class="rvts25">|commands|port0|port1|port2|</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Field </span><span class="rvts25">commands</span><span class="rvts21"> is a variable length decimal integer which is interpreted as a bit field corresponding to miscellaneous input states which are valid at the start of the frame. Current values for this are:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">bit 0 (number = 1) – Soft Reset</span></li>
|
||||
<li class="rvps10"><span class="rvts21">bit 1 (number = 2) – Power</span></li>
|
||||
<li class="rvps10"><span class="rvts21">bit 2 (number = 4) – Eject/Insert Disk</span></li>
|
||||
<li class="rvps10"><span class="rvts21">bit 3 (number = 8) – Switch Disk Side</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The format of </span><span class="rvts25">port0</span><span class="rvts21">, </span><span class="rvts25">port1</span><span class="rvts21">, </span><span class="rvts25">port2</span><span class="rvts21"> depends on which types of devices were attached.</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">SI_NONE: the field must be empty</span></li>
|
||||
<li class="rvps10"><span class="rvts21">SI_GAMEPAD: the field consists of eight characters which constitute a bit field. Any character other than ' ' (spacebar) or '.' (dot) means that the button was pressed. By convention, the following mnemonics are used in a column to remind us of which button corresponds to which column: RLDUTSBA (</span><span class="rvts29">Right</span><span class="rvts21">, </span><span class="rvts29">Left</span><span class="rvts21">, </span><span class="rvts29">Down</span><span class="rvts21">, </span><span class="rvts29">Up</span><span class="rvts21">, </span><span class="rvts29">Start</span><span class="rvts21">, </span><span class="rvts29">Select</span><span class="rvts21">, </span><span class="rvts29">B</span><span class="rvts21">, </span><span class="rvts29">A</span><span class="rvts21">)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">SI_ZAPPER: the field consists of several characters in the following pattern </span><span class="rvts25">XXX YYY B Q Z</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 60px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts25">XXX</span><span class="rvts21">: %03d – the X position of the mouse</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts25">YYY</span><span class="rvts21">: %03d – the Y position of the mouse</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts25">B</span><span class="rvts21">: %01d – 1 if the mouse button is pressed; 0 if not</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts25">Q</span><span class="rvts21">: %01d – an internal value used by the emulator's zapper code</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts25">Z</span><span class="rvts21">: %d – a variable-length decimal integer; an internal value used by the emulator's zapper code </span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">If fourscore is used, then port0 and port1 are irrelevant and ignored. The input types must all be gamepads, and each input log record must be in the following format:</span></p>
|
||||
<p class="rvps10"><span class="rvts25">|commands|RLDUTSBA|RLDUTSBA|RLDUTSBA|RLDUTSBA|port2|</span></p>
|
||||
<p class="rvps10"><span class="rvts21">(commands, player 1, player 2, player 3, player 4, port2)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts34">Binary format:</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Input Log section starts with a | (pipe).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Every frame of the movie is represented by a record of a fixed length. The length can be determined by the devices on </span><span class="rvts25">port0</span><span class="rvts21"> and </span><span class="rvts25">port1</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The first byte of each record stores "commands" bit field:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">bit 0 – Soft Reset</span></li>
|
||||
<li class="rvps10"><span class="rvts21">bit 1 – Power</span></li>
|
||||
<li class="rvps10"><span class="rvts21">bit 2 – Eject/Insert Disk</span></li>
|
||||
<li class="rvps10"><span class="rvts21">bit 3 – Switch Disk Side</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">If fourscore is not used, the remaining bytes in the record depend on which types of devices are attached to </span><span class="rvts25">port0</span><span class="rvts21"> and </span><span class="rvts25">port1</span><span class="rvts21">:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">SI_NONE: 0 bytes added to the size of record</span></li>
|
||||
<li class="rvps10"><span class="rvts21">SI_GAMEPAD: 1 byte added to the size of record. Bits of the byte represent the state of buttons (bit0 = </span><span class="rvts29">A</span><span class="rvts21">, bit1 = </span><span class="rvts29">B</span><span class="rvts21">, bit2 = </span><span class="rvts29">Select</span><span class="rvts21">, bit3 = S</span><span class="rvts29">Start</span><span class="rvts21">, bit4 = </span><span class="rvts29">Up</span><span class="rvts21">, bit5 = </span><span class="rvts29">Down</span><span class="rvts21">, bit6 = </span><span class="rvts29">Left</span><span class="rvts21">, bit7 = </span><span class="rvts29">Right</span><span class="rvts21">). If the bit is set, respective button is considered to be pressed, if the bit is clear, the button is not pressed</span></li>
|
||||
<li class="rvps10"><span class="rvts21">SI_ZAPPER: 12 bytes added to the size of record:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 60px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">1st byte – the X position of the mouse</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">2nd byte – the Y position of the mouse</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">3rd byte – 1 if the mouse button is pressed; 0 if not</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">4th byte – an internal value used by the emulator's zapper code</span></li>
|
||||
<li class="rvps10" style="text-indent: 60px"><span class="rvts21">bytes 5-12 (</span><span class="rvts70">uint64</span><span class="rvts21">) – an internal value used by the emulator's zapper code</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">If fourscore is used, then </span><span class="rvts25">port0</span><span class="rvts21"> and </span><span class="rvts25">port1</span><span class="rvts21"> are irrelevant and ignored. 4 bytes are added to the size of record. The bits of the 1st byte represent the state of buttons of the 1st joypad (bit0 = </span><span class="rvts29">A</span><span class="rvts21">, bit1 = </span><span class="rvts29">B</span><span class="rvts21">, bit2 = </span><span class="rvts29">Select</span><span class="rvts21">, bit3 = </span><span class="rvts29">Start</span><span class="rvts21">, bit4 = </span><span class="rvts29">Up</span><span class="rvts21">, bit5 = </span><span class="rvts29">Down</span><span class="rvts21">, bit6 = </span><span class="rvts29">Left</span><span class="rvts21">, bit7 = </span><span class="rvts29">Right</span><span class="rvts21">); bits of the 2nd byte represent the state of buttons of the 2nd joypad, and so on.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="TaseditorData"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Taseditor Data</span></p>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps21"><table width="450" border="1" cellpadding="0" cellspacing="0" style="border-color: #ffffff #000000 #000000 #ffffff; border-style: solid;">
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 104px;"><p class="rvps5"><span class="rvts6">4 bytes</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 146px;"><p class="rvps5"><span class="rvts79">unsigned int32</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 192px;"><p class="rvps5"><span class="rvts6">FM3 version</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 104px;"><p class="rvps5"><span class="rvts6">4 bytes</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 146px;"><p class="rvps5"><span class="rvts79">unsigned int32</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 192px;"><p class="rvps5"><span class="rvts6">Saved modules</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 104px;"><p class="rvps5"><span class="rvts6">4 bytes</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 146px;"><p class="rvps5"><span class="rvts79">unsigned int32</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 192px;"><p class="rvps5"><span class="rvts6">Number of offsets (N = 6)</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 104px;"><p class="rvps5"><span class="rvts6">4 * 6 bytes</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 146px;"><p class="rvps5"><span class="rvts6">pointers</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 192px;"><p class="rvps5"><span class="rvts6">Offsets</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 104px;"><p class="rvps5"><span class="rvts6">???</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 146px;"><p class="rvps5"><span class="rvts6">stream</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 192px;"><p class="rvps5"><span class="rvts6">MARKERS DATA</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 104px;"><p class="rvps5"><span class="rvts6">???</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 146px;"><p class="rvps5"><span class="rvts6">stream</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 192px;"><p class="rvps5"><span class="rvts6">BOOKMARKS DATA</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 104px;"><p class="rvps5"><span class="rvts6">???</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 146px;"><p class="rvps5"><span class="rvts6">stream</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 192px;"><p class="rvps5"><span class="rvts6">GREENZONE DATA</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 104px;"><p class="rvps5"><span class="rvts6">???</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 146px;"><p class="rvps5"><span class="rvts6">stream</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 192px;"><p class="rvps5"><span class="rvts6">HISTORY DATA</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 104px;"><p class="rvps5"><span class="rvts6">???</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 146px;"><p class="rvps5"><span class="rvts6">stream</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 192px;"><p class="rvps5"><span class="rvts6">PIANO ROLL DATA</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 104px;"><p class="rvps5"><span class="rvts6">???</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 146px;"><p class="rvps5"><span class="rvts6">stream</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 192px;"><p class="rvps5"><span class="rvts6">SELECTION DATA</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The data starts right after the last record of the Input Log. If there's EOF after the last record, TAS Editor will interpret the file as an FM2 file.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">First 4 bytes of Taseditor Data contain the version of the project file format. The first release version of TAS Editor 1.0 saves projects with version = 3.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Next 4 bytes contain bit field that can be used for determining which modules of Taseditor were saved to the FM3 file:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">bit 0 – Markers were saved</span></li>
|
||||
<li class="rvps10"><span class="rvts21">bit 1 – Bookmarks were saved</span></li>
|
||||
<li class="rvps10"><span class="rvts21">bit 2 – entire Greenzone was saved</span></li>
|
||||
<li class="rvps10"><span class="rvts21">bit 3 – History Log was saved</span></li>
|
||||
<li class="rvps10"><span class="rvts21">bit 4 – Piano Roll position was saved</span></li>
|
||||
<li class="rvps10"><span class="rvts21">bit 5 – Selection History was saved</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Next 4 bytes contain the total number of modules, in the version 3 this number must be 6.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Then there are six offsets (4 bytes each) pointing at the data of each module. The offsets are counted from the beginning of the file.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When Taseditor saves the project, it calls all 6 modules that need saving. Each of them saves current writing offset and then serializes its own data into the file stream and moves current write position forward. The order of calling modules is always the same (Markers, Bookmarks, Greenzone, History, Piano Roll, Selection). When loading a project Taseditor calls those modules in the same order and they seek to the given offset and load / deserialize the data from the file.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To check the integrity of the data loaded, every module writes its own ID (string) into the file stream before writing the data. When loading the data it expects the ID to match, if it doesn't match then the module refuses to load following data, creates default state and reports "loading error" to Taseditor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When using Save Compact settings, modules either save all their data as usual or write dummy ID which indicates that this module didn't save its data into the file. When loading the file a module that detects dummy ID refuses to load following data, creates default state but then reports "loading success" to Taseditor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps21"><table width="450" border="1" cellpadding="0" cellspacing="0" style="border-color: #ffffff #000000 #000000 #ffffff; border-style: solid;">
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; background-color: #0000ff; width: 106px;"><p class="rvps5"><span class="rvts78">Module</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; background-color: #0000ff; width: 174px;"><p class="rvps5"><span class="rvts78">ID when saved</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; background-color: #0000ff; width: 162px;"><p class="rvps5"><span class="rvts78">ID when not saved</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 106px;"><p class="rvps5"><span class="rvts6">Markers</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 174px;"><p class="rvps5"><span class="rvts6">MARKERS</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 162px;"><p class="rvps5"><span class="rvts6">MARKERX</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 106px;"><p class="rvps5"><span class="rvts6">Bookmarks</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 174px;"><p class="rvps5"><span class="rvts6">BOOKMARKS</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 162px;"><p class="rvps5"><span class="rvts6">BOOKMARKX</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 106px;"><p class="rvps5"><span class="rvts6">Greenzone</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 174px;"><p class="rvps5"><span class="rvts6">GREENZONE</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 162px;"><p class="rvps5"><span class="rvts6">GREENZONX</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 106px;"><p class="rvps5"><span class="rvts6">History</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 174px;"><p class="rvps5"><span class="rvts6">HISTORY</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 162px;"><p class="rvps5"><span class="rvts6">HISTORX</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 106px;"><p class="rvps5"><span class="rvts6">Piano Roll</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 174px;"><p class="rvps5"><span class="rvts6">PIANO_ROLL</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 162px;"><p class="rvps5"><span class="rvts6">PIANO_ROLX</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 106px;"><p class="rvps5"><span class="rvts6">Selection</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 174px;"><p class="rvps5"><span class="rvts6">SELECTION</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-right: none; border-bottom: none; width: 162px;"><p class="rvps5"><span class="rvts6">SELECTIOX</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/help-authoring-tool">Single source CHM, PDF, DOC and HTML Help creation</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,285 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Glossary</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("Glossary");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Glossary</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="Reference.html">Reference</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="Reference.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="Reference.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="Controls.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Glossary</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Here you can find definitions for many terms that are used throughout this Manual. Most of them were used in the context of TASing before TAS Editor was created. Some of those terms are described more thoroughly in the </span><a class="rvts27" href="BeginnersGuide.html">Beginner's Guide</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's recommended to read the Glossary at once, because many terms are interconnected.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="Input"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/game-player-taser.png"/></p>
|
||||
<p class="rvps10"><span class="rvts25">Input</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Data about player's actions, that can be received by a game.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">TASing became feasible because of general assumption that behavior of a game is always determined by its initial state and player's input, and nothing else (see Determinism).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Examples of Input: pressing a button on a gamepad, pushing analog stick, touching by stylus, shouting into a microphone, etc.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Taseditor works with Input in the form of "sequence of buttons states".</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Note: the fact of player not pressing any button is also considered an Input.</span></p>
|
||||
<p class="rvps10"><a name="Output"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Output</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Data sent from a game as a result of processing player's Input.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The process of playing a game can be depicted as a loop of interaction between a subject (player) and an object (game).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Examples of Output: displaying an image, producing a sound, vibrating gamepad, changing the value of an observed RAM address, providing an information about lag, etc.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Playthrough / Walkthrough </span><span class="rvts21">(Solution)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A sequence of player's actions needed for successful completion of the game.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This sequence is inputted into the game using an input device (e.g. gamepad). The sequence can be either performed live (created in real-time) or constructed in advance in a form of reproducible recording (e.g. a log of button presses). The latter form allows editing of the sequence.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Speedrun</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A walkthrough aimed on fastest completion of the game.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Some games have build-in "Speedrun" or "Time Attack" mode, where the game counts the time spent while playing. For other games it's possible to use external timer, measuring time in seconds or TV frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">TAS</span><span class="rvts21"> (Tool-Assisted Superplay / Tool-Assisted Speedrun)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A walkthrough made with use of tools for editing the sequence of player's actions.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The process of creating TASes is called "TASing", authors are usually called "TASers".</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Input editing exempts TASers from certain human limitations (e.g. slow reflexes), allowing to spend full energy on making extraordinary walkthroughs. It can be either speedruns or entertainment videos (playarounds).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">TASes can be distributed:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">in the form of finished videos containing Output (youtube, AVI files and so on) – easy to watch</span></li>
|
||||
<li class="rvps14"><span class="rvts21">in the form of source files containing Input (FM2 movies and so on) – easy to edit</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Movie</span><span class="rvts21"> (replay)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Container for storing Input and associated data.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Unlike video containers, the movies don't contain Output (game footage). The Output appears only when user applies the movie Input to appropriate game file.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Lag</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The term used when the delay between Input and Output is greater than normally.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The loop of interaction between player and game usually establishes fixed amount of time between polling Input and updating Output, for example 60 times per second.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A computer processor can only make fixed amount of operations in this fixed amount of time. But videogames try to mimic the unboundedness of real life, so the quantity of in-game objects may vary greatly. Thus it's possible that processing all objects takes more time than allotted. In such cases the Output update will be delayed, and next Input polling will be delayed too.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Speedrunners try to avoid excessive delays, and the lag is often considered as a factor when TASing. Usually TASers try to minimize the number of "frames containing lag".</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Emulators can detect lag in a frame right after finishing the frame emulation. The criterion is simple: if the game didn't poll Input during the frame then it's the lag frame. If it did poll Input then this is normal frame. Taseditor highlights lag frames with red color, and it's useless to draw any Input on these frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Desync</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Discrepancy between expected and received Output, which results in player's Input not syncing with the logic of the game.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Desync may appear when the Input made for one game is applied to another game, using different emulator version or different settings. Also desyncs appear when emulator doesn't support deterministic emulation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Segment</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Part of the movie, representing the period of time between two in-game events.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Breaking the movie into segments is used to decompose huge task to small subtasks.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The size of a segment can be measured in frames, but the limits of a segment are defined by in-game events. The beginning event cuts all previous tasks and concentrates TASer's attention on the nearest set of conditions. The ending event serves as an optimality criterion for all possible approaches for current task solution.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="TASingProcess.html">TASing Process</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Optimization</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The process of searching for optimal (the best) solution of the task in current segment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Almost any task in videogames can be solved in a variety of ways. Every way has its own pluses and minuses. When starting a project, TASer chooses his goal (e.g. pacifist speedrun), thus setting priorities to those pluses and minuses, so all the ways of solving a task can be evaluated and compared to each other to determine which one is better.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Optimization of a TAS consists of editing Input and evaluating resulting Output. When TASer gets better result, he marks current Input as the best until he finds even more optimal Input. Final product (TAS movie) contains best solution for every subtask.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="TASingMethodology.html">TASing Methodology</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Improvement</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A way to solve the task better (closer to optimum).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Examples of improvements in speedruns: removing inaccuracy, applying unused timesaver, increasing the usefulness of an old timesaver, adding entertainment without losing speed.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Timesaver</span></p>
|
||||
<p class="rvps10"><span class="rvts21">An in-game trick that can save time.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When making a speedrun, TASer is supposed to use every unprohibited opportunity to make the walkthrough become as fast as possible. One thing is polishing the Input to find the best outcome from current knowledge about the game. Another important activity is expanding this knowledge base – finding and applying tricks. True TASer strives to gather the maximum information about the game and use all known tricks to full extent, so that his record wouldn't be easily beaten.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Examples of timesavers: features of the game, bugs of the game, luck manipulation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Note: sometimes TASers deliberately refuse certain timesavers, in this case the TAS aims for extra category. Examples: Super Mario Bros TAS without using B button (denying one feature of the game), Sonic the Hedgehog TAS without zipping (denying one bug of the game).</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Feature</span></p>
|
||||
<p class="rvps10"><span class="rvts21">An intended aspect of the game. </span></p>
|
||||
<p class="rvps10"><span class="rvts21">Some features are unimportant (or even unnoticeable) for an ordinary player, but substantial for a TASer. So before optimizing Input it's recommended to make a research of the game engine.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Examples of such features: damage boost, forced waiting for score countdown, coordinate subpixels, AI peculiarities, etc...</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Bug / Glitch</span></p>
|
||||
<p class="rvps10"><span class="rvts21">An unintended aspect of the game. </span></p>
|
||||
<p class="rvps10"><span class="rvts21">Bugs abused by TASer should be reproducible on real console (at least theoretically). Bugs caused by emulation are not permitted.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Many bugs are discovered during real-time play. Some of them require thorough research and disassembly of the game code.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Examples of bugs: simplistic collision detection system, not checking save data corruption, race conditions, mistake in the order of checks, etc...</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Luck Manipulation</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Unrestricted exploiting of certain game features, which are normally limited by the shortage of player's knowledge.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Although any experiments with Input modification are manipulations of game features, but some aspects of games appear especially unpredictable for an ordinary player. Developers intentionally entangle algorithms of those features, so that for a naked eye they seem completely random and uncontrollable.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">However, in deterministic world all aspects of videogames are predictable (defined by Input). Using tools and careful analysis you can reveal those hidden laws and dependencies, and then use the knowledge when creating the Input. And sometimes you don't even have to dissect algorithms, when you can use trial-and-error method.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="NonlinearTASing.html#turbo-seeking">Nonlinear TASing</a><span class="rvts21"> (example of luck manipulation)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Subpixels</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The term used when in-game objects have coordinates with fractional parts.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Generally, there's difference between on-screen coordinates of a sprite and in-game coordinates of the object this sprite represents. In some games those coordinates have the same scale and their values coincide, but usually on-screen images represent a rough outline of the real state of things. So, to get max precision TASers observe the memory of emulated console, using Memory Watch tool or custom Lua HUD. This way even allows to see hidden variables of the game, that aren't displayed on-screen normally.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Recording</span></p>
|
||||
<p class="rvps10"><span class="rvts21">One of ways to create Input for a movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It consists of appending new Input sequentially to the end of current movie, while watching interim results of the Input.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Another way would be drawing Input directly in the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="Toolbox.html#recorder">Toolbox</a><span class="rvts21">, </span><a class="rvts27" href="TASingMethodology.html#linear-tasing">TASing Methodology</a><span class="rvts21">, </span><a class="rvts27" href="TraditionalTASing.html">Traditional TASing</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Rerecording</span></p>
|
||||
<p class="rvps10"><span class="rvts21">One of ways to edit Input in a movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It consists of rewriting old Input sequentially from starting frame to ending frame, while watching interim results of the Input changes.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Another way would be direct modification of existing Input in the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="TASingMethodology.html#linear-tasing">TASing Methodology</a><span class="rvts21">, </span><a class="rvts27" href="TraditionalTASing.html">Traditional TASing</a><span class="rvts21">, </span><a class="rvts27" href="Ideas.html#RerecordsCounter">Rerecords counter</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Multitracking</span><span class="rvts21"> (multi-track recording)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">One of ways to record Input for a walkthrough of the game in multi-player mode.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It consists of recording Input for a segment of the movie by taking turns for every player separately.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Another way would be recording Input for all players simultaneously.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="Toolbox.html#multitracking">Toolbox</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Frame Advance</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Step-by-step emulation of a game using the minimum units of measuring time – frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used for manual control of progression of time. Considered to be more effective replacement to "slow motion".</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Turbo</span><span class="rvts21"> (turbo speed)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The feature of speeding up emulation to the maximum possible speed.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used for skipping meaningless in-game events and reducing waiting time when emulator is seeking.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Most emulators allow to customize emulation speed, slowing it down or speeding up when needed. Turbo speed means the fastest speed possible, which depends on your computer performance.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="Toolbox.html#turbo-seek">Toolbox</a><span class="rvts21">, </span><a class="rvts27" href="NonlinearTASing.html#turbo-seeking">Nonlinear TASing</a><span class="rvts21">, </span><a class="rvts27" href="SemiautomaticTASing.html#turbo-seeking">Semiautomatic TASing</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Savestate</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A snapshot of the emulated system's state at that current moment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Unlike in-game saves, savestate contains comprehensive data on the state of emulated hardware.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Piano Roll</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A type of visual representation of data, similar to table or grid view.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The interface is used in many music editing programs (MIDI sequencers and MOD trackers). Its name and basic concept was derived from existing storage medium used to operate a mechanic piano (paper rolls).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Taseditor's Piano Roll displays current movie data (Input and Markers) and allows editing the data by mouse clicks. It also displays auxillary information like pointers, Bookmarks, Lag log, etc.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Every row of the Piano Roll corresponds to one frame of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="PianoRoll.html">Piano Roll</a><span class="rvts21">, </span><a class="rvts27" href="Ideas.html#PianoRoll">Piano Roll specs</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Playback cursor</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Pointer at currently played frame of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Events of this frame are displayed in emulator's main window as current screenshot. Piano Roll marks respective row with light-blue color and the "Play" symbol (light-blue arrow).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Only one frame of the movie can be seen at any given moment. To see the screenshot of upcoming events you'll have to move Playback cursor forward (down in Piano Roll). To see the screenshot of previous events you'll have to move Playback cursor backward (up in Piano Roll).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="PianoRoll.html">Piano Roll</a><span class="rvts21">, </span><a class="rvts27" href="Navigation.html#playback-cursor">Playback cursor Navigation</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Greenzone </span><span class="rvts21">(access zone)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The storage designed for speeding up Playback cursor navigation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This storage automatically collects savestates for all emulated frames of the movie, and when it's necessary to rewind or jump forward to a frame, Taseditor loads respective savestate from Greenzone.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="Toolbox.html#progressbar">Toolbox</a><span class="rvts21">, </span><a class="rvts27" href="ProgramCustomization.html#SetGreenzonecapacity">Program Customization</a><span class="rvts21">, </span><a class="rvts27" href="Ideas.html#Greenzone">Greenzone specs</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Selection</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Set of rows in Piano Roll that are highlighted by special color (usually dark-blue).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Any row of Piano Roll (and respective frame of the movie) can be either selected or not selected.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Selection allows to operate with many frames at once, for example, delete whole section of the movie instead of deleting every single frame in it.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Upper row of the Selection is called "Selection cursor".</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Selection cursor automatically follows the process of Input editing.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="PianoRoll.html">Piano Roll</a><span class="rvts21">, </span><a class="rvts27" href="Navigation.html#selection-cursor">Selection cursor Navigation</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Marker</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Yellow mark for a row in Piano Roll that emphasizes the frame among its neighbors.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Any row in the Piano Roll can be marked. Markers can improve the distinctness of movie data.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Markers can be used to:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">organize the Input</span></li>
|
||||
<li class="rvps10"><span class="rvts21">formalize knowledge (using text Notes)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">speed up navigation</span></li>
|
||||
<li class="rvps10"><span class="rvts21">speed up selection of segments (</span><span class="rvts30">Ctrl + A</span><span class="rvts21">)</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="PianoRoll.html#markers">Piano Roll</a><span class="rvts21">, </span><a class="rvts27" href="Ideas.html#Markers">Markers specs</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Note</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Single line of text accompanying every Marker.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="PianoRoll.html#markers">Piano Roll</a><span class="rvts21">, </span><a class="rvts27" href="Controls.html#notes">Controls</a><span class="rvts21">, </span><a class="rvts27" href="AdvancedFeatures.html#UsingMarkers">Advanced Features</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Bookmark</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A numbered mark for a frame of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Bookmark stores all necessary data about the frame it was placed on. Including the movie branch that contains Input that definitely leads the game to events of this frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Bookmarks can be used for Playback cursor navigation, but their main purpose is to store branches.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="Toolbox.html#bookmarks">Toolbox</a><span class="rvts21">, </span><a class="rvts27" href="Ideas.html#BookmarksBranches">Bookmarks specs</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Branch</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A copy of the movie, storing its state at the moment of creating the Bookmark.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Current movie can be replaced by the branch when necessary, thus restoring saved state of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">With branches you can have many different movies in one project, and you can instantly switch among them:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">to compare alternative strategies of walkthrough</span></li>
|
||||
<li class="rvps10"><span class="rvts21">to store current best approach when testing different solutions in a segment</span></li>
|
||||
<li class="rvps10"><span class="rvts21">to store examples of unused tricks that could be useful in future</span></li>
|
||||
<li class="rvps10"><span class="rvts21">to compare your own movie with somebody else's movie (e.g. when making an improvement)</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="Toolbox.html#bookmarks">Toolbox</a><span class="rvts21">, </span><a class="rvts27" href="ProgramCustomization.html#BranchesrestoreentireMovie">Program Customization</a><span class="rvts21">, </span><a class="rvts27" href="Ideas.html#BookmarksBranches">Branches specs</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Project</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Container for storing work data in Taseditor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="AdvancedFeatures.html#ProjectsSharing">Advanced Features</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Lua</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A programming language used in many TAS-friendly emulators.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Useful for making custom tools and data visualization.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="AdvancedFeatures.html#UsingLua">Advanced Features</a><span class="rvts21">, </span><span class="rvts27">Lua</span><span class="rvts21">, </span><a class="rvts27" href="LuaAPI.html">Lua API</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Bot </span><span class="rvts21">(robot)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A program made for automation of a task.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Bots are created to free humans from tedious work that doesn't require high intelligence. Unlike humans, bots don't invent the solution, they just methodically test all possible approaches within given limits, following strict algorithm made by the programmer.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Nowadays bots are only practical for running exhaustive search within a small segment of the movie. Most of time it's faster to search for best solution manually, using human intuition to eliminate dead ends without unnecessary tests.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Making bots requires programming skills. TASing bots are either written in Lua or built-in into emulators by modifying open source code.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Pattern</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A predefined sequence of Input values for a button.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">More: </span><a class="rvts27" href="AdvancedFeatures.html#UsingPatterns">Advanced Features</a><span class="rvts21">, </span><a class="rvts27" href="Ideas.html#Patterns">Patterns specs</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com">Free EBook and documentation generator</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,583 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Ideas</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("Ideas");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Ideas</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="TASEditorInside.html">TAS Editor Inside</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="TASEditorInside.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="TASEditorInside.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="Implementation.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Ideas</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Тасэдитор объединяет множество экспериментальных идей в единую систему. Многие из этих идей были озвучены очень давно (см. темы на форуме в духе "</span><a class="rvts27" href="http://tasvideos.org/forum/viewtopic.php?t=4559" target="_blank">инструмент мечты</a><span class="rvts21">" и т.д.), но для их реализации в рамках единой непротиворечивой системы понадобилось немалое время.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Основообразующей идеей Тасэдитора является интерфейс Piano Roll, позволяющий взаимодействовать с мувиком в интуитивно понятной форме. </span><span class="rvts21">Первые упоминания о необходимости создания инструмента для ТАСинга на основе Piano Roll звучали ещё в </span><a class="rvts27" href="http://tasvideos.org/forum/viewtopic.php?p=38496#38496" target="_blank">2005 году</a><span class="rvts21">, возможно, даже ранее. П</span><span class="rvts21">рототип под названием TASEdit был создан в 2008 году. Окончательное видение Тасэдитора сформировалось в сентябре 2011 года и дорабатывалось по ходу разработки вплоть до лета 2012. Помимо реализованных идей в</span><span class="rvts21"> это время было придумано множество перспективных, но второстепенных или сложно реализуемых идей, которые было решено отложить на будущее.</span></p>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps21"><table width="700" border="1" cellpadding="0" cellspacing="0" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid; background-color: #0000ff;"><p class="rvps5"><a class="rvts77" href="Ideas.html#ImplementedIdeas">Реализовано в 1.0</a></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; background-color: #0000ff;"><p class="rvps5"><a class="rvts77" href="Ideas.html#PlannedIdeas">Запланировано на 2.0</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid;"><p class="rvps18"><a class="rvts57" href="Ideas.html#PianoRoll">Piano Roll</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#Selection">Выделение</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#Markers">Маркеры</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#HotChanges">Горячие Правки</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#Greenzone">Гринзона</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#Playback">Проигрыватель</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#GreenArrow">Зелёная стрелка</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#AutoRestoring">Автовосстановление утраченной позиции</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#Recorder">Мультитрекинг-рекордер</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#Lua">Lua-автоматизация</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#BookmarksBranches">Закладки и ответвления</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#PopupWindows">Всплывающие окна</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#HistoryLog">Журнал Истории</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#RerecordsCounter">Счётчик перезаписей</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#Modifiers">Система клавиш-модификаторов</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#Patterns">Шаблоны</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#CrossingGaps">Пересечение промежутков</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#SaveCompact">Компактное сохранение</a></p>
|
||||
<p class="rvps18"><a class="rvts57" href="Ideas.html#Autosave">Автосохранение</a></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid;"><p class="rvps5"><a class="rvts76" href="Ideas.html#OutputLog">Журнал Вывода</a></p>
|
||||
<p class="rvps5"><a class="rvts76" href="Ideas.html#Minimap">Миникарта</a></p>
|
||||
<p class="rvps5"><a class="rvts76" href="Ideas.html#VirtualJoypad">Виртуальный Джойстик</a></p>
|
||||
<p class="rvps5"><a class="rvts76" href="Ideas.html#BetterSelection">Усовершенствование Выделения</a></p>
|
||||
<p class="rvps5"><a class="rvts76" href="Ideas.html#BetterColumns">Гибкая настройка колонок</a></p>
|
||||
<p class="rvps5"><a class="rvts76" href="Ideas.html#RerecordsHeatmap">Теплокарта перезаписей</a></p>
|
||||
<p class="rvps5"><a class="rvts76" href="Ideas.html#Etc">Прочие мелочи</a></p>
|
||||
<p class="rvps5"><a class="rvts76" href="Ideas.html#OtherPlatforms">Поддержка платформ, отличных от NES</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="ImplementedIdeas"></a>
|
||||
<span class="rvts34"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts75">Реализованные идеи</span></p>
|
||||
<p class="rvps10"><a name="PianoRoll"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Piano Roll</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Основа Тасэдитора, вокруг этой идеи и были сформированы все остальные.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Представляет собой значительно переработанный компонент Список (ListView) или Таблица (GridView). Столбцы Списка соответствуют кнопкам Ввода, строки Списка соответствуют кадрам мувика. Количество строк Списка регулярно автоматически обновляется, чтобы соответствовать количеству кадров текущего мувика. Строки нумеруются сверху вниз от нуля. Номер строки равен номеру кадра, с которым ассоциируется эта строка. Количество столбцов зависит от типа мувика (от количества джойстиков и, соответственно, количества кнопок).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Слева перед столбцами Ввода располагаются два дополнительных столбца. Самый первый столбец (шириной ~17 пикселей) отвечает за отображение иконок и за управление Курсором Проигрывателя. Текущее положение Курсора Проигрывателя отображается иконкой в виде голубой стрелки. При щелчке левой кнопкой по этому столбцу Курсор Проигрывателя посылается на соответствующий кадр, и начинается перетаскивание Курсора, пока не будет отпущена левая кнопка.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Второй столбец (шириной 75 пикселей) отвечает за отображение номеров кадров, отображение Маркеров, управление Выделением и управление Маркерами. При одинарном щелчке левой кнопкой по этому столбцу изменяется Выделение (и можно растягивать Выделение перетаскиванием). При двойном щелчке на этом кадре ставится Маркер, и начинается перетаскивание этого Маркера, пока не будет отпущена левая кнопка.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В Заголовке Списка отображаются названия столбцов. Самый первый столбец (столбец иконок) не имеет названия, второй столбец назван "Frame#" (номер кадра), остальные столбцы обозначены символом соответствующей кнопки джойстика. Этот же символ отображается в ячейках данного столбца на тех строках, где данная кнопка является нажатой. По ячейкам Заголовка Списка можно щёлкать, изменяя Ввод соответствующей кнопки в выделенных кадрах. А при щелчке по "Frame#" изменяются Маркеры в выделенных кадрах. Кроме того, Заголовок служит индикатором зажатых кнопок джойстика, а при Записи Ввода в Заголовке вспыхивают символы, кнопки которых были только что записаны в мувик.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Столбцы Ввода отображают состояние соответствующей кнопки джойстика для каждого кадра мувика. Чтобы узнать состояние кнопки, нужно визуально найти пересечение строки требуемого кадра и столбца требуемой кнопки. Если в этой ячейке находится символ кнопки, то кнопка в данном кадре нажата. Если в этой ячейке пустота или прочерк, то кнопка отпущена. Щелчком левой кнопкой мыши по любой ячейке Ввода можно инвертировать состояние соответствующей кнопки Ввода. Кроме того, если зажать левую кнопку мыши, можно рисовать или стирать Ввод в соседних кадрах, перемещая курсор мыши выше или ниже. Эти и другие возможности быстрого редактирования Ввода призваны полностью заменить линейную Запись нелинейным редактированием.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Строки Piano Roll раскрашиваются разными цветами в пастельных тонах, чтобы на их фоне были чётко видны номера кадров (отображаемые чёрным цветом) и символы кнопочных нажатий (отображаемые тёмными цветами). По цвету строки Piano Roll пользователь может сразу определить, находится ли данный кадр мувика в Гринзоне, проявляется ли лаг в данном кадре, является ли данный кадр текущим (отображаемым в окне эмулятора в данный момент), является ли данный кадр выделенным. Также дополнительными цветами можно акцентировать внимание пользователя на определённых кадрах, например, на кадре окончания добегания (мигающий голубой цвет) или на ключевом кадре отката (фиолетовый цвет). Кроме того, по цвету фона ячеек с номерами кадров пользователь может определить наличие Маркера на этом кадре (жёлтый цвет).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Расцветка ячеек Piano Roll зависит не только от строки, но и от столбца (хоть и в меньшей мере). Столбец иконок всегда отображается белым цветом. Стобец номеров кадров отображается бледным оттенком текущего цвета строки. Столбцы кнопок Ввода для первого (а также третьего) джойстика отображаются нормальным оттенком текущего цвета строки (зелёным, красным, голубым и т.д.), а столбцы кнопок Ввода для второго (а также четвёртого) джойстика отображаются немного затемнённым оттенком текущего цвета строки.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Видимая область Piano Roll может скроллироваться колесом мыши или с помощью скроллбаров, а также с помощью множества других способов </span><a class="rvts38" href="Navigation.html#scrolling-piano-roll">навигации</a><span class="rvts21">. Многообразие способов призвано ускорить навигацию к любому желаемому участку мувика, так как в видимой области отображается лишь ограниченное количество строк. Это количество зависит от текущей высоты Piano Roll в пикселах, которая зависит от текущей высоты окна TAS Editor.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="Selection"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Выделение</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Как и в любом другом редакторе, в Тасэдиторе Выделение служит для применения операций к множеству кадров одновременно. Кроме того, здесь Выделение служит в качестве указателя (курсора) на место последнего щелчка по Вводу.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Выделение хранится в виде списка номеров кадров, считающихся выделенными.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В памяти хранится Журнал Выделений в виде массива списков. Размер массива равен размеру Журнала Истории, можно возвращаться к предыдущим выделениям с помощью </span><span class="rvts30">Ctrl + Q</span><span class="rvts21"> и </span><span class="rvts30">Ctrl + W</span><span class="rvts21">. Это полезно для быстрого отслеживания истории недавних щелчков по Piano Roll.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Для управления Выделением служит столбец с номерами кадров. Если после щелчка по номеру кадра зажать левую кнопку, можно растягивать Выделение на соседние кадры. Если зажать клавишу </span><span class="rvts30">Ctrl</span><span class="rvts21"> перед щелчком по номеру кадра, ранее выделенные кадры останутся выделенными. А при простом щелчке по номеру кадра или Ввода текущее Выделение уходит в историю Выделений, и вместо него создаётся новое Выделение, состоящее из одного кадра (по которому был сделан щелчок). Если зажать клавишу </span><span class="rvts30">Shift</span><span class="rvts21">, выделятся все кадры от начала старого Выделения до кадра щелчка. Если зажать </span><span class="rvts30">Alt</span><span class="rvts21">, создастся Выделение по шаблону. Также Выделение меняется и при щелчке по ячейкам Ввода, но только когда не зажаты клавиши модификаторы,</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Самый верхний выделенный кадр называется Курсором Выделения. Если не выделено ни одного кадра, подразумевается, что Курсор Выделения указывает на кадр с номером -1. Это нужно для некоторых ситуаций, например, при отсутствии Выделения в нижнем текстовом поле отображается Заметка нулевого Маркера.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Журнал Выделений (в том числе текущее Выделение) сохраняется и загружается из файла проекта. При изменении настройки "undo levels" происходит соответствующее изменение размера Журнала Выделений.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При вставке и удалении кадров текущее Выделение смещается на соответственное количество строк вниз или вверх, чтобы оставаться на тех же позициях относительно Ввода, что и перед вставкой/удалением.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Текущее Выделение можно сдвигать (</span><span class="rvts30">Ctrl + Вверх</span><span class="rvts21"> / </span><span class="rvts30">Ctrl + Вниз</span><span class="rvts21"> / </span><span class="rvts30">Ctrl + Home</span><span class="rvts21"> / </span><span class="rvts30">Ctrl + End</span><span class="rvts21">). Если часть Выделения выходит за рамки Piano Roll, эта часть исчезает. То есть пользователь не может выделить кадры за пределами текущего мувика.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Курсором Выделения можно осуществлять прыжки по Маркерам (</span><span class="rvts30">Ctrl + Page Up</span><span class="rvts21"> / </span><span class="rvts30">Ctrl + Page Down</span><span class="rvts21">), при этом текущее Выделение уходит в Историю, а вместо него появляется один выделенный кадр на месте следующего Маркера.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Видимая область Piano Roll всегда следует за Выделением. При этом, если Выделение не помещается целиком на экране, Piano Roll скроллируется таким образом, чтобы Курсор Выделения был в середине, а если Выделение помещается – центрирует всё Выделение.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В нижнем текстовом поле отображается текст Заметки маркера, на участке которого находится Курсор Выделения. Этот текст обновляется при каждом изменении Выделения, а также при изменении текущих Маркеров.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При нажатии </span><span class="rvts30">Ctrl + A</span><span class="rvts21"> текущее Выделение уходит в Историю, вместо него становятся выделенными все кадры, начиная с Маркера, на участке которого был Курсор Выделения, заканчивая следующим Маркером (не включая этот Маркер). Таким образом выделяется весь участок текущего Маркера. При следующем нажатии </span><span class="rvts30">Ctrl + A</span><span class="rvts21"> Выделение изменится на набор кадров между Маркерами, не включая верхний и нижний Маркеры. При третьем </span><span class="rvts30">Ctrl + A</span><span class="rvts21"> Выделение изменится на набор кадров между Маркерами, не включая верхний, но включая нижний Маркер. Наконец, при четвёртом нажатии </span><span class="rvts30">Ctrl + A</span><span class="rvts21"> Выделение изменится на набор кадров между Маркерами, включающий оба Маркера. При дальнейших нажатиях </span><span class="rvts30">Ctrl + A</span><span class="rvts21"> будет повторение предыдущих вариантов выделения. Это позволяет пользователю быстро выделить нужный участок, причём в большинстве случаев ТАСеру будет нужен именно первый вариант выделения между Маркерами.</span></li>
|
||||
</ul>
|
||||
<p class="rvps14"><a name="Markers"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Маркеры</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">При редактировании больших мувиков пользователю может понадобиться установка отметок на некоторые строки Piano Roll, чтобы эти строки визуально отличались от соседних. После ряда усовершенствований эта идея вылилась в многогранную фичу.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Любой кадр мувика может быть отмечен. При желании пользователь может отметить Маркерами сразу все кадры мувика. Кроме того, пользователь может оставить отметку, например, на кадре 1200, а затем сделать усечение Ввода после кадра 1000, оставив отвязанный от Ввода Маркер за пределами мувика. Этот Маркер будет оставаться в проекте; чтобы увидеть его наличие, нужно проэмулировать мувик до кадра 1200, чтобы в Piano Roll отражалась строка с этим Маркером.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Неотмеченные строки Piano Roll отображаются обычными цветами, а в отмеченных строках ячейка с номером кадра имеет жёлтый цвет фона. Этот цвет выбран, так как Маркеры призваны акцентировать внимание пользователя на отмеченных кадрах. Также номера отмеченных кадров отображаются особым шрифтом, чтобы о наличии Маркера можно было догадаться, даже когда жёлтый фон ячейки загораживается синим цветом Выделения.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Маркеры могут быть привязаны к Вводу (тогда они отображаются бледно-жёлтым цветом), а могут быть отвязанными (отображаются более насыщенным жёлтым цветом). Когда Маркеры привязаны, на них действуют операции по смещению Ввода вверх/вниз, а также усечению Ввода.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Маркер ставится двойным щелчком левой кнопкой мыши по номеру желаемого кадра. Если сделать двойной щелчок по уже установленному Маркеру, начинается его перетаскивание (до момента отпускания левой кнопки). Так можно перенести Маркер на другой кадр или удалить, перенеся за рамки Piano Roll. При перетаскивании под курсором мыши висит образ Маркера в виде жёлтого прямоугольника с номером кадра, с которого был снят этот Маркер. Чтобы отменить перетаскивание, нужно опустить Маркер либо на ту же самую ячейку с номером кадра, либо на любую ячейку Ввода.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Также Маркеры можно устанавливать и удалять с помощью контекстного меню по правой кнопке или с помощью щелчка по Frame#.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Обычно Маркеры ставятся относительно далеко друг от друга, и между ними находятся промежутки из неотмеченных кадров. Поэтому Маркеры можно воспринимать не только как цветовое выделение особенных кадров, но и как пограничные отметки для участков мувика. Для стандартизации принята следующая терминология: каждому Маркеру соответствует участок кадров мувика, начинающийся с отмеченного кадра и заканчивающийся последним неотмеченным кадром. Например, если в мувике на кадрах 10 и 20 стоят Маркеры, то участком первого маркера является регион кадров с 10-го по 19-й, а участком второго маркера – регион с 20-го по последний кадр мувика.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Промежутки между Маркерами можно пересекать прыжками от текущего к следующему (или предыдущему). Это позволяет в ряде случаев ускорить навигацию по мувику.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">С помощью функции </span><span class="rvts25">Select between Markers</span><span class="rvts21"> (</span><span class="rvts30">Ctrl + A</span><span class="rvts21">) можно быстро выделить все кадры на участке текущего Маркера. Таким образом Маркеры позволяют ускорить не только навигацию, но и редактирование.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Каждый Маркер имеет свою текстовую Заметку. При создании она пустая. Пользователь может просматривать и редактировать Заметку с помощью любого из двух имеющихся текстовых полей. В верхнем текстовом поле отображается Заметка Маркера, на участке которого находится Курсор Проигрывателя. В нижнем текстовом поле отображается Заметка Маркера, на участке которого находится Курсор Выделения. Таким образом, чтобы отредактировать желаемую Заметку, нужно сначала поставить один из курсоров на её Маркер или на кадр под Маркером. В теории это звучит неудобно, но рабочий процесс в Тасэдиторе организован таким образом, что под нужными Маркерами обязательно стоит какой-нибудь курсор.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Объём Заметки ограничен сотней символов, так как Заметки предназначены не для хранения длинных текстов, а для коротких комментариев, тегов и тому подобных записок на салфетках. В крайнем случае можно разместить несколько Маркеров подряд, разбив длинный текст на несколько соседствующих Заметок.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">По тексту Заметок можно осуществлять обычный поиск (Find Note) и нечёткий поиск (Similar/More). Подробнее см. </span><a class="rvts38" href="AdvancedFeatures.html#UsingMarkers">Продвинутые возможности</a><span class="rvts21">.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Маркеры сохраняются и восстанавливаются из ответвлений Закладок вместе с Вводом. Каждая операция с Маркерами заносится в Журнал Истории аналогично операциям с Вводом. В файле проекта Маркеры сохраняются сразу после Ввода.</span></li>
|
||||
</ul>
|
||||
<p class="rvps14"><a name="HotChanges"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Горячие Правки</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Раскраска текстовых символов в ячейках Ввода разными цветами, в зависимости от давности редактирования каждой ячейки. Подробнее см. </span><a class="rvts27" href="PianoRoll.html#HotChanges">Интерфейс программы</a><span class="rvts21"> и </span><a class="rvts27" href="ProgramCustomization.html#EnableHotChanges">Настройка программы</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">В памяти хранятся значения сразу всех ячеек Ввода, даже несмотря на то, что большинство из них имеет нулевой уровень горячести. Это необходимо для тех редких случаев, когда массово изменяются почти все ячейки мувика (например, при операциях Import или Paste). Массив Горячих Правок занимает много места в оперативной памяти, но хорошо сжимается и занимает мало места на диске.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">16 градаций цвета, чтобы в одном байте умещалась информация о горячести двух ячеек. Кроме того, добавлять ещё больше градаций нет смысла, так как человеческий глаз будет хуже различать их, а ценность Горячих Правок именно в возможности быстрой визуальной оценки Ввода, не требующей длительного обдумывания.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Состояние текущей карты Горячих Правок меняется только при добавлении нового пункта в Журнал истории и при откатах Истории.</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 40px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">при редактировании Ввода старые ячейки теряют один уровень горячести, а изменённые ячейки приобретают максимальный уровень</span></li>
|
||||
<li class="rvps14"><span class="rvts21">при удалении кадров старые ячейки теряют один уровень горячести</span></li>
|
||||
<li class="rvps14"><span class="rvts21">при вставке кадров старые ячейки теряют один уровень горячести, а все ячейки вставленных кадров приобретают максимальный уровень</span></li>
|
||||
<li class="rvps14"><span class="rvts21">при изменении Маркеров или Закладок, а также при усечении мувика Горячие Правки не меняются</span></li>
|
||||
<li class="rvps14"><span class="rvts21">при прыжке на Закладку во времени текущие Горячие Правки замещаются Горячими Правками из ответвления Закладки</span></li>
|
||||
<li class="rvps14"><span class="rvts21">при импорте Ввода старые ячейки обнуляют уровень горячести, а изменённые ячейки приобретают максимальный уровень</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="Greenzone"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Гринзона</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Так как интерфейс Piano Roll предоставляет пользователю почти мгновенный доступ к изменению Ввода на любом кадре мувика, желательно также предоставить быстрый доступ к просмотру состояния игры на любом кадре мувика. Это реализуется с помощью кеширования данных о всех полученных состояниях игры.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Гринзона представляет собой массив информации о Выводе игры на начало каждого кадра. То есть в ячейке с номером 0 хранится состояние игры до начала эмуляции, в ячейке 1 – состояние игры перед началом эмуляции второго кадра (кадра с номером 000001) и т.д. Помимо сэйва для каждого кадра хранится информация о лаге в этом кадре, теоретически возможно хранение и другой информации.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Гринзона начинается с нулевого кадра и имеет нижнюю границу (голову) – номер кадра, начиная с которого в Гринзоне отсутствует информация о дальнейших состояниях игры. Для кадров, номер которых меньше головы, в Гринзоне может иметься информация.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Данные в Гринзону собираются в начале каждого кадра (перед эмуляцией) по следующему принципу: если в массиве Гринзоны ячейка с номером, равным текущему кадру, пустует, или же позиция головы Гринзоны меньше номера текущего кадра, то ячейка массива заполняется информацией о текущем состоянии игры (из эмулятора), а голова Гринзоны при необходимости перемещается вперёд.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Для экономии памяти Гринзона периодически разреживается, удаляя сэйвы (но не информацию о лаге) некоторых ранних кадров, от которых Курсор Проигрывателя ушёл достаточно далеко. </span><span class="rvts21">Подробнее см. </span><a class="rvts27" href="ProgramCustomization.html#SetGreenzonecapacity">Настройка программы</a><span class="rvts21">.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Вся Гринзона сохраняется и загружается из файла проекта. После загрузки проекта Тасэдитор восстанавливает состояние Курсора Проигрывателя с помощью Гринзоны.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При любом изменении Ввода текущего мувика из Гринзоны удаляется информация о кадрах, идущих после первого изменённого кадра. Это реализуется с помощью уменьшения позиции головы Гринзоны и удаления устаревшей информации из массива (но без освобождения памяти, так как на место старых сэйвов вскоре будут записаны новые данные примерно того же размера). Обычно одновременно с этим перемещается Курсор Проигрывателя, чтобы он всегда находился внутри Гринзоны (чтобы на экране FCEUX никогда не отображалось неактуальное состояние игры).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При создании Закладки в неё копируется информация из соответствующего кадра Гринзоны. При загрузке ответвления этой Закладки из неё копируется информация в соответствующую ячейку Гринзоны, и при необходимости передвигается позиция головы.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Информация из Гринзоны используется при раскрашивании строк Piano Roll. Информация о лаге (Журнал лага) отображается не только для кадров, содержащихся в Гринзоне, но и для отсутствующих в ней кадров. Если в Гринзоне нет информации о лаге на определённом кадре, то предполагается, что этот кадр без лага.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Информация о лаге собирается в Гринзону одновременно со сбором текущего состояния игры, то есть перед началом эмуляции текущего кадра. В этот момент эмулятор обладает информацией о лаге предыдущего кадра, поэтому на кадре с номером 000020 данные о лаге сохраняются в ячейку 19. Также именно в этот момент может сработать операция </span><a class="rvts27" href="Operations.html#AdjustLag">AdjustLag</a><span class="rvts21">, которая сдвигает весь Ввод в последующих кадрах мувика на 1 кадр вверх или вниз. Ввод сдвигается вверх, если в Журнале лага на прошлом кадре был лаг, а теперь его не стало. Ввод сдвигается вниз, если в Журнале лага на прошлом кадре не было лага, а теперь он есть. Вместе с Вводом аналогично сдвигается и все последующие ячейки Журнала лага, чтобы красные строки Piano Roll по-прежнему соответствовали сдвинувшимся пропускам во Вводе. Кроме того, после операции AdjustLag Курсор Проигрывателя насильно возвращается на предыдущий кадр (в котором изменилась информация о лаге), чтобы проэмулировать его заново. Это реализуется не простой перемоткой назад, а усечением Гринзоны после предыдущего кадра.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="Playback"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Проигрыватель</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Проигрыватель – это собрание всех функций по просмотру Вывода (состояния игры в нужных кадрах).</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Главный атрибут Проигрывателя – текущий проигрываемый кадр мувика, скриншот этого кадра отображается в окне эмулятора в данный момент времени. Этому кадру соответствует голубая строка в Piano Roll, которая носит название Курсор Проигрывателя. Так как Курсор Проигрывателя привязан к состоянию эмулируемой игры, можно использовать его не только в качестве индикатора, но и в качестве управляющего элемента. Чтобы увидеть на экране FCEUX события интересующего кадра, нужно передвинуть Курсор Проигрывателя на строку с номером этого кадра. Для этого есть </span><a class="rvts27" href="Navigation.html#playback-cursor">множество способов</a><span class="rvts21">.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Когда пользователь посылает Курсор Проигрывателя на кадр, содержащийся в Гринзоне, состояние эмулируемой игры восстанавливается из соответствующего сэйва. Так как при этом не было никакой эмуляции, Тасэдитор имитирует события "frame boundary" и "frame begin"/"frame end", чтобы сработали соответствующие функции Lua.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Когда пользователь посылает Курсор Проигрывателя на кадр, не содержащийся в Гринзоне, Тасэдитор восстанавливает состояние игры на ближайший предшествующий кадр, для которого имеется сэйв Гринзоны, а затем запускает добегание к желаемому кадру. Добегание – это эмуляция, которая автоматически останавливается при достижении целевого кадра. Во время добегания на целевом кадре мигает копия голубого курсора.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Так как эмулятор обеспечивает детерминизм, состояние игры на любом кадре можно гарантированно получить, используя базовое состояние игры (состояние на начало мувика) и Ввод из мувика. Более того, можно получить требуемое состояние, используя состояние на любой предыдущий кадр (сэйв из Гринзоны) и Ввод из мувика. На этом принципе и основано добегание.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Процесс добегания отображается на прогрессбаре, чтобы в случае длительного добегания пользователь мог оценить оставшееся время ожидания. Когда добегания нет, прогрессбар полностью заполнен во время паузы и пуст во время эмуляции.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Добегание может осуществляться на максимально возможной скорости эмуляции. В этом случае для относительно небольших участков добегание будет завершено практически мгновенно.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Во многих случаях полезно автоматически останавливать эмуляцию на последнем кадре, для которого в мувике есть Ввод. Для этого служит настройка </span><a class="rvts27" href="ProgramCustomization.html#AutopauseattheendofMovie">Autopause at the end of Movie</a><span class="rvts21">, благодаря которой Курсор Проигрывателя при отпущенной паузе не будет убегать слишком далеко.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В большинстве случаев пользователю не требуется автоматически скроллировать Piano Roll к Курсору Проигрывателя во время передвижения этого курсора. Для тех случаев, когда это всё-таки нужно, служит галочка "Follow cursor".</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="GreenArrow"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Зелёная стрелка</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">При создании спидранов ТАСер пытается обогнать свой рекорд на каждом участке. В большинстве случаев критерием оптимальности является номер кадра, на котором происходит конечное событие участка. Для его определения ТАСер перемещает Курсор Проигрывателя, одновременно просматривая экран FCEUX, и останавливает этот ручной поиск в тот момент, когда обнаружено начало интересующего события. Обычно Курсор Проигрывателя так и остаётся на найденном кадре, а ТАСер начинает изменять Ввод на участке, надеясь улучшить его и получить то же событие на более ранний кадр.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Во время изменения Ввода Гринзона усекается, и Курсор Проигрывателя отступает назад. Когда ТАСер считает, что внёс во Ввод достаточно существенные изменения, он начинает проверку Вывода, чтобы определить, на каком кадре начинается целевое событие теперь. Для этого он опять перемещает Курсор Проигрывателя, одновременно просматривая экран FCEUX.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Чтобы сделать вывод об улучшении, ТАСеру нужно сравнить старый номер кадра (найденный в прошлый раз) и новый номер, найденный только что. Тасэдитор визуализирует эти данные, чтобы пользователю не требовалось запоминать их в уме. На новый номер указывает Курсор Проигрывателя, на старый номер указывает зелёная стрелка.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Полное название зелёной стрелки – утерянная позиция Курсора Проигрывателя.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Более адекватной заменой зелёной стрелке служат Маркеры и Закладки, устанавливаемые вручную.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Иконка зелёной стрелки отображается в столбце иконок Piano Roll.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При рисовании иконок в Piano Roll зелёная стрелка имеет более высокий приоритет над голубой стрелкой (иконкой Курсора Проигрывателя), так как положение голубого курсора можно определить и по другим столбцам.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Зелёная стрелка появляется на кадре вместо Курсора Проигрывателя в момент усечения Гринзоны. И она остаётся на этом кадре до тех пор, пока не будет произведена следующая последовательность событий:</span></li>
|
||||
</ul>
|
||||
<ol style="text-indent: 30px; margin-left: 40px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">эмуляция хотя бы одного кадра (подразумевается, что пользователь запустил просмотр участка)</span></li>
|
||||
<li class="rvps14"><span class="rvts21">следующее отступление Курсора Проигрывателя из-за усечения Гринзоны</span></li>
|
||||
</ol>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Таким образом, зелёная стрелка не меняет своё положение, когда ещё до запуска эмуляции Гринзона усекается повторно (например, ТАСер изменил Ввод на кадре 90, а затем на кадре 80, но зелёная стрелка так и осталась на кадре 100).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Также зелёная стрелка не меняет своё положение, когда Гринзона усекается во время добегания, и эмулятор в этот момент не стоит на паузе.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Зелёная стрелка не меняет своё положение при операциях </span><a class="rvts27" href="Operations.html#AdjustLag">AdjustLag</a><span class="rvts21">, </span><a class="rvts27" href="Operations.html#Branch">Branch</a><span class="rvts21">, </span><a class="rvts27" href="Operations.html#Record">Record</a><span class="rvts21">.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При нажатии средней кнопки мыши запускается добегание к зелёной стрелке, если она находится за пределами Гринзоны.</span></li>
|
||||
</ul>
|
||||
<p class="rvps14"><a name="AutoRestoring"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Автоматическое восстановление последней позиции</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">При создании любых ТАСов критерием оптимальности может быть состояние игры на одном и том же кадре, либо ход событий на одном и том же участке. ТАСер просматривает участок и оставляет Курсор Проигрывателя на последнем кадре участка, затем изменяет Ввод на участке и опять просматривает участок, останавливая Курсор Проигрывателя на том же самом кадре. Вывод об улучшении ТАСер делает либо во время просмотра событий участка, либо после остановки эмуляции, оценивая характеристики последнего кадра.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Этот процесс можно автоматизировать, автоматически запуская добегание к утерянной позиции Курсора Проигрывателя после каждого усечения Гринзоны. Для этого служит галочка "Auto-restore last position".</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Когда галочка установлена, сразу после усечения Гринзоны запускается добегание к последней позиции Курсора Проигрывателя.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Если Гринзона была усечена во время добегания, при усечении будет продолжено добегание к целевому кадру, а не к текущему положению Курсора Проигрывателя. Но если во время усечения Гринзоны добегание стоит на паузе, это добегание отменяется, и будет запущено добегание к утерянной позиции Курсора Проигрывателя. Подразумевается, что если ТАСер не дождался окончания добегания, поставил эмулятор на паузу и начал изменять Ввод на участке, то он сосредоточился на подучастке, поэтому дальнейший автоматический просмотр будет запускаться именно для этого подучастка.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Автовосстановление не запускается при операциях </span><a class="rvts27" href="Operations.html#AdjustLag">AdjustLag</a><span class="rvts21">, </span><a class="rvts27" href="Operations.html#Branch">Branch</a><span class="rvts21">, </span><a class="rvts27" href="Operations.html#Record">Record</a><span class="rvts21">. При срабатывании операции </span><a class="rvts27" href="Operations.html#AdjustLag">AdjustLag</a><span class="rvts21"> продолжается проигрывание мувика.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="Recorder"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Мультитрекинг-рекордер</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Рекордер – это собрание всех функций по редактированию Ввода на кадре под Курсором Проигрывателя. Рекордер предоставляет ТАСеру второй способ редактирования Ввода – Запись.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Мультитрекинг позволяет ТАСеру в режиме Записи изменять данные только одного выбранного джойстика, оставляя данные других джойстиков на этом же кадре нетронутыми. Подробнее см. </span><a class="rvts27" href="Toolbox.html#multitracking">Панель инструментов</a><span class="rvts21">.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Когда включен режим Записи, перед началом каждого кадра эмулятор опрашивает виртуальные джойстики и записывает данные в текущий мувик. Затем сразу же передаёт управление Рекордеру.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Рекордер:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 40px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">использует данные из мувика на кадре Курсора Проигрывателя в качестве записываемых данных, либо (если идёт Запись по шаблону, и сейчас надо записывать отсутствие нажатий) использует ноль в качестве записываемых данных</span></li>
|
||||
<li class="rvps14"><span class="rvts21">сравнивает записываемые данные со старыми данными, хранящимися в Журнале Истории</span></li>
|
||||
<li class="rvps14"><span class="rvts21">накладывает на изменения фильтр, соответствующий выбранному режиму мультитрекинга</span></li>
|
||||
<li class="rvps14"><span class="rvts21">избирательно объединяет старые данные с новыми, в соответствии с галочкой "Superimpose"</span></li>
|
||||
<li class="rvps14"><span class="rvts21">сохраняет реальные изменения в текущий мувик</span></li>
|
||||
<li class="rvps14"><span class="rvts21">вызывает добавление пункта в Журнал Истории и усечение Гринзоны</span></li>
|
||||
<li class="rvps14"><span class="rvts21">затем возвращает управление эмулятору</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Эмулятор возвращает данные из текущего мувика в виртуальные джойстики, чтобы использовать эти данные для наступающего кадра. Также в этот момент эмулятор запускает записанные команды (сброс и т.д.).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В каждом кадре Рекордер получает от эмулятора информацию о зажатых в данный момент кнопках виртуальных джойстиков и подготавливает для Piano Roll информацию о том, какие столбцы в Заголовке Piano Roll должны загораться зелёным светом. Например, если выбрана радиокнопка "2P" и установлена галочка </span><a class="rvts27" href="ProgramCustomization.html#Use1PkeysforallsingleRecordings">Use 1P keys for all single Recordings</a><span class="rvts21">, то при нажатии кнопки </span><span class="rvts29">A</span><span class="rvts21"> на первом джойстике в Заголовке Piano Roll будет загораться столбец "A" второго джойстика. А если в предыдущем кадре кнопка </span><span class="rvts29">A</span><span class="rvts21"> не была зажата, то Рекордер воспринимает это как нажатие кнопки, и в соответствии с галочкой </span><a class="rvts27" href="ProgramCustomization.html#UseInputkeysforColumnSet">Use Input keys for Column Set</a><span class="rvts21"> вызывает либо установку/снятие Ввода в Выделении, либо установку Ввода в Выделении по шаблону (если зажат </span><span class="rvts30">Alt</span><span class="rvts21">).</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="Lua"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Lua-автоматизация</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Lua позволяет пользователю расширить возможности Тасэдитора, в частности, предоставляет ТАСеру третий способ редактирования Ввода – автоматическая генерация.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Интерпретатор Lua-функций вызывает соответствующую функцию Тасэдитора не напрямую, а через луа-шлюз Тасэдитора (taseditor_lua).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При срабатывании какой-либо функции из библиотеки "taseditor" луа-интерпретатор берёт входные данные из стека, при необходимости конвертирует их в формат, принимаемый луа-шлюзом Тасэдитора, и передаёт их соответствующей функции луа-шлюза Тасэдитора.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Луа-шлюз Тасэдитора вызывает соответствующие функции Тасэдитора и передаёт полученный результат обратно в луа-интерпретатор.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Луа-интерпретатор помещает полученные данные в стек, при необходимости конвертируя их в формат, принимаемый луа-кодом.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Функции </span><span class="rvts68">submitinputchange()</span><span class="rvts21">, </span><span class="rvts68">submitinsertframes()</span><span class="rvts21"> и </span><span class="rvts68">submitdeleteframes()</span><span class="rvts21"> не вызывают соответствующее изменение мувика, а только создают запись в массиве отложенных заданий, хранящемся в луа-шлюзе Тасэдитора. Все отложенные задания реализуются при вызове </span><span class="rvts68">applyinputchanges()</span><span class="rvts21">. Благодаря этому луа-скрипт может вносить в мувик сразу несколько изменений, создавая только один пункт Журнала Истории.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="BookmarksBranches"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Закладки и ответвления</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Закладки являются специализированной альтернативой Маркерам. А ответвления служат для хранения нескольких мувиков в одном проекте. Для упрощения создания и навигации по ответвлениям они привязаны к Закладкам, по аналогии с традиционными сохранениями.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">В проекте может храниться не более 10 Закладок. Это ограничение связано с количеством цифровых клавиш на клавиатуре. Также такое ограничение позволяет отображать в окне TAS Editor основную информацию сразу обо всех Закладках, без необходимости скроллинга. Кроме того, многолетний опыт традиционного ТАСинга подтверждает, что такого количества слотов для Закладок вполне достаточно для продуктивного ТАСинга. </span></li>
|
||||
<li class="rvps14"><span class="rvts21">Закладка может быть установлена на любой кадр мувика. Закладки не исчезают, даже когда мувик усекается. Например, если поставить Закладку на кадр 1200, а затем сделать усечение Ввода после кадра 1000, за пределами мувика останется Закладка, при прыжке на которую мувик автоматически расширится до кадра 1200.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В Piano Roll Закладки отображаются иконкой с соответствующей цифрой (номером слота). Закладка, хранящая текущее ответвление мувика, отображается голубой цифрой, остальные Закладки отображаются зелёными цифрами.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Закладка устанавливается нажатием соответствующего хоткея (для каждого слота есть отдельный хоткей сохранения) либо щелчком правой кнопки мыши по слоту Закладки. При этом Закладка устанавливается на тот кадр, где в данный момент находится Курсор Проигрывателя. Этот номер кадра запоминается в Закладке, и в дальнейшем можно в любой момент отправить Курсор Проигрывателя на этот кадр, щёлкнув левой кнопкой мыши по слоту Закладки или нажав соответствующий хоткей (для каждого слота есть отдельный хоткей прыжка). Прыжок на Закладку не является операцией, так как никаких изменений мувика не происходит.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В момент установки Закладки Тасэдитор проверяет, отличаются ли сохраняемые данные от уже содержащихся в этой Закладке данных. Если различий не найдено, операция </span><a class="rvts38" href="Operations.html#Bookmark">Bookmark</a><span class="rvts21"> не производится.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Помимо номера кадра в слот устанавливаемой Закладки сохраняются все данные текущего мувика (тип Ввода, Ввод, Горячие Правки, Маркеры). Тем самым в проекте сохраняется текущее ответвление из всех возможных ответвлений мувика. В дальнейшем мувик будет многократно изменён, но пользователь сможет в любой момент вернуться к состоянию мувика, сохранённому в данной Закладке.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В слот устанавливаемой Закладки сохраняются дополнительные данные, повышающие удобство использования. В частности, скриншот экрана FCEUX на момент создания Закладки позволяет быстро узнавать содержимое Закладки без загрузки её ответвления. А копия одного сэйва из Гринзоны (на закладочном кадре) позволяет после загрузки ответвления сразу же поставить Курсор Проигрывателя на кадр Закладки.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">После установки закладки она становится текущей (отображается голубой цифрой), так как её ответвление более остальных похоже на текущий мувик.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При смене текущего мувика на ответвление из Закладки происходит изменение Ввода, поэтому Гринзона усекается, начиная с первого отличающегося кадра. Но благодаря хранящемуся в Закладке сэйву в Гринзону возвращается один сэйв на кадре, где и установлена эта Закладка. Поэтому "прыжок на Закладку во времени" всегда мгновенно перемещает Курсор Проигрывателя на кадр Закладки, в то время как прыжок на Закладку в пространстве (без изменения мувика) может потребовать добегания.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Все операции с Закладками (установка, прыжок, загрузка) производятся после окончания эмуляции текущего кадра, даже если сигнал от пользователя сработает в середине кадра.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Для отображения основных Данных закладок используется Список (Listview) без скроллинга, содержащий 10 строк и 3 столбца. при создании нового проекта все 10 Закладок пустые, поэтому второй и третий столбец Списка Закладок будут пустовать.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В первом столбце Списка Закладок отображается номер слота, которому соответствует данная строка. Номер отображается как и в Piano Roll – с помощью цифровых иконок зелёного или голубого цвета. Нумерация слотов идёт в таком порядке: 1, 2, 3, 4, 5, 6, 7, 8, 9, 0. Этот порядок нужен, чтобы не нарушать ассоциацию с цифровыми клавишами на клавиатуре, которыми пользователь может контролировать Закладки.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Во втором столбце Списка Закладок отображается номер кадра, на который установлена Закладка.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В третьем столбце Списка Закладок отображается реальное время установки Закладки.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Список Закладок разделяется вертикальной чертой примерно пополам. Левая часть (где располагается первый и второй столбец Списка) ассоциируется с закладочным функционалом Закладок. Правая часть (где располагается третий столбец) ассоциируется с ответвлениями, хранящимися в Закладках. Левая часть отображается более светлым оттенком, правая – более тёмным. Щелчок левой кнопкой мыши по левой половине означает прыжок на Закладку, а щелчок по правой половине – загрузку ответвления.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Строки Списка Закладок окрашиваются цветами, соответствующими цветам строк Piano Roll, на которых установлены эти Закладки. Например, если Закладка установлена на кадре 1000, и на этом кадре в данный момент находится Курсор Проигрывателя, то в Списке Закладок строчка этой Закладки будет нарисована голубым цветом. Эта фича даёт пользователю дополнительную информацию о расположении Закладок в мувике.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Вместо постоянного просмотра Списка Закладок можно переключать вид на Дерево ответвлений. Переключение осуществляется щелчком по заголовку, расположенному над Списком Закладок.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Дерево ответвлений – это графическое представление взаимосвязей между ответвлениями всех Закладок в проекте. Обычно Закладки создаются по мере создания мувика, поэтому более поздние Закладки хранят ответвление, начальная часть которого совпадает с ответвлениями более ранних Закладок. Для каждой Закладки можно найти "родительскую" Закладку, из мувика которой, вероятнее всего, произошёл мувик данной Закладки. В результате все Закладки выстраиваются в иерархическую структуру, в начале которой находится корень (отображается в виде тучки), являющийся родителем Закладок, для которых не нашлось родителя. Поиск родителей для Закладок осуществляется при каждом изменении любой Закладки. При поиске учитывается номер кадра, на котором установлена каждая Закладка. Благодаря этому в начале иерархии находятся Закладки с наименьшим номером кадра.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При установке Закладки она становится текущей, и её содержимое ничем не отличается от текущего мувика. Но после внесения изменений в мувик текущая Закладка уже будет отличаться, поэтому в Дереве ответвлений появляется фаербол, сообщающий об этом. Фаербол символизирует текущий мувик, однако его родителем всегда считается текущая Закладка. Реального поиска лучшего родителя не производится, так как пришлось бы после каждой модификации мувика запускать сравнение его Ввода со всеми Закладками, что признано слишком ресурсоёмким.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Закладки в Дереве ответвлений отображаются цифровыми иконками (как и в Piano Roll). Текущая Закладка отображается голубой цифрой. Связи между Закладками отображаются тонкими линиями. Для текущей Закладки формируется последовательность красных линий, связывающих все закладки, при загрузке которых не будет изменения Ввода (то есть как минимум от начального кадра до кадра загружаемой Закладки Ввод будет совпадать с Вводом, хранящимся в текущей Закладке). Эти красные линии идут от тучки к текущей Закладке, либо ещё далее – к наследникам текущей Закладки, когда ответвление текущей Закладки содержит тот же самый Ввод, который содержится в ответвлениях этих наследников вплоть до кадра Закладки.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Благодаря расположению Закладок по возрастанию их номера кадра, последовательность красных линий можно воспринимать как хронологию текущего мувика. Началом этой хронологии служит тучка, при щелчке по ней Курсор проигрывателя посылается на начало мувика. Закладки, нанизанные на красную нить, являются промежуточными этапами этой хронологии, при щелчке по ним Курсор Проигрывателя посылается на кадр указанной Закладки. Фаербол (если он есть) считается концом текущей хронологии, и при щелчке по нему Курсор Проигрывателя посылается в конец мувика. Также любое положения Курсора Проигрывателя можно проецировать на эту хронологическую линию, найдя две Закладки, между кадрами которых располагается Курсор Проигрывателя, и переведя расстояние, измеряемое в кадрах, в пиксели. В результате текущее положение Курсора Проигрывателя постоянно отображается в Дереве ответвлений в виде маленького голубого треугольника (по аналогии с иконкой Курсора Проигрывателя в Piano Roll).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Аналогично просмотру текущей хронологии можно быстро увидеть альтернативную хронологию для любой Закладки, наведя на неё курсор мыши (будет отображаться синими линиями).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Маркеры, содержащиеся в ответвлениях Закладок, не влияют на процесс поиска родителей и формирования Дерева.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Все данные Закладок сохраняются и загружаются из файла проекта. Для Дерева ответвлений сохраняются и загружаются только кэшированные данные о номере первого кадра различий во Вводе для каждой пары Закладок. Исходя из этих данных Тасэдитор легко восстанавливает иерархию родительских отношений между закладками. А если эти данные отсутствуют, Тасэдитору придётся произвести сравнение Ввода всех Закладок относительно друг друга.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="PopupWindows"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Всплывающие окна</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Служат для показа контекстозависимой информации, которая нужна только в определённые моменты времени.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">В TAS Editor 1.0 реализовано только два вида всплывающих окон: скриншоты к Закладкам и текстовые описания к Закладкам. Оба окна всплывают при наведении курсора мыши либо на правую половину Списка Закладок, либо на любую иконку (карточку) Закладки в Дереве ответвлений.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Оба окна появляются (по альфа-каналу) в течение примерно полусекунды после наведения курсора мыши на активный элемент. Исчезают так же в течение примерно полусекунды после уведении курсора от элемента.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">В </span><a class="rvts27" href="ProgramCustomization.html#DisplayBranchScreenshots">настройках</a><span class="rvts21"> можно отключить тот или другой тип всплывающих окон.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">В окне </span><span class="rvts25">скриншота</span><span class="rvts21"> отображается сохранённая в указанной Закладке копия экрана FCEUX на момент создания Закладки. В зависимости от настройки </span><a class="rvts27" href="ProgramCustomization.html#HUDinBranchscreenshots">HUD in Branch screenshots</a><span class="rvts21"> в Закладку сохраняется либо просто содержимое буфера экрана эмулируемой приставки, либо изображение экрана приставки с наложенными данными эмулятора. Скриншоты служат для быстрой оценки содержимого Закладки, а также для сравнения альтернативных стратегий.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">В окне </span><span class="rvts25">описания</span><span class="rvts21"> отображается текстовое поле, по ширине равное ширине верхнего и нижнего текстового поля для редактирования Заметок. В поле отображается текст Заметки Маркера, взятого из ответвления указанной Закладки. Маркер определяется номером кадра, на котором установлена эта Закладка.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Окно скриншота отображается сбоку от раздела Закладок, окно описания отображается под окном скриншота.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">При перетаскивании окна TAS Editor всплывающие окна перемещаются вместе с ним (пока не погаснут).</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Если во время отображения всплывающих окон меняется содержимое указанной Закладки, содержимое всплывающих окон также мгновенно обновляется.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="HistoryLog"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Журнал Истории</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">История всех существенных изменений проекта служит, главным образом, для удобного отката этих изменений, а также для визуального отслеживания этой истории.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">В каждом пункте Журнала Истории хранится полная копия Ввода и Маркеров на момент создания пункта. Также в любом пункте может храниться резервная копия Закладки, если пункт создан из-за операции </span><a class="rvts27" href="Operations.html#Bookmark">Bookmark</a><span class="rvts21">.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Данные каждого пункта хранятся в оперативной памяти одновременно в двух видах – сжатом и несжатом. Несжатый используется при работе, сжатый сохраняется в fm3-файл. При создании нового пункта Истории он хранится только в несжатом виде, однако каждые полсекунды Тасэдитор проходится по Журналу Истории и создаёт сжатую версию для первого попавшегося пункта без сжатой версии. Таким образом, к моменту сохранения проекта на диск почти все пункты Истории уже имеют сжатую версию, а те, которые не имеют, сжимаются во время сохранения (что немного замедляет процесс сохранения). При загрузке fm3-файла пункты Журнала Истории загружаются в запакованном виде и распаковываются.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Благодаря Журналу Истории реализуется поиск первого изменившегося кадра, после которого затем усекается Гринзона. Большинство операций работают таким образом:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 40px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Вносятся изменения в мувик.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Для большинства операций запоминаются минимальный и максимальный номер кадра, в который были внесены изменения.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Вызывается регистрация изменений с помощью Истории, минимальный и максимальный кадр передаются в качестве параметров вместе с кодом операции и другими параметрами.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">История сверяет содержимое текущего мувика с содержимым последнего пункта Журнала Истории. Если задан минимальный кадр, то сверка начинается с этого кадра, игнорируя содержимое мувика до него. Иначе проверяется всё от начала мувика. Если задан максимальный кадр, то сверка заканчивается после этого кадра (но большинство операций не передают максимальный кадр, так как, например, вставка пустого кадра передвигает весь последующий Ввод, и нужно вести проверку до самого конца мувика).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Как только обнаруживается первое различие между Вводом/Маркерами мувика и Вводом/Маркерами последнего снимка мувика, создаётся новый пункт в Журнале Истории и заполняются все его атрибуты.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Если различия не были обнаружены, то считается, что операция не повлияла на мувик, и никаких изменений в проекте не производится. Например, если записать те же самые нажатия поверх уже имеющихся, операция </span><a class="rvts27" href="Operations.html#Record">Record</a><span class="rvts21"> не будет зарегистрирована.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Для операции </span><a class="rvts27" href="Operations.html#Record">Record</a><span class="rvts21"> регистрируется не только номер кадра с изменившимся Вводом, но и номер джойстика, кнопки которого были изменены.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Последовательно добавляемые пункты для операций </span><a class="rvts27" href="Operations.html#AdjustLag">AdjustLag</a><span class="rvts21">, </span><a class="rvts27" href="Operations.html#Record">Record</a><span class="rvts21">, </span><a class="rvts27" href="Operations.html#Set">Set</a><span class="rvts21"> и </span><a class="rvts27" href="Operations.html#Unset">Unset</a><span class="rvts21"> могут объединяться в один пункт Журнала Истории, чтобы их было удобнее откатывать в случае необходимости. Объединение производится во время заполнения атрибутов нового пункта Журнала Истории. Вместо добавления этого пункта в конец Журнала происходит замена последнего пункта на новый.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">После регистрации нового пункта История подаёт сигнал Дереву ответвлений (чтобы на нём появился фаербол) и менеджеру проекта (чтобы в заголовке окна появилась звёздочка), а затем возвращает номер кадра, на котором были обнаружено первое различие.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Вызывается усечение Гринзоны после кадра с первым обнаруженным различием. Этот номер может быть больше, чем минимальный номер кадра, в который были внесены изменения самой операцией. Например, если установить нажатия кнопки на всех кадрах в Выделении, минимальным номером кадра будет первый выделенный кадр, но Гринзона будет усечена только после того выделенного кадра, на котором раньше не было нажатия этой кнопки.</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Откат Истории осуществляется как переход с текущего пункта Журнала Истории на предыдущий. Можно сразу прыгать на любой пункт Журнала Истории. Текущий мувик и текущие Маркеры восстанавливаются из данных, содержащихся в этом пункте, а сам пункт становится текущим.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Одним из атрибутов каждого пункта Истории является "номер ключевого кадра". Для большинства операций это номер кадра, где обнаружилось первое различие. Для операций, сдвигающих Ввод, это номер минимального кадра.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При прыжках по Истории в Piano Roll на полсекунды появляется курсор-указка фиолетового цвета, акцентирующий внимание на ключевом кадре. При откате (undo) этот курсор указывает на ключевой кадр следующего пункта Истории (относительно текущего), при повторе (redo) этот курсор указывает на ключевой кадр текущего пункта истории.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="RerecordsCounter"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Счётчик перезаписей</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">По традиции во всех ТАСерских эмуляторах ведётся учёт количества перезаписей, использованных во время создания ТАСа. Это число может использоваться для примерной оценки трудозатрат.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Счётчик перезаписей хранится в мувике (а значит и в fm3-файле проекта). При создании нового мувика (либо нового проекта в Тасэдиторе) счётчик обнуляется.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При ТАСинге вне Тасэдитора: счётчик увеличивается на единицу каждый раз, когда ТАСер загружает сэйв в режиме Записи, чтобы изменить Ввод на уже просмотренном участке мувика. Счётчик не увеличивается, когда ТАСер записывает Ввод для кадров, события которых ему не известны.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При ТАСинге в Тасэдиторе: счётчик увеличивается на единицу каждый раз, когда ТАСер изменяет Ввод на отгринзоненном участке мувика. Счётчик не увеличивается, когда ТАСер изменяет Ввод для кадров, находящихся дальше головы Гринзоны.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Таким образом, в обоих случаях ведётся учёт, </span><span class="rvts34">сколько раз ТАСер изменил известное ему будущее</span><span class="rvts21">. Счётчик не увеличивается, когда ТАСер меняет будущее вслепую, то есть до просмотра игровых событий на изменяемых кадрах.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В старых эмуляторах счётчик увеличивается прямо в момент загрузки сэйва в режиме Записи, ещё до того, как ТАСер изменяет Ввод. Из-за этого возможна ситуация, когда пользователь несколько раз подряд нажимает хоткей загрузки сэйва (например, </span><span class="rvts26">F1</span><span class="rvts21">), и при каждом нажатии счётчик перезаписей будет увеличиваться. В Тасэдиторе счётчик увеличивается только в момент усечения Гринзоны, независимо от выбранного способа навигации. Поэтому при первом нажатии хоткея загрузки Закладки (например, </span><span class="rvts26">F1</span><span class="rvts21">) счётчик увеличится только в случае, если ответвление этой Закладки отличается от текущего мувика, причём расхождение должно начинаться с уже просмотренного кадра (кадра внутри Гринзоны). А при повторных нажатиях этого хоткея счётчик не будет увеличиваться, так как ответвление Закладки уже не отличается от текущего мувика, и изменения Ввода не происходит.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="Modifiers"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Система клавиш-модификаторов</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Для повышения интуитивности клавиатурного управления в Тасэдиторе используется строгое разделение функций клавиш модификаторов:</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts30">Shift</span><span class="rvts21"> ассоциируется с </span><a class="rvts27" href="Glossary.html#Output">Выводом</a><span class="rvts21"> мувика, а конкретно с Курсором Проигрывателя. Многие клавиатурные комбинации, содержащие эту клавишу, относятся к управлению этим курсором. Если быстро нажать </span><span class="rvts30">Shift </span><span class="rvts21">два раза подряд, Piano Roll автоматически скроллируется к Курсору Проигрывателя.</span></li>
|
||||
<li class="rvps14"><span class="rvts30">Ctrl</span><span class="rvts21"> ассоциируется с </span><a class="rvts27" href="Glossary.html#Input">Вводом</a><span class="rvts21"> мувика, а конкретно с Курсором Выделения. Многие клавиатурные комбинации, содержащие эту клавишу, относятся к управлению этим курсором. Если быстро нажать </span><span class="rvts30">Ctrl </span><span class="rvts21">два раза подряд, Piano Roll автоматически скроллируется к Курсору Выделения.</span></li>
|
||||
<li class="rvps14"><span class="rvts30">Alt</span><span class="rvts21"> ассоциируется с шаблонами и чередующимися последовательностями.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="Patterns"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Шаблоны</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Заготовленные последовательности нажатий для одной кнопки. Подробнее см. </span><a class="rvts27" href="AdvancedFeatures.html#UsingPatterns">Продвинутые возможности</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Хранятся во внешнем текстовом файле в формате, доступном для редактирования в Блокноте.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Формат файла должен быть описан в самом файле. Для каждого шаблона указывается его имя, которое будет отображаться в списке шаблонов.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Загружаются из файла в оперативную память в момент открытия окна TAS Editor.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В TAS Editor 1.0 нет встроенных средств редактирования шаблонов, так как формат очень прост, а фича не слишком востребована.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">По шаблону можно устанавливать Ввод, Маркеры и даже Выделение.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При установке шаблона может учитываться или не учитываться лаг. Подробнее: </span><a class="rvts27" href="ProgramCustomization.html#AutofirePatternskipsLag">Настройка программы</a></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="CrossingGaps"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Пересечение промежутков</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Дополнительный способ быстрой навигации по содержимому Piano Roll, облегчающий визуальное прослеживание длинных последовательностей для отдельно взятой кнопки или Маркеров.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Пересечение промежутков – это вертикальный скроллинг Piano Roll, срабатывающий при вращении колеса мыши с зажатой клавишей </span><span class="rvts30">Alt</span><span class="rvts21">. Конкретная величина скроллинга не зависит от скорости вращения колеса, а рассчитывается каждый раз индивидуально, исходя из ячейки Piano Roll под курсором мыши в данный момент.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При зажатом </span><span class="rvts30">Alt</span><span class="rvts21"> имеет значение только направление вращения колеса (вверх или вниз), а не скорость вращения.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Пересечение промежутков подразумевает, что пользователь хочет найти ячейку, находящуюся на расстоянии более одного кадра от ячейки под курсором мыши (иначе нет смысла использовать эту функцию, достаточно просто провести курсор мыши чуть выше).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Таким образом, при вращении колеса мыши вверх эта функция запоминает значение ячейки, предшествующей ячейке под курсором мыши. Затем функция начинает поиск ячейки, значение которой не совпадает с данным значением. Поиск идёт снизу вверх от ячейки, предшествующей ячейке под курсором мыши. При успешном обнаружении такой ячейки Piano Roll скроллируется таким образом, чтобы курсор мыши теперь указывал на найденную ячейку. Если же поиск дошёл до начала мувика, а ячейка не найдена, то Piano Roll не скроллируется.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Аналогично при вращении колеса мыши вниз эта функция запоминает значение ячейки, следующей за ячейкой под курсором мыши. Затем функция начинает поиск ячейки, значение которой не совпадает с данным значением. Поиск идёт сверху вниз от ячейки, следующей за ячейкой под курсором мыши.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="SaveCompact"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Компактное сохранение</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Файл проекта Тасэдитора в первую очередь предназначен для сохранения точного снимка рабочего процесса. Чтобы использовать тот же самый формат для обмена файлами между соавторами ТАСа или для опубликования в Интернете, необходимо предоставить пользователю возможность избирательного сохранения рабочих данных в файл. При открытии такого fm3-файла отсутствующие данные будут заменяться данными по умолчанию.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Подробнее см. </span><a class="rvts27" href="AdvancedFeatures.html#ProjectsSharing">Продвинутые возможности</a><span class="rvts21"> и </span><a class="rvts27" href="FM3format.html">Формат FM3</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><a name="Autosave"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Автосохранение</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Как и в случае с любым офисным документом, проект Тасэдитора желательно время от времени сохранять на диск, даже если не планируется выход из программы. Однако до Тасэдитора у ТАСеров не было такой привычки, поэтому имеет смысл сохранять проект автоматически, предоставив пользователю возможность настроить или отключить эту функцию.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Подробнее см. </span><a class="rvts27" href="ProgramCustomization.html#SetAutosaveperiod">Настройка программы</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="PlannedIdeas"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts74">Запланированные идеи</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="OutputLog"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Журнал Вывода (Output Log)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Следующий этап эволюции инструмента Memory Watch – просмотр состояния игровых данных в динамике, а не только в статике. Аналогично Журналу лага, эта фича позволит легче и точнее анализировать принципы изменения игрового Вывода.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Список (ListView), вертикальный скроллинг которого синхронизирован со скроллингом Piano Roll. Высота списка равна высоте Piano Roll, количество строк также всегда равно количеству строк Piano Roll. Количество колонок Списка зависит от нужд пользователя.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Можно гибко измененять ширину Списка (перетаскиванием узкой границы между ним и Piano Roll, соответственно изменяется ширина Piano Roll, таким образом их суммарная ширина всегда остаётся одинаковой). Можно также менять Список и Piano Roll местами, либо полностью отключать отображение Журнала Вывода. При отключении отображения Журнала Piano Roll расширяется на освобождённое пространство, в точности как в TAS Editor 1.0. Отключение отображения Журнала не означает отключение журналирования данных.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В Заголовке Списка отображаются названия журналируемых ячеек. Можно добавлять и удалять колонки, изменять названия, менять колонки местами и изменять их ширину. При создании нового проекта ни одной колонки в Журнале Вывода нет, и, соответственно, журналирование не ведётся.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В строках списка отображаются значения ячеек, сохранённые из состояния игры на соответствующем кадре мувика. Строки Списка раскрашиваются теми же цветами, что и соответствующие строки Piano Roll. При выделении строк в Piano Roll выделяются строки в Журнале.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Помимо ячеек RAM необходимо реализовать журналирование переменных Lua. Например, предоставить Lua-скриптам Read/Write-доступ к дюжине int-ячеек Тасэдитора и дать пользователю возможность журналировать любые ячейки из этой дюжины.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Кроме того, в будущем можно реализовать добавление колонки со скриншотами игры (либо выбранной прямоугольной областью игрового экрана). Причём отображаемый размер скриншота будет зависеть от текущей ширины колонки, и как следствие, скриншоты будут отображаться не на каждой строчке Журнала, а через каждые несколько строк. Однако съёмка скриншотов всегда осуществляется на каждом кадре.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Все журналируемые данные хранятся в Гринзоне, наравне с Журналом лага. При добавлении ячейки RAM возможно автоматическое заполнение всей колонки (Тасэдитор пробегает по всем сэйвам Гринзоны, распаковывает их и берёт значение из сохранённой копии RAM). При добавлении переменной Lua значения ячеек будут неопределёнными (пустые ячейки в Списке), и для их заполнения пользователю необходимо будет заново просмотреть мувик с запущенным Lua-скриптом.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При усечении Гринзоны старые данные, ставшие неактуальными, не удаляются, но отображаются менее ярким цветом, пока на их место не будут записаны новые данные. При удалении сэйвов из хвоста Гринзоны данные Журнала остаются и отображаются обычным цветом.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Возможна гибкая расцветка ячеек, например, подсветка одинаковых значений в Выделении, подсветка искомых значений, автоматическое изменение цвета при изменении значения, автоматическая индикация при достижении заданного значения и т.д.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Возможно чтение любых данных Гринзоны из Lua-скриптов с помощью API Тасэдитора.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Акселераторы </span><span class="rvts30">Shift + Вправо</span><span class="rvts21"> / </span><span class="rvts30">Shift + Влево</span><span class="rvts21"> теперь будут горизонтально скроллировать не Piano Roll, а Список Журнала. Скроллинг осуществляется по целым колонкам.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Необходимо также реализовать новые методы навигации по мувику в зависимости от значения ячеек. Например, с помощью </span><span class="rvts30">Alt</span><span class="rvts21"> и вращения колеса можно пересекать промежутки в Списке для поиска ближайшего неравного или, наоборот, равного значения.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="Minimap"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Миникарта</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Графически отображает в окне Тасэдитора весь мувик – Гринзону, лаг, Курсор Проигрывателя, Выделение, Маркеры, Закладки, точки Горячих Правок, подсветку Журнала Вывода и т.д. Предоставляет пользователю мгновенный образ текущего проекта, не обладающий детальностью, зато полностью умещающийся на экране. Также усовершенствует навигацию по мувику.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Миникарта представляет собой прямоугольный bitmap-холст, по высоте равный высоте Piano Roll, по ширине равный 30 пикселей. Может располагаться слева или справа от Piano Roll и Журнала Вывода.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В пункте View можно гибко настраивать отображаемые элементы на миникарте (устанавливать галочки напротив желаемых элементов). Также можно отключить отображение Миникарты.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Миникарта не хранит какие-либо данные проекта. Она втоматически перерисовывается с заданной периодичностью (по умолчанию раз в секунду).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Маркеры отображаются горизонтальными линиями жёлтого цвета на левой половине Миникарты. Каждая такая линия занимает по высоте как минимум 1 пиксель, поэтому Маркеры не теряются даже при мелком масштабе Миникарты (когда в мувике намного больше кадров, чем высота Миникарты в пикселях). Ширина линии равна трети ширины Миникарты.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Горячие Правки отображаются горизонтальными линиями соответствующего цвета на правой половине Миникарты. Каждая такая линия занимает по высоте как минимум 1 пиксель.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Закладки отображаются соответствующими иконками слева от Миникарты. По этим иконкам можно щёлкать левой и правой кнопкой мыши, эффект будет аналогичен щелчкам по иконкам в Дереве Ответвлений.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Щелчок правой кнопкой мыши – мгновенный скроллинг видимой области Piano Roll к указанному месту в мувике. Далее можно перетаскивать видимую область вверх/вниз по мувику, не отпуская правую кнопку.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Щелчок левой кнопкой мыши – навигация Курсором Проигрывателя. Далее можно перетаскивать Курсор Проигрывателя, не отпуская левую кнопку.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="VirtualJoypad"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Виртуальный Джойстик</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Альтернативный способ ввода инпута. Очень похож на изменение инпута щелчками по Заголовку Piano Roll, однако более удобен и нагляден.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Виртуальный Джойстик представляет собой всплывающее немодальное окно с изменяемыми размерами. Содержимое окна автоматически масштабируется при изменении размеров окна.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Окно Виртуального Джойстика появляется под курсором мыши при щелчке правой кнопкой в Piano Roll по выделенному Вводу или Вводу под Курсором Проигрывателя. В настройках пользователь может отключить появление Виртуального Джойстика под курсором при правом щелчке. Тогда можно оставить это окно в удобном месте рабочего стола и при необходимости перемещать курсор мыши то к нему, то обратно к Piano Roll.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">По цвету рамки окна можно определить, отображает ли Виртуальный Джойстик состояние Ввода в Выделении (синяя рамка) или под Курсором Проигрывателя (голубая рамка).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При уведении курсора мыши за пределы окна Виртуального Джойстика это окно автоматически скрывается (если установлена настройка "Hide on mouse leave") либо остаётся на месте.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При нажатии левой кнопкой мыши по неактивным областям начинается перетаскивание окна.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При нажатии правой кнопкой мыши в любом месте окна окно скрывается.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В окне расположены управляющие элементы – кнопки, соответствующие кнопкам реального джойстика эмулируемой приставки. Расположение кнопок соответствует реальному прототипу. По внешнему виду кнопок можно определить, являются ли соответствующая кнопка в Выделении нажатой, отпущенной или частично нажатой (когда выделено более одного кадра).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Содержимое окна автоматически обновляется при каждом внешнем изменении Ввода.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Виртуальный Джойстик отражает состояние только текущего джойстика (выбранного радиокнопкой в разделе Recorder).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При щелчке по кнопке происходит изменение Ввода текущего джойстика. Нажатая кнопка становится отпущенной, а отпущенная или частично нажатая становится нажатой. Соответственно меняется Ввод во всех выделенных кадрах или на кадре Курсора Проигрывателя.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В дополнение к кнопкам Ввода в окне Виртуального Джойстика можно разместить несколько кнопок-слотов для хранения макросов. Щелчок по кнопке Макроса будет аналогичен нескольким щелчкам по разным кнопкам Виртуального Джойстика. Это позволит ещё быстрее менять Ввод в Выделении, например, вместо трёх щелчков по кнопкам </span><span class="rvts29">Вверх</span><span class="rvts21">, </span><span class="rvts29">Вправо</span><span class="rvts21"> и </span><span class="rvts29">B</span><span class="rvts21"> можно будет сделать один щелчок по </span><span class="rvts73">Макросу1</span><span class="rvts21">.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Если перед щелчком по кнопке Виртуального Джойстика или кнопке макроса зажать клавишу </span><span class="rvts30">Alt</span><span class="rvts21">, будет установлен Ввод по шаблону.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">После реализации Виртуального Джойстика можно изменить принцип действия щелчков по Заголовку Piano Roll. Теперь вместо изменения инпута щелчки по Заголовку будут выделять соответствующие столбцы Piano Roll.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="BetterSelection"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Усовершенствование Выделения</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Архитектура TAS Editor 1.0 не рассчитана на выделение столбцов Piano Roll, однако в некоторых ситуациях это может быть необходимо при ТАСинге. Например, для очистки Ввода первого джойстика без очистки Ввода второго джойстика. Либо для перемещения Ввода одной/двух кнопок без смещения остальных внопок.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Кроме того, необходимо усовершенствовать процесс рисования Выделения, чтобы пользователь мог видеть цвет строк Piano Roll под полупрозрачным Выделением.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Выделение столбцов производится аналогично выделению строк – при щелчке левой кнопкой мыши по Заголовку Piano Roll соответствующий столбец становится выделенным, а все остальные столбцы перестают выть выделенными. Если перед щелчком зажать клавишу </span><span class="rvts30">Ctrl</span><span class="rvts21">, выделение остальных столбцов не изменится. Если зажать </span><span class="rvts30">Shift</span><span class="rvts21">, будет выделен регион столбцов от места предыдущего щелчка. Если зажать </span><span class="rvts30">Alt</span><span class="rvts21">, выделится регион по шаблону. После щелчка можно не отпускать левую кнопку и растягивать Выделение по горизонтали.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Выделять можно только столбцы Ввода. Маркеры же зависят от настройки "Bind markers to Input".</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Выделенные столбцы отмечаются в Заголовке синим фоном в соответствующих ячейках.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Отсутствие выделенных столбцов равносильно состоянию "выделены все столбцы".</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При рисовании строк Выделения ячейки Ввода из невыделенных столбцов рисуются с альфой ~0.4, в то время как ячейки из выделенных столбцов имеют альфу ~0.7.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В колонке с номерами кадров выделенные строки имеют альфу ~0.4, когда Маркеры отвязаны, и ~0.7, когда Маркеры привязаны.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В разделе Splicer отображается не только количество выделенных строк (rows), но и количество выделенных столбцов (columns).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При копировании в Буфер Обмена попадает только Ввод из выделенных столбцов, причём он попадает в виде прямоугольной таблицы, без пропусков между столбцами. Благодаря этому можно изменить выделенные столбцы и вставить Ввод одних кнопок на место других кнопок.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При изменении порядка следования столбцов или скрытии/раскрытии столбцоа Выделение сбрасывается в состояние "отсутствует выделение столбцов".</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При Записи Ввод фильтруется в соответствии с выделением столбцов. Невыделенные столбцы не будут изменяться, даже если пользователь записывает другое состояние кнопки этого столбца.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При инициализации объекта SELECTION (то есть при запуске Тасэдитора или создании проекта) Выделение сбрасывается в состояние "отсутствует выделение столбцов".</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Выделение столбцов также сохраняется в файле проекта.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">На Историю Выделений это нововведение никак не влияет. Изменение выделения столбцов не сохраняется в Истории Выделений, так как навигация по истории изменения выделения столбцов не требуется.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="BetterColumns"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Гибкая настройка колонок</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">В TAS Editor 1.0 столбцы Piano Roll имеют фиксированную ширину. Количество и порядок следования столбцов также фиксированы, Для команд приставки (сброс, вставка диска и т.д.) отдельные столбцы не отводятся, так как эти команды используются крайне редко. Однако при портировании Тасэдитора на другие эмуляторы количество столбцов будет возрастать (например, у PSX нужно отображать столбцы для 14 кнопок), необходимо предоставить пользователю возможность настраивать их.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Так как подобная настройка обычно производится только один раз при первом запуске программы, она не обязательно должна осуществляться средствами Piano Roll, можно и в отдельном окне, вызываемом из Config.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Возможность отображать любые колонки Ввода, в том числе колонки команд.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Возможность прятать любые колонки. Однако от каждого джойстика должна оставаться отображаемой как минимум одна колонка (но если пользователь настроил проект на режим 1P, то колонки второго джойстика в любом случае не будут отображаться).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Возможность изменять порядок следования колонок.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">При копировании в Буфер Обмена копируются только абстрактные значения вида "кнопка нажата" / "не нажата". Поэтому если после копирования изменить порядок следования столбцов и вставить Ввод из Буфера Обмена, реальный Ввод мувика изменится (кнопки изменённых столбцов поменяются местами).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Возможность изменять ширину колонок.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Возможность одним щелчком восстановить значения по умолчанию (рекомендуемые автором).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Все настройки сохраняются при выходе.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="RerecordsHeatmap"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Теплокарта перезаписей</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Хранит и отображает статистику "изменений после просмотра" (перезаписей). Может быть полезна для выявления сложных мест в мувике.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Хранит массив int, по одному элементу на каждый кадр мувика (в том числе за пределами инпута). Значение элемента соответствует количеству усечений Гринзоны до данного кадра.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Сохраняет и загружает свои данные из файла проекта.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В качестве холста следует использовать холст Миникарты. При ТАСинге не имеет смысла постоянно видеть Теплокарту, пользователь может изредка (например, в конце каждого дня) переключать Миникарту в режим отображения Теплокарты и оценивать проделанный труд.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Так как эта фича несёт не столько рабочую, сколько эстетическую функцию, необходимо продумать алгоритм рисования телокарты, чтобы было не только информативно, но и красиво.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="Etc"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Прочие мелочи</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Отдельный Журнал Истории для операций </span><a class="rvts27" href="Operations.html#Bookmark">Bookmark Set</a><span class="rvts21"> (</span><span class="rvts30">Alt + Z</span><span class="rvts21"> и </span><span class="rvts30">Alt + Y</span><span class="rvts21">), для отката изменений Ввода/Маркеров без отката изменений Закладок.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Возможность работать с </span><span class="rvts21">мувиками, начинающимися с сэйва.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Возможность работать с несколькими эмулируемыми играми одновременно (для Multi-TAS-проектов).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Усовершенствование Lua API.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Поддержка мультитач-управления.</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Продумать концепцию заполнения Гринзоны в фоне (насколько она соответствует особенностям ТАСинга).</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="OtherPlatforms"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Поддержка платформ, отличных от NES</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Если Тасэдитор приобретёт популярность среди ТАСеров, необходимо расширить его доступность для всех эмулируемых платформ.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Продумать управляющие элементы для отображения и изменения аналогового Ввода в Piano Roll. Виртуальный Джойстик отчасти решает эту проблемы, однако должна быть возможность быстро и легко рисовать аналоговый Ввод мышкой. Например, растягивать на много кадров однократно установленное значение наклона стика, запоминать значение только что очищенной ячейки и предлагать его при рисовании. В ячейке отображается не один символ, а число от -1.0 до +1.0. При двойном щелчке по клетке можно набрать с клавиатуры точное значение этого числа. С зажатым </span><span class="rvts30">Ctrl</span><span class="rvts21"> можно растягивать значение ячейки левой кнопкой мыши вправо/влево или вверх/вниз. В столбце отображается значение наклона только по одной координатной оси (таким образом, для аналогового стика требуется две колонки Piano Roll).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">В Виртуальном Джойстике должна быть возможность рисовать огибающую для региона кадров, а не только устанавливать одинаковое значение для всех выделенных кадров. Также необходимо переработать формат Шаблонов, чтобы они могли представлять последовательности значений уровня, в том числе с относительными значениями (например, возрастание по параболе, где начальное и конечное значение берётся из начального и конечного кадра выделенного региона).</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Скорее всего, потребуется переход на 64-разрядную платформу, так как объёмы Гринзоны значительно возрастут при хранении сэйвов более продвинутых приставок.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour/create-ebooks-for-amazon-kindle">Produce Kindle eBooks easily</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,419 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Implementation</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("Implementation");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Implementation</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="TASEditorInside.html">TAS Editor Inside</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="TASEditorInside.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="Ideas.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="MistakeProofing.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Implementation</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">At first the TAS Editor was based on the codebase of experimental tool named TASEdit, using FCEUX 2.1.5 as a kick-start.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The premise of TASEdit was to build an input editor (like TAS Movie Editor) into emulator, so that the delay between editing and checking results would greatly shrink. Since there was no research done on typical behaviors in TASing process, the concept was vague and the code wasn't scalable. Thus, soon after formulating the new vision of the editing tool the code of TAS Editor was fully rewritten to make adding new features easier.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The following architecture of TAS Editor was designed according to author's notion of a methodical TASing and of features needed for such TASing.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts75">TAS Editor modules (classes)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">taseditor.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Main – Main gate between emulator and Taseditor</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">the point of launching TAS Editor from emulator</span></li>
|
||||
<li class="rvps10"><span class="rvts21">the point of quitting from TAS Editor</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly (at the end of every frame) updates all modules that need regular update</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements operations of the "File" menu: creating New project, opening a file, saving, compact saving, import, export</span></li>
|
||||
<li class="rvps10"><span class="rvts21">handles some FCEUX hotkeys</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">taseditor_window.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Window – User Interface</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">implements all operations with TAS Editor window: creating, redrawing, resizing, moving, tooltips, clicks</span></li>
|
||||
<li class="rvps10"><span class="rvts21">subclasses all buttons and checkboxes in TAS Editor window GUI in order to disable Spacebar key and process Middle clicks</span></li>
|
||||
<li class="rvps10"><span class="rvts21">processes OS messages and sends signals from user to TAS Editor modules (also implements some minor commands on-site, like Greenzone capacity dialog and such)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">switches off/on emulator's keyboard input when the window loses/gains focus</span></li>
|
||||
<li class="rvps10"><span class="rvts21">on demand: updates the window caption; updates mouse cursor icon</span></li>
|
||||
<li class="rvps10"><span class="rvts21">updates all checkboxes and menu items when some settings change</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores info about 10 last projects (File->Recent) and updates it when saving/loading files</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: window caption, help filename, size and other properties of all GUI items</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">bookmarks.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Bookmarks – Manager of Bookmarks</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores 10 Bookmarks</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements all operations with Bookmarks: initialization, setting Bookmarks, jumping to Bookmarks, deploying Branches</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads the data from a project file. On error: resets all Bookmarks and Branches</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements the working of Bookmarks List: creating, redrawing, mouseover, clicks</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly updates flashings in Bookmarks List</span></li>
|
||||
<li class="rvps10"><span class="rvts21">on demand: updates colors of rows in Bookmarks List, reflecting conditions of respective Piano Roll rows</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: save id, ids of commands, labels for panel, gradients for flashings, id of default slot</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">branches.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Branches – Manager of Branches</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores info about Branches (relations of Bookmarks) and the id of current Branch</span></li>
|
||||
<li class="rvps10"><span class="rvts21">also stores the time of the last modification (see fireball) and the time of project beginning (see cloudlet)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">also caches data used in calculations (cached_first_difference, cached_timelines)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads the data from a project file. On error: sends warning to caller</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements the working of Branches Tree: creating, recalculating relations, animating, redrawing, mouseover, clicks</span></li>
|
||||
<li class="rvps10"><span class="rvts21">on demand: reacts on Bookmarks/current Movie changes and recalculates the Branches Tree</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly updates animations in Branches Tree and calculates Playback cursor position on the Tree</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: coordinates for building Branches Tree, animation timings</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">bookmark.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Bookmark – Single Bookmark data</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores all info of one specific Bookmark: movie snapshot, a savestate of 1 frame, a screenshot of the frame, a state of flashing for this Bookmark's row</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads the data from a project file. On error: sends warning to caller</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements procedure of "Bookmark set": creating movie snapshot, setting key frame on current Playback position, copying savestate from Greenzone, making and compressing screenshot, launching flashing animation</span></li>
|
||||
<li class="rvps10"><span class="rvts21">launches respective flashings for "Bookmark jump" and "Branch deploy"</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">snapshot.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Snapshot – Snapshot of all edited data</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores the data of specific snapshot of the movie: InputLog, LagLog, Markers at the moment of creating the snapshot, keyframe, start and end frame of operation, type of operation and description of the snapshot (including the time of creation)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">also stores info about sequential recording/drawing of input</span></li>
|
||||
<li class="rvps10"><span class="rvts21">streamlines snapshot creation: copying Input from movie data, copying LagLog from Greenzone, copying Markers from Markers Manager, setting time of creation</span></li>
|
||||
<li class="rvps10"><span class="rvts21">streamlines restoring Markers data from snapshot</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads the data from a project file. On error: sends warning to caller</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">inputlog.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">InputLog – Log of Input</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores the data about Input state: size, type of Input, Input Log data (commands and joysticks)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">optionally can store map of Hot Changes</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements InputLog creation: copying Input, copying Hot Changes</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements full/partial restoring of data from InputLog: Input, Hot Changes</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements compression and decompression of stored data</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads the data from a project file. On error: sends warning to caller</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements searching of first mismatch comparing two InputLogs or comparing this InputLog to a movie</span></li>
|
||||
<li class="rvps10"><span class="rvts21">provides interface for reading specific data: reading Input of any given frame, reading value at any point of Hot Changes map</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements all operations with Hot Changes maps: copying (full/partial), updating/fading, setting new hot places by comparing two InputLogs</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">laglog.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">LagLog – Log of Lag occurrence</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores the frame-by-frame log of lag occurrence</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements compression and decompression of stored data</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads the data from a project file. On error: sends warning to caller</span></li>
|
||||
<li class="rvps10"><span class="rvts21">provides interface for reading and writing log data</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">markers.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Markers – Snapshot of Markers state</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores the data about Markers state: array of distributing Markers among movie frames, and array of Notes</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements compression and decompression of stored data</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads the data from a project file. On error: sends warning to caller</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: max length of a Note</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">popup_display.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Popup display – Manager of popup windows</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">implements all operations with popup windows: initialization, redrawing, centering, screenshot decompression and conversion</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly inspects changes of Bookmarks Manager and shows/updates/hides popup windows</span></li>
|
||||
<li class="rvps10"><span class="rvts21">on demand: updates contents of popup windows</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: coordinates and appearance of popup windows, timings of fade in/out</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">history.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">History – History of movie modifications</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores array of History items (snapshots, backup_bookmarks, backup_current_branch) and pointer to current snapshot</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads the data from a project file. On error: clears the array and starts new history by making snapshot of current movie data</span></li>
|
||||
<li class="rvps10"><span class="rvts21">on demand: checks the difference between the last snapshot and current movie, and makes a decision to create new point of rollback. In special cases it can create a point of rollback without checking the difference, assuming that caller already checked it</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements all restoring operations: undo, redo, revert to any snapshot from the array</span></li>
|
||||
<li class="rvps10"><span class="rvts21">also stores the state of "undo pointer"</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly updates the state of "undo pointer"</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly (when emulator is paused) searches for uncompressed items in the History Log and compresses first found item</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements the working of History List: creating, redrawing, clicks, auto-scrolling</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: save id, ids and names of all possible types of modification, timings of "undo pointer"</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">piano_roll.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Piano Roll – Piano Roll interface</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">implements the working of Piano Roll List: creating, redrawing, scrolling, mouseover, clicks, drag</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly updates the size of the List according to current movie input</span></li>
|
||||
<li class="rvps10"><span class="rvts21">on demand: scrolls visible area of the List to any given item: to Playback Cursor, to Selection Cursor, to "undo pointer", to a Marker</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads current position of vertical scrolling from a project file. On error: scrolls the List to the beginning</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements the working of Piano Roll List Header: creating, redrawing, animating, mouseover, clicks</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly updates lights in the Header according to button presses data from Recorder and Alt key state</span></li>
|
||||
<li class="rvps10"><span class="rvts21">on demand: launches flashes in the Header</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements the working of mouse wheel: List scrolling, Playback cursor movement, Selection cursor movement, scrolling across gaps</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements context menu on Right-click</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: save id, ids of columns, widths of columns, tables of colors, gradient of Hot Changes, gradient of Header flashings, timings of flashes, all fonts used in TAS Editor, images</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">selection.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Selection – Manager of selections</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">contains definition of the type "Set of selected frames"</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores array of Sets of selected frames (History of selections)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads the data from a project file. On error: clears the array and starts new history by making empty selection</span></li>
|
||||
<li class="rvps10"><span class="rvts21">constantly tracks changes in selected rows of Piano Roll List, and makes a decision to create new point of selection rollback</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements all selection restoring operations: undo, redo</span></li>
|
||||
<li class="rvps10"><span class="rvts21">on demand: changes current selection: remove selection, jump to a frame with Selection cursor, select region, select all, select between Markers, reselect clipboard</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly ensures that selection doesn't go beyond curent Piano Roll limits, detects if selection moved to another Marker and updates Note in the lower text field</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements the working of lower buttons << and >> (jumping on Markers)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">also here's the code of lower text field (for editing Marker Notes)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resource: save id, lower text field prefix</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">editor.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Editor – Tool for editing</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">implements operations of changing Input: toggle input in region, set input by pattern, toggle selected region, apply pattern to input selection</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements operations of changing Markers: toggle Markers in selection, apply patern to Markers in selection, mark/unmark all selected frames</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores Autofire Patterns data and their loading/generating code</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: patterns filename, id of buttonpresses in patterns</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">splicer.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Splicer – Tool for montage</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">implements operations of mass-changing input: copy/paste, cloning, clearing region, insertion and deletion of frames, truncating</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores data about the selection used in last "Copy to Clipboard" operation</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly checks the state of current selection and displays info on GUI, also displays info about input in Clipboard</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when launching TAS Editor, it checks Clipboard contents</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: mnemonics of buttons, texts for selection/clipboard info on GUI</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">taseditor_config.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Config – Current settings</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores current state of all TAS Editor settings</span></li>
|
||||
<li class="rvps10"><span class="rvts21">all TAS Editor modules can get or set any data within Config</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when launching FCEUX, the emulator writes data from fceux.cfg file to the Config, when exiting it reads the data back to fceux.cfg</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: default values of all settings, min/max values of settings</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">playback.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Playback – Player of emulation states</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">implements the working of movie player: show any frame (jump), run/cancel seekng. pause, rewinding</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly tracks and controls emulation process, prompts redrawing of Piano Roll List rows, finishes seeking when reaching target frame, animates target frame, makes Piano Roll follow Playback cursor, detects if Playback cursor moved to another Marker and updates Note in the upper text field</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements the working of upper buttons << and >> (jumping on Markers)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements the working of buttons < and > (frame-by-frame movement)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements the working of button || (pause) and middle mouse button, also reacts on external changes of emulation pause</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements the working of progressbar: init, reset, set value, click (cancel seeking)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">also here's the code of upper text field (for editing Marker Notes)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: upper text field prefix, timings of target frame animation, response times of GUI buttons, progressbar scale</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">greenzone.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Greenzone – Access zone</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores array of savestates, used for faster movie navigation by Playback cursor</span></li>
|
||||
<li class="rvps10"><span class="rvts21">also stores LagLog of current movie Input</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads the data from a project file. On error: truncates Greenzone to last successfully read savestate</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly checks if there's a savestate of current emulation state, if there's no such savestate in array then creates one and updates lag info for previous frame</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements the working of "Auto-adjust Input according to lag" feature</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly runs gradual cleaning of the savestates array (for memory saving), deleting oldest savestates</span></li>
|
||||
<li class="rvps10"><span class="rvts21">on demand: (when movie input was changed) truncates the size of Greenzone, deleting savestates that became irrelevant because of new input. After truncating it may also move Playback cursor (which must always reside within Greenzone) and may launch Playback seeking</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: save id, properties of gradual cleaning, timing of cleaning</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">recorder.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Recorder – Tool for input recording</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">at the moment of recording movie input (at the very end of a frame) by emulator's call the Recorder intercepts input data and applies its filters (multitracking/etc), then reflects input changes into History and Greenzone</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly tracks virtual joypad buttonpresses and provides data for Piano Roll List Header lights. Also reacts on external changes of Recording status, and updates GUI (Recorder panel and Bookmarks/Branches caption)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements input editing in Read-only mode (ColumnSet by pressing buttons on virtual joypad)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: ids and names of multitracking modes, suffixes for TAS Editor window caption</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">markers_manager.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Markers_manager – Manager of Markers</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores one snapshot of Markers, representing current state of Markers in the project</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saves and loads the data from a project file. On error: clears the data</span></li>
|
||||
<li class="rvps10"><span class="rvts21">regularly ensures that the size of current Markers array is not less than the number of frames in current input</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements all operations with Markers: setting Marker to a frame, removing Marker, inserting/deleting frames between Markers, truncating Markers array, changing Notes, finding frame for any given Marker, access to the data of Snapshot of Markers state</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements full/partial copying of data between two Snapshots of Markers state, and searching for first difference between two Snapshots of Markers state</span></li>
|
||||
<li class="rvps10"><span class="rvts21">also here's the code of searching for "similar" Notes</span></li>
|
||||
<li class="rvps10"><span class="rvts21">also here's the code of editing Marker Notes</span></li>
|
||||
<li class="rvps10"><span class="rvts21">also here's the code of Find Note dialog </span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: save id, properties of searching for similar Notes</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">taseditor_lua.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Lua – Manager of Lua features</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">implements logic of all functions of "taseditor" Lua library</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores the list of pending input changes</span></li>
|
||||
<li class="rvps10"><span class="rvts21">on demand: (from FCEUX Lua engine) updates "</span><span class="rvts29">Run function</span><span class="rvts21">" button</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: ids of joypads for input changes, max length of a name for </span><span class="rvts20">applychanges()</span><span class="rvts21">, default caption for the "</span><span class="rvts29">Run function</span><span class="rvts21">" button</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts20">taseditor_project.cpp</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Project – Manager of working project</span></p>
|
||||
<p class="rvps10"><span class="rvts39">[singleton]</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">stores the info about current project filename and about having unsaved changes</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements saving and loading project files from filesystem</span></li>
|
||||
<li class="rvps10"><span class="rvts21">implements autosave function</span></li>
|
||||
<li class="rvps10"><span class="rvts21">stores resources: autosave period scale, default filename, fm3 format offsets</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts75">Emulator modifications</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Taseditor needs the following modifications to be applied to an emulator code.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Main</span><span class="rvts21">/</span><span class="rvts25">Window</span><span class="rvts21">:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">call Taseditor's update() function after every emulated frame and when emulation is paused, no less than 20 times per second (necessary for adequate animations and controls in TAS Editor window)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">dispatch OS messages to Taseditor window, including accelerator table commands</span></li>
|
||||
<li class="rvps10"><span class="rvts21">if emulator doesn't make use of mouse wheel, it should resend WM_MOUSEWHEEL to Taseditor, same with middle mouse clicks on emulator's own window</span></li>
|
||||
<li class="rvps24" style="text-indent: 30px"><span class="rvts21">on exit: emulator should ask Taseditor, so it can check unsaved changes in current project and allow user to save it before quitting. If the </span><span class="rvts20">AskSave()</span><span class="rvts21"> function returns </span><span class="rvts70">false</span><span class="rvts21">, the exit should be cancelled (means that user chose "Cancel")</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Movie</span><span class="rvts21">:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">there should be an interface for full control over current movie data (creating/reading/writing/any modification). The movie should be the last layer between user's input and emulated game, which means that the game should not take input from virtual pads, only from movie data. Alternative (FCEUX example) would be to always sync changes into virtual pads every time the movie data changes. Either way, Taseditor interacts with the game by reading and modifying movie data and doesn't poll virtual pads. Piano Roll displays current movie data and edits Input of current movie data</span></li>
|
||||
<li class="rvps10"><span class="rvts21">in Recording mode: at the very beginning of a frame (right after the Input for the frame is written into current movie data) emulator should call Taseditor's Recorder function (and Recorder may change the movie data)</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Input</span><span class="rvts21">:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">provide an interface for reading which buttons are currently held (for Piano Roll's Header)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">hardware commands (Reset/Power/etc) should not be executed immediately after user invokes them, they should work as well as buttons input from virtual pads, meaning that when Taseditor is on it may either allow or prohibit the commands. Also when Taseditor is on and is not Recording, user should not be able to even invoke hardware commands</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Output</span><span class="rvts21">:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">provide read access to current state of lag indicator (needed at the end of every frame)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">have public function for storing current screenshot in RAM (also screenshot with Lua HUD)</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">SaveStates</span><span class="rvts21">:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">have public function for making savestate in RAM and function for loading the state from RAM</span></li>
|
||||
<li class="rvps10"><span class="rvts21">savestates must restore the game state precisely</span></li>
|
||||
<li class="rvps10"><span class="rvts21">saving and loading should not take too much time, because the Greenzone automatically creates new savestate for every frame, which should be transparent for user</span></li>
|
||||
<li class="rvps10"><span class="rvts21">savestates should be stored in compressed form, so that they don't take too much space, because for a comfortable work in Taseditor the Greenzone should have at least 1000 savestates for nearby frames</span></li>
|
||||
<li class="rvps10"><span class="rvts21">savestates should not store current movie data (that would be a waste of space)</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Config</span><span class="rvts21">:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">on emulator start: emulator should load </span><span class="rvts70">taseditor_config</span><span class="rvts21"> data from the common settings file. If the file is not found, no changes should be made to </span><span class="rvts70">taseditor_config</span><span class="rvts21"> (it will have its settings by default)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">on emulator exit: save </span><span class="rvts70">taseditor_config</span><span class="rvts21"> data to the common settings file</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Lua engine</span><span class="rvts21">:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">add support for </span><span class="rvts20">taseditor</span><span class="rvts21"> library. The core of each function is implemented by Taseditor, but emulator should take parameters from Lua stack and send them to respective function of Taseditor's Lua gate, then receive returned data and push it into Lua stack</span></li>
|
||||
<li class="rvps10"><span class="rvts21">add support for no more than one </span><a class="rvts27" href="LuaAPI.html#registermanual">Manual function</a><span class="rvts21"> and at least one </span><a class="rvts27" href="LuaAPI.html#registerauto">Auto function</a></li>
|
||||
<li class="rvps10"><span class="rvts21">notify Taseditor about changing Manual function status (registered/re-registered/empty) so that it can change the state of the "</span><span class="rvts29">Run function</span><span class="rvts21">" button</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Replay</span><span class="rvts21">:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">emulator should be able to replay Taseditor project files as usual movie files, ignoring the additional data at the end of the file</span></li>
|
||||
<li class="rvps10"><span class="rvts21">since Taseditor project file can be huge, emulator shouldn't load it into memory when opening</span></li>
|
||||
<li class="rvps10"><span class="rvts21">emulator must distinguish between normal movie and Taseditor project file. If it's a project file: when user tries to rerecord, emulator should refuse and suggest launching TAS Editor instead. If user agrees, emulator should send Taseditor the reference to the project file</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">Other</span><span class="rvts21">:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">emulator environment should be stable and deterministic. Desyncs will invalidate Playback cursor navigation and make TASing unfeasible</span></li>
|
||||
<li class="rvps10"><span class="rvts21">it's recommended to implement all the points mentioned in </span><a class="rvts27" href="MistakeProofing.html">Mistake-proofing</a><span class="rvts21"> that are related to emulator modification. In particular, Taseditor should be able to change certain settings, and user shouldn't be able to change them while Taseditor is on</span></li>
|
||||
<li class="rvps10"><span class="rvts21">good emulation speed is necessary for adequate </span><a class="rvts27" href="NonlinearTASing.html#turbo-seeking">Turbo seeking</a><span class="rvts21"> feature. Also there should be an option to mute sound when turbo is on.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/help-authoring-tool">Single source CHM, PDF, DOC and HTML Help creation</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,146 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>1. Introduction</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("Introduction");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>1. Introduction</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="BeginnersGuide.html">Beginner's Guide</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="BeginnersGuide.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="BeginnersGuide.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="ProgramInterface.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Introduction</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/famtasia-smb3j.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">TASing – the process of creating an extraordinary game playthrough. For a true TASer, just simply beating the game is not enough. You must do something unique, something that would justify the use of tools.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">And that requires a non-standard way of thinking. During the regular play, almost entire flow of our thoughts is determined by the gameplay rules, and those who try to question the rules are quickly fined with a game over and other means. These trivial psychological methods help the game to direct player's fantasy to an intended path, in order to give him a credible atmosphere of integral world and to keep him within a craftily devised comfort zone.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">So, to create an extraordinary playthrough, TASer needs to both use emulator tools masterfully and be able to mentally abstract from the original game rules, while still obeying them physically (because TASing is not cheating, we won't influence the game other way than by joypad input).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Early TASing, just as regular speedrunning, was not much far away from the "normal" gaming process. TASer simply launched an emulator, switched on buttons logging and played a game, saving and loading often enough to fix the most obvious mistakes, slowing down the gameplay at the most intense moments, thus compensating for the slow reaction of the human organism.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The ability to fix mistakes emancipates man's imagination and incites him to experiment. Illusions of the game realm now confine his mind much less than before. But real-world stereotypes still affect his thinking. For instance, if a harmful object usually kills you, it's only natural to assume it always kills. But in truth it may appear to be killing only while even frame numbers, or when the subpixel value is equal to zero. But how would you guess it using only savestates and slowdown? First you have to stop being a gamer and become a researcher.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A huge breakthrough in the TASing history was the introduction of </span><span class="rvts25">Frame Advance</span><span class="rvts21"> – a frame-by-frame emulation. Now when you're TASing, the game is constantly being held paused, thus allowing to analyze every in-game aspect separately. Until then the game still appeared as a coherent stream of events (with simple slowdown). The stream that the player had to perceive as a complex emotional cocktail. And now with frame-by-frame play TASer can mentally isolate any given event of the current frame. This drastically alters the principles of consuming the in-game information. Material world stereotypes don't dictate how to act in the virtual world anymore, and you see the game more objectively, thus finding imperfections/loopholes in its rules.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Of course the game still keeps trying to impose typical behavior templates, and they are harder to resist when you're newbie rather than experienced TASer. That's the exact reason why a skilled TASer can beat someone's speedrun (even his own old TAS) – not because of handling the tools better, but owing to "Déformation professionnelle" that helps to notice vulnerabilities in games.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Many more TASing tools were invented since then, but the very way of interaction between a TASer and a game remained the same. Using rerecords, TASer edits Input in the same succession as the flow of in-game time. This linearity of TASing process builds certain limits in TASer's thinking. When you get used to receiving the game reaction on each button press, you involuntarily associate yourself with a game character. This makes it harder to try to look at the events from an outsider's viewpoint. And yet TASer is expected to have the most objective point of view possible!</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The development of the toolset named "TAS Editor" aims for 2 main goals:</span></p>
|
||||
<ol style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">to lower the threshold of joining TASing</span></li>
|
||||
<li class="rvps14"><span class="rvts21">to raise the objectivity of gameplay analysis</span></li>
|
||||
</ol>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The first goal is achieved by detailed visualization of all major aspects of TASing.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The second goal is achieved by switching from linear recording of movie segments to non-linear Input editing. The higher level of abstracting from in-game rules is reached by giving the TASer the following new abilities:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps15"><span class="rvts0"><span class="rvts21">changing Input in an arbitrary order (not just in the order the events flow in the game) – thanks to Piano Roll interface</span></span></li>
|
||||
<li class="rvps15"><span class="rvts0"><span class="rvts21">watching game events in an arbitrary order (not just frame by frame) – thanks to Greenzone</span></span></li>
|
||||
<li class="rvps15"><span class="rvts0"><span class="rvts21">emphasizing the Cause-Effect relation between Input and its remote consequences (not just the nearest ones) – thanks to Turbo-seeking</span></span></li>
|
||||
<li class="rvps15"><span class="rvts0"><span class="rvts21">enforcing custom logic of the movie segmentation (not just dividing into TV frames or into in-game levels) – thanks to Markers</span></span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">In addition, TAS Editor 1.0 developed some old TASing tools up to a new level:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">Lag log – evolved from Lag counter</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Input log – evolved from Input Display</span></li>
|
||||
<li class="rvps14"><span class="rvts21">step-by-step undo – in addition to movie state reloads</span></li>
|
||||
<li class="rvps14"><span class="rvts21">inbuilt editor – in place of hex-editors and a Notepad</span></li>
|
||||
<li class="rvps14"><span class="rvts21">auto-identification of current logical segment – in addition to current frame number display</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Selection counter (ruler) – in addition to frame counter</span></li>
|
||||
<li class="rvps14"><span class="rvts21">patterns – in place of Autofire settings</span></li>
|
||||
<li class="rvps14"><span class="rvts21">Superimpose – in place of Auto-hold</span></li>
|
||||
</ul>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps14"><span class="rvts21">When launching Taseditor, get ready to control the game from bird's eye view. The following chapters of this tutorial will explain you almost everything a prolific TASer needs to know. If you already have an experience in traditional TASing, some learning aspects should come easier, but some may appear more difficult to you than to a newcomer. Either way, try to finish the whole Guide, and you will likely learn a thing or two about TASing in general.</span></p>
|
||||
<p class="rvps14"><span class="rvts21">One of the most unconventional features of TASing with Taseditor is the stress on mouse control. Mouse allows high speed of Input editing and unparalleled convenience of Playback navigation. Even though most of Taseditor functions also have keyboard shortcuts, the comfortable work would be impossible without a mouse.</span></p>
|
||||
<p class="rvps14"><span class="rvts21">The gamepad is useful when you need to quickly record an Input without caring about accuracy. But most of his time TASer spends on various manipulations with once created Input. And here the mouse or keyboard becomes much more handy than gamepad. For example, using a key combination you can move any part of Input one frame back or forth. And when you need to adjust the jump height (the duration of holding the </span><span class="rvts29">A</span><span class="rvts21"> button), it's easier to do with single click, than to switch Recording on and retype the whole range of frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Nevertheless, it's still possible to work in Taseditor the same way people were TASing before. The program interface supports all essential aspects of the traditional TASing method. If you were to use the TAS Editor window only as an informational panel left in a corner of the desktop, you probably would not even notice any difference from usual flow of TASing. It can be good reason to smoothly move from the old method of TASing to the new one. At first you may only like some accessory features of Taseditor, such as the Lag visualization or the Branches Tree. Then you'll need some Input copy/paste, and Taseditor is the best alternative to an external editor. After some time you'll notice that direct Input editing turns out faster than rerecording.</span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/chip-and-dale.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">Advantages of the new method reveal themselves quicker when you're making a TAS controlling 2 and more players simultaneously. In old times people invented plenty of hacks and workarounds to make such kind of TASing easier, e.g. binding several buttons to one key, using "Auto-hold", macros and custom multitracking scripts. Now all of this is irrelevant with Taseditor, because here TASer does not play the role of a gamer that associates himself with the controlled character. Now you are not playing the game, you are meditating over the decomposed continuum of the game, while creating a scenario of events via Input. And thus it's does not matter whether you control 1 character, or 2, or many.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Taseditor was also designed to reduce the rut. There are always lots of tedious recurring activities in TASing. Surely, the program won't save you from the necessity to test all possible branches of gameplay development, but it automates some actions and increases the efficiency in many little things, allowing TASer to keep patience longer than during raw TASing.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Interesting facts:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">During the development of TAS Editor, the actual programming took less time than was spent on thinking out the ways to improve the TASing process.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Most of the actions in Taseditor can be done multiple ways.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Any operation can be undone and redone.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">You can totally ignore any part of Taseditor's functionality, using only the features you actually like.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Special attention was paid to user interface. When you gain enough experience, you'll be able to do most of things mechanically, staying focused on the in-game situation analysis.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you happen to get a nice idea how to reduce the rut some more, feel free to post on TASVideos forums. Many ideas implemented in TAS Editor were first voiced on these forums as "dream tools".</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Besides the new approach to TASing, Taseditor offers simple means for organization of your working process. Because of unsystematic approach to TASing many newcomers waste their time ineffectively, dissipate the effort and get tired quickly, then start to save the energy by reducing the amount of tests. As a result, they end up with a very suboptimal TAS. Then, as the time goes, they acquire a set of methods and habits, become experienced TASers. But every newbie had to learn by his own mistakes. In this Guide we will try to formulate a clear notion on a methodical TASing (both traditional and new), so that newcomers can realize the essence of the process faster.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Working with Taseditor is pretty similar to an interactive programming using an interpreted language. You just edit the code and instantly see the result of its execution on the screen. TASer can either immediately observe the effect of his interim actions, or he can get carried away by the construction of a code section and watch the result only after the section is finished.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Programmers have the valuable ability to increase the code readability with comments. It allows to keep more clear picture of the project in mind, and proceed without constant re-inspection of results, because in most cases the result is rather predictable, when the context is known.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Also, good code readability allows to quickly refresh all necessary memories when you return to a project delayed long ago. Granted that this project was well documented.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Taseditor helps to document TAS project on the fly – write comments, assign clear names to structures (patterns and Input sections), test different code versions in separate branches of the repository (see "Branches Tree") and efficiently work in co-authorship. And no, there's no strict conventions to follow. You set your own rules for when and how to shape your project. For example, if you didn't hesitate to describe a trick used in the first level, in next levels you'll be able to quickly duplicate the trick Input by several key strokes. If you didn't – you'll have to search the trick location manually. In simple TASes you can disregard comments and any long-term plans, but in complicated projects this program functionality should be very appropriate.</span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="http://tasvideos.org" target="_blank">TASVideos.org</a><span class="rvts21"> site supports uploading and publishing Taseditor projects (.fm3 files), so you may share not just the TAS movie, but your groundwork as well, encouraging the spirit of openness and mutual aid. If you don't want to share, export the data to .fm2 format and upload that.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">FM3 files are played back by FCEUX emulator since version 2.2.0 the same way as FM2 files. Older versions of FCEUX can also play such files if you change the extension to fm2.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Next chapter: </span><a class="rvts28" href="ProgramInterface.html">learning the basics of the program usage</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour/iphone-website-generation">Easily create iPhone documentation</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,328 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Lua API</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("LuaAPI");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Lua API</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="Reference.html">Reference</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="Reference.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="Operations.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="FAQ.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Lua API</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">TAS Editor v1.0 comes with the library of 24 functions available for Lua scripts running in FCEUX emulator. With Lua scripts you can automate some aspects of TASing and even create your own tools for movie editing.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">In FCEUX folder there's </span><span class="rvts20">/luaScripts</span><span class="rvts21"> folder with </span><span class="rvts20">/taseditor</span><span class="rvts21"> subfolder in it. There you can find examples of scripts using functions of this library.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you don't know how to make and run Lua scripts in emulators, read </span><a class="rvts27" href="AdvancedFeatures.html#UsingLua">Advanced Features</a><span class="rvts21"> and also refer to </span><a class="rvts27" href="http://www.fceux.com/web/help/fceux.html?Commands.html" target="_blank">FCEUX Help</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps3"><span class="rvts7">Full list of functions:</span></p>
|
||||
<p class="rvps2"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#registerauto">taseditor.registerauto(function func)</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#registermanual">taseditor.registermanual(function func, [string name])</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#engaged">bool taseditor.engaged()</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#markedframe">bool taseditor.markedframe(int frame)</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#getmarker">int taseditor.getmarker(int frame)</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#setmarker">int taseditor.setmarker(int frame)</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#removemarker">taseditor.removemarker(int frame)</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#getnote">string taseditor.getnote(int index)</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#setnote">taseditor.setnote(int index, string newtext)</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#getcurrentbranch">int taseditor.getcurrentbranch()</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#getrecordermode">string taseditor.getrecordermode()</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#getsuperimpose">int taseditor.getsuperimpose()</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#getlostplayback">int taseditor.getlostplayback()</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#getplaybacktarget">int taseditor.getplaybacktarget()</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#setplayback">taseditor.setplayback(int frame)</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#stopseeking">taseditor.stopseeking()</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#getselection">table taseditor.getselection()</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#setselection">taseditor.setselection(table new_set)</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#getinput">int taseditor.getinput(int frame, int joypad)</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#submitinputchange">taseditor.submitinputchange(int frame, int joypad, int input)</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#submitinsertframes">taseditor.submitinsertframes(int frame, int number)</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#submitdeleteframes">taseditor.submitdeleteframes(int frame, int number)</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#applyinputchanges">int taseditor.applyinputchanges([string name])</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#clearinputchanges">taseditor.clearinputchanges()</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="LuaAPI.html#clearinputchanges"><br/></a></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="registerauto"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">taseditor.registerauto(function func)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Registers a callback function ("Auto Function") that runs periodically. The Auto Function can be registered and will be called even when TAS Editor isn't engaged.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When FCEUX is unpaused, your function will be called at the end of every frame (running 60 times per second on NTSC and 50 times per second on PAL).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When FCEUX is paused, your function will be called 20 times per second.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">User can switch on/off auto-calling by checking "Auto function" checkbox in TAS Editor GUI.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Like other callback-registering functions provided by FCEUX, there is only one registered callback at a time per registering function per script. If you register two callbacks, the second one will replace the first, and the call to </span><span class="rvts20">taseditor.registerauto()</span><span class="rvts21"> will return the old callback. You may register </span><span class="rvts71">nil</span><span class="rvts21"> instead of a function to clear a previously-registered callback.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If a script returns while it still has registered callbacks, FCEUX will keep it alive to call those callbacks when appropriate, until either the script is stopped by the user or all of the callbacks are de-registered.</span></p>
|
||||
<p class="rvps10"><a name="registermanual"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">taseditor.registermanual(function func, [string name])</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Registers a callback function ("Manual Function") that can be called manually by TAS Editor user. The function can be registered even when TAS Editor isn't engaged.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Manual function doesn't depend on paused or unpaused FCEUX status. It will be called once every time user presses </span><span class="rvts29">Run function</span><span class="rvts21"> button in TAS Editor GUI.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can provide a new name for this button.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Manual function cannot be run more often than TAS Editor window updates (60/50 FPS or 20FPS when emulator is paused).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In FCEUX code Manual function runs right after Auto Function.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can use this feature to create new tools for TAS Editor. For example, you can write a script that reverses currently selected input, so user will be able to reverse input by selecting a range and clicking </span><span class="rvts29">Run function</span><span class="rvts21"> button.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Like other callback-registering functions provided by FCEUX, there is only one registered callback at a time per registering function per script. If you register two callbacks, the second one will replace the first, and the call to </span><span class="rvts20">taseditor.registermanual()</span><span class="rvts21"> will return the old callback. You may call </span><span class="rvts20">taseditor.registermanual(</span><span class="rvts71">nil</span><span class="rvts20">)</span><span class="rvts21"> to clear a previously-registered callback.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If a script returns while it still has registered callbacks, FCEUX will keep it alive to call those callbacks when appropriate, until either the script is stopped by the user or all of the callbacks are de-registered.</span></p>
|
||||
<p class="rvps10"><a name="engaged"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">bool taseditor.engaged()</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns </span><span class="rvts71">true</span><span class="rvts21"> if TAS Editor is currently engaged, </span><span class="rvts71">false</span><span class="rvts21"> if otherwise.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Also when TAS Editor is engaged, </span><span class="rvts20">movie.mode()</span><span class="rvts21"> returns "taseditor" string.</span></p>
|
||||
<p class="rvps10"><a name="markedframe"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">bool taseditor.markedframe(int frame)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns </span><span class="rvts71">true</span><span class="rvts21"> if given frame is marked in TAS Editor, </span><span class="rvts71">false</span><span class="rvts21"> if not marked.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, returns </span><span class="rvts71">false</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><a name="getmarker"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">int taseditor.getmarker(int frame)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns index number of the Marker under which given frame is located.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns -1 if TAS Editor is not engaged.</span></p>
|
||||
<p class="rvps10"><a name="setmarker"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">int taseditor.setmarker(int frame)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Sets Marker on given frame. Returns index number of the Marker created.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If that frame is already marked, no changes will be made, and the function will return the index number of existing Marker.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can set markers even outside input range.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, returns -1.</span></p>
|
||||
<p class="rvps10"><a name="removemarker"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">taseditor.removemarker(int frame)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Removes marker from given frame. If that frame was not marked, no changes will be made.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, no changes will be made.</span></p>
|
||||
<p class="rvps10"><a name="getnote"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">string taseditor.getnote(int index)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns string representing the Note of given Marker.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns </span><span class="rvts71">nil</span><span class="rvts21"> if TAS Editor is not engaged.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given index is invalid (if Marker with this index number doesn't exist), returns note of the zeroth marker.</span></p>
|
||||
<p class="rvps10"><a name="setnote"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">taseditor.setnote(int index, string newtext)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Sets text of the Note of given Marker.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given index is invalid (if Marker with this index number doesn't exist), no changes will be made.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, no changes will be made.</span></p>
|
||||
<p class="rvps10"><a name="getcurrentbranch"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">int taseditor.getcurrentbranch()</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns number from 0 to 9 representing current Branch.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns -1 if there's no Branches or if TAS Editor is not engaged.</span></p>
|
||||
<p class="rvps10"><a name="getrecordermode"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">string taseditor.getrecordermode()</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns string representing current recorder mode.</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">"All"</span></li>
|
||||
<li class="rvps10"><span class="rvts21">"1P"</span></li>
|
||||
<li class="rvps10"><span class="rvts21">"2P"</span></li>
|
||||
<li class="rvps10"><span class="rvts21">"3P"</span></li>
|
||||
<li class="rvps10"><span class="rvts21">"4P"</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21">Returns </span><span class="rvts71">nil</span><span class="rvts21"> if TAS Editor is not engaged.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you want to check Recorder's read-only state, use </span><span class="rvts20">emu.readonly()</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><a name="getsuperimpose"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">int taseditor.getsuperimpose()</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns number representing current state of Superimpose checkbox in TAS Editor GUI.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">0 – unchecked</span></p>
|
||||
<p class="rvps10"><span class="rvts21">1 – checked</span></p>
|
||||
<p class="rvps10"><span class="rvts21">2 – indeterminate (you can interpret is as half-checked)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, returns -1.</span></p>
|
||||
<p class="rvps10"><a name="getlostplayback"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">int taseditor.getlostplayback()</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns the number of the frame where Playback cursor was before input was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If Playback didn't lose position during Greenzone invalidation, returns -1.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, returns -1.</span></p>
|
||||
<p class="rvps10"><a name="getplaybacktarget"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">int taseditor.getplaybacktarget()</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor's Playback is currently seeking, returns number of target frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If Playback is not seeking or if TAS Editor is not engaged, returns -1.</span></p>
|
||||
<p class="rvps10"><a name="setplayback"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">taseditor.setplayback(int frame)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Sends Playback cursor (current frame counter) to given frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given frame wasn't found in TAS Editor Greenzone, starts seeking to the frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, nothing will be done.</span></p>
|
||||
<p class="rvps10"><a name="stopseeking"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">taseditor.stopseeking()</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Stops Playback seeking and pauses emulation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If Playback wasn't seeking, this function only pauses emulation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, nothing will be done.</span></p>
|
||||
<p class="rvps10"><a name="getselection"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">table taseditor.getselection()</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns a table (array) containing numbers of currently selected frames. These numbers are sorted in ascending order.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If no frames are selected at the moment, returns </span><span class="rvts71">nil</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, returns </span><span class="rvts71">nil</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><a name="setselection"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">taseditor.setselection(table new_set)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Changes current selection to the given set of frames. Frame number in your table don't have to be sorted.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Call </span><span class="rvts20">taseditor.setselection(</span><span class="rvts71">nil</span><span class="rvts20">)</span><span class="rvts21"> to clear selection.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, nothing will be done.</span></p>
|
||||
<p class="rvps10"><a name="getinput"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">int taseditor.getinput(int frame, int joypad)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns a number representing input of given joypad stored in current movie at given frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given frame is negative, returns -1.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given frame is outside current input range, returns 0, which can be interpreted as a blank frame (no buttons pressed at this frame yet).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Joypad value must be one of the following:</span></p>
|
||||
<p class="rvps10"><span class="rvts21">0 – </span><span class="rvts21">to get hardware commands (bit 0 = reset, bit 1 = poweron, bit 2 = FDS insert disk, bit 3 = FDS switch side)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">1 – </span><span class="rvts21">to get 1P buttons</span><span class="rvts21"> (</span><span class="rvts21">bit</span><span class="rvts21"> 0 = A, </span><span class="rvts21">bit</span><span class="rvts21"> 1 = B, </span><span class="rvts21">bit</span><span class="rvts21"> 2 = Select, </span><span class="rvts21">bit</span><span class="rvts21"> 3 = Start, </span><span class="rvts21">bit</span><span class="rvts21"> 4 = Up, </span><span class="rvts21">bit</span><span class="rvts21"> 5 = Down, </span><span class="rvts21">bit</span><span class="rvts21"> 6 = Left, </span><span class="rvts21">bit</span><span class="rvts21"> 7 = Right)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">2 – </span><span class="rvts21">to get 2P buttons</span></p>
|
||||
<p class="rvps10"><span class="rvts21">3 – </span><span class="rvts21">to get 3P buttons</span></p>
|
||||
<p class="rvps10"><span class="rvts21">4 – </span><span class="rvts21">to get 4P buttons</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You should handle returned number (if it's not equal to -1) as a byte, each bit corresponds to one button (e.g. if bit 1 is set that means A button is pressed). Use Bitwise Operations to retrieve the state of specific buttons.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given joypad is outside [0-4] range, returns -1.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, returns -1.</span></p>
|
||||
<p class="rvps10"><a name="submitinputchange"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">taseditor.submitinputchange(int frame, int joypad, int input)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Sends request to TAS Editor asking to change input of given joypad at given frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Actual movie input won't be changed until the moment you call </span><span class="rvts20">taseditor.applyinputchanges()</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Using several consecutive requests and then calling </span><span class="rvts20">applyinputchanges()</span><span class="rvts21"> at the end, you can change several frames of current movie in one moment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When applying the pile of requests, TAS Editor will execute them in consecutive order.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given frame is negative, TAS Editor will ignore such request.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given frame is outside current input range, TAS Editor will expand movie during </span><span class="rvts20">applyinputchanges()</span><span class="rvts21"> to fit the frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given joypad is outside [0-4] range, TAS Editor will ignore such request.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Given input will be treated by TAS Editor as a sequence of bits representing state of each button of given joypad </span><span class="rvts21">(</span><span class="rvts21">bit</span><span class="rvts21"> 0 = A, </span><span class="rvts21">bit</span><span class="rvts21"> 1 = B, </span><span class="rvts21">bit</span><span class="rvts21"> 2 = Select, </span><span class="rvts21">bit</span><span class="rvts21"> 3 = Start, </span><span class="rvts21">bit</span><span class="rvts21"> 4 = Up, </span><span class="rvts21">bit</span><span class="rvts21"> 5 = Down, </span><span class="rvts21">bit</span><span class="rvts21"> 6 = Left, </span><span class="rvts21">bit</span><span class="rvts21"> 7 = Right)</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, nothing will be done.</span></p>
|
||||
<p class="rvps10"><a name="submitinsertframes"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">taseditor.submitinsertframes(int frame, int number)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Sends request to TAS Editor asking to insert given number of blank frames before given frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Actual movie won't be changed until the moment you call </span><span class="rvts20">taseditor.applyinputchanges()</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Insertion can move down some old input and Markers (if "</span><a class="rvts27" href="ProgramCustomization.html#BindMarkerstoInput">Bind Markers to Input</a><span class="rvts21">" option is checked by user).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given number is less or equal to zero, TAS Editor will ignore such request.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given frame is negative, TAS Editor will ignore such request.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given frame is outside current input range, TAS Editor will expand movie during </span><span class="rvts20">applyinputchanges()</span><span class="rvts21"> to fit the frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, nothing will be done.</span></p>
|
||||
<p class="rvps10"><a name="submitdeleteframes"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">taseditor.submitdeleteframes(int frame, int number)</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Sends request to TAS Editor asking to delete given number of frames starting from given frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Actual movie won't be changed until the moment you call </span><span class="rvts20">taseditor.applyinputchanges()</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Deletion can move up some old input and Markers (if "</span><a class="rvts27" href="ProgramCustomization.html#BindMarkerstoInput">Bind Markers to Input</a><span class="rvts21">" option is checked by user).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given number is less or equal to zero, TAS Editor will ignore such request.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given frame is negative, TAS Editor will ignore such request.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If given frame is outside current input range, TAS Editor will expand movie during </span><span class="rvts20">applyinputchanges()</span><span class="rvts21"> to fit the frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, nothing will be done.</span></p>
|
||||
<p class="rvps10"><a name="applyinputchanges"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">int taseditor.applyinputchanges([string name])</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instantly applies the list of previously requested changes to current movie. If these requests actually modified movie data, new item will appear in History Log (so user can undo these changes), and Greenzone may become truncated, Playback cursor may lose its position, auto-seeking may be triggered.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Returns number of frame where first actual changes occurred.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If no actual changes were found (for example, you asked TAS Editor to set buttons that were already pressed), returns -1.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If pending list of changes is empty, returns -1.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can provide a name that will be assigned to this change. This name will be shown in History Log. If you don't provide a name, TAS Editor will use default name ("Change").</span></p>
|
||||
<p class="rvps10"><span class="rvts21">After applying all requests TAS Editor clears the list of requests.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, nothing will be done.</span></p>
|
||||
<p class="rvps10"><a name="clearinputchanges"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps9"><span class="rvts68">taseditor.clearinputchanges()</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Clears the list of previously requested changes, making TAS Editor forget about them before you call </span><span class="rvts20">applyinputchanges()</span><span class="rvts21">. Use this function to discard previously submitted input changes.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's also recommended to call this function before making several requests in a row, so that you'll be sure that only your new changes will apply.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If TAS Editor is not engaged, nothing will be done.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com">Full-featured Documentation generator</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,201 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Mistake-proofing</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("MistakeProofing");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Mistake-proofing</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="TASEditorInside.html">TAS Editor Inside</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="TASEditorInside.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="Implementation.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="FM3format.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Mistake-proofing</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">This page lists many small details of implementation that improve interaction between user and the program. All these points must be considered when porting Taseditor to other platforms.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">When the user closes the emulator, emulator sends a request to Taseditor in order to allow it to close the project first. If the project contains unsaved data, Taseditor shows the Yes/No/Cancel dialog. The user can either save the changes, or save none of them, or cancel the attempt to close the emulator.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When playing back an fm3 project outside Taseditor (like a regular movie), the user can switch the emulator to Recording mode and try rerecording. In this case, the emulator tells the user that current movie is a Taseditor project, and suggests to start editing it. In case of refuse, emulator disables the Recording mode and resumes playing back the project movie. In case of agreement, emulator sends a signal to Taseditor, and at the end of the current frame Taseditor will launch and load the currently played project.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When a ROM is loaded into emulator, the user can launch Taseditor at any moment. If he opens the Taseditor window while playing or recording a movie, Taseditor will automatically create a nameless project containing this movie Input. But if the movie is starting from a savestate, Taseditor will display a warning about not supporting such movies and then create a blank project.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">While the project has no name, autosave function doesn't work.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When saving a nameless project, Taseditor suggests the current ROM name as a name for the fm3 project, with the extension changed to .fm3.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Since the FM3 format is a superstructure over the FM2 format, the user can open fm2 files just like Taseditor projects, using the "Open TAS Editor Project" dialog and choosing the filter "All Files (*.*)". When opening fm2 files, Taseditor additionally informs the user about it with the Yes/No dialog. The user can either load the fm2 file as a new project or cancel the loading.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">After opening an fm2 file or a corrupted fm3 file, the project is considered nameless, even though the TAS Editor window caption displays the name of the loaded file. At the first saving attempt (</span><span class="rvts30">Ctrl + S</span><span class="rvts21">) Taseditor will bring the SaveAs dialog, where the loaded fm2/fm3 file name will be suggested as a name for the project. The user can either save the project with this name or change the name. This way Taseditor draws your attention to the fact that the new project significantly differs from the file that exists on the disk under the same name.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">FM3 projects store the version number of the FM3 format used when saving the file. Different versions can be totally or partially incompatible with each other. If the loaded project version doesn't match the currently supported one, Taseditor shows the Yes/No/Cancel dialog. The user can either resume his attempt to load the whole project (not recommended), or load only the Input from the FM2 data (recommended), or cancel loading.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">FM2 format (and therefore fm3 too) stores the MD5 checksum of the ROM used when creating the movie/project. When loading a project, Taseditor compares the current ROM checksum with the project's one, and if they don't match, brings the Yes/No dialog, displaying the original and the current ROM names. The user can resume loading or cancel it. Later, when saving this project, Taseditor will notice the checksum mismatch again and suggest replacing the ROM name and the checksum in the file before saving. The user can either approve the replacing, or save the project with the old name and checksum, or cancel the saving.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When loading a corrupted project file, Taseditor tries the best of its ability to prevent emulator crash. If an error is found in the middle of loading, the further loading stops and the rest data is replaced with the default data. Particularly, if the error occurred while loading the Greenzone, the project is left with only the Greenzone frames that were successfully pulled out of the file, the rest frames will be pale. Project loading error messages are logged into the FCEUX Message Log.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When loading a project, Taseditor respects current settings of "Greenzone capacity" and "Undo levels". For example, if while saving a project the Greenzone capacity was 5000, but when loading the project the Greenzone capacity is 3000, some frames will be skipped when loading. It's necessary so that a project saved on a more powerful computer can be opened on a less powerful one, that doesn't have enough memory.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When launching, Taseditor loads the data about patterns from the </span><span class="rvts20">taseditor_patterns.txt</span><span class="rvts21"> file. If this file cannot be opened (fer example, it was removed), Taseditor creates a small set of default patterns, in order to keep the Patterns menu filled.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Savestates used by the Greenzone differ from regular savestates a bit. They don't contain movie data, because it's useless information for the Greenzone purposes. Besides, they are always compressed, in order to save memory.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">If after a </span><a class="rvts27" href="Operations.html#Delete">Delete</a><span class="rvts21"> or </span><a class="rvts27" href="Operations.html#LUAChange">Lua Change</a><span class="rvts21"> operation the user effectively removes all Input from the movie, Taseditor will create one blank frame in the movie beginning.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When user is selecting a range of frames by stretching, it's still possible to use hotkeys with the other hand. To avoid conflict, during DRAG_MODE_SELECTION and DRAG_MODE_DESELECTION some functions related to changing the Selection will not work:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 40px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts20">ClearSelection()</span></li>
|
||||
<li class="rvps10"><span class="rvts20">SelectAll()</span></li>
|
||||
<li class="rvps10"><span class="rvts20">SelectBetweenMarkers()</span><span class="rvts21"> – </span><span class="rvts30">Ctrl + A</span></li>
|
||||
<li class="rvps10"><span class="rvts20">selection.undo()</span><span class="rvts21"> – </span><span class="rvts30">Ctrl + Q</span></li>
|
||||
<li class="rvps10"><span class="rvts20">selection.redo()</span><span class="rvts21"> – </span><span class="rvts30">Ctrl + W</span></li>
|
||||
<li class="rvps10"><span class="rvts20">ReselectClipboard()</span><span class="rvts21"> – </span><span class="rvts30">Ctrl + B</span></li>
|
||||
<li class="rvps10"><span class="rvts20">selection.Transpose()</span><span class="rvts21"> – </span><span class="rvts30">Ctrl + Up</span><span class="rvts21">, </span><span class="rvts30">Ctrl + Down</span><span class="rvts21">, </span><span class="rvts30">Ctrl + Home</span><span class="rvts21">, </span><span class="rvts30">Ctrl + End</span></li>
|
||||
<li class="rvps10"><span class="rvts20">selection.JumpPrevMarker()</span><span class="rvts21"> – </span><span class="rvts30">Ctrl + Page Up</span></li>
|
||||
<li class="rvps10"><span class="rvts20">selection.JumpNextMarker()</span><span class="rvts21"> – </span><span class="rvts30">Ctrl + Page Down</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">When dragging the Playback cursor, there is small limitation related to how seeking works. After the leftclick on the icons column, the Playback starts seeking to the frame, and the user can't drag the Playback cursor to other frames until it reaches the target frame. During this initial seeking the mouse cursor is replaced by an arrow with a hourglass. Once the initial seeking is over, the Playback cursor dragging is fully functional. This is necessary, because there's possibility that the user clicks a frame very far from the Greenzone head and the "Follow cursor" checkbox makes the Piano Roll immediately jump to the current position of the light-blue cursor, so the frame under the mouse cursor changes before user even released the left button.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Since the icon column is rather narrow, the user may accidentally miss clicking it. So when you click the left border of the Piano Roll or a bit to the left from it, Taseditor assumes that was a click on the icons column. As a result, the user doesn't have to precisely aim when he needs to move the Playback cursor or start dragging it.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When emulator is paused, the middle mouse button works only under condition that the right button is released. Since the middle button is usually a wheel, the user can accidentally push it while rolling the wheel with the right button held (Playback cursor navigation). As for rolling the wheel with modifier keys held, this is used much less often, so they don't need such protection.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Any middleclick over the FCEUX window is sent to Taseditor window. Similarly, the wheel rolling message is sent to Taseditor, when the focus is on the FCEUX window. And the rightclick on the FCEUX window doesn't work at all. Thanks to that, you can use the middle button (the wheel) even when the mouse cursor is over the FCEUX window.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Even when the Recording mode is on, Taseditor won't rerecord Input while seeking. Thanks to that, you can safely drag the Playback cursor without disabling the Recording mode.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When Taseditor is engaged, the following menu commands are available only when the Recording mode if on and the Playback is not seeking:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 40px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">NES -> Reset</span></li>
|
||||
<li class="rvps10"><span class="rvts21">NES -> Power</span></li>
|
||||
<li class="rvps10"><span class="rvts21">NES -> Eject/insert Disk</span></li>
|
||||
<li class="rvps10"><span class="rvts21">NES -> Switch Disk Side</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">When Taseditor is engaged, the following FCEUX menu commands are unavailable:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 40px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">File -> Open ROM</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Close</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Recent</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Savestate -> Load State</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Savestate -> Save State</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Savestate -> Load State From</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Savestate -> Save State As</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Savestate -> Next save slot</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Savestate -> Previous save slot</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Savestate -> View save slots</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Movie -> Recent</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Movie -> Record Movie</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Movie -> Play Movie</span></li>
|
||||
<li class="rvps10"><span class="rvts21">File -> Movie -> Stop Movie</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Config -> Enable -> Auto-savestates (always off when Taseditor is engaged)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Config -> Enable -> Backup Savestates (always off when Taseditor is engaged)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Config -> Enable -> Compress Savestates (always on when Taseditor is engaged)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Config -> PAL Emulation (set up this before launching Taseditor)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Config -> PPU -> New PPU / Old PPU (set up this before launching Taseditor)</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">It's also necessary to ensure that the user can not change the movie synchronization settings while editing the project. So when Taseditor is engaged, the following GUI elements in the "Input Configuration" window are locked:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 40px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">the "Attach four-score" checkbox</span></li>
|
||||
<li class="rvps10"><span class="rvts21">the "Replace port 2 Start With Microphone" checkbox</span></li>
|
||||
<li class="rvps10"><span class="rvts21">ListBox for port0</span></li>
|
||||
<li class="rvps10"><span class="rvts21">ListBox for port1</span></li>
|
||||
<li class="rvps10"><span class="rvts21">ListBox for port2</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">When Taseditor is engaged, the following hotkeys are not working:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 40px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Hide Menu Toggle</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Fastest Speed</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Save State As...</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Load State From...</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Record Movie To...</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Play Movie From...</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Stop Movie</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Insert Coin / Toggle Dipswitch – because these commands are not supported by the FM2 format yet</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Load Last Auto-save</span></li>
|
||||
<li class="rvps10"><span class="rvts21">View save slots</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Open ROM</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Close ROM</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Undo/Redo Savestate</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Toggle Fullscreen</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Hotkeys that change their behavior when Taseditor is engaged:</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 40px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Power</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Reset</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Eject or Insert FDS Disk</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Switch FDS Disk Side</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Savestate Slot 0</span><span class="rvts21"> – </span><span class="rvts26">Savestate Slot 9</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Save State to Slot 0</span><span class="rvts21"> – </span><span class="rvts26">Save State to Slot 9</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Load State from Slot 0</span><span class="rvts21"> – </span><span class="rvts26">Load State from Slot 9</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Play Movie From Beginning</span></li>
|
||||
<li class="rvps10"><span class="rvts26">Reload ROM or TAS Editor Project</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Open TAS Editor</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Since the </span><span class="rvts30">Alt</span><span class="rvts21"> and </span><span class="rvts26">F10</span><span class="rvts21"> keys are actively used in Taseditor work, their standard behavior (open main menu) is disabled.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Since the </span><span class="rvts26">Spacebar</span><span class="rvts21"> key is used as a hotkey by default, its standard behavior (simulate the click on the currently focused GUI element) is disabled. Also, all GUI elements of the TAS Editor window handle the middleclick message and send it to the Playback, thus the middleclick works independently of the mouse cursor position.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Since the context menu on the rightclick at the Piano Roll is not often used, it appears only if the user clicks the selected line in the frame number column (Frame#). In all the rest cases the context menu doesn't appear, instead the rightclick-and-hold at the Piano Roll allows to drag its contents in any direction.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Since the right button is often used for the Playback cursor navigation with the wheel, the user is encouraged to click it without caring about the current mouse cursor position. In theory it's possible that the user accidentally rightclicks a Bookmark. To avoid such unintended commands, the Bookmark List and the Branches Tree both require to press and release the right button over the same Bookmark. Also, if between pressing and releasing the user rotated the wheel, the Bookmark won't be changed.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">The user can jump to a Bookmark with a single click on the desired icon in the Branches Tree. Doing so he expects that after the click the light-blue triangle (the Playback cursor icon) will also jump to the place in the Branches Tree. It is indeed so for Bookmarks that don't contradict with the current timeline, but it's not so for Bookmarks representing alternative strategies. After jumping to the frame of such Bookmark, the Playback cursor will appear on another branch (even though it's on the same frame of the movie). To notify the user about possible misconception, the mouse cursor turns into an arrow with a question mark when the user points to such Bookmarks.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When the Branches Tree transforms, hovering the mouse cursor over its elements doesn't work, because the active element area is constantly moving and running away from the mouse cursor.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com">Full-featured Documentation generator</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,371 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Navigation</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("Navigation");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Navigation</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="Reference.html">Reference</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="Reference.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="Controls.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="Operations.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Navigation</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">FCEUX main window can only display data of one frame of a movie at any given moment. Piano Roll can cover data for tens of frames at the same time. But average movie has thousands of frames. So TASer constantly needs to scroll the Piano Roll up and down or rewind emulator playback to get the data about needed frame or group of frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Throughout the documentation this is called "movie navigation". It takes major part of TASing, and Taseditor introduces many new ways of navigation, striving to make it as fast as possible. Depending on the situation some of them are better then others, so it's not recommended to stick to a single one.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Ideally, the navigation skills should move to muscle memory, allowing you to always appear in necessary place of the movie without interrupting the analysis of current task.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">All ways of navigating a movie:</span></p>
|
||||
<p class="rvps10"><span class="rvts52"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><a class="rvts57" href="Navigation.html#scrolling-piano-roll">Scrolling Piano Roll</a></li>
|
||||
</ul>
|
||||
<ol style="text-indent: 32px; margin-left: 20px; list-style-position: inside;">
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#scrollbar-drag">Using vertical scrollbar</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#wheel">Rolling mouse wheel</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#crossing-gaps">Crossing gaps</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#jumping-by-pages">Paging through</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#jump-home-end">Jumping to the beginning / to the end of the movie</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#scroll-to-playback">Jumping to Playback cursor</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#scroll-to-selection">Jumping to Selection cursor</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#scroll-to-playback-marker">Jumping to the Marker above Playback cursor</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#scroll-to-selection-marker">Jumping to the Marker above Selection cursor</a></li>
|
||||
</ol>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><a class="rvts58" href="Navigation.html#playback-cursor">Playback cursor navigation</a></li>
|
||||
</ul>
|
||||
<ol style="text-indent: 32px; margin-left: 20px; list-style-position: inside;">
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#frame-advance-rewind">Frame-by-frame shift</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#rewinding-by-wheel">Rewinding by mouse wheel</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts61" href="Navigation.html#drag-playback">Dragging with mouse</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#playback-jumping-markers">Jumping on Markers</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#jump-bookmark">Jumping to Bookmarks</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#playback-home-end">Jumping to the beginning / to the end of the movie</a></li>
|
||||
</ol>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><a class="rvts60" href="Navigation.html#selection-cursor">Selection cursor navigation</a></li>
|
||||
</ul>
|
||||
<ol style="text-indent: 32px; margin-left: 20px; list-style-position: inside;">
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#selection-up-down">Frame-by-frame shift</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#selection-home-end">Moving Selection to the beginning / to the end of the movie</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#selection-jumping-markers">Jumping on Markers</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#selection-history">Tracking the Selection History</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#reselect-clipboard">Returning to the origin of Clipboard data</a></li>
|
||||
</ol>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><a class="rvts59" href="Navigation.html#special">Special</a></li>
|
||||
</ul>
|
||||
<ol style="text-indent: 32px; margin-left: 20px; list-style-position: inside;">
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#find-note">Finding Markers with given text</a></li>
|
||||
<li class="rvps10" style="text-indent: 32px"><a class="rvts57" href="Navigation.html#similar-note">Jumping to segment with similar description</a></li>
|
||||
</ol>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="scrolling-piano-roll"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p><span class="rvts53">Scrolling Piano Roll</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="scrollbar-drag"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">1. Using vertical scrollbar</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on the scrollbar or drag its thumb to scroll Piano Roll like any other list.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Playback cursor and Selection cursor positions are not affected by Piano Roll scrolling.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">when you need to get to a far away section of the movie. The scrollbar allows to traverse thousands of frames at once</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when you're searching for a segment which can be anywhere in the movie</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="wheel"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">2. Rolling mouse wheel</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Roll mouse wheel up or down </span><span class="rvts21">to scroll Piano Roll like any other list.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Mouse cursor can be pointing anywhere except History Log window.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">when you're observing a segment that doesn't fit into Piano Roll visible area</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when you're searching for a nearby segment</span></li>
|
||||
</ul>
|
||||
<p><a name="crossing-gaps"></a>
|
||||
<span class="rvts62"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">3. Crossing gaps</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Point mouse cursor to any cell in Input/Markers/icons, hold </span><span class="rvts30">Alt</span><span class="rvts21"> and roll the mouse wheel up or down to scroll the Piano Roll to the closest cell that contains data different from the data of adjacent cell.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">when you see an emptiness in specific button column and want to find nearest frame where the button is pressed</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when you see the specific button is held for many frames and want to find exactly the first frame where the button was pressed, or the frame where it will be released</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when you need to find previous/next Marker</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when you need to find previous/next buttonpress</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when you need to find the Bookmark above/below (in the icons column)</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="jumping-by-pages"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">4. Paging through</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Press</span><span class="rvts21"> </span><span class="rvts30">Page Up</span><span class="rvts21"> or </span><span class="rvts30">Page Down</span><span class="rvts21"> key </span><span class="rvts21">to scroll Piano Roll like any other list. The amount of scrolling depends on the size of Piano Roll visible area.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">when you're searching for a segment which is probably somewhere nearby</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="jump-home-end"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">5. Jumping to the beginning / to the end of the movie</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Press</span><span class="rvts21"> </span><span class="rvts30">Home</span><span class="rvts21"> or </span><span class="rvts30">End</span><span class="rvts21"> </span><span class="rvts21">to scroll Piano Roll to the beginning or to the end of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to go to </span><span class="rvts21">the beginning or to the end of the movie</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="scroll-to-playback"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">6. Jumping to Playback cursor</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on the upper "Marker #" label (colored light-blue) to immediately scroll Piano Roll to Playback cursor position. Alternative way to do it is to press </span><span class="rvts30">Shift</span><span class="rvts21"> key twice within a short amount of time.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to see the context of currently played frame of the movie</span></li>
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you wish to return to currently played segment from any other place</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="scroll-to-selection"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">7. Jumping to Selection cursor</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on the lower "Marker #" label to immediately scroll Piano Roll to Selection cursor position. Alternative way to do it is to press </span><span class="rvts30">Ctrl</span><span class="rvts21"> key twice within a short amount of time.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you wish to return to currently edited segment from any other place</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="scroll-to-playback-marker"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">8. Jumping to the Marker above Playback cursor</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on the upper edit field to immediately scroll Piano Roll to the Marker which Note is going to be edited.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Works only when the </span><a class="rvts27" href="ProgramCustomization.html#FollowMarkerNotecontext">View -> Follow Marker Note context</a><span class="rvts21"> option is enabled.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to see the beginning of </span><span class="rvts21">currently played segment</span></li>
|
||||
</ul>
|
||||
<p class="rvps14"><a name="scroll-to-selection-marker"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">9. Jumping to the Marker above Selection cursor</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on the lower edit field to immediately scroll Piano Roll to the Marker which Note is going to be edited.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Works only when the </span><a class="rvts27" href="ProgramCustomization.html#FollowMarkerNotecontext">View -> Follow Marker Note context</a><span class="rvts21"> option is enabled.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to see the beginning of </span><span class="rvts21">currently edited segment</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="playback-cursor"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p><span class="rvts53">Playback cursor navigation</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Playback cursor is always bound to current state of emulated game. This means that emulator affects this cursor when emulating the game, and vice versa, when you move this cursor, you affect the emulator.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">There's one limitation in the controlling of the cursor: sometimes it can't immediately move to the desired frame, seeking takes some time.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When the "Follow cursor" checkbox in the Playback panel is checked, the Piano Roll automatically scrolls after the Playback cursor.</span></p>
|
||||
<p class="rvps10"><a name="frame-advance-rewind"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">1. Frame-by-frame shift</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on </span><span class="rvts29"><</span><span class="rvts21"> or </span><span class="rvts29">></span><span class="rvts21"> button in the Playback panel, or press </span><span class="rvts30">Shift + Up</span><span class="rvts21"> or </span><span class="rvts30">Shift + Down</span><span class="rvts21">, or use </span><span class="rvts26">Frame Rewind </span><span class="rvts21">or </span><span class="rvts26">Frame Advance</span><span class="rvts21"> hotkey to move Playback cursor 1 frame back of forward.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to explore events of current segment carefully</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="rewinding-by-wheel"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">2. Rewinding by mouse wheel</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Hold right mouse button and r</span><span class="rvts21">oll mouse wheel up or down </span><span class="rvts21">to move Playback cursor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Mouse cursor can be pointing anywhere.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to explore events of current segment carefully/quickly</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="drag-playback"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts46">3. Dragging with mouse</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on any cell in the leftmost column of the Piano Roll ("Icons" column) to send the Playback cursor to the frame. Also, click on any cell of the column and hold the left mouse button to drag the Playback cursor by moving the mouse. This method also allows to scroll the Piano Roll by dragging the Playback cursor outside (above or below the Piano Roll).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen </span><span class="rvts21">you're </span><span class="rvts21">searching for an in-game event of the movie</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="playback-jumping-markers"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">4. Jumping on Markers</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on </span><span class="rvts29"><<</span><span class="rvts21"> or </span><span class="rvts29">>></span><span class="rvts21"> button in the Playback panel, or press </span><span class="rvts30">Shift + Page Up</span><span class="rvts21"> or </span><span class="rvts30">Shift + Page Down</span><span class="rvts21">, or hold </span><span class="rvts30">Shift</span><span class="rvts21"> and roll the mouse wheel to move Playback cursor to previous or next Marker.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to set Playback cursor to the beginning of currently played segment (provided that the frame of the beginning is marked)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when you want to see </span><span class="rvts21">events of previous/next segments</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="jump-bookmark"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">5. Jumping to Bookmarks</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Press the hotkey (</span><span class="rvts26">0-9</span><span class="rvts21">) corresponding to the number of desired Bookmark, or click on a frame number in Bookmarks List, or click on a Bookmark icon in the Branches Tree to send Playback cursor to the bookmarked frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to re-watch events of the movie starting from a bookmarked frame (e.g. watch the movie from the beginning of Level 2)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when you changed Input before the bookmarked frame and want to see new events at the frame</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="playback-home-end"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">6. Jumping to the beginning / to the end of the movie</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Press </span><span class="rvts30">Shift + </span><span class="rvts30">Home</span><span class="rvts21"> or </span><span class="rvts30">Shift + </span><span class="rvts30">End</span><span class="rvts21">, or click the cloudlet or the fireball in the Branches Tree to move Playback cursor to the beginning or to the end of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can also press the </span><span class="rvts26">Play movie from the beginning</span><span class="rvts21"> hotkey (</span><span class="rvts26">Shift + R</span><span class="rvts21"> by default) to move Playback cursor to the beginning of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you want to replay the movie from the very beginning</span></li>
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to fill all movie frames with Greenzone data</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="selection-cursor"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p><span class="rvts53">Selection cursor navigation</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Selection cursor is usually located on the frame where the most recent changes of Input were made, but you can also move the cursor to any other frame when needed.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Piano Roll automatically scrolls after the Selection.</span></p>
|
||||
<p class="rvps10"><a name="selection-up-down"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">1. Frame-by-frame shift</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Press </span><span class="rvts30">Ctrl + Up</span><span class="rvts21"> or </span><span class="rvts30">Ctrl + Down</span><span class="rvts21"> to move current Selection 1 frame up or down.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to transpose Selection up or down</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="selection-home-end"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">2. Moving Selection to the beginning / to the end of the movie</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Press </span><span class="rvts30">Ctrl + </span><span class="rvts30">Home</span><span class="rvts21"> or </span><span class="rvts30">Ctrl + </span><span class="rvts30">End</span><span class="rvts21"> to move current Selection to the beginning or to the end of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to select the same set of frames at the beginning or at the end of the movie</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="selection-jumping-markers"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">3. Jumping on Markers</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Click on </span><span class="rvts29"><<</span><span class="rvts21"> or </span><span class="rvts29">>></span><span class="rvts21"> button at the bottom of the Toolbox, or press </span><span class="rvts30">Ctrl + Page Up</span><span class="rvts21"> or </span><span class="rvts30">Ctrl + Page Down</span><span class="rvts21">, or hold </span><span class="rvts30">Ctrl</span><span class="rvts21"> and roll the mouse wheel</span><span class="rvts21"> to move Selection cursor </span><span class="rvts21">to previous or next Marker.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">when you need to set Selection cursor to the beginning of currently edited segment (provided that the frame of the beginning is marked)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you want to move to </span><span class="rvts21">previous/next segments</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="selection-history"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">4. Tracking the Selection History</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Press </span><span class="rvts30">Ctrl + Q</span><span class="rvts21"> or </span><span class="rvts30">Ctrl + W</span><span class="rvts21"> to revert Selection to its previous or next state.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This method of navigation allows to return to previously edited segments and quickly remember the sequence of recent changes. </span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to return to previously edited segment</span></li>
|
||||
<li class="rvps10"><span class="rvts21">w</span><span class="rvts21">hen you need to select the same set of frames as before</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="reselect-clipboard"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">5. Returning to the origin of Clipboard data</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Press </span><span class="rvts30">Ctrl + B</span><span class="rvts21"> to revert Selection to its state at the moment of the last "Copy to Clipboard" operation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">when you need to remember where the Input was copied from</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="special"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p><span class="rvts53">Special</span></p>
|
||||
<p><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="find-note"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">1. Finding Markers with given text</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Open the </span><span class="rvts25">Find Note</span><span class="rvts21"> window, enter the text to search and click </span><span class="rvts29">Find next</span><span class="rvts21"> or press Enter key to set Selection cursor to the closest Marker which Note contains the text. </span><span class="rvts21">The Piano Roll automatically scrolls after the Selection. You can search up or down from current position of Selection cursor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">when you need to find the segment, knowing some of the text it is labeled with</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><a name="similar-note"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">2. Jumping to segment with similar description</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Leave Playback cursor in current segment and click the </span><span class="rvts29">Similar</span><span class="rvts21"> or </span><span class="rvts29">More</span><span class="rvts21"> button to set Selection cursor to the Marker containing the most relevant Note. </span><span class="rvts21">The Piano Roll automatically scrolls after the Selection.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This method is described in the </span><a class="rvts27" href="AdvancedFeatures.html#UsingMarkers">Advanced Features</a><span class="rvts21"> chapter.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When to use:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">when you need to find the segment with description similar to currently played segment.</span></li>
|
||||
</ul>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/create-epub-ebooks">Write EPub books for the iPad</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,164 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>4.2. Nonlinear TASing</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("NonlinearTASing");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>4.2. Nonlinear TASing</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="BeginnersGuide.html">Beginner's Guide</a> ›› <a href="TASingMethodology.html">4. TASing Methodology</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="TASingMethodology.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="TraditionalTASing.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="SemiautomaticTASing.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Nonlinear TASing</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-method2.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">This is the main method when working with Taseditor. At first it may seem rather different from the traditional TASing, however, they are essentially very similar.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When using this method, the Recording mode should always be off. The </span><span class="rvts21">"Auto-restore last position" checkbox should be disabled. The "Turbo seek" and "Follow cursor" checkboxes are usually disabled, but may be enabled when necessary.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">General activity:</span></p>
|
||||
<p class="rvps10"><span class="rvts48"><br/></span></p>
|
||||
<ol style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Scroll the Piano Roll to the beginning of the edited segment, put</span><span class="rvts21"> the Playback cursor here, define the goal. It's also recommended to mark the beginning with a Marker</span><span class="rvts21">.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Suppose there's a mistake in the segment, weigh known factors of optimality and figure out the way to fix the mistake.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">The mouse cursor navigation to any frame of the current segment is practically instant.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Edit the segment with the mouse. You can either change the Input blindly, or move the Playback cursor from time to time in order to check with the game. The steps 3 and 4 are constantly alternating until you consider the editing complete.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Detect the end of the segment by putting the Playback cursor at the target event.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">[</span><span class="rvts34">optional step</span><span class="rvts21">] Save the finished approach to any free Bookmark, e.g. to slot </span><span class="rvts26">8</span><span class="rvts21">.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">If this isn't the first approach to the segment, compare the new result to the best old result, using the optimality criterion. If the new approach is better (or it's the first approach), save the result to the Bookmark </span><span class="rvts26">9</span><span class="rvts21">. The slot </span><span class="rvts26">9</span><span class="rvts21"> will be used for keeping the best result of polishing the segment.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">If you still want to try different approaches, return to step 2, until you run out of ideas.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">[</span><span class="rvts34">optional step</span><span class="rvts21">] If you need more ideas, you can get some information from the past or the future by moving the Playback cursor to different segments of the movie or unpausing the emulator. When necessary, you can quickly draw a rough Input for watching the upcoming events of the game.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When there's no more ideas, restore the best approach from the History Log or the Bookmark </span><span class="rvts26">9</span><span class="rvts21"> into the current movie and proceed to the next segment.</span></li>
|
||||
</ol>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Since all created approaches to playing the segment are automatically saved in the History Log, you could follow the temptation to rely on the Log and not save the approaches to Bookmarks (steps 6 and 7), instead just reach the target event once and then experiment with this Input, gradually improving it (and simply undoing all the changes that are for the worse). Such perfunctory way of TASing is technically possible, but not recommended, because it doesn't let you think far outside the terms of the first approach (because you subconsciously fear to lose the old best approach by leaving it too far away).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Even if the outcome of the latest modification of the Input made the game behave worse, you should not immediately revert to the previous state of the movie, better try to examine the cause of the worsening and continue the modification to turn it into an improvement. And in order to never be afraid to lose the previous successful playthrough in the depths of the History Log, you should do exactly like they do in the traditional TASing – allot a special slot for storing the best result and set this Bookmark to the end of the segment every time you improve the result.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">And you can do the same with those promising approaches that are somewhat better, but somewhat worse than the current best result. When you're saving all alternative approaches to separate Bookmarks, you can safely remove their Input from the working movie or change it beyond recognition, because you can return to any of them with a single key press, and no need to search within the History Log.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Unlike the traditional TASing method, here you may lose sight of dividing the movie into logical segments, because now you don't have to mark the beginning and the end of the current segment with Bookmarks. However, it's still recommended to keep an order and mark the beginning of every important segment with Markers, in order to limit the number of optimality factors.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The beginning and the end of a segment are usually associated with certain events of the game, and not with a soulless frame number. But since the starting event of the segment is not affected by modifying the Input of the segment, this event will always occur in the same frame, so you can lock the frame with a Marker.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The ending event of the segment may occur in various points of time, depending on the Input in the segment. So if you mark the end with a Marker, you will need to move the Marker up or down every time you change the target event by modifying the Input. Often it's impractical to spend time on dragging, so instead of the trailing Marker you can use aforementioned Bookmark which both stores the best approach and serves as a mark of the end of current segment.</span></p>
|
||||
<p class="rvps10"><a name="GreenArrow"></a>
|
||||
<span class="rvts21">As for simple segments, you can polish them without marking the ending frame at all, by simply relying on your own memory and on the green arrow provided by Taseditor. With this green arrow the Taseditor hints you the frame where you've stopped watching the segment the last time (before you started modifying the Input of the segment). Usually this is the frame where the target event was detected in previous approach. So you may as well replay the updated segment up to the frame and compare the new result with the old one. If the target event is now detected 2 frames above the green arrow, it means you've outran previous result by 2 frames, so the new Input is better (if your criterion is speed). This entire logical chain pops in your mind once you glance at the Piano Roll after watching the outcome of the recent Input modification.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The process of polishing the Input in the nonlinear method is a constant alternation of editing and watching the segment. You analyze the situation during the watching and right after stopping the watching.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Possible ways to watch the outcome of Input:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">unpause the emulator by pressing the </span><span class="rvts26">Pause</span><span class="rvts21"> hotkey or the middle mouse button. After the segment ends, you have to pause emulator manually (and no problem if you stop it a bit later, since you can always rewind up)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">start seeking to the green arrow by pressing the </span><span class="rvts26">Restore Playback</span><span class="rvts21"> hotkey or the middle mouse button (when the green arrow is outside the Greenzone).</span></li>
|
||||
<li class="rvps10"><span class="rvts21">start seeking to the nearest Marker by holding </span><span class="rvts30">Shift</span><span class="rvts21"> and pressing the middle mouse button</span></li>
|
||||
<li class="rvps10"><span class="rvts21">start seeking to the Selection cursor by holding </span><span class="rvts30">Ctrl </span><span class="rvts21">and pressing the middle mouse button, granted that the Selection cursor is below the Playback cursor</span></li>
|
||||
<li class="rvps10"><span class="rvts21">rewatch the segment from the Selection cursor position to the Playback cursor position by by holding </span><span class="rvts30">Ctrl </span><span class="rvts21">and pressing the middle mouse button, granted that the Selection cursor is above the Playback cursor</span></li>
|
||||
<li class="rvps10"><span class="rvts21">drag the Playback cursor manually, using the mouse cursor</span></li>
|
||||
<li class="rvps10"><span class="rvts21">move the Playback cursor by holding the right mouse button and rolling the mouse wheel</span></li>
|
||||
<li class="rvps10"><span class="rvts21">shift the Playback cursor frame-by-frame using </span><span class="rvts26">Frame Rewind</span><span class="rvts21"> and </span><span class="rvts26">Frame Advance</span><span class="rvts21"> hotkeys or </span><span class="rvts29"><</span><span class="rvts21"> and </span><span class="rvts29">> </span><span class="rvts21">buttons or </span><span class="rvts30">Shift + Up</span><span class="rvts21"> и </span><span class="rvts30">Shift + Down</span><span class="rvts21"> keys</span></li>
|
||||
<li class="rvps10"><span class="rvts21">and there are other </span><a class="rvts27" href="Navigation.html#playback-cursor">ways of navigation with the Playback cursor</a><span class="rvts21">.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Most often you are going to either click the middle mouse button or move the Playback cursor by scrolling the mouse wheel. Don't attach yourself to a single one of the ways, learn to use them depending on a situation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The ratio between the time spent on editing and on watching depends on the complexity of the current segment and on the volume of your knowledge about the game. The more you TAS a single game, the better you are aware of its regularities. So near the end of your project you'll be able to foresee the outcome of your Input modifications before even attempting to edit them in. Then you'll only need to watch the segment in order to confirm your guess.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In some cases you can judge about the optimality of an Input by seeing its interim results and not even watching the segment to the end. For example, if the character bumps into a wall and nullifies his speed in the middle of the segment, you can immediately guess that he is going to reach the target event later than previous time. So sometimes you want to only watch a few frames and continue the editing. However, such a hurry may lead you to reject a solution that is suboptimal at first glance but has a potential to be very successful in another segment. For example, after bumping the wall Mario may accidentally enter inside and go through it. That's why it's recommended to never hurry when TASing, and to watch the current segment to the end, where you can be sure the optimality criterion won't let you down.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Technically you can watch and edit the Input simultaneously. When the </span><span class="rvts21">"Follow cursor" checkbox is disabled, the Piano Roll stays still, while the movie is played, so you can draw buttonpresses right when they are executed (replayed). For example, when Mario jumps over an obstacle, try to change the height of the jump by drawing and erasing the </span><span class="rvts29">A</span><span class="rvts21"> button presses without pausing the emulation. You can slow the emulation down by the </span><span class="rvts26">-</span><span class="rvts21"> and </span><span class="rvts26">=</span><span class="rvts21"> hotkeys, in order to have more time for clicking while watching.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">But when you need to have enough time both for clicking and for thinking, better pause the emulator and TAS properly.</span></p>
|
||||
<p class="rvps10"><a name="turbo-seeking"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The emulation speed can be both decreased and increased. Before Taseditor, speeding up the emulation was used only for quick replay of the finished part of the movie. But now the </span><span class="rvts37">turbo emulation</span><span class="rvts21"> also serves as an original way of TASing. With an extremely fast emulation you can feel the interconnection between a buttonpress and its distant outcome.</span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/dw-luck_manipulation.gif"/></p>
|
||||
<p class="rvps10"><a name="LuckManipulation"></a>
|
||||
<span class="rvts21">A good example would be the process of luck manipulation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Normally, when shooting you can see the connection between pressing the </span><span class="rvts29">B</span><span class="rvts21"> button and a bullet appearing on screen at the next frame. Applying this association (</span><span class="rvts29">B</span><span class="rvts21"> = shot) to an in-game situation makes you think "the later I press </span><span class="rvts29">B</span><span class="rvts21">, the later the bullet will appear".</span></p>
|
||||
<p class="rvps10"><span class="rvts21">But with turbo-seeking you effectively skip all irrelevant steps of the movie (shooting, bullet flying, collision, enemy death, etc), so right after making the </span><span class="rvts29">B</span><span class="rvts21"> buttonpress you immediately see which item was dropped by the enemy. This new association (</span><span class="rvts29">B</span><span class="rvts21"> = possibility of a bonus item) makes you think about this in-game situation more like "the type of the item drop depends on when I press </span><span class="rvts29">B</span><span class="rvts21">".</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This way turbo allows to automatically filter useless information that is produced by the game in the middle of the segment, and only consume the necessary data that appears at the end of the segment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Here's how you do it:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Switch on the "Turbo seek" checkbox. Switch of the </span><span class="rvts21">"Follow cursor".</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Set a trial buttonpress of the </span><span class="rvts29">B</span><span class="rvts21"> at the beginning of the segment where you can shoot the enemy.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Watch how the bullet hits the enemy and leave the Playback cursor at the frame where the item is supposedly laying on the ground for a second or two. That will be the end of current segment.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">So we assume that the first try didn't bring you the needed item, but you know that killing the enemy a bit later may change the outcome. </span><span class="rvts21">Move the </span><span class="rvts29">B</span><span class="rvts21"> buttonpress forward one frame (just insert a blank frame before the old position of the buttonpress).</span></li>
|
||||
<li class="rvps10"><span class="rvts21">This action makes Taseditor rewind the game back, and on FCEUX screen you can see the moment before shooting.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Press the middle mouse button or </span><span class="rvts26">Spacebar</span><span class="rvts21"> (the key assigned to the </span><span class="rvts26">Restore Playback</span><span class="rvts21"> hotkey). The game events will replay like a flash, and you'll almost immediately see which item now falls from the enemy.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">If the result is not satisfying, press </span><span class="rvts30">Ctrl + Shift + Insert</span><span class="rvts21"> again, thus inserting another blank frame before the existing </span><span class="rvts29">B</span><span class="rvts21"> buttonpress. The shot is delayed one more frame. Restore Playback again to see the new result.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Continue until you find the frame where shooting the enemy brings you the needed item. This way you can test a hundred of options within a minute, by simply pressing the hotkeys and only watching the FCEUX screen.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Pros of the method:</span></p>
|
||||
<p class="rvps14"><span class="rvts22">+ </span><span class="rvts21">Instant navigation.</span></p>
|
||||
<p class="rvps14"><span class="rvts22">+ </span><span class="rvts21">Possibility to skip useless scenes.</span></p>
|
||||
<p class="rvps14"><span class="rvts22">+ </span><span class="rvts21">Detachment from the game flow increases the objectivity.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Cons of the method:</span></p>
|
||||
<p class="rvps14"><span class="rvts22">– </span><span class="rvts21">Lack of the feedback inherent to normal game-player interaction.</span></p>
|
||||
<p class="rvps14"><span class="rvts22">– </span><span class="rvts21">Emphasis on the mouse controls.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">When the method is recommended to use:</span><span class="rvts21"> most of time. Combine this method with the next method in order to create the full picture of the in-game possibilities.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="SemiautomaticTASing.html">The next method</a><span class="rvts21"> fixes the main disadvantage of this method.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour">Easily create EBooks</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,716 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Operations</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("Operations");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Operations</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="Reference.html">Reference</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="Reference.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="Navigation.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="LuaAPI.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Operations</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">All modifications of the movie are registered in History Log. Every record of the Log contains the time when the modification was done and the keyframe (or starting and ending frames of the section) to which the modification was applied.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Here you can find the list of </span><span class="rvts24">all possible types of History records and corresponding operations with the movie.</span></p>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps21"><table width="420" border="1" cellpadding="0" cellspacing="0" style="border-color: #000000 #ffffff #ffffff #000000; border-style: solid;">
|
||||
<tr valign="middle">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #0000ff; width: 132px; height: 10px;"><p class="rvps5"><span class="rvts66">Input change</span></p>
|
||||
</td>
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #0000ff; width: 150px; height: 10px;"><p class="rvps5"><span class="rvts66">Markers change</span></p>
|
||||
</td>
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #0000ff; width: 124px; height: 10px;"><p class="rvps5"><span class="rvts66">Other</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ccffff; width: 132px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Set">Set</a></p>
|
||||
</td>
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #f2f2c8; width: 150px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#MarkerSet">Marker Set</a></p>
|
||||
</td>
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ede4e4; width: 124px; height: 10px;"><p class="rvps5"><span class="rvts67">Initialization</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ccffff; width: 132px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Unset">Unset</a></p>
|
||||
</td>
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #f2f2c8; width: 150px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#MarkerRemove">Marker Remove</a></p>
|
||||
</td>
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ede4e4; width: 124px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Undefined">Undefined</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ccffff; width: 132px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Pattern">Pattern</a></p>
|
||||
</td>
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #f2f2c8; width: 150px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#MarkerPattern">Marker Pattern</a></p>
|
||||
</td>
|
||||
<td rowspan="12" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; width: 124px;"><p class="rvps5"><span class="rvts65"><br/></span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ccffff; width: 132px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Clear">Clear</a></p>
|
||||
</td>
|
||||
<td rowspan="3" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ffffff; width: 150px;"><p class="rvps1"><br/></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ccffff; width: 132px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Cut">Cut</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="middle">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ccffff; width: 132px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Paste">Paste</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td colspan="2" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #d3f8d6; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#PasteInsert">PasteInsert</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td colspan="2" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #d3f8d6; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Clone">Clone</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td colspan="2" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #d3f8d6; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Insert">Insert</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td colspan="2" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #d3f8d6; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#InsertNum">Insert#</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td colspan="2" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #d3f8d6; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Delete">Delete</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td colspan="2" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #d3f8d6; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Truncate">Truncate</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ccffff; width: 132px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Record">Record</a></p>
|
||||
</td>
|
||||
<td rowspan="2" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; width: 150px; height: 10px;"><p class="rvps5"><span class="rvts65"><br/></span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ccffff; width: 132px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Import">Import</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td colspan="2" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #d3f8d6; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Branch">Branch</a></p>
|
||||
</td>
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #ede4e4; width: 124px;"><p class="rvps5"><a class="rvts67" href="Operations.html#Bookmark">Bookmark</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td rowspan="8" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; width: 132px; height: 10px;"><p class="rvps5"><span class="rvts65"><br/></span></p>
|
||||
</td>
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #f2f2c8; width: 150px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#MarkerBranch">Marker Branch</a></p>
|
||||
</td>
|
||||
<td rowspan="9" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; width: 124px;"><p class="rvps5"><span class="rvts6"><br/></span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #f2f2c8; width: 150px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#MarkerRename">Marker Rename</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #f2f2c8; width: 150px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#MarkerDrag">Marker Drag</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #f2f2c8; width: 150px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#MarkerSwap">Marker Swap</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #f2f2c8; width: 150px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#MarkerShift">Marker Shift</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #f2f2c8; width: 150px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#LUAMarkerSet">LUA Marker Set</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #f2f2c8; width: 150px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#LUAMarkerRemove">LUA Marker Remove</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #f2f2c8; width: 150px; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#LUAMarkerRename">LUA Marker Rename</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td colspan="2" valign="middle" style="border-color : #ffffff #000000 #000000 #ffffff; border-style: solid; background-color: #d3f8d6; height: 10px;"><p class="rvps5"><a class="rvts67" href="Operations.html#LUAChange">LUA Change</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="Initialization"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Initialization</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: other</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created automatically when new History Log is created.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">when creating a new project</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when loading a compactly saved project that has no History Log</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:24:53 Initialization</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">very rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after zeroth frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="Undefined"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Undefined</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: other</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Undefined modification. </span><span class="rvts21">The record should not appear in TAS Editor 1.0.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">never</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="Set"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Set</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when one or more buttonpresses appear in one or several frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts21">click on an empty Input cell of the Piano Roll</span></li>
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts21">draw a new stroke by dragging mouse after the click on an empty Input cell</span></li>
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts30">Shift</span><span class="rvts21"> + click on an empty Input cell</span></li>
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts21">select some frames and then click on a button symbol in the Header of the Piano Roll</span></li>
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts21">select some frames and then press a key assigned to a virtual gamepad button</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:25:18 Set 15-21</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">very often</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input was changed.</span></p>
|
||||
<p class="rvps11"><span class="rvts22"><br/></span></p>
|
||||
<p class="rvps11"><a name="Unset"></a>
|
||||
<span class="rvts22"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Unset</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when one or more buttonpresses disappear from one or several frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts21">click on an occupied Input cell of the Piano Roll</span></li>
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts21">erase some Input by dragging mouse after the click on an occupied Input cell</span></li>
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts30">Shift</span><span class="rvts21"> + click on an occupied Input cell</span></li>
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts21">select some frames and then click on a button symbol in the Header of the Piano Roll</span></li>
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts21">select some frames and then press a key assigned to a virtual gamepad button</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:25:22 Unset 21</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">very often</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Pattern"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Pattern</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when a sequence of buttonpresses changes to currently chosen pattern.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The name of the pattern is added to the text of the record.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps24" style="text-indent: 30px"><span class="rvts30">Alt</span><span class="rvts21"> + click on an Input cell of the Piano Roll</span></li>
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts30">Alt</span><span class="rvts21"> + dragging mouse after the click on an Input cell</span></li>
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then </span><span class="rvts30">Alt</span><span class="rvts21"> + click on a button symbol in the Header of the Piano Roll</span></li>
|
||||
<li class="rvps27" style="text-indent: 30px"><span class="rvts21">select some frames and then </span><span class="rvts30">Alt</span><span class="rvts21"> + press a key assigned to a virtual gamepad button</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:25:40 Pattern 21-30 Alternating (1010...)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Clear"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Clear</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when all buttonpresses disappear from one or several frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then press </span><span class="rvts30">Delete</span></li>
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then choose </span><span class="rvts25">Edit -> Clear</span><span class="rvts21"> in TAS Editor menu</span></li>
|
||||
<li class="rvps10"><span class="rvts21">right-click on a selected frame number and choose </span><span class="rvts25">Clear</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:26:51 Clear 15-20</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">moderately</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Cut"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Cut</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when all buttonpresses disappear from one or several frames, caused by "Cut" operation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This is identical to </span><a class="rvts27" href="Operations.html#Clear">Clear</a><span class="rvts21"> operation, except that buttonpresses are copied to the Clipboard before clearing.</span></p>
|
||||
<p class="rvps10"><span class="rvts34">Note:</span><span class="rvts21"> although you can undo this operation, the Clipboard contents won't revert.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then press </span><span class="rvts30">Ctrl + X</span></li>
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then choose </span><span class="rvts25">Edit -> Cut</span><span class="rvts21"> in TAS Editor menu</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:27:05 Cut 21-23</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Paste"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Paste</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when a Clipboard data is pasted into the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Depending on the "Superimpose" checkbox the old Input on those frames is either erased or combined with the new Input. The Piano Roll Header briefly flashes symbols of those buttons that were added in the Paste process.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then press </span><span class="rvts30">Ctrl + V</span></li>
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then choose </span><span class="rvts25">Edit -> Paste</span><span class="rvts21"> in TAS Editor menu</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:27:11 Paste 21</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">moderately/rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="PasteInsert"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">PasteInsert</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change, Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when a Clipboard data is inserted into the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Old Input and Markers are shifted down to make place for the Input from Clipboard.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then press </span><span class="rvts30">Ctrl + Shift + V</span></li>
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then choose </span><span class="rvts25">Edit -> PasteInsert</span><span class="rvts21"> in TAS Editor menu</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:27:16 PasteInsert 21</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input or Lag was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Clone"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Clone</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change, Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when copies of one or several frames are inserted into the movie, shifting the following Input and Markers down.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then press </span><span class="rvts30">Ctrl + Insert</span></li>
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then choose </span><span class="rvts25">Edit -> Clone</span><span class="rvts21"> in TAS Editor menu</span></li>
|
||||
<li class="rvps10"><span class="rvts21">right-click on a selected frame number and choose </span><span class="rvts25">Clone</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:27:34 Clone 23</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">often</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input or Lag was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Insert"></a>
|
||||
<span class="rvts63"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Insert</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change, Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when one or several blank frames are inserted into the movie, shifting the following Input and Markers down.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then press </span><span class="rvts30">Ctrl + Shift + Insert</span></li>
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then choose </span><span class="rvts25">Edit -> Insert</span><span class="rvts21"> in TAS Editor menu</span></li>
|
||||
<li class="rvps10"><span class="rvts21">right-click on a selected frame number and choose </span><span class="rvts25">Insert</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:25:58 Insert 21</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">moderately</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input or Lag was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="InsertNum"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Insert#</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change, Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when specific number of blank frames is inserted into the movie, shifting the following Input and Markers down.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If there's Selection in the Piano Roll, this operation inserts frames before the Selection, otherwise it inserts frames before Playback cursor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The number of inserted frames is added to the text of the record.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">press </span><span class="rvts30">Insert</span><span class="rvts21"> and enter the number of frames to insert</span></li>
|
||||
<li class="rvps10"><span class="rvts21">choose </span><span class="rvts25">Edit -> Insert # of Frames</span><span class="rvts21"> in TAS Editor menu</span></li>
|
||||
<li class="rvps10"><span class="rvts21">right-click on a selected frame number and choose </span><span class="rvts25">Insert # of Frames</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:26:09 Insert#4 29</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input or Lag was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Delete"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Delete</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change, Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when one or several frames are deleted from the movie, shifting the following Input and Markers up.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then press </span><span class="rvts30">Ctrl + Delete</span></li>
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then choose </span><span class="rvts25">Edit -> Delete</span><span class="rvts21"> in TAS Editor menu</span></li>
|
||||
<li class="rvps10"><span class="rvts21">right-click on a selected frame number and choose </span><span class="rvts25">Delete</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:26:12 Delete 33</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">often</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input or Lag was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Truncate"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Truncate</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change, Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when the tail of the movie is truncated, deleting all Input (and Markers) starting from either the Selection cursor or Playback cursor (if there's no Selection in Piano Roll).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">choose </span><span class="rvts25">Edit -> Truncate movie</span><span class="rvts21"> in TAS Editor menu</span></li>
|
||||
<li class="rvps10"><span class="rvts21">right-click on a selected frame number and choose </span><span class="rvts25">Truncate movie</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:26:28 Truncate 42</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">very rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the frame of movie truncation.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Record"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Record</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when emulator is recording Input using virtual gamepads.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The new Input appears in the Playback cursor frame. Depending on the "Superimpose" checkbox the old Input the frame is either erased or combined with the new Input. The Piano Roll Header briefly flashes symbols of those buttons that were added in the Recording process.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">IDs of gamepads whose Input was changed are added to the text of the record.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">switch Recording mode on, unpause the emulator and press any keys assigned to buttons of virtual pads</span></li>
|
||||
<li class="rvps10"><span class="rvts21">switch Recording mode on, unpause the emulator and do not press any keys assigned to buttons of virtual pads</span></li>
|
||||
<li class="rvps10"><span class="rvts21">when emulator is paused, switch Recording mode on, hold any keys assigned to buttons of virtual pads and press </span><span class="rvts26">Frame Advance</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:28:01 Record(1P) 18-24</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">moderately</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the Playback cursor position.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Import"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Import</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when an Input of another FM2/FM3 movie is imported to current project.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Current movie Input is substituted by the Input of imported file. Markers are not changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The filename of the Input source is added to the text of the record. </span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">choose </span><span class="rvts25">File -> Import Input</span><span class="rvts21"> in TAS Editor menu and open the file which should be the source of Input</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:28:53 Import Battletoads-WIP1.fm2</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">very rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Bookmark"></a>
|
||||
<span class="rvts64"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Bookmark0</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Bookmark1</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Bookmark2</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Bookmark3</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Bookmark4</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Bookmark5</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Bookmark6</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Bookmark7</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Bookmark8</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Bookmark9</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: other</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when the data of a Bookmark slot is changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Re-saving a Bookmark into the same slot only works when the new Bookmark data differs from the data stored in the slot, e.g. when the Bookmark is set to another frame or when current movie Input is different from the Input stored in the slot.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When a Bookmark is successfully saved, its Branch becomes "current branch of the movie", and emulator shows the "Branch # saved." message.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">press a "Save state" hotkey: </span><span class="rvts25">Shift + </span><span class="rvts21">key in the row from </span><span class="rvts26">F1</span><span class="rvts21"> to </span><span class="rvts26">F10</span></li>
|
||||
<li class="rvps10"><span class="rvts21">right-click on the Bookmarks List</span></li>
|
||||
<li class="rvps10"><span class="rvts21">right-click on a Bookmark icon in the Branches Tree</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:28:53 Bookmark1 10</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">often</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="Branch"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Branch0 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Branch1 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Branch2 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Branch3 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Branch4 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Branch5 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Branch6 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Branch7 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Branch8 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Branch9 to</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change, Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when current movie is substituted with the data of a Bookmark slot. Both Input and Markers are substituted.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The time of the Bookmark creation is added to the text of the record, because the movie is in fact being reverted to its state at that time.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When a Bookmark is successfully loaded, its Branch becomes "current branch of the movie", and emulator shows the "Branch # loaded." message.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">press a "Load state" hotkey: </span><span class="rvts25">Shift + </span><span class="rvts21">key in the row from </span><span class="rvts26">F1</span><span class="rvts21"> to </span><span class="rvts26">F10</span></li>
|
||||
<li class="rvps10"><span class="rvts21">click on the right half of the Bookmarks List</span></li>
|
||||
<li class="rvps10"><span class="rvts21">double-click on the a Bookmark icon in the Branches Tree</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:29:02 Branch1 to 20:28:15</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">moderately</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input or Lag was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="MarkerBranch"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Branch0 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Branch1 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Branch2 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Branch3 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Branch4 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Branch5 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Branch6 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Branch7 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Branch8 to</span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Branch9 to</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when current movie is substituted with the data of a Bookmark slot, but new Input was identical to old Input, and only Markers were different.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">press a "Load state" hotkey: </span><span class="rvts25">Shift + </span><span class="rvts21">key in the row from </span><span class="rvts26">F1</span><span class="rvts21"> to </span><span class="rvts26">F10</span></li>
|
||||
<li class="rvps10"><span class="rvts21">click on the right half of the Bookmarks List</span></li>
|
||||
<li class="rvps10"><span class="rvts21">double-click on the a Bookmark icon in the Branches Tree</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:29:33 Marker Branch1 to 20:28:15</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">very rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="MarkerSet"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Set</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when a Marker appears on one or several frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">double-click on a non-marked frame number in the Piano Roll</span></li>
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then click on the "Frame#" in the Piano Roll Header (granted that some selected frames don't have Markers)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">right-click on a selected frame number and choose </span><span class="rvts25">Set Markers</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:29:47 Marker Set 15-18</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">often</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="MarkerRemove"></a>
|
||||
<span class="rvts64"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Remove</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when Markers disappear from one or several frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">double-click on a marked frame number in the Piano Roll, drag the Marker outside the Piano Roll and release it</span></li>
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then click on the "Frame#" in the Piano Roll Header (granted that all selected frames have Markers)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">right-click on a selected frame number and choose </span><span class="rvts25">Remove Markers</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:29:52 Marker Remove 16-18</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">moderately</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="MarkerPattern"></a>
|
||||
<span class="rvts64"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Pattern</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when a sequence of Markers is created using currently chosen pattern.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The name of the pattern is added to the text of the record.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">select some frames and then </span><span class="rvts30">Alt</span><span class="rvts21"> + click on the "Frame#" in the Piano Roll Header</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:30:11 Marker Pattern 20-30 One Quarter (10001000...)</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">very rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="MarkerRename"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Rename</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when Note of a Marker is changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The new text of the Note is added to the text of the record.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">type the text of the Note right after creating the new Marker by double-click</span></li>
|
||||
<li class="rvps10"><span class="rvts21">click on the upper edit field, erase old text and type new, then press </span><span class="rvts25">Enter</span><span class="rvts21"> or click anywhere outside the edit field</span></li>
|
||||
<li class="rvps10"><span class="rvts21">click on the lower edit field, erase old text and type new, then press </span><span class="rvts25">Enter</span><span class="rvts21"> or click anywhere outside the edit field</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:31:01 Marker Rename 20 Testing...</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">often</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="MarkerDrag"></a>
|
||||
<span class="rvts64"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Drag</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when moving a Marker from one frame to another.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The old and new frame number, as well as the Note of the Marker is added to the text of the record.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">double-click on a marked frame number in the Piano Roll, drag the Marker to a non-marked frame number and release</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:31:08 Marker Drag 20=>15 Testing...</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">moderately</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="MarkerSwap"></a>
|
||||
<span class="rvts64"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Swap</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when two Markers switch places.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The old and new frame number of the dragged Marker, as well as its Note is added to the text of the record.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">double-click on a marked frame number in the Piano Roll, drag the Marker to another marked frame number and release</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:31:14 Marker Swap 24<=>28</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="MarkerShift"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">Marker Shift</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when an operation didn't change Input but still shifted some Markers up or down.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">insert blank frame near the end of the movie (granted that there's no buttonpresses after the frame, yet there is at least one Marker)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">clone a blank frame near the end of the movie (granted that there's no buttonpresses after the frame, yet there is at least one Marker)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">copy a blank frame to the Clipboard and </span><span class="rvts25">PasteInsert</span><span class="rvts21"> it somewhere near the end of the movie (granted that there's no buttonpresses, yet there is at least one Marker)</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:31:44 Marker Shift 21</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">very rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="LUAMarkerSet"></a>
|
||||
<span class="rvts64"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">LUA Marker Set</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when a Marker appears on a frame as a result of using </span><span class="rvts20">taseditor.setmarker()</span><span class="rvts21"> function.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">run a Lua script with a </span><span class="rvts20">taseditor.setmarker(framenum)</span><span class="rvts21"> line</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:35:14 LUA Marker Set 0</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="LUAMarkerRemove"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">LUA Marker Remove</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when a Marker disappears from one frame as a result of using </span><span class="rvts20">taseditor.removemarker()</span><span class="rvts21"> function.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">run a Lua script with a </span><span class="rvts20">taseditor.removemarker(framenum)</span><span class="rvts21"> line</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:36:12 LUA Marker Remove 0</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="LUAMarkerRename"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">LUA Marker Rename</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when Note of a Marker is changed as a result of using </span><span class="rvts20">taseditor.setnote()</span><span class="rvts21"> function.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The new text of the Note is added to the text of the record.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">run a Lua script with a </span><span class="rvts20">taseditor.setnote(markernum, newtext)</span><span class="rvts21"> line</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:37:03 LUA Marker Rename 0 Hello from Lua!</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is not truncated.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><a name="LUAChange"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps11"><span class="rvts22">LUA Change</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Category: Input change, Markers change</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The record is created when Input or Markers were changed as a result of using </span><span class="rvts20">taseditor.applyinputchanges()</span><span class="rvts21"> function.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instead of the word "Change" the operation can be named with any other text provided by the parameter of </span><span class="rvts20">taseditor.applyinputchanges()</span><span class="rvts21"> function.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instances:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">run a Lua script containing such lines as </span><span class="rvts20">taseditor.submitinputchange(frame, joypad, input)</span><span class="rvts21"> and </span><span class="rvts20">taseditor.applyinputchanges(name)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">run a Lua script containing such lines as </span><span class="rvts20">taseditor.submitinsertframes(frame, number)</span><span class="rvts21"> or </span><span class="rvts20">taseditor.submitdeleteframes(frame, number)</span><span class="rvts21"> and </span><span class="rvts20">taseditor.applyinputchanges(name)</span></li>
|
||||
</ul>
|
||||
<p class="rvps22"><span class="rvts39">Example:</span></p>
|
||||
<p class="rvps22"><span class="rvts39">20:39:56 LUA Corruptor 10</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Used: </span><span class="rvts37">rarely</span></p>
|
||||
<p class="rvps10"><span class="rvts64">Greenzone is truncated after the first frame where Input or Lag was changed.</span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts64"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour/create-ebooks-for-amazon-kindle">Free Kindle producer</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,155 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>2.1. Piano Roll</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("PianoRoll");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>2.1. Piano Roll</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="BeginnersGuide.html">Beginner's Guide</a> ›› <a href="ProgramInterface.html">2. Program Interface</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="ProgramInterface.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="ProgramInterface.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="Toolbox.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Piano Roll</span></p>
|
||||
<p class="rvps5"><span class="rvts36"><br/></span></p>
|
||||
<p class="rvps5"><img alt="" style="padding : 1px;" src="lib/taseditor-smb.png"/></p>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Taseditor's workspace is similar to the interface used in music-sequencing programs. Piano Roll is a table containing the most necessary data about the edited project. Users can both observe that data and edit it by mouse clicks on various cells of the table.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you just opened the Taseditor window you will most likely see an empty project that contains only the starting (zeroth) frame of the movie. So, before you begin any experiments, you should temporarily unpause the emulator to let the movie reach at least the title screen of the game, the point where players can already affect the game with buttons Input. By default the hotkey to pause/unpause emulator is the </span><span class="rvts26">Pause</span><span class="rvts21"> key on the keyboard, but in Taseditor you can use </span><span class="rvts34">middle mouse button</span><span class="rvts21"> (the wheel) instead. Try watching the running game for a couple of seconds, then again press the </span><span class="rvts26">Pause</span><span class="rvts21"> key or make the middle-click (anywhere) to stop emulation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">During the emulation, Piano Roll contents become filled with the information about the processed frames. Each line in the Piano Roll list is responsible for a single frame. The index number of the frame is shown at the beginning of the line, the numeration goes top-down. When the window size is not enough to display all the frames, the list gets a vertical scrollbar.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">By the color of each line you can tell the following data about the corresponding frame:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Pale (almost white) lines stand for frames that are outside of the Greenzone. This means that the emulator haven't processed these frames yet and thus it knows nothing about them. For example, if you import some finished movie into Taseditor, at first Piano Roll will display all frames in whitish colors, before running through them. In the above picture such lines begin from the frame 21, because the Greenzone ends at the frame 20.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Green and red lines mean that those frames are contained in the Greenzone, the emulator has already played back that part of the movie, and you've already seen on the FCEUX screen what happens with the game during these frames. Lag frames are marked red, otherwise there's no difference between red and green lines.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">The light-blue line (frame 18 on the picture) shows the currently emulated frame. Events of the frame are displayed on the FCEUX screen at the moment. This is always a sole line. In this Manual we will call it the </span><span class="rvts25">Playback cursor</span><span class="rvts21">. When emulator is paused, the Playback cursor stays at the same frame, and while emulation the cursor runs down, leaving the trail of green and red Greenzone frames behind. You can put the Playback cursor at any frame of the movie to see the game events of that frame. To do that, click the very left column of the Piano Roll (the column where the blue triangle pointer travels down) in the line you wish to observe – the blue pointer will jump to the chosen line along with the Playback cursor, and the FCEUX window will update accordingly, showing the in-game state of the frame. Now, if you don't let go of the left mouse button, you can drag the light-blue cursor up and down.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">The dark-blue line highlights the selected movie segment. The actual color may differ depending on your Windows settings (the Visual theme chosen). Piano Roll lines become selected as you left-click on them. </span><span class="rvts21">In the above picture the</span><span class="rvts21"> single frame 27 is selected, but you can select any number of frames. To select a range of frames, click on the number of the first frame and stretch the selection by dragging the mouse up or down. </span><span class="rvts34">Note:</span><span class="rvts21"> Piano Roll lines will also be selected by clicking on the Input (i.e. almost any other column), but the column with frame numbers is specifically dedicated to working with the Selection. In this Manual we will call all dark-blue lines the </span><span class="rvts25">Selection</span><span class="rvts21">, and a single selected line will be called the </span><span class="rvts25">Selection cursor</span><span class="rvts21">. Unlike the Playback cursor, the Selection cursor isn't tied to the game state. To totally remove the Selection you could right-click the number of a selected frame and choose "Deselect" in the context menu, but usually there's no need to remove the Selection left from previous operations with the movie, because the next operation will automatically bring the Selection cursor to a new place.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">A purple line appears for a brief moment when you use the Undo feature. This way the program shows you the exact place of the reverted changes. A huge convenience of Taseditor is that absolutely any change can be reverted with the standard key combination </span><span class="rvts30">Ctrl + Z</span><span class="rvts21">, so don't be afraid to experiment.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">To start adding and changing the movie Input, click cells of those columns to the right of the column with frame numbers. If you click an empty cell, a symbol corresponding to the real joypad button will appear there.</span></p>
|
||||
<div class="rvps21"><table width="600" border="0" cellpadding="6" cellspacing="0" style="border-width: 0px;">
|
||||
<tr valign="middle">
|
||||
<td style="width: 586px; height: 14px;"><p class="rvps14"><span class="rvts25">A</span><span class="rvts21"> – </span><span class="rvts29">A </span><span class="rvts21">button</span></p>
|
||||
<p class="rvps14"><span class="rvts25">B</span><span class="rvts21"> – </span><span class="rvts29">B </span><span class="rvts21">button</span></p>
|
||||
<p class="rvps14"><span class="rvts25">S</span><span class="rvts21"> – </span><span class="rvts29">Select </span><span class="rvts21">button</span></p>
|
||||
<p class="rvps14"><span class="rvts25">T</span><span class="rvts21"> – </span><span class="rvts29">Start </span><span class="rvts21">button</span></p>
|
||||
<p class="rvps14"><span class="rvts25">U</span><span class="rvts21"> – D-pad </span><span class="rvts29">Up</span></p>
|
||||
<p class="rvps14"><span class="rvts25">D</span><span class="rvts21"> – </span><span class="rvts21">D-pad</span><span class="rvts21"> </span><span class="rvts29">Down</span></p>
|
||||
<p class="rvps14"><span class="rvts25">L</span><span class="rvts21"> – </span><span class="rvts21">D-pad</span><span class="rvts21"> </span><span class="rvts29">Left</span></p>
|
||||
<p class="rvps14"><span class="rvts25">R</span><span class="rvts21"> – </span><span class="rvts21">D-pad</span><span class="rvts21"> </span><span class="rvts29">Right</span></p>
|
||||
</td>
|
||||
<td style="width: 258px; height: 178px;"><p class="rvps5"><img alt="" style="padding : 1px;" src="lib/NES-controller.png"/></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21">If you click on an occupied cell, it will become cleared, and the corresponding button will be considered released on that frame. There is no other button states except these two: either pressed or released.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">At first it might not be very trivial to correlate these 8 symbols with plastic buttons of a real joypad, but try pressing the first player input keys (set in your emulator) while you are in Taseditor. As you tap the buttons, the corresponding letters will flash in the Piano Roll Header, and you can easily associate the columns with buttons.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When working in Taseditor, the most of time is spent on that very process of setting and removing buttons at different frames. This way you form the </span><span class="rvts34">sequence of button states</span><span class="rvts21">, which is then fed to the game and reflected by actions of the game character(s). For example, if you put the letter "A" to a chosen Piano Roll cell at the middle of Super Mario Bros gameplay, Mario will perform a low jump, because a short </span><span class="rvts29">A</span><span class="rvts21"> button press occurred in the movie. And if you set several "A" symbols in a row (vertically), Mario will do a high jump, because </span><span class="rvts29">A</span><span class="rvts21"> was held longer.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Every time you change the Input above the line with the Playback cursor, the light-blue cursor steps back (up in the Piano Roll) also clearing some part of the Greenzone. This happens because the change of Input leads to a change in the game events, so the game data memorized inside the Greenzone becomes irrelevant. Thus after you change Input you need to replay some frames of the movie again – either by unpausing the emulator, or by manually dragging the Playback cursor to the frame of interest – and you will see results of the latest Input changes on FCEUX screen (and also restore a part of the Greenzone).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Besides, you can hold the </span><span class="rvts25">right mouse button</span><span class="rvts21"> and roll the mouse wheel down to move the Playback cursor to the needed frame manually. Wheel-based navigation is the most responsive way to observe a little segment of the movie. You may use a single hand, and the mouse pointer may be anywhere, e.g. it may be left over the edited cells. Try this method, it's a very effective way to rewind back and forth. Just hold the right mouse button with one finger and roll the wheel with another finger while looking at the FCEUX window.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">In addition to single cell clicks, you can also change button states in many frames at once. For instance, if you want the </span><span class="rvts29">R</span><span class="rvts21"> button (</span><span class="rvts29">Right</span><span class="rvts21">) to be pressed for 20 straight frames, you don't have to click all 20 cells. You can just click on one of them, hold the left mouse button and move the mouse cursor up or down – it will leave a trail of symbols, thus you will draw a vertical row of buttonpresses. Similarly, you can quickly erase a row of symbols by clicking the first one and moving the eraser up or down. As you may notice, erasing starts when you click an occupied cell, and drawing starts when you click an empty cell.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Moreover, you can hold the </span><span class="rvts30">Shift</span><span class="rvts21"> key before clicking on the Input to spread the effect of the click across all frames between the point of click and the Selection cursor. For example, you can set "R" in the first frame, then scroll the Piano Roll to the end, hold </span><span class="rvts30">Shift</span><span class="rvts21"> and set "R" in the last frame – the </span><span class="rvts29">R</span><span class="rvts21"> button press will appear in all frames.</span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/piano-roll-header-l.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">There's one more way to mass set or mass remove buttonpresses. First, select several frames, for example, the 5th, the 10th and the 20th (to do it you have to hold </span><span class="rvts30">Ctrl</span><span class="rvts21"> while clicking on numbers </span><span class="rvts21">0000005, 0000010 and 0000020)</span><span class="rvts21">. Then click on the "L" letter in the Piano Roll Header. If the selected frames didn't have the </span><span class="rvts29">Left</span><span class="rvts21"> button symbols, they will get it. And if all of the frames had the </span><span class="rvts29">Left</span><span class="rvts21"> button already pressed, the click will clear it.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Later you will find a few other ways to edit the Input, but these were the main ones. At first it might look unnatural to draw buttonpresses with the mouse instead of simulating them using keyboard keys. But this discomfort feeling will disappear soon after you devote a few some days to Taseditor.</span></p>
|
||||
<p class="rvps10"><a name="HotChanges"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When drawing the Input you've probably noticed that previously drawn letters have different color, and as you add new buttonpresses old letters change their color from orange to violet and blue, eventually becoming standard black. This is one of experimental features of Taseditor, called "Hot Changes". It was invented to unobtrusively increase TASer's awareness about recent changes. Every time you modify the Input, the latest buttonpresses receive the hottest color (bright orange), and all the previous edits cool down by one level, becoming less bright.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Because of the coloring, even a cursory glance on the Piano Roll is enough to get the idea which buttonpresses were added just recently and which were set long ago. Also, you can see which of them were recently removed (they are replaced with a dash).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you don't like this feature, you can disable it, but within this Guide we'll imply that you have the "Hot Changes" enabled.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The narrow column to the left from the column with frame numbers is not just for dragging the Playback cursor. It also displays various informational icons. The blue arrow pointer always points to the frame where the Playback cursor is now. The green arrow pointer shows where the Playback cursor was before the Input above it has changed. And the digit cards in this column indicate Bookmarks, they will be described later.</span></p>
|
||||
<p class="rvps10"><a name="markers"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The yellow marks on the numbers of some frames (frames 12 and 22 on the above picture) are called </span><span class="rvts25">Markers</span><span class="rvts21">. Besides the yellow color, they can be recognized by the wide font of the frame number.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Markers are meant to facilitate the movie navigation and improve TASer's self-organization. You decide how to use them on your own: whether to put them at the beginning of each level or to mark every jump, shot or any in-game event. Essentially, by setting Markers you logically break your movie down into sections, and then you can cross the movie not just by jumping from frame to frame, but from section to section. This allows you to interpret the movie on a higher level of abstraction.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Such structuring helps to keep a precise image of the entire movie in mind. That kind of an image exists in each TASer's mind, but usually it's rather fuzzy – we remember a rough sequence of the evens, but omit the details (because most of time they are insignificant). When TASer turns emulator off, the image starts to gradually become vague and forgotten. Thus at the next session one needs to re-watch his own movie from the beginning in order to refresh memories, figure key events, arrange priorities and, in general, mentally prepare for resumption of TASing. Sometimes this is needed even more often – depending on the complexity of the TAS. That's why it's recommended to consolidate that image by setting real Markers, not just in your mind but in actual movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A Marker can be set at any frame. Unlike the Input, Markers don't affect the game events. There are several ways to set Markers:</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Example 1. </span><span class="rvts21">Double-click on a frame number. If there was no Marker at this frame, it will appear there. If the Marker already exists, you can drag it while the left button is still held after the double-click. This way you can move any Marker to a different frame or simply dump it outside the Piano Roll, thus removing it from the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Example 2. </span><span class="rvts21">Select one or several frames by clicking the frame number(s), then click the "Frame#" label in the Piano Roll Header. If some of the selected frames didn't have Markers, they will all become marked. If all of them were already marked, all the Markers will be removed. This way you may mass set or mass remove Markers the same way as Input.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Example 3. </span><span class="rvts21">Select one or several frames in the Piano Roll, right-click on any of the selected frame numbers and choose "Set Markers" or "Remove Markers" in the context menu. This is the slowest way, so the other two are more preferred.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Any Marker operation may be undone (</span><span class="rvts30">Ctrl + Z</span><span class="rvts21">) anytime, just like any Input operation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Markers are automatically numbered by the order they are located in the movie – top-down from first to last. In the upper left corner of TAS Editor window you can see the number of the Marker that is located just above the Playback cursor in the movie (light-blue "Marker </span><span class="rvts37">#</span><span class="rvts21">" label). This label both informs you and serves as a button for auto-scrolling. E.g. if you left the Playback cursor in one part of the movie and scrolled the Piano Roll far from that point, you can immediately return to the light-blue cursor anytime by clicking the "Marker" label (or tapping the </span><span class="rvts30">Shift</span><span class="rvts21"> key twice). You are definitely going to need this feature when editing large movies.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">A similar button can be found in the lower left corner of Taseditor. The "Marker </span><span class="rvts37">#</span><span class="rvts21">" label of a dark blue color (the same color as the Selection cursor) displays the number of the Marker located just above the Selection. If you click this label, the Piano Roll will automatically jump to Selection. This button is going to be used as often as the upper one. Its keyboard alternative is tapping the </span><span class="rvts30">Ctrl</span><span class="rvts21"> key twice.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It should be easy to remember that the </span><span class="rvts30">Shift</span><span class="rvts21"> key is almost always used to control the Playback cursor, while the </span><span class="rvts30">Ctrl</span><span class="rvts21"> key is to control the Selection cursor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If both Playback and Selection cursors are below the same Marker, the numbers in both corners will obviously be the same.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Markers can do more than just divide the movie into logical parts. They may also contain text records (comments and work notes). The Marker </span><span class="rvts25">Note</span><span class="rvts21"> is displayed right near its number. The upper edit field contains the Note of the Marker above the Playback Cursor, and the lower field shows the Note of the Marker above the Selection cursor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">By default, every new Marker contains an empty Note. When you create a new Marker by double-click, the lower edit field automatically becomes active, because the Selection cursor points to the just marked frame. So you may quickly type any text for the Note of that Marker and then resume your work with the movie. Text changes are saved automatically.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can edit an old Marker Note in any of the following ways:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Put the Selection cursor to that frame and click the lower edit field to activate it.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Simply double-click on the Marker, and the lower edit field will activate automatically.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Put the Playback cursor to that frame and click the upper edit field to activate it.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21">When typing a Note, press </span><span class="rvts25">Enter</span><span class="rvts21"> or just click any unrelated element of TAS Editor window to finish editing. If you changed your mind, press </span><span class="rvts25">Esc</span><span class="rvts21"> to cancel the editing. All the controls when editing Notes are listed in the </span><a class="rvts35" href="Controls.html#notes">Reference</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It is recommended to enter Notes when creating Markers, so you won't forget why the Marker was set there. This won't take much time if you set Markers by double-clicks and type laconic messages at the same second.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps17"><a class="rvts23" href="Toolbox.html">Proceed to the Toolbox description</a></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com">Full-featured Documentation generator</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,292 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>5. Program customization</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("ProgramCustomization");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>5. Program customization</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="BeginnersGuide.html">Beginner's Guide</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="BeginnersGuide.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="SemiautomaticTASing.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="AdvancedFeatures.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Program customization</span></p>
|
||||
<p class="rvps2"><span class="rvts36"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts36"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Certain useful features of Taseditor are disabled by default, because using them requires understanding of their working principles. This chapter describes all Taseditor options and settings, as well as FCEUX settings that affect your work in Taseditor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Settings are kept in the </span><span class="rvts37">fceux.cfg</span><span class="rvts21"> file in emulator's main folder. If you delete this file, all settings will reset to default values when you launch FCEUX.</span></p>
|
||||
<div class="rvps10"><table width="100%" border="0" cellpadding="4" cellspacing="0" style="border-width: 0px;">
|
||||
<tr valign="top">
|
||||
<td style="width: 847px;"><p class="rvps10"><span class="rvts21">First, if you've already read </span><a class="rvts27" href="ProgramInterface.html">chapter 2</a><span class="rvts21"> and understood the purpose of all GUI elements, you should disable pop-up tooltips (intended for newbies only). Go to "Help" submenu of Taseditor main menu and uncheck the option "Enable Tooltips". Before doing it you may want to actually read all the tooltips by pointing the mouse cursor at different elements of TAS Editor window, and thus consolidate your knowledge of the GUI.</span></p>
|
||||
</td>
|
||||
<td valign="top" style="width: 148px;"><p class="rvps19"><img alt="" style="padding : 1px;" src="lib/help-menu.png"/></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21">Now open the "View" submenu.</span></p>
|
||||
<p class="rvps10"><img align="left" alt="" style="padding : 6px;" src="lib/view-menu.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">The "Find Note window" brings up the window dedicated to searching text in Marker Notes. This function is useful when you're documenting your movie with Notes. It's described in the next chapter.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Then there are several checkboxes allowing to customize the program interface. To try the customization possibilities, create a test project right now (just open Taseditor) and experiment with it.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="DisplayBranchScreenshots"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">View -> Display Branch Screenshots</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Displays pop-up screenshots when you point mouse cursor over Bookmarks. The screenshot helps you to recall movie events saved to the Bookmark, which simplifies searching for the needed branch of the movie, as you don't have to load the Bookmark to have an idea on its contents. This way you can also quickly compare results of several alternative approaches.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This option is enabled by default. If disabled, no screenshots will pop up on mouse hover.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's recommended to have it enabled, unless you're annoyed with pop-up pictures, partially obstructing the view on Piano Roll.</span></p>
|
||||
<p class="rvps10"><a name="DisplayBranchDescriptions"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">View -> Display Branch Descriptions</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Displays pop-up descriptions </span><span class="rvts21">when you point mouse cursor over Bookmarks.</span><span class="rvts21"> The text, as well as the screenshot, gives you additional information about the contents of the Bookmark, helping to decide whether this branch should be loaded or not.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The description text is taken from the Marker above the frame of that Bookmark. The Marker itself may be actually removed from the working movie long ago, but if the Bookmark was created while the Marked existed, then this Marker still exists in the branch of this Bookmark. And if you load this Bookmark, the Marker will reappear on its place.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">So, when trying alternative strategies of playing through a large segment (e.g. whole level of the game), before saving every approach to a separate branch, you can make a name for the approach by setting a Marker at the Playback cursor position and typing a text message like "</span><span class="rvts37">here I chose upper way</span><span class="rvts21">". After that, save a Bookmark on that frame. Then you can remove the Marker together with the Input of the old approach and create next approach by applying another strategy of playing current segment. When the new approach if finished and replayed, you can again create a Marker with a Note like "</span><span class="rvts37">here I chose lower way</span><span class="rvts21">" and save all that to another Bookmark. After that you can save the project and, say, close Taseditor. Next day you can easily recall all pros and cons of the two strategies you tried. Each Bookmark will show you the screenshot of the bookmarked frame and the text you wrote for that Bookmark. While it can be hard to distinguish the strategies by screenshots (since both approaches end at the same event of the game), but text descriptions will make them easy to recognize.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This option is enabled by default. </span><span class="rvts21">If disabled, no descriptions will pop up on mouse hover.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's recommended to have it enabled, unless you're annoyed with pop-up text fields.</span></p>
|
||||
<p class="rvps10"><a name="EnableHotChanges"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">View -> Enable Hot Changes</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Switches the Hot Changes feature on and off.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Enabled by default. If disabled, all buttonpress symbols will be displayed in a standard black color. Otherwise, each symbol will have its own level of "hotness", depending on how long ago the corresponding Piano Roll cell was edited. Recently modified buttonpresses are more hot, so they are displayed by more intense shade of red. As the hotness decreases, the symbol colors become darker (more cold) and finally turn into standard black.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps18"><img alt="" style="padding : 1px;" src="lib/hotchanges-colors.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">In total, Taseditor supports 15 shades of hotness + zeroth black color. When you change the state of an Input cell, it receives maximum hotness value (15), and all the previously edited cells cool down by 1. Thereby you only need a quick look at the Piano Roll to get an idea which edits were done just recently and which were done before, or long ago.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Also, with Hot Changes you can see which buttonpresses were recently removed – instead of an empty cell there will be a dash of the corresponding color. The dash also changes its color while cooling down, and after 15 levels it finally disappears.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The same dashes appear when you insert new frames in the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's recommended to </span><span class="rvts21">enable this feature to increase the usability of Taseditor. In theory it should even increase your working speed, because this way you never have to recall which actions you did a minute ago. Of course even without Hot Changes you can always remind the sequence of last actions by reverting History (making several </span><span class="rvts30">Ctrl + Z</span><span class="rvts21"> keypresses) and then returning the movie to normal state again (making as many </span><span class="rvts30">Ctrl + Y</span><span class="rvts21"> keypresses). But in this case you will also truncate the Greenzone. So better just leave the Hot Changes enabled.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The only downside of this feature is that Hot Changes data will be stored in the History Log and in FM3 project file, thus increasing the occupied memory.</span></p>
|
||||
<p class="rvps10"><a name="Followundocontext"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">View -> Follow undo context</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Scrolls the Piano Roll to relevant place every time you make an undo or redo. A purple pointer appears on the modified frame </span><span class="rvts21">for a brief moment</span><span class="rvts21">, thus drawing your attention to the movie changes.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This option is enabled by default. </span><span class="rvts21">If disabled, the Piano Roll won't automatically scroll to the purple pointer.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's recommended to have it enabled, in order</span><span class="rvts21"> to be able to backtrack undos. Usually, right after you revert an operation you want to make another edit on the same frame or nearby, so the autoscrolling is useful.</span></p>
|
||||
<p class="rvps10"><a name="FollowMarkerNotecontext"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">View -> Follow Marker Note context</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Scrolls the Piano Roll to relevant Marker when you start editing its Note.</span><span class="rvts21"> For example, when you click the upper edit field to start editing the Note of the Marker above the Playback cursor, Piano Roll jumps to that Marker, allowing you to see its context (neighbor Markers and Input). And when you click the lower edit field (a Note above the Selection cursor), Piano Roll scrolls to the Marker above the Selection. This way you can observe the surroundings of the relevant Marker while editing its Note.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This option is enabled by default. </span><span class="rvts21">If disabled, the Piano Roll won't automatically scroll to the Markers.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's recommended to have it enabled.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">And the View settings are over. During your future work you likely won't need to change these checkboxes.</span></p>
|
||||
<p class="rvps10"><img align="left" alt="" style="padding : 6px;" src="lib/config-menu.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">Now open the "Config" submenu. Options listed in this menu affect Taseditor workflow more significantly. You may need reconfiguring some of them more than once.</span></p>
|
||||
<p class="rvps10"><a name="SetGreenzonecapacity"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/greenzone-capacity.png"/></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Set Greenzone capacity</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Defines the maximum size of the Greenzone. The Greenzone is used for easier Playback cursor navigation, allowing to instantly return to any frame that was emulated. It needs a lot of computer memory to store emulator's information and disk space for saving FM3 projects.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The more of green and red frames there are in the Piano Roll, the more memory the Greenzone occupies. For most NES games 1 frame costs about 10 kilobytes (compressed data). So, big movie projects may take hundreds of megabytes. It affects the project loading and saving time.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To decrease the amount of needed memory, Taseditor regularly cleans the Greenzone tail, forgetting the info about segments that are too far from from the Playback cursor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This cleaning doesn't mean the Greenzone becomes inaccessible (white) on those frames. That would be very inconvenient, because to replay these frames you would need to wait until the emulation runs from the beginning of the movie. </span><span class="rvts21">To avoid such inconvenience and still free some memory from old Greenzone sections, Taseditor uses </span><span class="rvts37">gradual rarefication</span><span class="rvts21"> of the Greenzone tail.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This process works like shown in the picture to the right. The light-blue cursor runs down along the Piano Roll. The cursor is the head of the Greenzone. It leaves green/red lines behind, but far above it some of the lines become pale again. At first, every odd frame is cleared, then 3 of every 4, then 7 of 8, and finally 15 of 16.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Thus the Greenzone tail contains many hollow sections. And if you decide to send emulator to a frame inside such hollow section, you'll need to wait while emulation runs to it from the nearest bright Greenzone frame. But since bright frames alternate every 2 or 4 frames, the waiting will only last a split second, so you won't likely notice the difference between jumping to a regular Greenzone frame (instant jump) and jumping to a cleared tail (instant seeking).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">By adjusting the "</span><span class="rvts21">Set greenzone capacity</span><span class="rvts21">" setting you can specify how many Greenzone frames (starting from its head) must stay untouched. On the picture to the right this number is 8.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">For an experiment, choose the "</span><span class="rvts21">Set greenzone capacity</span><span class="rvts21">" item, a dialog window will appear asking you to enter a number, type 100 and press OK. This will mean that first hundred of frames above the Playback cursor should not be cleaned. Any cursor navigation along this area will be instant, so you may drag the light-blue cursor and use rewind with maximum comfort. After the first hundred of frames the cleaning will be removing every other frame – you'll see alternation of bright and pale lines in the Piano Roll. This alternation will last for about 200 frames. The Playback cursor navigation along the area of 200 frames will also be almost instant.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This way the Greenzone covers 100 + 200 = 300 frames, while only 100 + 100 = 200 frames are stored in memory. Then, during next 400 frames, every filled line will alternate with 3 cleared lines, and so on. In total, the Greenzone will only occupy memory needed for storing the data of 500 frames (about 5 MB), while the accessible area will be 3100 frames (about a minute).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">By default, the Greenzone capacity is 10000 frames. This should be enough for most TASes. </span><span class="rvts21">It's recommended to TAS with</span><span class="rvts21"> no less than 1000 frames of Greenzone capacity, because the further economy would be impractical.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The minimum number for that parameter is 1 (just for tests), the maximum number is 50000.</span></p>
|
||||
<p class="rvps10"><a name="Setmaxundolevels"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Set max undo levels</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Specifies</span><span class="rvts21"> the maximum number of undo steps, how many times you can restore previous state of the project by pressing </span><span class="rvts30">Ctrl + Z</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The History Log needs a lot of computer memory and takes some disk space to save FM3 files. The whole Log is stored in project files in compressed state. The compression is done in background – when the emulator is idle, Taseditor gradually compresses new items of the History Log. Thanks to this behavior, the History Log size doesn't affect FM3 saving time much.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">With this setting you can adjust the amount of memory occupied by History Log. By default you have 100 undo levels, which means you can revert up to hundred of recent movie edits. It's not very much, because during real TASing you make lots of various edits within a small time span, as the time runs imperceptibly. If your computer has enough RAM, you can increase the "max undo levels" value up to the maximum possible number – 1000.</span></p>
|
||||
<p class="rvps10"><a name="SetAutosaveperiod"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Set Autosave period</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Specifies how many minutes the project can be left with unsaved changes.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Taseditor has the feature of automatically saving current project to disk when user doesn't save it manually </span><span class="rvts21">(</span><span class="rvts30">Ctrl + S</span><span class="rvts21">)</span><span class="rvts21"> for too long. Before Taseditor, TASers saved their movie to disk every time they saved a savestate. But Taseditor projects store much more data, and saving FM3 files can take several seconds, so it's not reasonable to resave them too often.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The default autosave period is 15 minutes. This means, if you've made some substantial changes to the project (e.g. you edited Input, and an asterisk appeared in the TAS Editor window caption), and then didn't save project for 15 minutes, Taseditor will remind you about that or just execute autosaving itself (see </span><span class="rvts21">"</span><a class="rvts27" href="ProgramCustomization.html#SilentAutosave">Silent autosave</a><span class="rvts21">"</span><span class="rvts21">).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The autosave function only works when current project already has a filename.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Maximum possible value for this parameter is 1440 minutes (24 hours). You can disable this function by specifying 0 as an autosave period, but that's not recommended.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The above were numeric settings of Taseditor, next go the checkboxes.</span></p>
|
||||
<p class="rvps10"><a name="EnableGreenzoning"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Enable Greenzoning</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Controls the process of collecting data to the Greenzone.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If the option is enabled, every new frame is saved into the Greenzone right after it has been emulated. This is intended behavior of Taseditor, so the option is enabled by default.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Disabling this option may be useful in rare cases, for example, when running bots which need high performance. But in normal situations it's recommended to have this function enabled.</span></p>
|
||||
<p class="rvps10"><a name="SilentAutosave"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Silent Autosave</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Defines the behavior of the autosave function.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If the option is enabled, after the </span><a class="rvts27" href="ProgramCustomization.html#SetAutosaveperiod">autosave period</a><span class="rvts21"> is over, Taseditor silently saves the project to disk under the same filename.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If the option is disabled, after the autosave period, Taseditor brings up the "Save As" dialog, where you can confirm the saving or cancel it. In the latter case Taseditor will wait another "autosave period" of time until reminding you about the unsaved data.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This option is enabled by default. </span><span class="rvts21">If you want complete control over project (e.g. to prevent saving any accidental changes done while watching somebody else's fm3), disable it. But when you're TASing it's recommended to let Taseditor use silent autosave.</span></p>
|
||||
<p class="rvps10"><a name="AutofirePatternskipsLag"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Autofire Pattern skips Lag</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Accounts for lag when you're using patterns (</span><span class="rvts30">Alt</span><span class="rvts21"> + clicks on Input).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If the option is disabled, patterns appear in the Piano Roll exactly (e.g. for the "Alternating (1010...)" pattern the buttonpresses will actually alternate one after another).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If </span><span class="rvts21">the option is</span><span class="rvts21"> enabled, the resulting sequence of buttonpresses may differ from original pattern (lag frames will have additional gaps not present in the pattern).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Since lag frames aren't accounted by most games, you have to skip red lines of the Piano Roll to correctly calculate the space between presses. For instance, if there must be exactly 3 blank frames between every buttonpress (pattern "10001000"), but there's also one lag frame in the middle of current segment, you have to add 1 more blank frame (100</span><span class="rvts25">0</span><span class="rvts21">01000).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This option is enabled by default.</span><span class="rvts21"> It's recommended to leave it enabled, because in vast majority of cases you need to skip lag frames, in order to adapt buttonpresses to how the game interprets Input.</span></p>
|
||||
<p class="rvps10"><a name="AutoAdjustInputAccordingtoLag"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Auto-adjust Input according to Lag</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Enables automatic adjustment of Input according to changes of lag data.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Basically, games only care about Input at green lines of the Piano Roll. It's pointless to draw any Input on red lines, because during lag frames the game doesn't poll Input. Those frames simply don't exist from the point of view of the game engine.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you edit Input, you change the flow of game events, and lag may appear on different frames too. If those frames previously had a meaningful Input, this Input must be shifted to the frames without lag, to allow it to affect the game.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If this checkbox is enabled, you won't have to adjust the Input manually every time the Lag appears on different frames. Taseditor will insert an extra line at every new lag frame, thus shifting Input 1 frame down. And when an old lag frame disappears, Taseditor will remove respective frames from the movie, thus shifting Input up. As a result, you can be sure that the game will perceive your old Input correctly, no matter any Lag changes.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Auto-adjustment operations are done by Taseditor only when you're watching (emulating) a segment, i.e. when Playback cursor runs through pale Piano Roll lines. The result of these operations is saved into the current History Log item.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This feature is enabled by default, and it's recommended to always work with the function enabled. It significantly increases the comfort of TASing, especially when dealing with lag-heavy games.</span></p>
|
||||
<p class="rvps10"><a name="DrawInputbydragging"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Draw Input by dragging</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Allows to draw Input by holding the left mouse button and moving the mouse cursor over the Piano Roll.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This option is enabled by default, so you can </span><span class="rvts21">quickly draw or erase a long line of buttonpresses.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Drawing/erasing is usually constrained by single column, which allows user to do sweeping motions with the mouse. But if you hold the </span><span class="rvts30">Shift</span><span class="rvts21"> key while drawing, you will be able to draw/erase Input freely (it's rather impractical, but fun).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you disable this option, your clicks will only set/unset single buttonpresses. It may be necessary, for example, if you have trembling hands. But otherwise enabling this feature is recommended.</span></p>
|
||||
<p class="rvps10"><a name="CombineconsecutiveRecordings"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Combine consecutive Recordings/Draws</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Combines consecutive operations of Input Recording into single item of the History Log. Also combines all Input drawn with the same press of mouse button.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This feature is disabled by default. So when you're recording Input, </span><span class="rvts21">every recorded frame will create a separate item in the History Log, and you can undo changes for any frame. Also, when you're drawing Input, every new stroke will create a new History Log item, and you can undo each of them separately.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">However, in real TASing you don't need such precision of the undo. So, to save considerable amount of space in History Log, it's recommended to enable this option.</span></p>
|
||||
<p class="rvps10"><a name="Use1PkeysforallsingleRecordings"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Use 1P keys for all single Recordings</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Allows to record any joypad Input using only the first gamepad (1P). This function is used when you record Input traditional way using multitracking method to take turns for different players, e.g. first you record a short segment of Input for player one (1P), then record the Input for 2P and so on.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Thanks to multitracking, you don't have to press buttons on both controllers at once. And with the "Use 1P keys for all single Recordings" option you don't even have to confugure 2P controls, because the same keys used for 1P can be used for all the rest joypads too.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The option is enabled by default. If you disable it, emulator will use the second controller keys for recording 2P.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's recommended to have it enabled, in order to save the space on the keyboard.</span></p>
|
||||
<p class="rvps10"><a name="UseInputkeysforColumnSet"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Use Input keys for Column Set</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Allows editing Input in selected frames by pressing corresponding joypad keys.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This feature is intended to speed up the Input editing process. To mass-set/mass-unset buttonpresses in a given segment, you usually either draw with mouse, or select a range of frames and click the necessary symbol in the Piano Roll Header – the symbol flashes and the respective Input changes in all selected frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">With the "Use Input keys for Column Set" option you can press real keys (assigned to joypads) instead of clicking the Piano Roll Header. The result will be the same.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The option is disabled by default. </span><span class="rvts21">Turn it on if you mostly use the new TASing methods and don't record Input traditional way. But when you're using Recording, either disable it or just remove the Selection to avoid Input changes on the selected frames when pressing joypad buttons.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">With this feature you can record joypad buttons even when Recording is off. Put the Selection cursor to the frame you want to apply Input to, and press the needed joypad buttons.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Multitracking mode in this case works the same way as with regular Recording. For example, if the "2P" radiobutton is chosen at the moment, pressing the key assigned to the </span><span class="rvts29">A</span><span class="rvts21"> button will only record Input for the "A" column of the 2nd player.</span></p>
|
||||
<p class="rvps10"><a name="BindMarkerstoInput"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Bind Markers to Input</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Attaches Markers to Input. If the option is enabled, various Input editing functions will also affect Markers. For example, inserting blank frames into the movie will shift down both Input and Markers.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Usually Markers are set to frames where certain in-game events occur. And when you improve previous result and reach the given place earlier than before, the corresponding Marker (set there after previous attempt) must point to an earlier frame now. Sometimes you have to drag such Markers manually. But thanks to the binding feature, Markers will shift themselves during Input modifications, so the manual adjustment of Markers is rarely needed.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Detaching Markers may be necessary when you need to edit Input without shifting Markers. For example, when you need to remove a part of Input, leaving Markers intact.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The option is on by default. It's</span><span class="rvts21"> recommended to work with attached Markers most of the time, temporarily detaching them when necessary.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">For clarification, Taseditor highlights attached Markers with a pale yellow color, and detached Markers with more bright yellow.</span></p>
|
||||
<p class="rvps10"><a name="EmptynewMarkerNotes"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Empty new Marker Notes</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Defines the default Notes text. If the option is set, each newly created Marker will have an empty Note. If not set, the new Marker will copy the above Marker's Note text.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The option is enabled by default. It's</span><span class="rvts21"> recommended to </span><span class="rvts21">left it on, and type original Notes for important Markers, thus not leaving all Notes blank.</span></p>
|
||||
<p class="rvps10"><a name="OldcontrolschemeforBranching"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Old control scheme for Branching</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Imitates certain limitations of the traditional TASing method, particularly related to handling the Bookmarks (savestates).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The option is disabled by default</span><span class="rvts21">, so hotkeys </span><span class="rvts26">F1</span><span class="rvts21">-</span><span class="rvts26">F10</span><span class="rvts21"> are used to load branch of the the corresponding Bookmarks, and the numeric keys </span><span class="rvts26">1</span><span class="rvts21">-</span><span class="rvts26">10</span><span class="rvts21"> are used for simple jumps to bookmarked frames without changing the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Besides, Input Recording is switched on with a simple press of the </span><span class="rvts26">Toggle Read-Only</span><span class="rvts21"> hotkey.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">But if you enable this option, the controls scheme will be the same as in old emulators. Pressing </span><span class="rvts26">F1</span><span class="rvts21">-</span><span class="rvts26">F10</span><span class="rvts21"> will work depending on the Recording mode. When the Recording is off, functional keys jump to respective Bookmark frame, and when Recording is on, </span><span class="rvts26">F1</span><span class="rvts21">-</span><span class="rvts26">F10</span><span class="rvts21"> keys load the branch of the Bookmark.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Besides, Input Recording won't work until you load some Bookmark. This behavior allows you to press the </span><span class="rvts26">Toggle Read-Only</span><span class="rvts21"> hotkey in the middle of watching the movie, without overwriting old Input until you actually load a savestate.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Also, there will be a red frame around the "current slot" number in the Bookmarks List. Press numeric keys </span><span class="rvts26">1</span><span class="rvts21">-</span><span class="rvts26">10</span><span class="rvts21"> to switch the current slot.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This option is left to help old TASers move to TASing in Taseditor. However, it's not recommended to use it, because the new controls scheme much better fits the specifics of TASing process in Taseditor.</span></p>
|
||||
<p class="rvps10"><a name="BranchesrestoreentireMovie"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Branches restore entire Movie</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Defines the way the branch is restored when you load a Bookmark.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The option is enabled by default, so </span><span class="rvts21">when you're loading a Bookmark, you replace the current movie with the movie state stored in that Bookmark.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If this option is disabled, when you're loading a Bookmark, the current movie is replaced with a truncated version of the bookmarked movie state. The movie will be truncated at the bookmarked frame, thus imitating the traditional behavior of loading a savestate: savestates only recover the part of the movie before the Playback cursor, and the rest frames (from the light-blue cursor to the movie end) aren't loaded. This makes sense when TASing traditional way, because after loading a savestate TASer usually records a new Input starting from the position of the Playback cursor, so there's no need to load the data that will be overwritten anyway. But in Taseditor the movie is edited independently from the Playback cursor position, so you can load the entire movie state from Bookmarks, without caring if the Playback cursor is in the end of the movie or it is in the middle.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's recommended to leave this option enabled.</span></p>
|
||||
<p class="rvps10"><a name="HUDinBranchscreenshots"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> HUD in Branch screenshots</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Defines the way to capture screenshots when creating Bookmarks.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If the option is on, it takes a snapshot of the whole emulator window, including icons and emulator messages, Lua output and other data placed over the game picture. If the option is disabled, Bookmarks will only capture the game output.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The option is enabled by default. </span><span class="rvts21">It's recommended to leave it on, in order to use Lua output and frame counter when comparing alternate approaches to playing through a segment.</span></p>
|
||||
<p class="rvps10"><a name="AutopauseattheendofMovie"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">Config -> Autopause at the end of Movie</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Automatically stops movie playback at the last frame, unless it started playing from the last frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When replaying a finished (or partially finished) movie, you usually don't want to pass over the boundary of its Input. That's why the "Autopause at the end of Movie" option is enabled by default. If you disable it, the emulator will play infinitely after the current movie Input ended, expanding the movie size until you press </span><span class="rvts26">Pause</span><span class="rvts21"> or the middle mouse button.</span></p>
|
||||
<p class="rvps10"><span class="rvts49">It's recommended to leave this option enabled.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="fceux-config"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Now you are aware of all Taseditor settings, the remaining part of the chapter describes FCEUX emulator settings that may be useful for a TASer.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you are going to TAS traditional way, it's obligatory to set the first controller buttons to such keys that would be easy to press together with the </span><span class="rvts26">Frame Advance</span><span class="rvts21"> hotkey. While FCEUX supports binding the virtual NES joypad to a real PC gamepad, it's recommended to use the keyboard for recording Input, in order to have fast access to </span><span class="rvts26">Frame Advance</span><span class="rvts21">, </span><span class="rvts26">Frame Rewind</span><span class="rvts21">, </span><span class="rvts26">Pause</span><span class="rvts21">, and to all 10 savestate slots.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">However, if you use Taseditor as intended, you won't need to use Recording too much, and even in cases when you use it (for example, when recording a test playthrough of a level), an access to functional keys isn't critical. So, you can reassign the game controls to a USB gamepad, if you have one.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Virtual controller buttons are configured in FCEUX the following way. Choose </span><span class="rvts25">Config -> Input</span><span class="rvts21"> in emulator main menu. In the appeared dialog, select the "Gamepad" item from the leftmost drop-down listbox (it's usually already selected). Click the left </span><span class="rvts29">Configure</span><span class="rvts21"> button (since you need to configure the first gamepad). In the new window click the </span><span class="rvts29">Up</span><span class="rvts21"> button, then a small window will appear, now press the keyboard key you want to set for the virtual </span><span class="rvts29">Up</span><span class="rvts21"> button. Press that key 2nd time to confirms your choice, or just click </span><span class="rvts29">Close</span><span class="rvts21">. Then you need to do the same for the rest buttons of NES gamepad – </span><span class="rvts29">Down</span><span class="rvts21">, </span><span class="rvts29">Left</span><span class="rvts21">, </span><span class="rvts29">Right</span><span class="rvts21">, </span><span class="rvts29">Select</span><span class="rvts21">, </span><span class="rvts29">Start</span><span class="rvts21">, </span><span class="rvts29">B</span><span class="rvts21">, </span><span class="rvts29">A</span><span class="rvts21">. After you're done with the first controller buttons (Virtual Gamepad 1), you may close both windows: Gamepad and Input Configuration.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can check the assigned buttons while playing the game or while Taseditor is engaged – as you press them, the corresponding symbols in the Piano Roll Header will shine with green color. Besides, if you enable Input display (FCEUX: </span><span class="rvts25">Config -> Display -> Input Display -> 2 player</span><span class="rvts21">), FCEUX screen will show you the pressed buttons too.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In addition to recording the regular gaming session, virtual gamepad buttons may be used to quickly set Input when editing movie (see </span><a class="rvts27" href="ProgramCustomization.html#UseInputkeysforColumnSet">Config -> Use Input keys for Column Set</a><span class="rvts21">). Select a range of frames where you want to change Input and press the key you assigned to a button of the virtual gamepad.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you map the virtual buttons to keyboard keys, make sure none of the emulator or Taseditor hotkeys are already assigned to those keys. The full list of default hotkeys can be found in </span><a class="rvts27" href="Controls.html#hotkeys">Reference</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Some FCEUX hotkeys don't have default mapping (they're not mapped to any key yet), you can configure them this way. In the emulator main menu choose </span><span class="rvts25">Config -> Map Hotkeys</span><span class="rvts21">. A window listing all possible emulator hotkeys will appear. Choose the necessary hotkey, double-click it and then press the desired keyboard key.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">First of all, find the item called "</span><span class="rvts25">Open TAS Editor</span><span class="rvts21">" and double-click it. In the appearing window press the key that you will always use to quickly launch Taseditor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Second, find the item "</span><span class="rvts26">Reload ROM or TAS Editor Project</span><span class="rvts21">" and either remap it or remember the default combination (</span><span class="rvts26">Ctrl + F1</span><span class="rvts21">). This hotkey will help you quickly return to your interrupted work – just launch FCEUX, press the </span><span class="rvts26">Reload ROM</span><span class="rvts21"> hotkey, then the aforementioned </span><span class="rvts25">Open TAS Editor</span><span class="rvts21"> hotkey, and then again </span><span class="rvts26">Reload ROM</span><span class="rvts21"> (this time it will work as </span><span class="rvts26">Reload TAS Editor Project</span><span class="rvts21">). This way you'll return to the state of your paused work in a split second.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Then look at the hotkeys "</span><span class="rvts26">Frame Advance</span><span class="rvts21">" и "</span><span class="rvts26">Frame Rewind</span><span class="rvts21">". They are used for Playback cursor navigation. By default they are mapped to "</span><span class="rvts26">\</span><span class="rvts21">" and "</span><span class="rvts26">Backspace</span><span class="rvts21">". You can reconfigure them to more handy keys or just ignore and use just the mouse wheel for Playback cursor navigation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Also see the "</span><span class="rvts26">Speed Down</span><span class="rvts21">" and "</span><span class="rvts26">Speed Up</span><span class="rvts21">" hotkeys. You may consider remapping them to Numpad keys "</span><span class="rvts25">+</span><span class="rvts21">" and "</span><span class="rvts25">-</span><span class="rvts21">".</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts26">Pause</span><span class="rvts21">" и "</span><span class="rvts26">Restore Playback</span><span class="rvts21">" hotkeys are set to "</span><span class="rvts26">Pause/Break</span><span class="rvts21">" and "</span><span class="rvts26">Spacebar</span><span class="rvts21">" keys by default, but in most cases it's easier to use the middle mouse button instead of these hotkeys, so you can even reassign the "</span><span class="rvts26">Spacebar</span><span class="rvts21">" for something else if you wish.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Finally, there is the "</span><span class="rvts26">Cancel Seeking</span><span class="rvts21">" hotkey ("</span><span class="rvts26">Esc</span><span class="rvts21">" key by default). Pressing it is the same as clicking the Taseditor progressbar – if the Playback was seeking to a target frame, the seeking will be canceled.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Some FCEUX hotkeys don't work when Taseditor is engaged. For example, the "</span><span class="rvts25">Open ROM</span><span class="rvts21">" won't work – you have to load ROM before running Taseditor. This is done for </span><a class="rvts27" href="MistakeProofing.html#DisabledHotkeys">mistake-proofing</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The next chapter describes </span><a class="rvts27" href="AdvancedFeatures.html">additional features of Taseditor</a><span class="rvts21">. You may postpone reading it until you are used to main features. Anyway, now you're ready enough for productive work in Taseditor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/create-epub-ebooks">Write EPub books for the iPad</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,129 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>2. Program Interface</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("ProgramInterface");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>2. Program Interface</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="BeginnersGuide.html">Beginner's Guide</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="BeginnersGuide.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="Introduction.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="PianoRoll.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Program Interface</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">This chapter describes the program interface and ways of interacting with it.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The description uses many specific terms, so make sure you know the </span><a class="rvts32" href="Glossary.html">Glossary</a><span class="rvts21"> before starting the read. Also, it's advisable to run Taseditor right now, to be able to check everything you read in practice.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">To enter Taseditor do the following:</span></p>
|
||||
<ol style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><span class="rvts21">launch FCEUX emulator</span></li>
|
||||
<li class="rvps14"><span class="rvts21">load any game ROM (File -> Open ROM)</span></li>
|
||||
<li class="rvps14"><span class="rvts21">open Taseditor window (Tools -> TAS Editor)</span></li>
|
||||
</ol>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you engage Taseditor, the game is reset, and the emulator pauses. It shall stand paused as you TAS, to prevent the game from urging you on and distracting from analysis of information.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps18"><img alt="" style="padding : 1px;" src="lib/Monitor-example.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">While TASing in Taseditor, a considerable part of the desktop is covered by the very Taseditor window. Emulator window is used for picture output, and you'd better scale it up to 2x size, so you won't miss a tiny detail even at a cursory glance. During your work you'll have to move eyes between emulator window and Taseditor window (mostly contents of the Piano Roll). So put those windows close to each other. The remaining space of the desktop can be populated with RAM Watch window, Lua console, etc.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can adjust the size of TAS Editor window by dragging its edges with the mouse. The size and position are automatically saved and restored at next launch.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The window caption displays the program name ("TAS Editor") and the name of current project. If there are any unsaved changes, an asterisk is added to the end of the text. Besides, when the Input Recording mode is on, the word "Recording" appears in the window caption.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The main menu of the program is similar to one found in text editors like Notepad.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The </span><span class="rvts25">File</span><span class="rvts21"> item is responsible for all file operations – creating a new TAS project, opening an existing file, saving, data importing and exporting. There's also a "Recent" sub-menu that stores direct paths to recently used projects.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The </span><span class="rvts25">Edit</span><span class="rvts21"> item contains functions that let you edit TAS movie like a simple text file or a table file. Most of those functions can be accessed through standard key combinations, such as </span><span class="rvts30">Ctrl + C</span><span class="rvts21">, </span><span class="rvts30">Ctrl + V</span><span class="rvts21"> and others. They will be reviewed later.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The </span><span class="rvts25">View</span><span class="rvts21"> item allows to adjust the program appearance. Besides, here you can open the "Find Note" window, used to search text in Marker Notes. All of that will be described later. Until you study the </span><a class="rvts33" href="ProgramCustomization.html">Chapter 5</a><span class="rvts21"> of this Guide, it's recommended to keep default preferences.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The </span><span class="rvts25">Config</span><span class="rvts21"> item stores the rest settings, e.g. project auto-saving timer, the number of undo levels and other features that will be described during the learning flow. Don't change those settings for now.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Finally, the </span><span class="rvts25">Help</span><span class="rvts21"> item contains the link to local copy of this Guide and the "About" window. Here you can also switch on/off hints (tooltips).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To the right of the main menu there is the </span><span class="rvts25">Pattern</span><span class="rvts21"> item, displaying the name of current pattern. Patterns are just templates for speeding up the Input creation. They will be described in </span><a class="rvts31" href="AdvancedFeatures.html#UsingPatterns">Chapter 6</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps10"><table width="100%" border="0" cellpadding="0" cellspacing="0" style="border-width: 0px;">
|
||||
<tr valign="top">
|
||||
<td style="width: 125px;"><p class="rvps2"><img alt="" style="padding : 1px;" src="lib/pianoroll.png"/></p>
|
||||
</td>
|
||||
<td style="width: 797px;"><div class="rvps10"><table width="100%" border="0" cellpadding="10" cellspacing="0" style="border-width: 0px;">
|
||||
<tr valign="top">
|
||||
<td><p class="rvps10"><span class="rvts21">Contents of the TAS Editor window can be divided into 2 parts – the workspace (Piano Roll) to the left and the Toolbox to the right.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps17"><a class="rvts23" href="PianoRoll.html">Proceed to the Piano Roll description</a></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts6"><br/></span></p>
|
||||
</td>
|
||||
<td style="width: 67px;"><p class="rvps19"><img alt="" style="padding : 1px;" src="lib/toolbox.png"/></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com">Free PDF documentation generator</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,95 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Reference</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("Reference");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Reference</h1>
|
||||
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="AdvancedFeatures.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="Glossary.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Reference</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Glossary.html">Glossary</a></p>
|
||||
<p class="rvps12"><span class="rvts24">Terms that are used throughout this documentation</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Controls.html">Controls</a></p>
|
||||
<p class="rvps12"><span class="rvts24">Exhaustive review of controls</span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Navigation.html"><br/></a></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Navigation.html">Navigation</a></p>
|
||||
<p class="rvps12"><span class="rvts24">The summary of all ways to navigate a movie</span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Operations.html"><br/></a></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Operations.html">Operations</a></p>
|
||||
<p class="rvps12"><span class="rvts24">The list and mini-reviews of all possible operations with a movie</span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="LuaAPI.html"><br/></a></p>
|
||||
<p class="rvps10"><a class="rvts23" href="LuaAPI.html">Lua API</a></p>
|
||||
<p class="rvps12"><span class="rvts24">Specifications of </span><span class="rvts24">"taseditor" library of Lua functions</span></p>
|
||||
<p class="rvps10"><span class="rvts23"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="FAQ.html">FAQ</a></p>
|
||||
<p class="rvps12"><span class="rvts24">Answers to some expected questions</span></p>
|
||||
<p class="rvps10"><span class="rvts23"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="SpeedrunningSynopsis.html">Speedrunning synopsis</a></p>
|
||||
<p class="rvps12"><span class="rvts24">Abstract classification of typical issues arising when optimizing a segment for fastest time</span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour/create-ebooks-for-amazon-kindle">Write eBooks for the Kindle</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,168 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>4.3. Semiautomatic TASing</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("SemiautomaticTASing");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>4.3. Semiautomatic TASing</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="BeginnersGuide.html">Beginner's Guide</a> ›› <a href="TASingMethodology.html">4. TASing Methodology</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="TASingMethodology.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="NonlinearTASing.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="ProgramCustomization.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Semiautomatic TASing</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-method3.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">This method further develops the ideas of the nonlinear TASing method.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In many cases TASer needs to see the result of the Input modification immediately. Ideally, he should realize all the consequences of his decision right at the moment of making the decision. But in reality he has to spend precious time on inputting the decision and navigating with the Playback cursor to the end of the segment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In these cases you can leave the Playback navigation to Taseditor and just focus on editing. Taseditor will immediately react on any Input modification and display the new result.by bringing the Playback cursor to the end of the current segment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Since you feel the influence of every click, you build very high level of interconnection between TASer and the game. In such close interaction both TASer controls the game and the game urges TASer's actions into right direction. Of course, such high level of interdependency is not always useful, because it narrows your spectrum of thoughts, not allowing to look down on the game and apply the logic from different games and other fields of life.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">However, when the current segment is simple and all optimality factors are already known (and you only need to find the perfect combination of them), it's useful to abstract from everything else and devote full attention to going over the possible options. This way you can test a lot of approaches before you become bored with the current segment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Recording mode and the </span><span class="rvts21">"Follow cursor" checkbox</span><span class="rvts21"> should be off. The </span><span class="rvts21">"Auto-restore last position" checkbox should be on. The "Turbo seek" checkbox can be either disabled or enabled.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">General activity:</span></p>
|
||||
<p class="rvps10"><span class="rvts48"><br/></span></p>
|
||||
<ol style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Scroll the Piano Roll to the beginning of the edited segment, put the Playback cursor here, define the goal.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Detect the end of the segment and leave the Playback cursor there.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Suppose there's a mistake in the segment, weigh known factors of optimality and figure out the way to fix the mistake.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">The mouse cursor navigation to any frame of the current segment is practically instant.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Edit the segment with the mouse. After every Input modification the Playback cursor will automatically replay the segment and stop at the frame that was considered to be the end of the segment. If necessary, you can shift the end of the segment by moving the Playback cursor manually (using the wheel). The steps 4 and 5 are constantly alternating until you consider the editing complete, according to the optimality criterion.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">[</span><span class="rvts34">optional step</span><span class="rvts21">] Save the finished approach to any free Bookmark, e.g. to slot </span><span class="rvts26">8</span><span class="rvts21">.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">If this isn't the first approach to the segment, compare the new result to the best old result, using the optimality criterion. If the new approach is better (or it's the first approach), save the result to the Bookmark </span><span class="rvts26">9</span><span class="rvts21">. The slot </span><span class="rvts26">9</span><span class="rvts21"> will be used for keeping the best result of polishing the segment.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">If you still want to try different series of approaches, return to step 3, until you run out of ideas.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">[</span><span class="rvts34">optional step</span><span class="rvts21">] If you need more ideas, you can get some information from the past or the future by moving the Playback cursor to different segments of the movie or unpausing the emulator. When necessary, you can quickly draw a rough Input for watching the upcoming events of the game. But when returning to the segment modification you have to return the Playback cursor to the frame of the target event.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When there's no more ideas, restore the best approach from the History Log or the Bookmark </span><span class="rvts26">9</span><span class="rvts21"> into the current movie and proceed to the next segment.</span></li>
|
||||
</ol>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The main difference between this and previous method is that here the Playback cursor is generally located at the end of the current segment, and not at the beginning. Every time the Greenzone truncates, the Playback cursor seeks to the end of the segment, or rather to the frame where the segment end was before you modified the Input. If the Input modification also changed the frame of the target event, you can additionally move the light-blue cursor by mouse wheel if needed. But often there's no need for precise positioning, because you may only need to know the sequence of events occurring in the segment due to the Input modification.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The replay of the current segment is automatically launched after every interim step of the Input modifications, even when you haven't finished the thought yet and are not ready to compare the current result to the result of the previous approach. Fortunately, when TASer is carried away by the editing process, he doesn't look at FCEUX screen and only clicks the Piano Roll, until his idea is implemented in the form of a full-fledged button combination. And when the Input is starting to become interesting, TASer pays attention to the emulator screen or the Memory Watch window.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">For example, when you need to create a jump over a pit, you first draw a long row of the </span><span class="rvts29">R</span><span class="rvts21"> button presses, and you don't care that at the same time the FCEUX screen displays how Mario runs and falls into the pit. You just draw some </span><span class="rvts29">A</span><span class="rvts21"> buttonpresses, then look at the emulator window and erase or draw additional </span><span class="rvts29">A</span><span class="rvts21"> buttonpresses, thus changing the beginning and the duration of the jump while watching the trajectory of Mario sprite.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">So, the process of polishing the Input in this method is a simultaneous editing and watching the segment. TASer gets in close informational contact with the game and soon starts to think synchronously with its responses. The game starts to help TASer filter and accept decisions. As a result, you may lose impartiality of your mind and stick to obvious decisions encouraged by the game. That's why you shouldn't use this method all the time, it's recommended to alternate it with the previous one.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">As with the simple nonlinear method, you can change the speed of emulation and get different variations of the semiautomatic method:</span></p>
|
||||
<ol style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">editing and watching the changes in real time</span></li>
|
||||
<li class="rvps10"><span class="rvts21">editing and watching the changes in slow motion</span></li>
|
||||
<li class="rvps10"><span class="rvts21">editing and instantly seeing the final result (turbo)</span></li>
|
||||
</ol>
|
||||
<p class="rvps10"><a name="turbo-seeking"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Turbo-seeking creates an association between two distant events (the beginning and the end of the segment). Here the association is even more efficient, because there's even less intermediaries – the seeking starts before you even release the mouse button when drawing the Input. So you see the distant result almost at the same time you change the decisive Input, even if the game normally only shows the result in a several seconds.</span></p>
|
||||
<p class="rvps10"><a name="LuckManipulation"></a>
|
||||
<span class="rvts21">A good example would be the process of searching for the first possible frame of pressing the </span><span class="rvts29">Start</span><span class="rvts21"> button. Some games actually allow to press the button before there's even any graphics on screen. Besides, after the </span><span class="rvts29">Start</span><span class="rvts21"> button is activated, games often meditate for some time, not giving you any information if the button worked or not. Only after a second or two you can see the changes in the scenery, thus learning the buttonpress was successful.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In the traditional method of TASing you would need to spend 5-10 minutes on examination of approaches (searching for the very first frame), but the semiautomatic method allows to go over all the approaches much faster:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Switch on the </span><span class="rvts21">"Auto-restore last position" and </span><span class="rvts21">"Turbo seek" checkboxes. Switch off the </span><span class="rvts21">"Follow cursor" checkbox.</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Set a trial </span><span class="rvts29">Start</span><span class="rvts21"> button press at the frame where it definitely works, e.g. at the frame 100.</span></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Watch the game up to the frame where you can already tell by the picture that the </span><span class="rvts29">Start</span><span class="rvts21"> was successful (e.g. the screen changed to "World 1-1" text). For example, it's the frame 150. Leave the Playback cursor at this frame – this will be the end of the segment.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Now remove the trial buttonpress (the FCEUX window will flash and the "World 1-1" will disappear, leaving only the title screen, since there's no more </span><span class="rvts29">Start</span><span class="rvts21"> button press).</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Set the </span><span class="rvts29">Start </span><span class="rvts21">buttonpress to the beginning of the segment, which is the place where you know it's too early for the buttonpress to be registered. For example, set it to the first frame of the movie. The image in the FCEUX window will flash but then still show the title screen, because the </span><span class="rvts29">Start</span><span class="rvts21"> didn't work.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Hold </span><span class="rvts30">Ctrl + Shift</span><span class="rvts21"> by one hand and begin pressing </span><span class="rvts30">Insert</span><span class="rvts21"> key once per a second or so (that really depends on your computer performance). After every </span><span class="rvts30">Ctrl + Shift + Insert</span><span class="rvts21"> combination the </span><span class="rvts29">Start</span><span class="rvts21"> buttonpress moves one frame forward, and the FCEUX window shows you if the buttonpress changed the state of the game at frame 150 or not.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Until the </span><span class="rvts29">Start</span><span class="rvts21"> doesn't reach the moment when the game is ready to accept the Input, the FCEUX window will show you the title screen. But when another press of </span><span class="rvts30">Ctrl + Shift + Insert</span><span class="rvts21"> moves the </span><span class="rvts29">Start</span><span class="rvts21"> to a suitable frame, the emulator will display the "</span><span class="rvts21">World 1-1" screen.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">This way you've found the very first frame to press the </span><span class="rvts29">Start</span><span class="rvts21"> button. Most likely the frame number will be much less than 100.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">In the same way you can search for an optimal duration of holding the </span><span class="rvts29">A</span><span class="rvts21"> button, trying to land at certain point. Also consider using this method for quick luck manipulation in many games. The automatic turbo-seeking works best when you deal with a single factor of optimality and need to quickly test a hundred of similar approaches.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In general, the semiautomatic method induces you to think less and experiment more. Sure, many videogames allow this way of solving tasks, but TASing requires more from you, so try not to take a fancy to the comfort of this method.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Pros of the method:</span></p>
|
||||
<p class="rvps14"><span class="rvts22">+ </span><span class="rvts21">Instant navigation and high</span><span class="rvts21"> speed of the working process incites to conduct more tests.</span></p>
|
||||
<p class="rvps14"><span class="rvts22">+ </span><span class="rvts21">Constant feedback allows to adapt to the game while editing the Input, adjust your decisions and discard incorrect approaches prematurely.</span></p>
|
||||
<p class="rvps14"><span class="rvts22">+ </span><span class="rvts21">Possibility to skip useless scenes.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Cons of the method:</span></p>
|
||||
<p class="rvps14"><span class="rvts22">– </span><span class="rvts21">The insistent game feedback provokes TASer to discard some illogical but potentially advantageous approaches.</span></p>
|
||||
<p class="rvps14"><span class="rvts22">– </span><span class="rvts21">Emphasis on the mouse controls.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">When the method is recommended to use:</span><span class="rvts21"> when you need to polish the segment already knowing its all optimality factors. E.g. for quick resyncing of the old Input this method is better than previous. Also it may be better for making an initial playthrough of a segment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Now that you know the main principles of working in Taseditor, you can begin TASing your game of interest. Practice is the best teacher, so you'll only learn all intricacies of the activity by engaging in real development of your own TAS.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">After several weeks of practical TASing it's recommended to reread the 3rd and 4th chapters of this Guide, in order to understand the text on a deeper level.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">In the next chapter: </span><a class="rvts27" href="ProgramCustomization.html">tweaking the program</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps10"><table width="100%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid;"><p class="rvps10"><span class="rvts25">PRACTICE: </span><span class="rvts21">Thoroughly polish the Input in the segments of your test movie. If the initial dividing appears to be wrong – just redo it on the fly.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Use only the 2nd and the 3rd method of TASing, because traditional method is obsolete. Also try using turbo when suitable.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Estimated time: </span><span class="rvts21">30-60 minutes.</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour/create-ebooks-for-amazon-kindle">Produce Kindle eBooks easily</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,167 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Speedrunning synopsis</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("SpeedrunningSynopsis");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Speedrunning synopsis</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="Reference.html">Reference</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="Reference.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="FAQ.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="TASEditorInside.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Speedrunning synopsis</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Thanks to the definite goal, creating tool-assisted speedruns is the easiest application of TASing, and relevant techniques are examined pretty well. Here you can find the summary of generic tasks emerging in the process of polishing the Input for a speedrun. Before reading this, make sure you've learned the materials in </span><a class="rvts27" href="TASingProcess.html">TASing Process</a><span class="rvts21"> and </span><a class="rvts27" href="TASingMethodology.html">TASing Methodology</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Speedrunners have to search for the shortest way of completing every segment of the game. This process of searching consists of testing a multitude of approaches for playing the segment and finally choosing the best approach. Here we will discuss only the problem of choice.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To simplify the problem, TASers usually compare only two approaches: the </span><span class="rvts25">new working</span><span class="rvts21"> approach and the </span><span class="rvts25">old best</span><span class="rvts21"> approach; all other old approaches are promptly forgotten (although the interesting ones can always be saved in the Bookmarks).</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The best of all old (previously tested) approaches can be stored:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">in Bookmarks – recommended</span></li>
|
||||
<li class="rvps10"><span class="rvts21">in the History Log – automatically but temporary</span></li>
|
||||
<li class="rvps10"><span class="rvts21">in TASer's own memory – not recommended</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When the new working approach is considered to be better (more optimal) than the old best approach, it's naturally assumed that it's also better than any of the old approaches, so this working approach instantly becomes the best. In the case of using Bookmarks you should re-save the new approach to the slot where the old best approach was stored. At the end of the search the contents of this Bookmark slot are loaded into the final movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Optimality criteria in speedruns:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">presence/absence of the specific event in the new and old approach </span><span class="rvts70">(bool)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">the time of occurrence of the target event in the new and old approach </span><span class="rvts70">(int)</span></li>
|
||||
<li class="rvps10"><span class="rvts21">the state of the game at the same frame in the new and old movie </span><span class="rvts70">(string)</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Respectively, when you're comparing any pair of approaches you are doing one of the three:</span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="SpeedrunningSynopsis.html#CompareEvent">1. Comparing presence/absence of the event.</a></p>
|
||||
<p class="rvps31"><a class="rvts57" href="SpeedrunningSynopsis.html#CompareEvent-A">A. By memory</a></p>
|
||||
<p class="rvps31"><a class="rvts57" href="SpeedrunningSynopsis.html#CompareEvent-B">B. Using Bookmarks</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="SpeedrunningSynopsis.html#CompareTime">2. Comparing the time of occurrence.</a></p>
|
||||
<p class="rvps31"><a class="rvts57" href="SpeedrunningSynopsis.html#CompareTime-A">A. By memory</a></p>
|
||||
<p class="rvps31"><a class="rvts57" href="SpeedrunningSynopsis.html#CompareTime-B">B. Using the green arrow</a></p>
|
||||
<p class="rvps31"><a class="rvts57" href="SpeedrunningSynopsis.html#CompareTime-C">C. Using a Marker</a></p>
|
||||
<p class="rvps31"><a class="rvts57" href="SpeedrunningSynopsis.html#CompareTime-D">D. Using Bookmarks</a></p>
|
||||
<p class="rvps10"><a class="rvts27" href="SpeedrunningSynopsis.html#CompareState">3. Comparing the state of the game at the same frame.</a></p>
|
||||
<p class="rvps31"><a class="rvts57" href="SpeedrunningSynopsis.html#CompareState-A">A. By memory</a></p>
|
||||
<p class="rvps31"><a class="rvts57" href="SpeedrunningSynopsis.html#CompareState-B">B. Using Bookmarks</a></p>
|
||||
<p class="rvps30"><span class="rvts42"><br/></span></p>
|
||||
<p class="rvps10"><a name="CompareEvent"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">1. Comparing presence/absence of the event.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Choose the approach where the needed event happens / unneeded event doesn't happen. The occurrence of the event is only the first (and often easy) step in creating the Input for current segment, and next step is to try speeding up the time of the occurrence.</span></p>
|
||||
<p class="rvps10"><span class="rvts37">The search for approaches goes on until the first successful approach is found, or until you're tired (then the event is considered to be unfeasible).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Programming analogy: comparing two Booleans, comparing two arrays of Booleans.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="CompareEvent-A"></a>
|
||||
<span class="rvts21">A. Most of time it's enough to simply keep in mind the fact that target event didn't occur in previous approaches. Example: </span><a class="rvts27" href="SemiautomaticTASing.html#FindStartButtonPress">finding the </a><a class="rvts72" href="SemiautomaticTASing.html#FindStartButtonPress">Start buttonpress</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="CompareEvent-B"></a>
|
||||
<span class="rvts21">B. When the target event is complex (e.g. you plan to shoot 3 enemies simultaneously), it's recommended to save the most promising approaches into Bookmarks (e.g. an approach where you shot 2 enemies simultaneously and 3rd one shortly after), because if the target event is unfeasible, you might be satisfied with such partial success.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="CompareTime"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">2. Comparing the time of occurrence.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Choose the approach where the target event occurs earlier. The time of occurrence is defined by the frame in which the event can be detected, while in previous frame it cannot be detected. The number of this frame is found by bringing the Playback cursor to the frame and watching the FCEUX screen (or Memory Watch) for confirming.</span></p>
|
||||
<p class="rvps10"><span class="rvts37">The search for approaches goes on until you're tired, or until all possible types of approaches are exhausted (then the current best approach is considered to be frame perfect, until new factors are found).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Programming analogy: comparing two Integer Numbers.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="CompareTime-A"></a>
|
||||
<span class="rvts21">A. For simplest segments and small subsegments it may be enough to just keep in mind current fastest frame number and compare results of all new approaches with this number. But in general it's not recommended to rely on human memory. Details: </span><a class="rvts27" href="TASingProcess.html#EndOfSegment">TASing Process</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="CompareTime-B"></a>
|
||||
<span class="rvts21">B. On simple segments you can refer to the green arrow of Taseditor. When using it you're supposed to always leave the Playback cursor at the frame of target event (which is only natural). Thus if the new frame of target event is located above the green arrow, it means the new approach is faster than previous approach. Details:</span><a class="rvts27" href="NonlinearTASing.html#GreenArrow">TASing Methodology</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="CompareTime-C"></a>
|
||||
<span class="rvts21">C. On complex segments use an unbound Marker that always points at current fastest frame number in the Piano Roll. Every time you beat the old result you're supposed to manually move the Marker higher. Thus if the new frame of target event is located above the Marker, it means the new approach is faster than the old best approach. Details: </span><a class="rvts27" href="ProgramCustomization.html#BindMarkerstoInput">Program Customization</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="CompareTime-D"></a>
|
||||
<span class="rvts21">D. On segments of any level of complexity it's recommended to use Bookmarks that are displayed in the icons column of the Piano Roll. Every time you beat the old result you're supposed to manually save current approach to the same Bookmark slot, replacing the old best approach stored there. Thus if the new frame of target event is located above the Bookmark icon, it means the new approach is faster than the old best approach.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="CompareState"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">3. Comparing the state of the game at the same frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Choose the approach where properties of the game are more advantageous in a whole. This type of comparison is useful when you need to evaluate compound in-game situations. For example, in Formula 1 racing you have to care both about being as fast as possible and wearing tyres as little as possible, so you need to find an optimal balance on each segment of the track instead of just simply hurrying up.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Here the segment has defined end frame, and every new test is supposed to replay the segment up to that frame. Taseditor stores this frame number in the form of the green arrow, which automatically pauses emulation when you watch new approaches. So TASer only needs to edit Input (creating new approaches), launch replaying, wait for the stopping and evaluate the result (judging by FCEUX screen or Memory Watch).</span></p>
|
||||
<p class="rvps10"><span class="rvts37">The search of approaches goes on until you're tired, or until all possible types of approaches are exhausted (then the current best approach is considered to be perfect, until new factors are found).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Programming analogy: comparing two Strings, comparing two arrays of Integer Numbers.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="CompareState-A"></a>
|
||||
<span class="rvts21">A. For simple segments it may be enough to just keep in mind the value of the most important property of the game state achieved in the old best approach. Every time you watch the replaying of a new approach, you can compare results of the new approach with this value. If you decide the new value is better, you have to memorize it in place of old value. Example: </span><a class="rvts27" href="NonlinearTASing.html#LuckManipulation">luck manipulation</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When there's more than one important property, it's not recommended to rely on human memory.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a name="CompareState-B"></a>
|
||||
<span class="rvts21">B. On complex segments and especially on gigantic segments (with the size of a whole level of the game) use Bookmarks that store alternative branches of the movie. The best approach for playing the segment is saved into one Bookmark slot and the new approach is saved into another slot. Then you can easily switch between these slots and compare values of each property of the game state. In addition, you can point the mouse cursor to respective Bookmarks to see screenshots of the game state and visually compare their properties with current image on FCEUX screen.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To display important RAM data on screenshots you should use Lua graphical output, then Memory Watch window won't be required to judge important properties, and you will be able to successfully judge by screenshots only. Details: </span><a class="rvts27" href="ProgramCustomization.html#DisplayBranchScreenshots">Program Customization</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In the situation when some properties in the new approach are better and some others are worse you'll have to thoroughly weigh all of them (either in your mind or using a Lua-powered aggregate formula) and then decide which state of the game is better.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Every time you beat the old result you're supposed to manually save the new approach to the same Bookmark slot, replacing the old best approach stored there.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">After finding the fastest approach of playing the segment a good TASer is expected to improve the entertainment value of the play through the segment. The optimality criteria in such activity may be very diverse, but the general requirement is to keep the same time of playing through the segment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Alternatively, you can postpone the entertainment improvement of the segment and proceed to the next.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/help-authoring-tool">Single source CHM, PDF, DOC and HTML Help creation</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,93 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>TAS Editor Inside</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("TASEditorInside");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>TAS Editor Inside</h1>
|
||||
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="SpeedrunningSynopsis.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="Ideas.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">TAS Editor Inside</span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps2"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">This section of the documentation describes all ideas put into the Taseditor and reveals major details of the final implementation of TAS Editor 1.0. For more details check the source code of the program (in C++).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Taseditor is an open source program and is distributed under the </span><a class="rvts27" href="http://en.wikipedia.org/wiki/MIT_License" target="_blank">MIT</a><span class="rvts21"> license which allows unrestricted use. The license was chosen to encourage a modification and porting Taseditor to another platforms.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can download the source code of the FCEUX 2.2.0 emulator with built-in Taseditor from the official SVN repository: </span><a class="rvts27" href="http://sourceforge.net/p/fceultra/code/" target="_blank">http://sourceforge.net/p/fceultra/code/</a></p>
|
||||
<p class="rvps10"><span class="rvts21">To work with SVN you'll need some SVN client program, like </span><a class="rvts27" href="http://en.wikipedia.org/wiki/Tortoise_SVN" target="_blank">TortoiseSVN</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The source code of Taseditor is well-commented, and to understand the code you only need basic skills of programming in C++ under Win32 API.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Ideas.html">Ideas</a></p>
|
||||
<p class="rvps12"><span class="rvts24">The intended functionality of the program</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Implementation.html">Implementation</a></p>
|
||||
<p class="rvps12"><span class="rvts24">The actual program architecture</span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Navigation.html"><br/></a></p>
|
||||
<p class="rvps10"><a class="rvts23" href="MistakeProofing.html">Mistake-proofing</a></p>
|
||||
<p class="rvps12"><span class="rvts24">The list of unobvious nuances</span></p>
|
||||
<p class="rvps10"><a class="rvts23" href="Operations.html"><br/></a></p>
|
||||
<p class="rvps10"><a class="rvts23" href="FM3format.html">FM3 format</a></p>
|
||||
<p class="rvps12"><span class="rvts24">Taseditor project file specifications</span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p class="rvps12"><span class="rvts24"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/help-authoring-tool">Full-featured multi-format Help generator</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,213 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>4. TASing Methodology</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("TASingMethodology");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>4. TASing Methodology</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="BeginnersGuide.html">Beginner's Guide</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="BeginnersGuide.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="TASingProcess.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="TraditionalTASing.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">TASing Methodology</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">This chapter is dedicated to the principal activity in TASing – the way of creating an optimal Input for any given segment of the movie. TASes look so shiny exactly because of persistent manual polishing of Input. The size of the segment can be anything, criteria and factors of optimality can vary, but the method is basically one and the same</span><span class="rvts21">: retry all sorts of approaches and choose the best one. The only question is how to do it with minimum time and effort.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts34">Gamers</span><span class="rvts21"> erroneously think that to make a TAS you only have to complete the game once, using savestates when you make some fatal mistakes resulting in inability to complete current segment (for example, death of the character).</span></li>
|
||||
<li class="rvps10"><span class="rvts34">Newbie TASers</span><span class="rvts21"> understand that to make a beautiful TAS you have to revert and fix all noticed mistakes (e.g. such minor flaws as stumbling over a threshold). They also complete each segment only once, but spend more time than regular players, because of saving and loading savestates much more often. For TASing simple games this can be sufficient.</span></li>
|
||||
<li class="rvps10"><span class="rvts34">Experienced TASers</span><span class="rvts21"> know that to make a perfect TAS it's not enough to fix all noticed mistakes. You also have to fix unnoticed mistakes. Consider unknown factors. Approach the task from an unobvious side. To do all this they play through the same segment several times, both fixing all noticed mistakes and somehow trying not to make unnoticeable mistakes.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's rather difficult to convince yourself to spend time on alternative ways to play through the segment once it's already completed and all obvious mistakes are already fixed. After achieving the current in-game goal people usually want to set another in-game goal. But you must remember that TASer's goal is different from player's goals. So try to abstract away from the game rules and not to retreat from the segment until you complete real goal, not just player's small goal.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">That's actually the most difficult part – to invent new approaches to solving one and the same task. TASers mainly consider the same approach a regular player would have used in this place of the game. That's why people mostly use evolutionary way instead of revolutionary. You keep modifying the existing basic approach, both fixing its mistakes and conducting experiments. In the process of these thoughtful modifications you enrich your knowledge base about the game, and as a result you produce an Input that isn't immediately obvious.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Of course, sometimes you have a flash of inspiration, when a revolutionary idea leads to tremendous improvements that surpass all polishing gains. People love TASing exactly for these emotional moments. Yet it doesn't exempt you from the need to polish this new revolutionary approach using the same methods to bring it even closer to an ideal.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Instead of reading the techniques described here you can just immediately start real TASing, so in a course of several projects you would work out your own methods. But most likely after a year of TASing you'll come to the described scheme of work.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">So, the process of creating the best Input for the segment of optimization can be basically described as a loop of fixing mistakes in previous versions of Input of the segment. A mistake is any kind of divergence from the perfect yet unknown Input. Such statement of question is very advantageous, because it means that you can gradually approach the perfect Input by making small steps that you can elaborate even without being a genius. </span><span class="rvts25">The majority of mistakes can be successfully fixed by repeated examination and modification.</span><span class="rvts21"> That is, even when you don't have any original ideas, you can achieve a success by persistence. The successful progress motivates you to continue the work and thus prepare the ground for breakthrough ideas.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">To correct a mistake in the Input of a movie you have to:</span></p>
|
||||
<ol style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Become aware of the mistake.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Conjecture a solution.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Navigate to the place.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Apply changes.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Verify the outcome.</span></li>
|
||||
</ol>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">1. </span><span class="rvts21">Realizing a mistake happens either when watching the movie in Read-Only mode or right when recording/editing the Input.</span></p>
|
||||
<div class="rvps10"><table width="100%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid; height: 15px;"><p class="rvps10"><span class="rvts41">Comment: </span><span class="rvts42">Instead of detecting a tangible mistake TASers often just assume that current segment is still improvable. It's always wise to doubt the perfectness of current result and try experimenting with the Input – sometimes you indeed find unrealized possibilities.</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><a name="loop"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">2. </span><span class="rvts21">The means of solving the mistake are either immediately obvious or are found experimentally. In rare cases you have to resort to calculations and comparisons. A correctly chosen segment usually encompasses all key factors of optimality. The information from previous or next segments is rarely required.</span></p>
|
||||
<div class="rvps10"><table width="100%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid; height: 15px;"><p class="rvps10"><span class="rvts41">Comment: </span></p>
|
||||
<p class="rvps10"><span class="rvts42">Sometimes while fixing one mistake we unwittingly create another mistake. In this case the optimization process would go in wrong direction, but fortunately such situations are extremely rare in TASing, because videogames are much more obvious and linear than real life, so player can find all factors and correct criterion of optimality. Taseditor additionally simplifies the process by data visualization.</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">3. </span><span class="rvts21">The ability to navigate to the place of making the mistake is the essential distinction between TASing and normal speedrunning. Regular players can detect the mistake, but it's TASers who always return back to correct it.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In traditional method of TASing the navigation may take noticeable amount of time and effort. Taseditor makes the navigation lightning fast.</span></p>
|
||||
<div class="rvps10"><table width="100%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid; height: 15px;"><p class="rvps10"><span class="rvts41">Comment: </span></p>
|
||||
<p class="rvps10"><span class="rvts42">Sometimes the place of making the mistake is located long before the segment where it is revealed. In this case you have to find the segment affecting the mistake and edit it according to the information given by the played segment. And in this case the speed of navigation is even more important.</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">4. </span><span class="rvts21">Applying modifications to Input is how you make your thoughts real. The less the delay between an idea and its implementation is, the better.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In traditional method of TASing the Input modification takes longer, because in addition to rewriting erroneous frames you also have to rewrite adjacent frames In Taseditor this is mostly not necessary.</span></p>
|
||||
<div class="rvps10"><table width="100%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid; height: 15px;"><p class="rvps10"><span class="rvts41">Comment: </span><span class="rvts42">В</span></p>
|
||||
<p class="rvps10"><span class="rvts42">Since any Input modification entails a change in game flow, sometimes you still have to resync the old Input that follows the place of of fixing the mistake.</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">5. </span><span class="rvts21">To see the outcome you need to resume playing the movie from the beginning of current segment of right from the frame of fixing the mistake. There's no need to re-check previous segments of the movie, because the mistake fixing affects only subsequent events.</span></p>
|
||||
<div class="rvps10"><table width="100%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid; height: 15px;"><p class="rvps10"><span class="rvts41">Comment: </span><span class="rvts42">Although, when you're making an entertaining playthrough instead of a pure speedrun, after fixing a mistake (e.g. making the movement trajectory more smooth) you should ensure that this correction fits it with the general sequence of in-game events, so it's advised to rewatch some previous events together with current segment.</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21">You have to watch current segment up to its end, that is, to the moment when the target event occurs, so that you can safely apply the optimality criterion. Because the correction may seem profitable at first but appear worse in the end.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">After evaluating the outcome the mistake is either considered to be fixed/non-existent, or you have to return to </span><a class="rvts27" href="TASingMethodology.html#loop">step 2</a><span class="rvts21"> and rethink the situation.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="linear-tasing"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Before Taseditor, all mistakes (both explicit and supposed) were being fixed by creating and reloading savestates. If you're not familiar with the traditional method of TASing, here's its basic principles:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">The game emulation is almost always paused. You only unpause it to rewatch finished segments.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">TASer sequentially types the Input into frames pointed by the Playback cursor. You see the outcome of the committed Input next frame (or sometimes in several frames). Experienced TASers create a new savestate after each </span><span class="rvts37">hard-to-reproduce action</span><span class="rvts21">, so they are able to return back without the need to replay the whole segment from the beginning.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">To correct a mistake, TASer returns to the supposed place of making the mistake and rerecords the whole Input, starting from the frame that needs to be changed. If there was a savestate created at this frame, you can instantly load the savestate in Read+Write mode and begin typing buttonpresses right away. But if you only have a savestate created at some distance before the frame, there are two options. </span><span class="rvts34">Option 1:</span><span class="rvts21"> load the nearest savestate in Read-Only mode and replay the movie up to the needed frame, then switch back to Read+Write mode and start the correction, thus not touching the Input in the interval from the savestate frame to the mistake frame. </span><span class="rvts34">Option 2:</span><span class="rvts21"> just load the nearest savestate in Read+Write mode and repeat the old Input by memory, thus rewriting it up to the needed frame, and then start the correction. The 2nd way is used more often, because after the nearest savestate there's usually an </span><span class="rvts37">easy-to-reproduce Input</span><span class="rvts21"> (e.g. simply holding </span><span class="rvts29">R + B</span><span class="rvts21">). Also, upon arriving to the supposed frame of the mistake, an experienced TASer mechanically creates a savestate (just in case!), so next time he will be able to return directly to the frame, without wasting time on navigation. Such a prudence makes sense, because mistakes are seldom fixed at the first attempt, usually you need to repeatedly rerecord the same section of Input, starting from about the same frame.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">The disadvantages of the traditional method clearly reveal when you need to see a distant result of your Input (for example, you press the button now, but the roulette only stops in several seconds). In such cases TASer makes a savestate before entering the Input, records the decisive Input and makes a savestate after it, then unpauses the emulator and carelessly (suboptimally) plays through the game up to the point of seeing the result. If the result is satisfactory, TASer loads the savestate made after the decisive Input and records an optimal playthrough, already being sure in successful outcome. And if the result is unsatisfactory, TASer loads the initial savestate, changes the decisive Input and repeats previous actions (creates a savestate after the Input and hastily plays up to the result). And this process may go for a long while.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">In order to copy an old Input (for example, the intricate acceleration of Mario at the beginning of every level), TASer either learns the button combination by heart or copies it in parts by making several jumps between the source and the destination. First the game is sent to the place of old Input (by loading the savestate prepared at that frame) to watch the replay in Read-Only mode and memorize a few buttonpresses, then it's sent to the current segment (by loading the latest savestate in Read+Write mode) to lay out the buttonpresses. This way sounds tiresome, but if you keep moving both savestates a bit forward after every jump, the navigation between source and destination becomes rather quick. Still, when TASers need to copy a long sequence of buttonpresses, they use an external editor of Input, allowing to copy/paste. But the downside is that switching contexts is very distracting, so often it's less troublesome to just copy the Input manually.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">To examine the current progress, TASer makes a savestate, turns off the Recording and loads the savestate left at the beginning of current level (usually it's the slot assigned to a rarely used key, such as </span><span class="rvts26">F10</span><span class="rvts21">). Then he unpaused the emulator and watches the movie like an outsider. To continue the recording, he switches to Read+Write mode and returns directly to the latest recorded frame by loading the latest savestate (usually it's the most used slot, like </span><span class="rvts26">F1</span><span class="rvts21">). If while watching TASer decides to modify the old Input, he makes a savestate at this point, switches to Read+Write and loads the just created savestate. Beforehand, you should make sure the last state of the movie is saved to both </span><span class="rvts26">F1</span><span class="rvts21"> and another slot that won't be used in your experiments with the old Input. This is necessary in case your experiments fail, so you could restore the old movie even if the </span><span class="rvts26">F1</span><span class="rvts21"> slot becomes overwritten in the course of the experiments.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">So, the majority of the 10 available slots is used for navigation between different moments of the game. Or, using Taseditor's terms, they are used for Playback cursor navigation along the movie. The 10 slots are more than enough to teleport among all places of interest, even when current segment is very large. Usually 3-5 slots are enough. Experienced TASers juggle these slots with astounding speed.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">A couple of another slots are used to store alternative strategies of playing. When you don't know which approach to playing a large segment (e.g. a whole level of the game) will be better, you first polish the 1st approach and save it to a separate slot (say, </span><span class="rvts26">F8</span><span class="rvts21">), then you polish the 2nd approach and save it to an adjacent slot (e.g. </span><span class="rvts26">F7</span><span class="rvts21">). After that you alternately load these slots (or even alternately watch the two branches of the movie) and choose the best one, save it to </span><span class="rvts26">F1</span><span class="rvts21"> and continue TASing in this branch.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">As you see, almost everything in the traditional method of TASing is done using savestates (Bookmarks). In Taseditor some of their functions are replaced by the Greenzone and the History Log, yet Bookmarks still play important role, allowing to keep alternative branches of the movie in a single project. The Playback cursor navigation now can be done faster by either drag'n'drop or mouse wheel. In fact, now you don't need to put Playback cursor to the frame of modification, you can just scroll the Piano Roll to the place and change the Input by mouse.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Since the Recording is less effective than direct editing, there's no more need to constantly switch modes. Now the emulator is always in Read-Only mode.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The game is always paused, as before. But now you are seeing the outcome of your Input only when you actually want to see it. At first this may seem inconvenient (as you don't feel the habitual feedback from your keypresses), but it's actually very advantageous, because it means the higher level of independence from the game. Instead of the standard mechanism of "involvement into the gameplay" there are other mechanisms of data transmission. So in any case you will receive all needed information on how the game interprets your Input, it's just that this data stream won't continually flow into your mind, it will be delivered on command.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">And when it's really necessary, you can have an intensified feedback by switching to the third method of TASing in Taseditor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Let's review pros and cons of all three methods, one by one.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps10"><table width="100%" border="1" cellpadding="1" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid; height: 39px;"><p class="rvps10"><span class="rvts22"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">The three methods of TASing in Taseditor:</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 0px; margin-left: 50px; list-style-position: outside;">
|
||||
<li class="rvps14" style="text-indent: 0px"><a class="rvts43" href="TraditionalTASing.html">Traditional method</a></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 0px; margin-left: 55px; list-style-position: outside;">
|
||||
<li class="rvps14" style="text-indent: 0px"><span class="rvts21">navigating the Input using the Playback cursor by jumping to Bookmarks</span></li>
|
||||
<li class="rvps14" style="text-indent: 0px"><span class="rvts21">recording sequences of Input using the keyboard/joypad</span></li>
|
||||
<li class="rvps14" style="text-indent: 0px"><span class="rvts21">watching interim results of the Input automatically</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 0px; margin-left: 50px; list-style-position: outside;">
|
||||
<li class="rvps14" style="text-indent: 0px"><a class="rvts44" href="NonlinearTASing.html">Nonlinear method</a></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 0px; margin-left: 55px; list-style-position: outside;">
|
||||
<li class="rvps14" style="text-indent: 0px"><span class="rvts21">navigating the Input using the mouse</span></li>
|
||||
<li class="rvps14" style="text-indent: 0px"><span class="rvts21">editing the Input using the mouse/</span><span class="rvts21">keyboard/joypad</span></li>
|
||||
<li class="rvps14" style="text-indent: 0px"><span class="rvts21">watching interim or final results of the Input by user command</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 0px; margin-left: 50px; list-style-position: outside;">
|
||||
<li class="rvps14" style="text-indent: 0px"><a class="rvts45" href="SemiautomaticTASing.html">Semiautomatic method</a></li>
|
||||
</ul>
|
||||
<ul style="text-indent: 0px; margin-left: 55px; list-style-position: outside;">
|
||||
<li class="rvps14" style="text-indent: 0px"><span class="rvts21">navigating the Input using the mouse</span></li>
|
||||
<li class="rvps14" style="text-indent: 0px"><span class="rvts21">editing the Input using the mouse/</span><span class="rvts21">keyboard/joypad</span></li>
|
||||
<li class="rvps14" style="text-indent: 0px"><span class="rvts21">watching interim or final results of the Input </span><span class="rvts21">automatically</span></li>
|
||||
</ul>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour">Easily create Web Help sites</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,178 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>3. TASing Process</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("TASingProcess");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>3. TASing Process</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="BeginnersGuide.html">Beginner's Guide</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="BeginnersGuide.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="Toolbox.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="TASingMethodology.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">TASing Process</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">TASing is about striving for an absolute perfectness. For TASers, a game is more than just an amusement, it's an interesting and complex task.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">People enjoy solving creative tasks, because it allows them to express their individuality and improve various skills. However, complicated tasks require both inventiveness and methodicalness. This Manual describes dry and methodical side of TASing, as for inventiveness – you'll have to show it yourself in real setting.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In general, to create a perfect (or very close to perfect) playthrough of the game you have to record an imperfect walkthrough and then work on consecutive improvements of its separate parts. When every fragment of the movie is perfect, we may consider the whole TAS to be perfect as well.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The concentration of efforts on small segments of the movie is the key to success. Every working segment has to be large enough to represent an adequate subtask, but small enough to make the task simple.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Without such structuring an effective and comfortable TASing would not be possible. There's too many factors affecting the final result of the game, and some of those factors append or contradict each other. Human memory is not enough to keep and calculate all interconnections of the game factors within a large segment of the playthrough. Therefore, when TASers deal with long play sessions, they aren't different from regular players who are carried by the temptation to use the first observations as a base for making decisions. But regular players can get away with such carefree approach, while TASers would end up with a clearly imperfect walkthrough.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Thus real TASing implies that segments are small. Much smaller than a single level of a typical videogame. The whole process of TASing may be portrayed like this: a man watches the recording of his own unfinished playthrough of the game, selects a small piece of the movie and throws all forces into improving it, then selects another piece and so on until the end of the game.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Of course, it's an incomplete picture, because besides the movie editing TASers also research and experiment with the game (to expose hidden factors) and do many other things. But that's beyond the scope of this Guide.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The skill of choosing adequate segments comes with experience. Many TASers don't even think what makes them spontaneously focus on a segment of the game and unconsciously limit the beginning and the end of current work. Some believe that they simply record the movie frame-by-frame in succession, but if you watch it from outside you can note that those repeated rerecords occur within a window of 20-200 frames, and the window goes forward the movie by making jumps (the end of previous segment becomes the beginning of next segment). Consider watching live stream videos of TASing, and you'll see certain regularities in handling savestates.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Here we'll try to analyze the behavior, in order to learn how to define current segment limits sensibly. And then practical TASing will make you do it mechanically.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">An adequate segment (subtask) is supposed to give TASer a consistent goal and simple means to reach it.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The </span><span class="rvts25">goal</span><span class="rvts21"> of a segment playthrough is usually to achieve certain in-game event. For example, the goal of playing through the whole game is the event when "THE END" text appears on the screen. The goal of one level can be such event as "the value of the level counter in RAM was increased" or simply "the screen faded at the end of current level". And the goal of a small segment may be something like "the character successfully landed on the other side of the pit". These intermediate goals are defined by the context.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Based on the goal, TASer defines the </span><span class="rvts25">optimality criterion</span><span class="rvts21"> in mind. The criterion is the rule which let's you compare any two versions of playing through the current segment of the game. When you're TASing, it's not enough to simply reach the goal, you have to try many approaches to reaching it, and then choose the best approach of all. For example, in a speedrun the best approach to playing a segment is usually the one in which the target event occurs as early as possible. E.g. if the 1st approach to playing the segment made the event occur at frame 350, and the 2nd approach made it appear at frame 340, then the 2nd approach is better than the 1st, and the final movie should contain exactly the 2nd approach.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">There are too many </span><span class="rvts25">means</span><span class="rvts21"> for reaching the target event. In theory, any gameplay aspect (including those not planned by developers) may help or impede the progress in some way. So, to cope with this vague multitude of possibilities you should regard all aspects of the game as </span><span class="rvts21">optimality factors</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/smb-zigzag.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">An </span><span class="rvts25">optimality factor</span><span class="rvts21"> is an aspect of the game that directly affects optimality of playing current segment. The word "directly" implies a monotonous dependence of outcome from applying the factor. For example, on this picture there's no monotonous dependence between the distance to finish and the duration of holding </span><span class="rvts29">Right</span><span class="rvts21">. Pressing the same </span><span class="rvts29">R</span><span class="rvts21"> button either makes Mario be closer to the finish, or moves him away, depending on his position.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When people perceive such segment in a whole, it's difficult to guess the best moment to release the </span><span class="rvts29">R</span><span class="rvts21"> button, when to press the </span><span class="rvts29">L</span><span class="rvts21"> button and so on. So, in order to simplify the understanding of complex dependencies (and thus reveal factors), such segments should be broken into several subsegments.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Correct statement of question usually cuts off many irrelevant possibilities. For example, regular player could wait until the difficult enemy character walks away, but in a speedrun such tactic is not considered.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Thus even in an open-world game TASer is left with a limited set of useful actions and in-game indicators that must be followed while polishing one segment. And the less the segment is, the more limited is this set, so it's easier to find an ideal sequence of actions by going over combinations of factors.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">On the other hand, the less the segment is, the less its goal intersects with the final goal of the TAS. The final goal is to make perfect walkthrough, e.g. the fastest in the world (which means the frame counter at the end of the movie should be as low as possible). But in terms of every specific segment the goal may be completely different, sometimes even opposite (for example, to stay in bonus stage as long as possible, which then grants time saving at another point of the game). That's why in very small segments the optimality criterion is not used, and playing such micro-segment is only evaluated as a part of a full-fledged segment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">For example, when your character is jumping over a pit and shooting enemies at the same time, every bullet release can be considered a separate subsegment (so it becomes easy to isolate such factors as "recharge timer", "max 3 bullets on screen" and so on). But then, when comparing approaches, you should compare different versions of jumping over the pit. Even if the 1st approach to jumping (which ends at the frame 350) allowed you to shoot two enemies and the 2nd approach (which ends at frame 340) allowed to shoot only single enemy, you are supposed to choose the 2nd approach, because the optimality criterion of the unbroken segment fits the final goal of the speedrun better.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">While TASing you have to maintain an optimal balance between the necessity to decrease segments in order to grasp factors and the need to increase them in order to use a relevant criterion. This skill comes with time, so don't sweat it and just rely on your intuition.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps10"><table width="100%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td valign="top" style="border-color: #000000; border-style: solid; height: 160px;"><p class="rvps10"><span class="rvts21">Let's have an example when the segment is too large. In a Super Mario Bros speedrun you are expected to reach the end of World 1-1 as fast as possible, which means you have to maximize the X coordinate of the character moving from left to right. The basic premise is that at the beginning of the level the X value equals zero and at the end of the level it is one thousand. Using gamepad buttons you can influence the coordinate in various ways.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If we take the whole level from the moment </span><span class="rvts34">X = 0</span><span class="rvts21"> to the event </span><span class="rvts34">X = 1000</span><span class="rvts21"> as our working segment, we can immediately see the optimality criterion (the best approach will be the one with minimal value of the frame counter when </span><span class="rvts34">X >= 1000</span><span class="rvts21">), but we can't see definite factors. How exactly we're supposed to press buttons to get the </span><span class="rvts34">X = 1000</span><span class="rvts21"> within minimal number of frames? Well, we can apply a regular player's logic and intuition. When we press the </span><span class="rvts29">R</span><span class="rvts21"> button, the X coordinate usually increases, and with the </span><span class="rvts29">L</span><span class="rvts21"> button it decreases. So the most obvious decision is to hold the </span><span class="rvts29">R</span><span class="rvts21"> button and see how many frames is needed to grow the value of X to one thousand. When testing such approach in emulator, it appears that Mario is hampered by obstacles and the X coordinate does not grow, even though the </span><span class="rvts29">R</span><span class="rvts21"> button is held. This way a new factor comes to light – the need to jump over obstacles and pits. Using the </span><span class="rvts29">A</span><span class="rvts21"> button Mario eventually reaches the </span><span class="rvts34">X = 1000</span><span class="rvts21"> event, and the optimality criterion can eliminate all alternative playthroughs where the </span><span class="rvts29">A</span><span class="rvts21"> button presses were ill-timed (e.g. where Mario stumbled over edges of pipes, the frame counter at the end of the segment was higher).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Now the player (or rather, TASer who is stuck in player's mindset) may think that all factors are applied and the segment is perfect. But it isn't. Super Mario Bros has somewhat complex physics engine. The X coordinate is influenced by current horizontal speed, and speed is influenced by acceleration. Acceleration is affected by the </span><span class="rvts29">B</span><span class="rvts21"> button, skidding, Mario's direction and air-ground state. There are also teleporter pipes and useful glitches like the "flagpole glitch" and so on. A lot of things to bear in mind. But human working memory can only store </span><a class="rvts27" href="http://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two" target="_blank">about 7 objects</a><span class="rvts21">, thus some factors inevitably slip away when you're editing Input on large segment. You'd better shrink the segment to such a scale which reveals factors individually or in a small group.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If we focus on the segment from </span><span class="rvts34">X = 0</span><span class="rvts21"> to </span><span class="rvts34">X = 100</span><span class="rvts21">, the optimality criterion will be the same, but now it also becomes obvious that in the first half of the segment Mario runs slower, and in the second half he runs with constant speed which can be considered maximum. This way you begin to appreciate the acceleration factor, so you add the RAM address to Memory Watch and start analyzing possible ways to influence the acceleration. After some experiments with turning and jumping you can discover more factors. </span><span class="rvts21">As a result, you're going to find an intricate combination of </span><span class="rvts29">R</span><span class="rvts21">, </span><span class="rvts29">L</span><span class="rvts21">, </span><span class="rvts29">B</span><span class="rvts21"> and </span><span class="rvts29">A</span><span class="rvts21"> buttonpresses that makes the event </span><span class="rvts34">X = 100</span><span class="rvts21"> occur faster than simply holding </span><span class="rvts29">R</span><span class="rvts21"> and </span><span class="rvts29">B</span><span class="rvts21">. And even if the new playthrough of the segment is only several frames faster than old, it's much closer to perfectness.</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps10"><table width="100%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td valign="top" style="border-color: #000000; border-style: solid; height: 426px;"><p class="rvps10"><span class="rvts21">Now let's take a look at another extreme. When segment is too small, its optimality criterion may contradict the final goal of the TAS.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">First, if you get carried away by maximizing speed and acceleration in equal intervals between </span><span class="rvts34">every next hundred of pixels</span><span class="rvts21">, you may forget about the shortcut pipe, because diving into pipes resets speed value to zero, which contradicts with the goal of current segment. In short term the diving factor is disadvantageous for a speedrunner, and its long-term profit may be overlooked when you're busy with habitual actions.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In this case the segment was chosen without much foresight, and as a consequence it sprouted wrong criterion of optimality ("the frame counter at the event </span><span class="rvts34">X = 200</span><span class="rvts21"> must be minimal"). Here the segment should end at the moment when </span><span class="rvts34">any </span><span class="rvts40">Down</span><span class="rvts34"> button press will start diving animation</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Of course such mistakes are often noticed when replaying finished movie on a fresh mind, but sometimes the situation is less obvious and is only revealed after publishing.</span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/smb-segments.gif"/></p>
|
||||
<p class="rvps10"><span class="rvts21">Second, in the same SMB game after diving into the pipe (World 1-1) you have to reach the exit to the right. It may seem necessary to start maximizing speed from the very beginning. But as you may see in the picture, within first dozen of frames it's better to hold the </span><span class="rvts29">L</span><span class="rvts21"> button instead of </span><span class="rvts29">R</span><span class="rvts21">, so that Mario lands slightly aloof from the wall that needs to be jumped over. If you hold </span><span class="rvts29">R</span><span class="rvts21"> too early, Mario will land close to the wall and will have to jump vertically, thus losing gathered speed.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This peculiarity is not so obvious when you choose optimizing the segment from the event </span><span class="rvts34">Mario appears</span><span class="rvts21"> to the </span><span class="rvts34">Mario lands</span><span class="rvts21"> event. The optimality criterion of such small segment will direct you to wrong sequence of buttonpresses.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Here you should choose the segment from the frame when </span><span class="rvts34">Mario appears</span><span class="rvts21"> to the moment of </span><span class="rvts34">overcoming the corner of the wall</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Unfortunately, even experienced TASers not always choose correct limits right away. Sometimes you have to rethink and redo, throw away results of many tests and change the scale of the segment, play the same part of the game many times again.</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">As you might have noticed, this document avoids measuring segments in real frames of the movie. Because actual size of segment varies from game to game and from stage to stage. Some parts of the game contain so little possibilities that they can last for more than a thousand of frames and still be easy to play and replay. By the way, some segments don't even need to be played more than once, since they are so simple that any successful playthrough is optimal (for instance, watching unskippable cutscenes between levels). And on the contrary, some stages of the game are supersaturated with events and factors, so you are going to sweat even over a dozen of frames.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Experienced TASers regard every segment individually (although they don't think too much about it). It's bad idea to choose the next segment by the same principle as previous, this would only work well in extremely repetitive games.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">If you want, you can limit the end of current segment by a fixed frame number (e.g. set the goal to maximize the X coordinate value when </span><span class="rvts34">the frame counter = 200</span><span class="rvts21">). But usually it's more convenient to associate the end with some small frontier of the game (like passing over a trap or defeating another enemy) – then the goal itself is going to suggest you basic means for reaching it. The task "touch a flower as fast as possible" sounds more natural (for a gamer) than the task "at the frame 300 become as close to the flower as possible".</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In the vast majority of video games the gameplay divides into "rooms", "enemy waves" and "traps", which are always separated by short periods of relaxation. Even in constantly scrolling and open-world games the level design ensures that there are intense moments and filler intervals between them. The truth is, </span><span class="rvts25">game designers also structure player's task into subtasks</span><span class="rvts21">, and in some cases TASer can even borrow the prepared segmentation. Just don't forget to critically assess it and subdivide into more subsegments when needed. Though, such subdivision will naturally take place in the process of editing Input on a excessively large segment. So TASing doesn't always require intense intellectual efforts. If you're skillful and smart, most of time you can just go with the flow and enjoy TASing no less than conventional gaming.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">All this can be compared to how writers divide their books into chapters (game levels), and chapters into paragraphs and sentences (segments) in order to aid with comfortable reading and comprehending author's ideas. A regular reader (player) is satisfied with the author's subdivision, but a literary critic (TASer) needs to be able to "read between lines" by dividing text his own way.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">For example, in Super Mario Bros every group of enemies is separated by a quiet space which doesn't require any skills, and it can be light-heartedly ran over or jumped over while holding </span><span class="rvts29">Right</span><span class="rvts21"> (granted that Mario speed is already at maximum). So you don't even need TAS tools to be perfect at these moments. These intervals are the most suitable place to set a goal – if you mark an end of the segment at such place, the optimality criterion won't contradict with final goal of TAS for sure. And usually these moments occur often enough so the segment between them is of an acceptable size.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The division to segments was always present in TASing, but Taseditor allows to accentuate the process visually. Here you can mark the beginning and the end of a segment using Markers or Bookmarks. Thanks to the visible boundaries you won't be distracted onto adjacent Input and can focus on analyzing only closest factors.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The frame of current segment beginning is usually chosen when watching a test playthrough of the current segment. When recording or watching such playthrough you already pick one or two key factors of optimality. So it's only logical to start the segment at the moment when these factors join into force or dramatically change the behavior. For example, at the beginning of every level you usually start a new segment, because that's the point where you regain the ability to move forward (after the cutscene between levels ends). So it's wise to set a Marker or a Bookmark at the beginning of every level, thus marking both the level boundary and the beginning of current work segment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">And if in the process of optimizing the segment you reveal some factors that join into force earlier than current beginning of the segment, you can always adjust the chosen boundaries of the segment, or break it in two subsegments.</span></p>
|
||||
<p class="rvps10"><a name="EndOfSegment"></a>
|
||||
<span class="rvts21">The ending frame of current segment is more mobile than the frame of beginning. When you define your goal (e.g. to make the X coordinate reach the value of 50) you can mark the end of current segment by setting a Marker/Bookmark to the frame where current imperfect playthrough accomplishes this goal. Then by polishing the Input you try to reach the goal (</span><span class="rvts34">X = 50</span><span class="rvts21">) at an earlier frame. And if in the process of modifying and testing a new Input you discover that the goal indeed can be reached earlier, you move the closing Marker/Bookmark up (to the frame of the improved end). After that you continue testing new approaches, searching for even better one until you don't feel any more potential. In traditional TASing this is exactly how the main Bookmark (storing current best playthrough of the segment) gradually moves up.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Well, sometimes you can indulge in laziness and avoid marking the end of current segment, instead you just keep the goal in mind and remember the number of the frame where the target event occurs in the best case so far. Such behavior is reasonable when the segment is very simple and you don't plan to redo it many times.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Moreover, in many platformer games where the player character has constant running speed most of segments can be played optimally from the first try (you just have to hold the </span><span class="rvts29">Right</span><span class="rvts21"> button and maybe jump over trivial obstacles). So if you don't see any obvious mistakes and don't intend to search for hidden flaws, you may as well skip the segment shaping, just proceed to next segment right away. Such simple games are especially suitable for newbie TASers, because TASing them is very similar to casual playing through videogames using savestates (when you only revise the most obvious mistakes, like falling into a pit, and ignore non-fatal roughness).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">But in complex TASes, where the mind is occupied with many optimality factors, you shouldn't hurry. To make your thought process more precise, you'd better be perfectly aware of current segment boundaries. So mark the beginning of any difficult segment with a Marker, and mark the end by setting a Bookmark every time you find an improvement (use one and the same slot). Since it's not easy to find an improvement when dealing with difficult tasks, don't expect you'll have to re-set the Bookmark too often.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you're confident you've found perfect solution of the segment, move to the next segment. Don't remove old Markers, since they may be useful in future, in case you begin doubting the perfectness of your decisions (e.g. after finding a new trick). The logic of movie dividing will most likely remain the same even after finding the new factor (the trick).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Also, if in the middle of optimization process you become confident you've found perfect Input for the first half (or a third) of current segment, you can divide the segment in two and focus on optimizing the remaining section. Such situations often rise when the initially chosen segment was too large and its logical parts naturally emerged in the process of editing the Input.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">So, if you don't like to keep things organized, you can avoid Markers and Bookmarks whatsoever, working mostly in terms of fuzzy in-game concepts and imagining segments as some emotional sequences of events. Unfortunately, the data about fuzzy goals also occupies part of human working memory, and as a result you won't have enough resources to keep all optimality factors in mind. And you won't even notice how you're losing a multitude of possibilities.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">On the contrary, if you like to keep an order, it's recommended to accompany Markers with text Notes, either before, or during, or after the optimization of the current segment. For example, make up a name for the segment or put a tag. This way you document the development of the TAS during actual TASing, give an objective meaning to the Input appearing in the process. This is especially useful when TASing in co-authorship. But even when working alone, you may notice the documentation from previous levels motivates you to carry on. It only takes seconds to type that kind of texts, and then it helps not to abandon the project.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Notes also help to better unlock the potential of tricks and bugs of the game. By writing the text you actually formalize your knowledge about the described phenomenon. When the essence of the trick is kept in your mind, you may think that you already know everything about it, and that your current TAS uses the trick the best way possible. But when you construct an objective model (a verbal description of the trick) you often find its new sides.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's not uncommon for TASVideos.org to see how one TASer read the description of a trick in the submission text written by another TASer and found a way to use the trick better than original author. There were also cases when author himself reads his recent submission, facepalms and urgently records an improvement.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Making a perfect TAS can take anything from several days to several years, depending on complexity of the chosen game. Most of that time is spent on finding an ideal sequence of buttonpresses for every segment.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Often it seems right away that current Input is already the best possible. But usually it's not so, especially if you make the conclusion judging by the external image of the emulated game instead of its internal state (Memory Watch). So it's always reasonable to suppose that current result is not perfect. If you don't see any mistakes or potential improvements at the moment, try to watch the segment together with several previous segments (e.g. watch the last half a minute of your movie), because it's possible that previous segments contain some unregistered optimality factors that have an effect on current segment. And if you still don't get any ideas, consider moving to next segment, but don't completely refuse further attempts to criticize and improve finished segments.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Rewatch the finished part of your movie from time to time – either from the very beginning, or from the beginning of current level – and try to notice imperfections. Taseditor allows to edit Input in any part of the movie while the movie is still playing, so you can quickly test any spontaneous idea right when it comes to your mind. If the new idea appears to be unsuccessful, just undo latest changes or load the Bookmark containing the last stable state of the movie.</span></p>
|
||||
<p class="rvps10"><a name="resyncing"></a>
|
||||
<span class="rvts21">And if the new idea in fact improves you TAS, after a joyful anticipation you have to ensure that all the following segments of Input sync to the game (because implementing the idea has changed the flow of the game). Most of time it's not necessary to redo all the following Input. Usually you only have to delete or insert a few frames (thus shifting all following segments up or down), or modify several segments between the place of implementing the new idea and the nearest checkpoint (the end of current level, etc). Checkpoints usually reset many in-game properties to default value (e.g. they require you to walk over specific platform, thus equalizing the Y coordinate), so after the checkpoint you old Input will sync with new timeline of the game once you adjust it to match the flow of game events.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Anyway, even in cases when you have to redo considerable parts of the movie, resyincing is much easier than TASing from zero ground, because now you know the best approach for each segment and only have to match your previous results. And sometimes you can even excel them, because, when you're doing these forced modifications in order to resync old Input, you still possess TASer's critical thinking, so you may notice another mistake or unimplemented idea by the way.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Sometimes it's like a snowslide – as the trouble grows, so grows the thrill of all the discoveries. Many ingenious speedrun overtakes were made because of noticing a small improvement in the middle of the movie, which then forced TASer to re-record the remaining half of the movie (in order to resync it using traditional method) and stumble upon new discoveries in the process. And then these new tricks appear to be useful in the first level of the game! Since the game has single engine, a trick that works in one level may be applied in another, where the similar conditions are met. Even if some conditions aren't met, sometimes you can create them by losing something less important. In the end, as the movie gets rewritten many times, the small improvement rises into large-scale progress.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You should learn not to feel sorry when you have to throw away results of your hard work. In TASing you're expected to reconsider even polished parts of the movie from time to time. The traditional method of TASing quickly makes you accustomed to inevitable losses of time, because any inattention or slipped finger requires you to rerecord part of current segment. Taseditor averts such minor losses, but doesn't change the fact that you have to retry new approaches after finding new optimality factors.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">For example, when polishing the Input near the end of World 1-3, you've suddenly found a new trick allowing you to get a mushroom, and it also appears to work in the World 1-1. Now you have to redo both 1-1, 1-3 and even 1-2, because you now play World 1-2 with big Mario. Of course, TASing the same levels second time is easier, but the fact of wasted time may dispirit you at first. Sometimes it may seem that fixing the old mistake is not worth spending additional time. At this point you'd better stop thinking too much and just choose one of the two options – either immediately start fixing, or postpone it for an indefinite period (and leave the Marker with a note describing the issue). If at the end of the project you accumulate a critical mass of such postponed plans, the movie should be called a "test run" and probably also published, at least as a WIP (work in progress). Then take some considerable rest until you feel like redoing the TAS (making an improvement).</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Despite all the difficulties, TASing can bring enjoyment both to viewers and authors. TASes are made by people who consider this kind of work to be balanced by the excitement from intermediate and final results. In many senses TASing is similar to a special meta-videogame with a unique gameplay mechanic. And until games bring fun, people play them no matter how hardcore they are.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">In the next chapter: </span><a class="rvts27" href="TASingMethodology.html">descriptions of Input optimization methods</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps10"><table width="100%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid;"><p class="rvps10"><span class="rvts25">PRACTICE: </span><span class="rvts21">Watch the imperfect playthrough of the 1st level that you made in previous chapter, and divide it into segments using Markers and your own discretion. If the movie is rather long, no need to structure it all, you just have to feel the principles.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Estimated time: </span><span class="rvts21">5-10 minutes.</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/help-authoring-tool">Free help authoring environment</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,135 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>Title</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("Title");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>Title</h1>
|
||||
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="BeginnersGuide.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p class="rvps5"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps5"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps4"><span class="rvts8">TAS Editor 1.0</span></p>
|
||||
<p class="rvps1"><span class="rvts9"><br/></span></p>
|
||||
<p class="rvps1"><span class="rvts9"><br/></span></p>
|
||||
<p class="rvps1"><span class="rvts9">Welcome to the TAS Editor Manual!</span></p>
|
||||
<p class="rvps1"><span class="rvts9"><br/></span></p>
|
||||
<div class="rvps1"><table width="90%" border="0" cellpadding="0" cellspacing="0" style="border-width: 0px;">
|
||||
<tr valign="top">
|
||||
<td><p class="rvps1"><span class="rvts9">Taseditor is an Integrated development environment dedicated to TASing.</span></p>
|
||||
<p class="rvps1"><span class="rvts9">Playing videogames in Taseditor resembles both interactive programming and drawing notes by mouse in a music editor.</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps4"><span class="rvts6"><br/></span></p>
|
||||
<div class="rvps4"><table width="700" border="1" cellpadding="8" cellspacing="0" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="bottom">
|
||||
<td style="border-color: #000000; border-style: solid; border-bottom: none; background-color: #ffe5e3; width: 32%; height: 20px;"><p class="rvps6"><a class="rvts15" href="BeginnersGuide.html">Beginner's Guide</a></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-bottom: none; background-color: #d9ffdd; width: 32%; height: 20px;"><p class="rvps6"><a class="rvts15" href="Reference.html">Reference</a></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-bottom: none; background-color: #d0ffff; width: 30%; height: 20px;"><p class="rvps6"><a class="rvts16" href="TASEditorInside.html">TAS Editor Inside</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid; border-top: none; border-bottom: none; background-color: #ffe5e3; width: 32%; height: 38px;"><p class="rvps5"><span class="rvts14">If you're seeing the Manual for the first time, please study this whole course</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-top: none; border-bottom: none; background-color: #d9ffdd; width: 32%; height: 38px;"><p class="rvps5"><span class="rvts14">Look here when you need to know comprehensive specifications about limits and possibilities of TAS Editor</span></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-top: none; border-bottom: none; background-color: #d0ffff; width: 30%; height: 38px;"><p class="rvps5"><span class="rvts14">Read these docs when you wish to learn details of the system</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid; border-top: none; background-color: #ffe5e3; width: 32%; height: 163px;"><p class="rvps7"><a class="rvts12" href="Introduction.html">Introduction</a></p>
|
||||
<p class="rvps7"><a class="rvts12" href="ProgramInterface.html">Program Interface</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="TASingProcess.html">TASing Process</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="TASingMethodology.html">TASing Methodology</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="ProgramCustomization.html">Program Customization</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="AdvancedFeatures.html">Advanced Features</a></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-top: none; background-color: #d9ffdd; width: 32%; height: 163px;"><p class="rvps7"><a class="rvts13" href="Glossary.html">Glossary</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="Controls.html">Controls</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="Navigation.html">Navigation</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="Operations.html">Operations</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="LuaAPI.html">Lua API</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="FAQ.html">FAQ</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="SpeedrunningSynopsis.html">Speedrunning Synopsis</a></p>
|
||||
</td>
|
||||
<td style="border-color: #000000; border-style: solid; border-top: none; background-color: #d0ffff; width: 30%; height: 163px;"><p class="rvps7"><a class="rvts13" href="Ideas.html">Ideas</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="Implementation.html">Implementation</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="MistakeProofing.html">Mistake-proofing</a></p>
|
||||
<p class="rvps7"><a class="rvts13" href="FM3format.html">FM3 format</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps4"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps4"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps4"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps3"><span class="rvts6">Author of TAS Editor v1.0: AnS</span></p>
|
||||
<p class="rvps3"><span class="rvts6">Assistance in testing: feos</span></p>
|
||||
<p class="rvps3"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps3"><span class="rvts6">Author of this Manual: AnS</span></p>
|
||||
<p class="rvps3"><span class="rvts6">English translation: AnS, feos</span></p>
|
||||
<p class="rvps3"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps3"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps3"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps3"><span class="rvts6"><br/></span></p>
|
||||
<p class="rvps3"><span class="rvts6"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com">Free HTML Help documentation generator</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,278 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>2.2. Toolbox</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("Toolbox");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>2.2. Toolbox</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="BeginnersGuide.html">Beginner's Guide</a> ›› <a href="ProgramInterface.html">2. Program Interface</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="ProgramInterface.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="PianoRoll.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="TASingProcess.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Toolbox</span></p>
|
||||
<p class="rvps5"><span class="rvts36"><br/></span></p>
|
||||
<p class="rvps5"><img alt="" style="padding : 1px;" src="lib/taseditor-smb.png"/></p>
|
||||
<p class="rvps21"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Toolbox consists of 7 sections:</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps14"><a class="rvts38" href="Toolbox.html#playback">Playback</a></li>
|
||||
<li class="rvps14"><a class="rvts38" href="Toolbox.html#recorder">Recorder</a></li>
|
||||
<li class="rvps14"><a class="rvts38" href="Toolbox.html#splicer">Splicer</a></li>
|
||||
<li class="rvps14"><a class="rvts38" href="Toolbox.html#lua">Lua</a></li>
|
||||
<li class="rvps14"><a class="rvts38" href="Toolbox.html#bookmarks">Bookmarks</a></li>
|
||||
<li class="rvps14"><a class="rvts38" href="Toolbox.html#history">History</a></li>
|
||||
<li class="rvps14"><a class="rvts38" href="Toolbox.html#selection">Selection cursor navigation buttons</a></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="playback"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-playback.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">The top section is allotted to the Playback controls. The </span><span class="rvts25">Playback</span><span class="rvts21"> is the component of Taseditor dedicated to handle the game emulation: keep it paused, replay in any direction, rewind to desired frame and so on. It allows to treat video games as straightforwardly as if they were regular video recordings, disregarding the interactivity element inherent to them.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">There are 5 buttons at the top of the window.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts29">||</span><span class="rvts21">" button (pause/resume) is simple graphical analog of the </span><span class="rvts26">Pause Emulation</span><span class="rvts21"> hotkey. When you click it, the game emulation either pauses or resumes. However, if your mouse has a middle button, it's easier to press it instead of clicking the "</span><span class="rvts29">||</span><span class="rvts21">" button, in this case you won't need to move the mouse cursor to the Playback section.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts29">></span><span class="rvts21">" button (step forward / advance 1 frame) moves the light-blue cursor 1 frame down, forcing FCEUX to emulate one frame if necessary. You can either click that button or click and hold it to make several steps forward. This button's keyboard analog is </span><span class="rvts30">Shift + Down</span><span class="rvts21">. If your mouse has a wheel, it's easier to hold the right mouse button and scroll the wheel 1 step down instead of using the "</span><span class="rvts29">></span><span class="rvts21">" button.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts29"><</span><span class="rvts21">" button (step back / rewind 1 frame) moves the Playback cursor 1 frame up, displaying the previous frame's events in the FCEUX window. You can hold the button as well, when you wish to go several frames back. This button has its hotkey </span><span class="rvts26">Frame Rewind</span><span class="rvts21"> (mapped to </span><span class="rvts26">Backspace</span><span class="rvts21"> key by default), and has a keyboard analog: </span><span class="rvts30">Shift + Up</span><span class="rvts21">. If your mouse has a wheel, it's easier to hold the right mouse button and scroll the wheel 1 step up instead of using "</span><span class="rvts29"><</span><span class="rvts21">" button.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts29"><<</span><span class="rvts21">" button (fast rewind) also moves the Playback cursor back, just not by 1 frame but by multiple frames at once. This button moves the light-blue cursor to the frame where the nearest upper Marker is located. In the above picture, if you press the "</span><span class="rvts29"><<</span><span class="rvts21">", the light-blue cursor will jump to frame 12 (where the Marker 1 is set). Using this button you may quickly go back to the beginning of the edited segment or to any other past moment of the movie. The keyboard analog for this button is </span><span class="rvts30">Shift + Page Up</span><span class="rvts21">. You can also hold it – the light-blue cursor will rapidly jump on Markers up in the Piano Roll, and in the meantime you can look for the desired fragment of the movie by watching FCEUX screen.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts29">>></span><span class="rvts21">" button (fast forward) jumps on Markers forward. In the above picture, if you press the "</span><span class="rvts29">>></span><span class="rvts21">", the light-blue cursor will jump to frame 22 (where the Marker 2 is located). With this button you can rapidly skip to the game events forward in the movie. But in case the next Marker is out of the Greenzone range, emulator would need some time to process the unknown frames, so such jump may take some time. This button's keyboard analog is </span><span class="rvts30">Shift + Page Down</span><span class="rvts21">. You can click and hold this button as well.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">As an experiment, try to make a test movie of about 1000 frames in size and set a dozen of Markers, one per every 30-50 frames. Then hold </span><span class="rvts30">Shift</span><span class="rvts21"> and tap some </span><span class="rvts25">Page Up</span><span class="rvts21"> / </span><span class="rvts25">Page Down</span><span class="rvts21"> keys to feel the convenience of the fast scrolling. Alternatively you can roll the mouse wheel while holding the </span><span class="rvts30">Shift</span><span class="rvts21"> key.</span></p>
|
||||
<p class="rvps10"><a name="progressbar"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Below these 5 buttons you can see a progress bar and three checkboxes.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The </span><span class="rvts25">Progress bar</span><span class="rvts21"> helps to estimate the time needed for Playback seeking. Immediate jumps to any frame are only possible after FCEUX emulated the game up to the target frame by applying your movie as a game Input to get the actual game state for the frame. After the actual game state was rendered at least once, it is saved into the Greenzone, so next time the emulator can instantly jump to that frame, granted that Input above the frame didn't change. If the Input was changed, a new emulation attempt is required, because even the smallest change in buttonpresses may cause serious changes in the gameplay chronology. Thus after every such change the Greenzone is automatically truncated, removing the data of all those frames that might be affected by the new Input. These frames must be emulated again, and it takes some time.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">So, when you send the Playback cursor to a frame far from the Greenzone, instead of immediate jump the light-blue cursor starts </span><span class="rvts37">seeking</span><span class="rvts21"> to that frame. A shadow of the light-blue cursor will be blinking at the target line of the Piano Roll, and the game images on the FCEUX screen will rapidly change as the Playback cursor runs to the target.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In this case you'll have to wait. The seek time depends on the distance between the target frame and the end of the Greenzone, on your computer power and a few other factors. The progress bar helps to estimate the waiting time. If you don't want to wait, left-click on the progress bar (in addition to being an indicator, it's also a button) or use the </span><span class="rvts26">Cancel Seeking</span><span class="rvts21"> hotkey (</span><span class="rvts26">Esc</span><span class="rvts21"> by default). Then the target frame will quit blinking, the light-blue cursor will stop and the emulation will be paused.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">While Playback is seeking you may change the target by clicking on the desired frame row in the icons column of the Piano Roll. If you pause the emulator during seeking, the light-blue cursor will freeze and the target frame blinking will slow down, but the seeking won't be cancelled – when you unpause, the Playback cursor will continue running to the target and stop automatically after hitting it.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Progress bar is also used when loading and saving Taseditor project files to disk.</span></p>
|
||||
<p class="rvps10"><a name="turbo-seek"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts25">Turbo seek</span><span class="rvts21">" checkbox allows to change the seeking speed. When the Turbo is on, FCEUX emulates the game on the highest speed possible, reducing the seeking time tenfold. So, if you seek to a distant frame, check that option. But during the TASing process its often necessary to see all the intermediate frames, not just the last one. In such cases you should uncheck the checkbox and maybe even slow down the emulation with the </span><span class="rvts26">-</span><span class="rvts21"> and </span><span class="rvts26">=</span><span class="rvts21"> hotkeys to ensure you're not missing any important detail of the gameplay.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts25">Follow cursor</span><span class="rvts21">" checkbox forces the Piano Roll to follow the movement of the Playback cursor and autoscroll the view so that the light-blue cursor is always visible. This allows you to observe the Input played back when the emulator is unpaused. But when you edit the movie you should uncheck this option to prevent the Piano Roll from running away from the edited spot.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts25">Auto-restore last position</span><span class="rvts21">" checkbox makes the Playback automatically start seeking when the Playback cursor was moved back by the Greenzone. Every time you change an Input, the Greenzone is truncated after the first changed frame, forgetting old events that became irrelevant after that change. The Playback cursor must always be inside the Greenzone, so it steps back along with it. With the auto-restore checkbox you can instantly see new events on these frames. When the checkbox is checked, any Input modification triggers the replaying of the changed segment, helping you to compare different scenarios of the game events.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Thanks to auto-restore TASers can focus on Input editing and rapidly go over many approaches to playing current segment of the movie. This method of TASing will be described later.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="recorder"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-recorder.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">Below the Playback you can find the Recorder section. The </span><span class="rvts25">Recorder </span><span class="rvts21">is used to record buttons Input from keyboard (or gamepad) into the movie, just like in regular playing using any emulator.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts25">Recording</span><span class="rvts21">" checkbox turns the Recording mode on and off. Before you start recording any physical keypresses, make sure the Playback cursor is on the frame you want to record from. Then either press the "</span><span class="rvts26">Toggle Read-only</span><span class="rvts21">" hotkey (</span><span class="rvts26">Q</span><span class="rvts21"> key by default), or click the Recording checkbox. The word "Recording" will appear in the TAS Editor window caption, and the message "Movie is now Read+Write" will appear on the FCEUX screen. Now you can either unpause the emulator and play the game normally, or type the buttons frame-by-frame using the </span><span class="rvts26">Frame Advance</span><span class="rvts21"> hotkey. As the playback goes forward, the movie will fill with the data on the buttons you press.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You may rerecord the same segment of the movie multiple times, overwriting the old button log with new buttonpresses data. If you don't like how a segment was played (e.g. the character fell into a pit), put the Playback cursor before the frame where you made wrong buttonpresses (e.g. the </span><span class="rvts29">A</span><span class="rvts21"> button was pressed too late) and resume Recording, this time pressing buttons properly.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When the segment is ready, turn the Recording mode off to prevent accidental erasing of the Input when replaying the movie. Uncheck the checkbox by mouse click or via the hotkey. When TASing in Taseditor, the Recording checkbox is usually unchecked, because direct Input editing is preferred to Recording.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">It's recommended to rationally combine the Recorder features with those of the Piano Roll. For long and easy segments of the game it may be convenient to record buttonpresses from the keyboard or a handy USB-gamepad, but for small dislocated edits the mouse is way better.</span></p>
|
||||
<p class="rvps10"><a name="superimpose"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts25">Superimpose</span><span class="rvts21">" checkbox in the Recorder section allows to combine the existing Input with the newly recorded data on the same segment of the movie. For example, you can draw the </span><span class="rvts29">R</span><span class="rvts21"> buttonpresses on rather long segment with a single mouse stroke, to make the character run right. Then you can enable the "Superimpose" option, turn on Recording and play the game by pressing only jump and shoot buttons, without the need to hold </span><span class="rvts29">Right</span><span class="rvts21">. The character in the game will still run right, jumping and shooting on command.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Unlike other checkboxes, the "Superimpose" option has three possible states. In addition to "enabled" and "disabled" it can also be in an interim state between these two. The third state works like this: when the player presses some gamepad buttons during Recording, these buttons are recorded in place of old Input. But if the player presses no buttons during Recording, the old Input on these frames is not overwritten.</span></p>
|
||||
<p class="rvps10"><a name="UsePattern"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts25">Use pattern</span><span class="rvts21">" checkbox applies current pattern to the process of buttons Recording. The name of the current pattern can be seen in the upper right corner of TAS Editor window (the last item of the main menu). If you click this menu item, a pop-down menu will appear, allowing you to choose another pattern from the list.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Patterns are used to speed up the process of entering monotonous buttonpresses and releases. For example, when you need to shoot at maximum rate (that is, alternate 1 frame of pressing </span><span class="rvts29">B</span><span class="rvts21"> and 1 frame when </span><span class="rvts29">B</span><span class="rvts21"> is released), you can just choose the "</span><span class="rvts37">Alternating (1010...)</span><span class="rvts21">" pattern and hold the </span><span class="rvts29">B</span><span class="rvts21"> button without caring about manual mashing. Thanks to the pattern, the </span><span class="rvts29">B</span><span class="rvts21"> buttonpresses will be recorded only for every other frame.</span></p>
|
||||
<p class="rvps10"><a name="multitracking"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Besides the checkboxes the Recorder section also contains radio buttons that implement the </span><span class="rvts25">multitracking</span><span class="rvts21"> feature.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Multitrack Recording</span><span class="rvts21"> greatly simplifies the traditional method of TASing games made for 2 or more players. Instead of pressing buttons of both gamepads at once, you can record a short segment of controlling the Player 1 and then record actions of Player 2 on the same segment of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">By default the Recorder is set to recording "All" pads. You can choose a single pad by clicking the respective radio button ("1P", "2P", etc – the number of available gamepads depends on your project type). You can also use the "</span><span class="rvts26">Switch current Multitracking mode</span><span class="rvts21">" hotkey (</span><span class="rvts26">W</span><span class="rvts21"> key by default). Now during the Recording the emulator will accept only the chosen player's buttonpresses, and the Piano Roll columns for other pads won't change even if you accidentally press another player's buttons.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="splicer"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-splicer.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">The </span><span class="rvts25">Splicer</span><span class="rvts21"> section comes after the Recorder. It's dedicated to displaying the most necessary data used in non-linear editing of the movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Despite the similar sounding, editing TASes is totally different from using a non-linear video editing software, because Taseditor only allows you to edit Input, not the finished video footage (Output). The resulting video stream is built by the game itself.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In this section you can see the information on current Selection size: how many rows and columns are covered. With this info you can use the Selection as a measuring scale (ruler). E.g. to find the temporal distance between two in-game events, click the frame of the first event and stretch the Selection to the frame of another – all those frames will be selected, and in the Splicer section the message "Selection: </span><span class="rvts37">N</span><span class="rvts21"> rows, </span><span class="rvts37">M</span><span class="rvts21"> columns" will tell you the number of frames in question.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Also, here is the info about the Clipboard contents: whether it contains an Input that could be pasted to any place in the movie. When an Input is copied to the Clipboard, this line displays total amount of frames copied. The Clipboard data is stored independently of Taseditor, and it's kept there even after you close FCEUX, until some other application copies its own data to the Clipboard.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "Splicer" section has no controls, because all Input splicing commands are kept in the Edit menu item and are assigned with accelerator keys. In actual TASing process it's recommended to use the keyboard combinations, because they're easy to remember and the working speed increases immensely.</span></p>
|
||||
<p class="rvps10"><a name="splicing-operations"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">The list of all Editing functions</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Basically, these are the standard functions of any text editor, but in Taseditor they can be applied to Input in the middle of emulation, which allows to analyze the results on the fly and flexibly tune your plans.</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts22">Copy </span><span class="rvts21">(</span><span class="rvts30">Ctrl + C</span><span class="rvts21">) – copies the Input of all selected frames to the Clipboard.</span></li>
|
||||
<li class="rvps10"><span class="rvts22">Paste </span><span class="rvts21">(</span><span class="rvts30">Ctrl + V</span><span class="rvts21">) – pastes the Clipboard contents into the movie, starting from the position of the Selection cursor. Old Input data on the frames is replaced by the new data, or combined together if the "Superimpose" option in Recorder section is checked.</span></li>
|
||||
<li class="rvps10"><span class="rvts22">Paste Insert </span><span class="rvts21">(</span><span class="rvts30">Ctrl + </span><span class="rvts30">Shift</span><span class="rvts30"> + </span><span class="rvts30">V</span><span class="rvts21">) – expands the movie and inserts the Clipboard content at the position of the Selection cursor. Old movie data is shifted down.</span></li>
|
||||
<li class="rvps10"><span class="rvts22">Clear </span><span class="rvts21">(</span><span class="rvts30">Delete</span><span class="rvts21">) – clears selected frames, removing all buttonpresses from them.</span></li>
|
||||
<li class="rvps10"><span class="rvts22">Cut </span><span class="rvts21">(</span><span class="rvts30">Ctrl + X</span><span class="rvts21">) = </span><span class="rvts22">Copy</span><span class="rvts21"> + </span><span class="rvts22">Clear</span><span class="rvts21"> – copies Input from the selected movie segment and clears the segment.</span></li>
|
||||
<li class="rvps10"><span class="rvts22">Delete </span><span class="rvts21">(</span><span class="rvts30">Ctrl + Delete</span><span class="rvts21">) – removes selected frames from the movie, shifting all the following frames up in their place. A handy way to move Input up.</span></li>
|
||||
<li class="rvps10"><span class="rvts22">Insert </span><span class="rvts21">(</span><span class="rvts30">Ctrl + Shift + Insert</span><span class="rvts21">) – inserts blank frame into the movie before every selected frame, shifting </span><span class="rvts21">existing</span><span class="rvts21"> Input down. A handy way to move Input down.</span></li>
|
||||
<li class="rvps10"><span class="rvts22">Clone </span><span class="rvts21">(</span><span class="rvts30">Ctrl + Insert</span><span class="rvts21">) – similar to </span><span class="rvts22">Insert</span><span class="rvts21">, but instead of blank frames it inserts a copy of selected frames. Usually this is the preferred way of </span><span class="rvts21">moving Input down.</span></li>
|
||||
<li class="rvps10"><span class="rvts22">Insert number of frames </span><span class="rvts21">(</span><span class="rvts30">Insert</span><span class="rvts21">) – allows to insert any number of frames at the position of the Selection cursor. When you press the </span><span class="rvts30">Insert</span><span class="rvts21"> key, a small window pops up and prompts you to enter the number of frames to insert. Type the number and click OK. If you change your mind, press Cancel (Esc) to hide the window.</span></li>
|
||||
<li class="rvps10"><span class="rvts22">Truncate</span><span class="rvts21"> – removes all frames of the movie, starting from the frame next to the Selection cursor. It's a rarely used function, so it has no hotkey, it's only available through the main menu or by the right-click.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When TASing in Taseditor you're going to most often use </span><span class="rvts30">Ctrl + Delete</span><span class="rvts21"> (</span><span class="rvts22">Delete Frames</span><span class="rvts21">) and </span><span class="rvts30">Ctrl + Insert</span><span class="rvts21"> (</span><span class="rvts22">Clone Frames</span><span class="rvts21">) to quickly move edited segments up/down in the frame list, thus performing certain in-game actions sooner or later.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Unlike FCEUX hotkeys, these key combinations can't be reassigned, so if you have some other emulator functions assigned to </span><span class="rvts30">Ctrl</span><span class="rvts21">, </span><span class="rvts30">Insert</span><span class="rvts21"> or </span><span class="rvts30">Delete</span><span class="rvts21">, you'll have to change emulator settings.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="lua"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-lua.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">Under the Splicer you can see a small </span><span class="rvts25">Lua</span><span class="rvts21"> section.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">There is one inactive button and one checkbox here, their purpose will be described later. While you're not familiar with Lua scripting, you won't need this section.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Lua scripting language allows to automate some part of TASers' work and to create your own plug-ins for Taseditor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><a name="bookmarks"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-bookmarks.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">Then goes the Bookmarks/Branches section. We should speak of </span><span class="rvts21">Bookmarks</span><span class="rvts21"> at a greater length here.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Bookmarks</span><span class="rvts21"> are the evolution of emulator savestates. Before Taseditor the savestates were the main way to navigate the movie, with their help TASers return back to the place of a mistake and fix it. In Taseditor there are better navigation methods, but this one was left too.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">You have 10 slots for Bookmarks in your disposal. These are numbered with digits from 0 to 9. You can set any of 10 Bookmarks to any movie frame, pointing to that frame with the Playback cursor beforehand.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Example 1. </span><span class="rvts21">Set the light-blue cursor to the frame you want a Bookmark at, and make an emulator savestate (</span><span class="rvts30">Shift</span><span class="rvts21"> + </span><span class="rvts26">F1</span><span class="rvts21">-</span><span class="rvts26">F10</span><span class="rvts21"> by default). For example, press </span><span class="rvts26">Shift + F1</span><span class="rvts21"> to set the first Bookmark. It will appear in the Bookmarks List, flashing one time with the red light.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Example 2. </span><span class="rvts21">Set the light-blue cursor to the needed frame and right-click on any line in the Bookmarks List. For example, right-click on the line 2 to create the Bookmark in slot 2.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can undo the Bookmark set operations with </span><span class="rvts30">Ctrl + Z</span><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Bookmarks List displays the frame number where each Bookmark is sat, and the real time of setting the Bookmark. If you hover the mouse cursor over a Bookmark's time (the right column in the List), you'll see the screenshot from the game.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When setting a Bookmark, Taseditor saves to the chosen slot the data about the Playback cursor position and entire movie contents. Now at any time you can either make a "</span><span class="rvts37">spatial jump to the Bookmark</span><span class="rvts21">" (simply returning the Playback cursor to the bookmarked place), or make a "</span><span class="rvts37">temporal jump to the Bookmark</span><span class="rvts21">", returning the whole movie to the state saved in the Bookmark slot.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To jump to a Bookmark in space, left-click on the </span><span class="rvts25">left half</span><span class="rvts21"> of the needed Bookmark (the pale-colored half of the Bookmarks List where the frame number is displayed). Or use the keyboard – press the corresponding number key (numeric keys </span><span class="rvts26">0</span><span class="rvts21">-</span><span class="rvts26">9</span><span class="rvts21"> are under the </span><span class="rvts26">F1</span><span class="rvts21">-</span><span class="rvts26">F10</span><span class="rvts21"> keys). You can notice the jump by seeing the light-blue cursor movement in the Piano Roll and by green flash in the Bookmarks List.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To jump to a Bookmark in time, left-click on the </span><span class="rvts25">right half</span><span class="rvts21"> of the needed Bookmark (the brighter-colored half of the Bookmark List where the time is displayed). Or load the corresponding emulator savestate (keys </span><span class="rvts26">F1</span><span class="rvts21">-</span><span class="rvts26">F10</span><span class="rvts21"> by default). If any Input was changed during this jump in time (since it returns to its state at the time of creating the Bookmark), the Bookmark flashes with blue color, otherwise it flashes green, like in a simple Playback cursor jump. As usual, when an Input changes, the Greenzone truncates automatically. And of course you can undo the change using </span><span class="rvts30">Ctrl + Z</span><span class="rvts21"> to revert the movie to its state before the time jump to the Bookmark.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">So, part of the Bookmarks may be used to speed up your movie navigation. For example, set a Bookmark at the beginning of current game level to be able to return the Playback cursor to that frame and replay the level events anytime. You could use a Marker for the same purpose, but the advantage of the Bookmarks is that you can instantly jump to a Bookmark from any remote segment of the movie, no matter how many Markers are set in between, while to reach the desired Marker you would have to jump on the neighbor Markers.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Another part of the Bookmarks can be used to store alternative approaches to playing the same game segment. When TASing complex games we can't always immediately evaluate the optimality of a playing strategy. Sometimes TASer needs to record several different versions of playing the same segment and then carefully compare the resulting movies, choosing the most appropriate one to be left in the final TAS.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In traditional TASing every such movie is kept in separate file, so to switch between the alternative movies (or rather between alternative branches of your main movie) you need to load corresponding savestates created when recording these playthroughs.</span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-branches.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">In Taseditor all saved branches of the movie are held together, forming the hierarchy called the </span><span class="rvts25">Branches Tree</span><span class="rvts21">. To switch between the alternative branches you need to load the corresponding Bookmark, thus returning the working movie to one of the prepared versions. Basically, it's the same as before. But now we can visualize all alternative playthroughs in a graph scheme to facilitate TASer's comprehension of the multitude of options.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you test a couple of approaches to playing the 2nd level of the game, the 1st level playthrough remains the same in both branches, so the discrepancy of the Input starts not from the beginning, but from the 2nd level. So, if you left the Bookmark 1 before the beginning of the 2nd level, you'll see the fork in the graph starting from the card 1.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">As an experiment, create a new project and make a very short movie. Then set the Playback cursor to the end of existing Input and save a Bookmark into the first slot (</span><span class="rvts26">Shift + F1</span><span class="rvts21">). Advance a few frames after that Bookmark and draw some buttonpresses, then play this new Input and save to Bookmark 2 (</span><span class="rvts26">Shift + F2</span><span class="rvts21">). Now return the movie to the first Bookmark state (press </span><span class="rvts26">F1</span><span class="rvts21">) and add some buttonpresses after the bookmarked frame again, but make sure they are different from the last time. Play this new Input to the end and save the 3rd Bookmark (</span><span class="rvts26">Shift + F3</span><span class="rvts21">) or any other.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Now click on the header of the Bookmarks section ("Bookmarks/Branches" label). The Bookmarks List view will change to the Branches Tree view. If the third Bookmark movie differs from the second Bookmark movie, and the difference starts after the first Bookmark frame, you'll see the picture similar to the above. The cloudlet symbolizes the beginning of the movie (the root of the hierarchy). Bookmarks are presented with cards of corresponding numbers. The blue-colored number stands for the current Bookmark containing the branch that corresponds to working movie (currently displayed in the Piano Roll). If the working movie was changed after saving/loading this Bookmark, you'll see the fireball descending from the current Bookmark.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Red lines connect those Bookmarks that are compatible with the chronology of current working movie. For example, if you set one Bookmark at the end of every level, all such Bookmarks will be sitting on one red line, because the movie of every next Bookmark is actually composed from the movie of previous Bookmark plus an additional level playthrough.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Branches Tree also displays current Playback cursor position. Try dragging the cursor in the Piano Roll up and down, or just play the whole movie back (press </span><span class="rvts30">Shift + Home</span><span class="rvts21"> and unpause the emulator). You will see how the light-blue arrow pointer rides on red lines that connect all Bookmarks of the current timeline. E.g. if the current branch is the Bookmark 2, the pointer will ride that route: "cloudlet -> Bookmark 1 -> Bookmark 2". And the other Bookmarks will be left aside, because they represent an alternative timeline, conflicting with the currently played movie.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The Branches Tree is automatically rebuilt each time you create a new Bookmark or change an existing Bookmark's contents. Depending on how complex your project is, the graph may appear differently.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps21"><table width="10%" border="0" cellpadding="1" cellspacing="2" style="border-width: 0px;">
|
||||
<tr valign="top">
|
||||
<td><p class="rvps5"><img alt="" style="padding : 1px;" src="lib/branches-example1.png"/></p>
|
||||
</td>
|
||||
<td><p class="rvps5"><img alt="" style="padding : 1px;" src="lib/branches-example2.png"/></p>
|
||||
</td>
|
||||
<td><p class="rvps5"><img alt="" style="padding : 1px;" src="lib/branches-example3.png"/></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr valign="top">
|
||||
<td><p class="rvps5"><img alt="" style="padding : 1px;" src="lib/branches-example4.png"/></p>
|
||||
</td>
|
||||
<td><p class="rvps5"><img alt="" style="padding : 1px;" src="lib/branches-example5.png"/></p>
|
||||
</td>
|
||||
<td><p class="rvps5"><img alt="" style="padding : 1px;" src="lib/branches-example6.png"/></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">You can hover the mouse cursor over any Bookmark number to see some info about it.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Also you can make a </span><span class="rvts25">single left-click</span><span class="rvts21"> on any Bookmark card to send the Playback cursor to the bookmarked frame (spatial jump). By clicking the cloudlet you send the Playback cursor to the beginning of the movie (equal to pressing </span><span class="rvts30">Shift + Home</span><span class="rvts21">), and by clicking the fireball you send the Playback cursor to the end of the movie (equal to </span><span class="rvts30">Shift + End</span><span class="rvts21">).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Besides, you can </span><span class="rvts25">double-click</span><span class="rvts21"> a Bookmark by the left mouse button to jump to the Bookmark in time. The working movie reverts to the Bookmark's state, the Bookmark becomes current branch and the Playback cursor moves to the Bookmark frame.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Finally, you can </span><span class="rvts25">right-click</span><span class="rvts21"> any card to save the current movie state and the Playback cursor position to the chosen Bookmark.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">As you see, the Branches Tree view supports the same functionality as the Bookmarks List view does. Thus it's recommended for advanced users to stick to the Branch Tree view, because it provides more info for a TASer. When you want to switch back to the Bookmarks List view, click the section header again (the "Branches" label).</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Now try using all 10 available slots. Each time slightly change the current movie Input and watch the changes on the FCEUX screen before saving them to a Bookmark. The position of each card on the Tree is defined by the Input preceding the bookmarked frame. It's implied that TASer always watches the edited Input segment in the emulator, and only then saves the tested work into a Bookmark.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In hands of an experienced TASer Bookmarks become very powerful tool, allowing to greatly simplify the TASing process and implement ideas that look impossible. Usually, an idea is labeled "impossible" only due to its monstrous unbounded complexity. But lower the complexity a hundred times (with the help of tools and a smart process organization), and the achievement moves from the "impossible" category to just "hard" one.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="history"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-history.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">The </span><span class="rvts25">History</span><span class="rvts21"> section is located below the Bookmarks.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Taseditor keeps strict accounting of all operations in the current project. Every user's action that changes an Input, Markers or Bookmarks is recorded to the log displayed in this section.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The current item of the History Log is highlighted blue. Other items have white background if they aren't related to the current item, or purple background if they represent the changes made in the same place as the current item. For example, if current History Log item was created by changing the Input of frame 27, all other items affecting that frame will be highlighted purple.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To undo logged operations you can either use the </span><span class="rvts30">Ctrl + Z</span><span class="rvts21"> and </span><span class="rvts30">Ctrl + Y</span><span class="rvts21"> keys, or simply click </span><span class="rvts21">any line in the History Log with the left mouse button, thus returning the movie to the time when the clicked item was created. </span></p>
|
||||
<p class="rvps10"><span class="rvts21">You may notice the purple cursor line appearing in the Piano Roll for a short moment. It's supposed to stress your attention on the place of the undone changes.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The maximum number of undo levels can be set in the </span><a class="rvts38" href="ProgramCustomization.html#Setmaxundolevels">Config</a><span class="rvts21"> menu, that value defines the maximum size of the History Log and therefore the amount of used memory.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The full list of all possible records in the History Log can be found in the </span><a class="rvts38" href="Operations.html">Reference</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><a name="selection"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-selection.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">At the very bottom of the Toolbox there are 4 buttons controlling the Selection cursor.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The meaning of the "</span><span class="rvts29"><<</span><span class="rvts21">" and "</span><span class="rvts29">>></span><span class="rvts21">" buttons can be easily guessed by analogy with the upper "</span><span class="rvts29"><<</span><span class="rvts21">" and "</span><span class="rvts29">>></span><span class="rvts21">" buttons in the Playback section. The upper part of TAS Editor window contains the Playback cursor-related elements, and the lower window part contains Selection cursor-related elements.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts29"><<</span><span class="rvts21">" button (jump back) moves the Selection cursor </span><span class="rvts21">to the frame where the nearest upper Marker is located. </span><span class="rvts21">In the above picture it will jump from frame 27 to frame 22 where the Marker 2 is set. Using this button you can quickly return the selection to the beginning of the edited segment or to any marked segment. This button has its keyboard analog: </span><span class="rvts30">Ctrl + Page Up</span><span class="rvts21">. You can hold this button to let the dark-blue cursor rapidly jump on Markers up in the Piano Roll.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The "</span><span class="rvts29">>></span><span class="rvts21">" button (jump forward) moves the Selection cursor to the nearest marked frame below it. In the above picture it will jump from frame 27 to a frame outside the visible area (where the next Marker is set), and Piano Roll will automatically scroll after the Selection cursor. Using this button you can quickly navigate down through the movie. This button has its keyboard analog: </span><span class="rvts30">Ctrl + Page Down</span><span class="rvts21">. You can hold this button as well.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Since the Selection cursor isn't tied to the game emulation, its jumps on Markers always happen instantly, regardless of the Greenzone presence on the target frame. So it's useful to read the Marker Notes one by one this way, watching them in the lower edit field and pressing </span><span class="rvts30">Ctrl + Page Down</span><span class="rvts21"> to make an instant jump to the next Note. </span><span class="rvts21">Besides </span><span class="rvts25">Page Up</span><span class="rvts21"> / </span><span class="rvts25">Page Down</span><span class="rvts21"> keys you can roll the mouse wheel while holding the </span><span class="rvts30">Ctrl</span><span class="rvts21"> key.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">The buttons "</span><span class="rvts29">Similar</span><span class="rvts21">" and "</span><span class="rvts29">More</span><span class="rvts21">" are used for searching similar Notes. This is another experimental feature of Taseditor, and it will be described later.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Now you are familiar with fundamental principles of the program usage.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">In the next chapter: </span><a class="rvts38" href="TASingProcess.html">systematic approach to TASing</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<div class="rvps10"><table width="100%" border="1" cellpadding="6" cellspacing="2" style="border-color: #000000; border-style: solid;">
|
||||
<tr valign="top">
|
||||
<td style="border-color: #000000; border-style: solid;"><p class="rvps10"><span class="rvts25">PRACTICE: </span><span class="rvts21">Beat the World 1-1 in Super Mario Bros (or any other game) using only the mouse, without Recording.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">No need to do a speedrun, just make yourself familiar with the routine of Input drawing / erasing and watching the results using the mouse wheel / middle mouse button.</span></p>
|
||||
<p class="rvps10"><span class="rvts25">Estimated time: </span><span class="rvts21">20-30 minutes.</span></p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour">Easily create Help documents</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,147 @@
|
|||
<html>
|
||||
|
||||
<head>
|
||||
<title>4.1. Traditional TASing</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||||
<meta name="generator" content="HelpNDoc Personal Edition 3.7.1.482">
|
||||
<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">
|
||||
$(document).ready(function()
|
||||
{
|
||||
if (top.frames.length == 0)
|
||||
{
|
||||
var sTopicUrl = top.location.href.substring(top.location.href.lastIndexOf("/") + 1, top.location.href.length);
|
||||
top.location.href = "index.html?" + sTopicUrl;
|
||||
}
|
||||
else if (top && top.FrameTOC && top.FrameTOC.SelectTocItem)
|
||||
{
|
||||
top.FrameTOC.SelectTocItem("TraditionalTASing");
|
||||
}
|
||||
});
|
||||
</script>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<div id="topic_header">
|
||||
<div id="topic_header_content">
|
||||
<h1>4.1. Traditional TASing</h1>
|
||||
|
||||
<div id="topic_breadcrumb">
|
||||
<a href="BeginnersGuide.html">Beginner's Guide</a> ›› <a href="TASingMethodology.html">4. TASing Methodology</a> ›› </div>
|
||||
</div>
|
||||
<div id="topic_header_nav">
|
||||
<a href="TASingMethodology.html"><img src="img/arrow_up.png" alt="Parent"/></a>
|
||||
|
||||
<a href="TASingMethodology.html"><img src="img/arrow_left.png" alt="Previous"/></a>
|
||||
|
||||
<a href="NonlinearTASing.html"><img src="img/arrow_right.png" alt="Next"/></a>
|
||||
|
||||
</div>
|
||||
<div class="clear"></div>
|
||||
</div>
|
||||
<div id="topic_content">
|
||||
|
||||
<p></p>
|
||||
<p><span class="rvts19">Traditional TASing</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><img align="right" alt="" style="padding : 6px;" src="lib/toolbox-method1.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21">This method is similar in form to normal videogames playing, however it is completely different in content and requires different way of thinking.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Editing Input is done here by recording a new Input over existing Input.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">To switch between movie watching and editing you have to turn the Recording mode on and off (default hotkey is </span><span class="rvts26">Q</span><span class="rvts21">). It's recommended to enable the "Follow cursor" checkbox, in order to observe the recorded Input in the Piano Roll.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts22">General activity:</span></p>
|
||||
<p class="rvps10"><span class="rvts48"><br/></span></p>
|
||||
<ol style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts21">Put the Playback cursor at the beginning of the edited segment, create a Bookmark, define the goal.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Suppose there's a mistake in the segment, weigh known factors of optimality and figure out the way to fix the mistake.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Navigate to the place of fixing the mistake (load a Bookmark and, if necessary, quickly repeat the existing Input up to the needed frame).</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Play the game in Read+Write mode up to the moment when the target event occurs. The newly recorded Input should be different from old Input in this segment. While recording, create Bookmarks in free slots from time to time to speed up navigation.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">If you make a mistake while typing the Input, return to step 3. If you can not reach the target event using the chosen approach, you can retreat and go to step 8.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">[</span><span class="rvts34">optional step</span><span class="rvts21">] Save the finished approach to a temporary Bookmark, e.g. to slot </span><span class="rvts26">8</span><span class="rvts21">.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">If this isn't the first approach to the segment, compare the new result to the best old result, using the optimality criterion. If the new approach is better (or it's the first approach), save the result to the Bookmark </span><span class="rvts26">9</span><span class="rvts21">. The slot </span><span class="rvts26">9</span><span class="rvts21"> will be used for keeping the best result of polishing the segment.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">If you still want to try different approaches, return to step 2, until you run out of ideas.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">[</span><span class="rvts34">optional step</span><span class="rvts21">] If you need more ideas, you can get some information from the past by replaying the old segments of the movie (e.g. load the Bookmark </span><span class="rvts26">0</span><span class="rvts21"> left at the beginning of current level). Also you can get some food for the mind from the future, by playing with the game events happening after the current segment.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When there's no more ideas, restore the best approach from the Bookmark </span><span class="rvts26">9</span><span class="rvts21"> into the current movie and proceed to the next segment.</span></li>
|
||||
</ol>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps2"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">When you're making a test playthrough of the game (i.e. playing with savestates, but without polishing), you only do steps 3 – 5. And you are satisfied with any successful accomplishment of a segment, so after reaching the target for the first time you proceed to the next segment right away. In this kind of playing you only use savestates to speed up navigation in case you make a fatal mistake (e.g. didn't press the </span><span class="rvts29">A</span><span class="rvts21"> button in time and fell into the pit), because you don't want to rewrite existing Input from the very beginning of the game.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">But when you're seriously TASing the game, you need to try many different approaches in order to find the best one. So you have to repeat steps 2 – 8 many times, until you think the segment is played perfectly. The steps 6 – 9 are what distinguishes real TASing from casual playing with savestates.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">The process of Input Recording (step 4) means that you're editing the Input right while watching the results. That is, when watching the game state at the frame 200 you prepare the Input for the frame 201 (lay fingers on necessary buttons) and then pass the Input to the game using </span><span class="rvts26">Frame Advance</span><span class="rvts21">, and immediately see the outcome – the game state at the frame 201 (granted that you look at the Memory Watch, because the game screen rendering is one frame behind). Usually this outcome is only an intermediate result, which means you can use it to estimate your progress (step 5) but should not use it to compare current and previous approaches of playing the segment (step 7). So you shouldn't apply the optimality criterion after every frame. Even if at the beginning of the segment you outrun the previous approach, you may fall behind somewhere in the middle. Only when you reach the end of the segment (step 6) you get an objective base for comparing.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Steps 3 and 4 take the most of time in this cycle. Often before reaching the target event you have to repeat steps 3, 5 and 5 several times in a row, recording and discarding decisions that are obviously wrong even without comparing them to old approaches. For example, if in the middle of acceleration Mario gets killed by an enemy, there's no point in entering the remaining buttons needed for acceleration. You have to return back and rewrite the Input in such a way that the enemy misses. In a tough situation it's even better to break current segment into two subsegments (before and after the interaction with the enemy), in order to optimize them separately. If you don't do so, you will probably become tired after finishing the first approach, and you'll decide to leave the segment as it is. See, you've got to manage your effort optimally as well!</span></p>
|
||||
<p class="rvps10"><a name="savestates"></a>
|
||||
<span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Since the Input editing in this method is done using the Playback cursor (and not the mouse cursor), for an effective work you must learn to quickly deliver the light-blue cursor to any frame necessary. Upon gaining an experience, TASers accustom themselves to "juggle" with Bookmarks using the motor memory. They mechanically create intermediate and auxillary Bookmarks while recording the Input, and find the necessary Bookmark slot without looking.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">This virtuosity comes with time, usually after having finished a couple of TASes. You cultivate certain habits, one finger adheres to </span><span class="rvts26">Frame Advance</span><span class="rvts21">, Bookmark slots become logically distributed according to their duties, so that fingers press right keys at right moments. For example, that's how some TASers distribute 10 slots:</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps21"><img alt="" style="padding : 1px;" src="lib/savestate_slots.png"/></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps10"><span class="rvts26">F10</span><span class="rvts21"> points to the beginning of current level of the game, so you can rewatch recent segments without watching whole movie. </span><span class="rvts34">Used for navigation.</span></li>
|
||||
<li class="rvps10"><span class="rvts26">F9</span><span class="rvts21"> is responsible for keeping the best result of current segment. </span><span class="rvts34">Used for storing.</span></li>
|
||||
<li class="rvps10"><span class="rvts26">F2</span><span class="rvts21">-</span><span class="rvts26">F6</span><span class="rvts21"> serve as Bookmarks left after every </span><span class="rvts37">hard-to-reproduce action</span><span class="rvts21"> of the current approach to the segment. These Bookmarks are needed for a quick navigation along the current segment. One of them points to the beginning of the segment, and other are used when necessary (may be left unused, if the segment is short and simple). These Bookmarks are created automatically while successfully progressing with Input Recording. </span><span class="rvts34">Used for navigation.</span></li>
|
||||
<li class="rvps10"><span class="rvts26">F1</span><span class="rvts21"> stores a backup copy of the movie at the last successful frame. Current movie state is saved to this slot with paranoid frequency, so you could always return to this stable state from any situation (e.g. after loading some other Bookmarks, or after recording an experiment). This is how the traditional method implements the simple undo feature. Sometimes in addition to the </span><span class="rvts26">F1</span><span class="rvts21"> people use </span><span class="rvts26">F2</span><span class="rvts21"> to provide two levels of undo, but this complicates the logic of backups (as you'd have to alternate the slots), and usually one slot is sufficient. </span><span class="rvts34">Used for storing.</span></li>
|
||||
<li class="rvps10"><span class="rvts26">F7</span><span class="rvts21">-</span><span class="rvts26">F8</span><span class="rvts21"> may store results of alternative strategies that aren't better than the contents of the </span><span class="rvts26">F9</span><span class="rvts21">, yet they are of some interest. Also, one of these slots (or one of </span><span class="rvts26">F2</span><span class="rvts21">-</span><span class="rvts26">F6</span><span class="rvts21">) is used during step 6 to temporarily save the result of the newly finished approach, in order to compare it to the old best result more precisely (by quickly switching between </span><span class="rvts26">F8</span><span class="rvts21"> and </span><span class="rvts26">F9</span><span class="rvts21">). </span><span class="rvts34">Used for storing.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">When creating an improvement for someone else's TAS, slots </span><span class="rvts26">F5</span><span class="rvts21">-</span><span class="rvts26">F7</span><span class="rvts21"> may be allotted for various points of the old movie. For example, </span><span class="rvts26">F5</span><span class="rvts21"> is responsible for the beginning of current level in old movie, </span><span class="rvts26">F6</span><span class="rvts21"> – for the beginning of current segment in old movie, </span><span class="rvts26">F7</span><span class="rvts21"> – for the end of the current segment in old movie. </span><span class="rvts34">Used for storing and navigating the old movie contents.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">This skill is very similar to the skill of playing a musical instrument. The quicker you work it out, the better, because until you master it you will think the traditional TASing is too tiresome. That's why many people consider the bar to be too high. But once you master the technique of rapid savestates usage, other intricacies of TASing will come easier.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">However, now there is Taseditor. It revokes the need to train fingers, allowing to quickly navigate the movie without using Bookmarks. Also, you don't need to accustom to constant backups into </span><span class="rvts26">F1</span><span class="rvts21">, since there is the History Log. So technically you can forget about the traditional method and right away start editing the movie and testing approaches using the </span><a class="rvts27" href="NonlinearTASing.html">nonlinear method of TASing</a><span class="rvts21">.</span></p>
|
||||
<p class="rvps10"><span class="rvts21">Anyway, Taseditor slightly expands possibilities of the traditional method:</span></p>
|
||||
<ul style="text-indent: 30px; margin-left: 0px; list-style-position: inside;">
|
||||
<li class="rvps24" style="text-indent: 30px"><span class="rvts21">New ways to navigate with the Playback cursor, allowing to get to the needed place faster and create savestates less often.</span></li>
|
||||
<li class="rvps24" style="text-indent: 30px"><span class="rvts21">When loading a Bookmark, the movie doesn't truncate after the bookmarked frame. This allows, for example, to record the segment of frames 900-1000 and then rerecord the segment 700-900 without losing the data from 900-1000.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">All possibilities of an external Input editor (copy/paste, etc).</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Visualization of Bookmarks, Input, lag and so on.</span></li>
|
||||
<li class="rvps10"><span class="rvts21">Additional tools: multitracking, superimposing, auto-adjustment of Input, etc.</span></li>
|
||||
</ul>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<hr style="height: 1px; color : #000000; background-color : #000000; border-width : 0px;"/>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Pros of the method:</span></p>
|
||||
<p class="rvps14"><span class="rvts46">+ </span><span class="rvts21">The process is intuitive for any gamer.</span></p>
|
||||
<p class="rvps14"><span class="rvts46">+ </span><span class="rvts21">Constant feedback allows to adapt to the game while editing the Input, adjust your decisions and discard incorrect approaches prematurely.</span></p>
|
||||
<p class="rvps14"><span class="rvts46">+ </span><span class="rvts21">The boundaries of current segment are always marked with Bookmarks (for navigation), thus training TASer to be orderly.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21">Cons of the method:</span></p>
|
||||
<p class="rvps14"><span class="rvts46">– </span><span class="rvts21">The insistent game feedback provokes TASer to discard some illogical but potentially advantageous approaches.</span></p>
|
||||
<p class="rvps14"><span class="rvts46">–</span><span class="rvts25"> </span><span class="rvts21">Slow navigation may distract and increase fatigability.</span></p>
|
||||
<p class="rvps14"><span class="rvts46">–</span><span class="rvts25"> </span><span class="rvts21">Since the number of Bookmarks is limited, the markings of previous segments are lost when creating a new segment, so you have to write down some things in a text file.</span></p>
|
||||
<p class="rvps14"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts25">When the method is recommended to use: </span><span class="rvts21">never. You can use the Recording to make the first test playthrough of a segment (or the whole game), i.e. when you don't need precision. But for polishing a segment this method is inferior. Yet it's reasonable to learn it, because many modern emulators have sufficient tools for applying the method, while Taseditor is only in FCEUX as yet.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><a class="rvts27" href="NonlinearTASing.html">The next method</a><span class="rvts21"> is more effective, but it even less resembles a normal gaming.</span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p class="rvps10"><span class="rvts21"><br/></span></p>
|
||||
<p></p>
|
||||
<p class="rvps8"><span class="rvts17">Created with the Personal Edition of HelpNDoc: </span><a class="rvts18" href="http://www.helpndoc.com/feature-tour">Easily create CHM Help documents</a></p>
|
||||
</div>
|
||||
|
||||
<div id="topic_footer">
|
||||
|
||||
<div id="topic_footer_content">
|
||||
Copyright © 2011-2012 AnS</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
||||
|
|
@ -0,0 +1,111 @@
|
|||
body {
|
||||
background-color: #fff;
|
||||
overflow: auto;
|
||||
width: 100%;
|
||||
}
|
||||
|
||||
.clear {
|
||||
border: 0;
|
||||
clear: both;
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
}
|
||||
|
||||
#topic_header, #topic_footer,
|
||||
#toc_header, #toc_footer {
|
||||
padding: 10px;
|
||||
}
|
||||
|
||||
#topic_content,
|
||||
#toc_content{
|
||||
margin: 10px;
|
||||
}
|
||||
|
||||
/* Backgrounds */
|
||||
|
||||
#topic_header {
|
||||
background: #fff url(../img/header-bg.png) repeat-x left top;
|
||||
border-bottom: 1px solid #ccc;
|
||||
margin-bottom: 15px;
|
||||
}
|
||||
|
||||
#topic_footer{
|
||||
background: #fff url(../img/footer-bg.png) repeat-x left top;
|
||||
margin-top: 20px;
|
||||
}
|
||||
|
||||
/* Topic */
|
||||
|
||||
#topic_header #topic_header_content {
|
||||
float: left;
|
||||
}
|
||||
|
||||
#topic_header #topic_header_nav {
|
||||
float: right;
|
||||
}
|
||||
|
||||
#topic_header #topic_header_nav img {
|
||||
margin-left: 5px;
|
||||
}
|
||||
|
||||
#topic_header a,
|
||||
#topic_footer a,
|
||||
#search_results a,
|
||||
#popupMenu a {
|
||||
color: #333;
|
||||
text-decoration: none;
|
||||
}
|
||||
|
||||
#topic_header a:hover,
|
||||
#topic_footer a:hover,
|
||||
#search_results a:hover,
|
||||
#popupMenu a:hover{
|
||||
text-decoration: underline;
|
||||
}
|
||||
|
||||
#topic_header h1 {
|
||||
color: #333;
|
||||
font-size: 18px;
|
||||
}
|
||||
|
||||
#topic_footer {
|
||||
font-size: 11px;
|
||||
}
|
||||
|
||||
#topic_breadcrumb {
|
||||
font-size: 11px;
|
||||
}
|
||||
|
||||
/* Popup */
|
||||
|
||||
#popupMenu {
|
||||
background-color: #eee;
|
||||
border: 1px solid #999;
|
||||
position: absolute;
|
||||
padding: 5px;
|
||||
webkit-box-shadow: 0px 0px 5px #cccccc;
|
||||
-moz-box-shadow: 0px 0px 5px #cccccc;
|
||||
box-shadow: 0px 0px 5px #cccccc;
|
||||
}
|
||||
|
||||
#popupMenu a{
|
||||
display: block;
|
||||
margin: 5px 10px 2px 5px;
|
||||
}
|
||||
|
||||
.close-button{
|
||||
color: #666;
|
||||
cursor: hand;
|
||||
cursor: pointer;
|
||||
float: right;
|
||||
font-size: 10px;
|
||||
position: relative;
|
||||
top: -5px;
|
||||
right: -3px;
|
||||
}
|
||||
|
||||
/* Search highlight */
|
||||
|
||||
.highlight {
|
||||
background-color: yellow;
|
||||
}
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 291 B |
Binary file not shown.
|
After Width: | Height: | Size: 266 B |
Binary file not shown.
|
After Width: | Height: | Size: 244 B |
Binary file not shown.
|
After Width: | Height: | Size: 262 B |
Binary file not shown.
|
After Width: | Height: | Size: 328 B |
Binary file not shown.
|
After Width: | Height: | Size: 327 B |
Binary file not shown.
|
After Width: | Height: | Size: 343 B |
Binary file not shown.
|
After Width: | Height: | Size: 344 B |
Binary file not shown.
|
After Width: | Height: | Size: 261 B |
Binary file not shown.
|
After Width: | Height: | Size: 277 B |
Binary file not shown.
|
After Width: | Height: | Size: 250 B |
Binary file not shown.
|
After Width: | Height: | Size: 275 B |
Binary file not shown.
|
After Width: | Height: | Size: 332 B |
Binary file not shown.
|
After Width: | Height: | Size: 249 B |
Binary file not shown.
|
After Width: | Height: | Size: 276 B |
Binary file not shown.
|
After Width: | Height: | Size: 299 B |
Binary file not shown.
|
After Width: | Height: | Size: 293 B |
Binary file not shown.
|
After Width: | Height: | Size: 286 B |
Binary file not shown.
|
After Width: | Height: | Size: 313 B |
Binary file not shown.
|
After Width: | Height: | Size: 296 B |
Binary file not shown.
|
After Width: | Height: | Size: 304 B |
Binary file not shown.
|
After Width: | Height: | Size: 309 B |
Binary file not shown.
|
After Width: | Height: | Size: 329 B |
Binary file not shown.
|
After Width: | Height: | Size: 283 B |
Binary file not shown.
|
After Width: | Height: | Size: 338 B |
Binary file not shown.
|
After Width: | Height: | Size: 363 B |
Binary file not shown.
|
After Width: | Height: | Size: 288 B |
Binary file not shown.
|
After Width: | Height: | Size: 310 B |
Binary file not shown.
|
After Width: | Height: | Size: 256 B |
Binary file not shown.
|
After Width: | Height: | Size: 294 B |
Binary file not shown.
|
After Width: | Height: | Size: 314 B |
Binary file not shown.
|
After Width: | Height: | Size: 304 B |
Binary file not shown.
|
After Width: | Height: | Size: 285 B |
Binary file not shown.
|
After Width: | Height: | Size: 319 B |
Binary file not shown.
|
After Width: | Height: | Size: 211 B |
Binary file not shown.
|
After Width: | Height: | Size: 320 B |
Binary file not shown.
|
After Width: | Height: | Size: 335 B |
Binary file not shown.
|
After Width: | Height: | Size: 255 B |
Binary file not shown.
|
After Width: | Height: | Size: 229 B |
Binary file not shown.
|
After Width: | Height: | Size: 273 B |
Binary file not shown.
|
After Width: | Height: | Size: 242 B |
Binary file not shown.
|
After Width: | Height: | Size: 266 B |
Binary file not shown.
|
After Width: | Height: | Size: 4.2 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 570 B |
|
|
@ -0,0 +1,440 @@
|
|||
/*******************************************************************************
|
||||
* Tree container
|
||||
*/
|
||||
ul.dynatree-container
|
||||
{
|
||||
font-family: tahoma, arial, helvetica;
|
||||
font-size: 10pt; /* font size should not be too big */
|
||||
white-space: nowrap;
|
||||
padding: 3px;
|
||||
margin: 0; /* issue 201 */
|
||||
background-color: white;
|
||||
border: 1px dotted gray;
|
||||
overflow: auto;
|
||||
height: 100%; /* issue 263 */
|
||||
}
|
||||
|
||||
ul.dynatree-container ul
|
||||
{
|
||||
padding: 0 0 0 16px;
|
||||
margin: 0;
|
||||
}
|
||||
|
||||
ul.dynatree-container li
|
||||
{
|
||||
list-style-image: none;
|
||||
list-style-position: outside;
|
||||
list-style-type: none;
|
||||
-moz-background-clip:border;
|
||||
-moz-background-inline-policy: continuous;
|
||||
-moz-background-origin: padding;
|
||||
background-attachment: scroll;
|
||||
background-color: transparent;
|
||||
background-repeat: repeat-y;
|
||||
background-image: url("vline.gif");
|
||||
background-position: 0 0;
|
||||
/*
|
||||
background-image: url("icons_96x256.gif");
|
||||
background-position: -80px -64px;
|
||||
*/
|
||||
margin: 0;
|
||||
padding: 1px 0 0 0;
|
||||
}
|
||||
/* Suppress lines for last child node */
|
||||
ul.dynatree-container li.dynatree-lastsib
|
||||
{
|
||||
background-image: none;
|
||||
}
|
||||
/* Suppress lines if level is fixed expanded (option minExpandLevel) */
|
||||
ul.dynatree-no-connector > li
|
||||
{
|
||||
background-image: none;
|
||||
}
|
||||
|
||||
/* Style, when control is disabled */
|
||||
.ui-dynatree-disabled ul.dynatree-container
|
||||
{
|
||||
opacity: 0.5;
|
||||
/* filter: alpha(opacity=50); /* Yields a css warning */
|
||||
background-color: silver;
|
||||
}
|
||||
|
||||
/*******************************************************************************
|
||||
* Common icon definitions
|
||||
*/
|
||||
span.dynatree-empty,
|
||||
span.dynatree-vline,
|
||||
span.dynatree-connector,
|
||||
span.dynatree-expander,
|
||||
span.dynatree-icon,
|
||||
span.dynatree-checkbox,
|
||||
span.dynatree-radio,
|
||||
span.dynatree-drag-helper-img,
|
||||
#dynatree-drop-marker
|
||||
{
|
||||
width: 16px;
|
||||
height: 16px;
|
||||
/* display: -moz-inline-box; /* @ FF 1+2 removed for issue 221 */
|
||||
/* -moz-box-align: start; /* issue 221 */
|
||||
display: inline-block; /* Required to make a span sizeable */
|
||||
vertical-align: top;
|
||||
background-repeat: no-repeat;
|
||||
background-position: left;
|
||||
background-image: url("icons.gif");
|
||||
background-position: 0 0;
|
||||
}
|
||||
|
||||
/** Used by 'icon' node option: */
|
||||
ul.dynatree-container img
|
||||
{
|
||||
width: 16px;
|
||||
height: 16px;
|
||||
margin-left: 3px;
|
||||
vertical-align: top;
|
||||
border-style: none;
|
||||
}
|
||||
|
||||
|
||||
/*******************************************************************************
|
||||
* Lines and connectors
|
||||
*/
|
||||
|
||||
span.dynatree-connector
|
||||
{
|
||||
background-position: -16px -64px;
|
||||
}
|
||||
|
||||
/*******************************************************************************
|
||||
* Expander icon
|
||||
* Note: IE6 doesn't correctly evaluate multiples class names,
|
||||
* so we create combined class names that can be used in the CSS.
|
||||
*
|
||||
* Prefix: dynatree-exp-
|
||||
* 1st character: 'e': expanded, 'c': collapsed
|
||||
* 2nd character (optional): 'd': lazy (Delayed)
|
||||
* 3rd character (optional): 'l': Last sibling
|
||||
*/
|
||||
|
||||
span.dynatree-expander
|
||||
{
|
||||
background-position: 0px -80px;
|
||||
cursor: pointer;
|
||||
}
|
||||
.dynatree-exp-cl span.dynatree-expander /* Collapsed, not delayed, last sibling */
|
||||
{
|
||||
background-position: 0px -96px;
|
||||
}
|
||||
.dynatree-exp-cd span.dynatree-expander /* Collapsed, delayed, not last sibling */
|
||||
{
|
||||
background-position: -64px -80px;
|
||||
}
|
||||
.dynatree-exp-cdl span.dynatree-expander /* Collapsed, delayed, last sibling */
|
||||
{
|
||||
background-position: -64px -96px;
|
||||
}
|
||||
.dynatree-exp-e span.dynatree-expander, /* Expanded, not delayed, not last sibling */
|
||||
.dynatree-exp-ed span.dynatree-expander /* Expanded, delayed, not last sibling */
|
||||
{
|
||||
background-position: -32px -80px;
|
||||
}
|
||||
.dynatree-exp-el span.dynatree-expander, /* Expanded, not delayed, last sibling */
|
||||
.dynatree-exp-edl span.dynatree-expander /* Expanded, delayed, last sibling */
|
||||
{
|
||||
background-position: -32px -96px;
|
||||
}
|
||||
.dynatree-loading span.dynatree-expander /* 'Loading' status overrides all others */
|
||||
{
|
||||
background-position: 0 0;
|
||||
background-image: url("loading.gif");
|
||||
}
|
||||
|
||||
|
||||
/*******************************************************************************
|
||||
* Checkbox icon
|
||||
*/
|
||||
span.dynatree-checkbox
|
||||
{
|
||||
margin-left: 3px;
|
||||
background-position: 0px -32px;
|
||||
}
|
||||
span.dynatree-checkbox:hover
|
||||
{
|
||||
background-position: -16px -32px;
|
||||
}
|
||||
|
||||
.dynatree-partsel span.dynatree-checkbox
|
||||
{
|
||||
background-position: -64px -32px;
|
||||
}
|
||||
.dynatree-partsel span.dynatree-checkbox:hover
|
||||
{
|
||||
background-position: -80px -32px;
|
||||
}
|
||||
|
||||
.dynatree-selected span.dynatree-checkbox
|
||||
{
|
||||
background-position: -32px -32px;
|
||||
}
|
||||
.dynatree-selected span.dynatree-checkbox:hover
|
||||
{
|
||||
background-position: -48px -32px;
|
||||
}
|
||||
|
||||
/*******************************************************************************
|
||||
* Radiobutton icon
|
||||
* This is a customization, that may be activated by overriding the 'checkbox'
|
||||
* class name as 'dynatree-radio' in the tree options.
|
||||
*/
|
||||
span.dynatree-radio
|
||||
{
|
||||
margin-left: 3px;
|
||||
background-position: 0px -48px;
|
||||
}
|
||||
span.dynatree-radio:hover
|
||||
{
|
||||
background-position: -16px -48px;
|
||||
}
|
||||
|
||||
.dynatree-partsel span.dynatree-radio
|
||||
{
|
||||
background-position: -64px -48px;
|
||||
}
|
||||
.dynatree-partsel span.dynatree-radio:hover
|
||||
{
|
||||
background-position: -80px -48px;
|
||||
}
|
||||
|
||||
.dynatree-selected span.dynatree-radio
|
||||
{
|
||||
background-position: -32px -48px;
|
||||
}
|
||||
.dynatree-selected span.dynatree-radio:hover
|
||||
{
|
||||
background-position: -48px -48px;
|
||||
}
|
||||
|
||||
/*******************************************************************************
|
||||
* Node type icon
|
||||
* Note: IE6 doesn't correctly evaluate multiples class names,
|
||||
* so we create combined class names that can be used in the CSS.
|
||||
*
|
||||
* Prefix: dynatree-ico-
|
||||
* 1st character: 'e': expanded, 'c': collapsed
|
||||
* 2nd character (optional): 'f': folder
|
||||
*/
|
||||
|
||||
span.dynatree-icon /* Default icon */
|
||||
{
|
||||
margin-left: 3px;
|
||||
background-position: 0px 0px;
|
||||
}
|
||||
|
||||
.dynatree-ico-cf span.dynatree-icon /* Collapsed Folder */
|
||||
{
|
||||
background-position: 0px -16px;
|
||||
}
|
||||
|
||||
.dynatree-ico-ef span.dynatree-icon /* Expanded Folder */
|
||||
{
|
||||
background-position: -64px -16px;
|
||||
}
|
||||
|
||||
/* Status node icons */
|
||||
|
||||
.dynatree-statusnode-wait span.dynatree-icon
|
||||
{
|
||||
background-image: url("loading.gif");
|
||||
}
|
||||
|
||||
.dynatree-statusnode-error span.dynatree-icon
|
||||
{
|
||||
background-position: 0px -112px;
|
||||
/* background-image: url("ltError.gif");*/
|
||||
}
|
||||
|
||||
/*******************************************************************************
|
||||
* Node titles
|
||||
*/
|
||||
|
||||
/* @Chrome: otherwise hit area of node titles is broken (issue 133)
|
||||
Removed again for issue 165; (133 couldn't be reproduced) */
|
||||
span.dynatree-node
|
||||
{
|
||||
/* display: -moz-inline-box; /* issue 133, 165, 172, 192. removed for issue 221*/
|
||||
/* -moz-box-align: start; /* issue 221 */
|
||||
/* display: inline-block; /* Required to make a span sizeable */
|
||||
}
|
||||
|
||||
|
||||
/* Remove blue color and underline from title links */
|
||||
ul.dynatree-container a
|
||||
/*, ul.dynatree-container a:visited*/
|
||||
{
|
||||
color: black; /* inherit doesn't work on IE */
|
||||
text-decoration: none;
|
||||
vertical-align: top;
|
||||
margin: 0px;
|
||||
margin-left: 3px;
|
||||
/* outline: 0; /* @ Firefox, prevent dotted border after click */
|
||||
}
|
||||
|
||||
ul.dynatree-container a:hover
|
||||
{
|
||||
/* text-decoration: underline; */
|
||||
background-color: #F2F7FD; /* light blue */
|
||||
border-color: #B8D6FB; /* darker light blue */
|
||||
}
|
||||
|
||||
span.dynatree-node a
|
||||
{
|
||||
font-size: 10pt; /* required for IE, quirks mode */
|
||||
display: inline-block; /* Better alignment, when title contains <br> */
|
||||
/* vertical-align: top;*/
|
||||
padding-left: 3px;
|
||||
padding-right: 3px; /* Otherwise italic font will be outside bounds */
|
||||
/* line-height: 16px; /* should be the same as img height, in case 16 px */
|
||||
}
|
||||
span.dynatree-folder a
|
||||
{
|
||||
font-weight: bold;
|
||||
}
|
||||
|
||||
ul.dynatree-container a:focus,
|
||||
span.dynatree-focused a:link /* @IE */
|
||||
{
|
||||
background-color: #EFEBDE; /* gray */
|
||||
}
|
||||
|
||||
span.dynatree-has-children a
|
||||
{
|
||||
}
|
||||
|
||||
span.dynatree-expanded a
|
||||
{
|
||||
}
|
||||
|
||||
span.dynatree-selected a
|
||||
{
|
||||
color: green;
|
||||
font-style: italic;
|
||||
}
|
||||
|
||||
span.dynatree-active a
|
||||
{
|
||||
background-color: #3169C6 !important;
|
||||
color: white !important; /* @ IE6 */
|
||||
}
|
||||
|
||||
/*******************************************************************************
|
||||
* Drag'n'drop support
|
||||
*/
|
||||
|
||||
/*** Helper object ************************************************************/
|
||||
div.dynatree-drag-helper
|
||||
{
|
||||
}
|
||||
div.dynatree-drag-helper a
|
||||
{
|
||||
border: 1px solid gray;
|
||||
background-color: white;
|
||||
padding-left: 5px;
|
||||
padding-right: 5px;
|
||||
opacity: 0.8;
|
||||
}
|
||||
span.dynatree-drag-helper-img
|
||||
{
|
||||
/*
|
||||
position: relative;
|
||||
left: -16px;
|
||||
*/
|
||||
}
|
||||
div.dynatree-drag-helper /*.dynatree-drop-accept*/
|
||||
{
|
||||
|
||||
/* border-color: green;
|
||||
background-color: red;*/
|
||||
}
|
||||
div.dynatree-drop-accept span.dynatree-drag-helper-img
|
||||
{
|
||||
background-position: -32px -112px;
|
||||
}
|
||||
div.dynatree-drag-helper.dynatree-drop-reject
|
||||
{
|
||||
border-color: red;
|
||||
}
|
||||
div.dynatree-drop-reject span.dynatree-drag-helper-img
|
||||
{
|
||||
background-position: -16px -112px;
|
||||
}
|
||||
|
||||
/*** Drop marker icon *********************************************************/
|
||||
|
||||
#dynatree-drop-marker
|
||||
{
|
||||
width: 24px;
|
||||
position: absolute;
|
||||
background-position: 0 -128px;
|
||||
margin: 0;
|
||||
/* border: 1px solid red; */
|
||||
}
|
||||
#dynatree-drop-marker.dynatree-drop-after,
|
||||
#dynatree-drop-marker.dynatree-drop-before
|
||||
{
|
||||
width:64px;
|
||||
background-position: 0 -144px;
|
||||
}
|
||||
#dynatree-drop-marker.dynatree-drop-copy
|
||||
{
|
||||
background-position: -64px -128px;
|
||||
}
|
||||
#dynatree-drop-marker.dynatree-drop-move
|
||||
{
|
||||
background-position: -64px -128px;
|
||||
}
|
||||
|
||||
/*** Source node while dragging ***********************************************/
|
||||
|
||||
span.dynatree-drag-source
|
||||
{
|
||||
/* border: 1px dotted gray; */
|
||||
background-color: #e0e0e0;
|
||||
}
|
||||
span.dynatree-drag-source a
|
||||
{
|
||||
color: gray;
|
||||
}
|
||||
|
||||
/*** Target node while dragging cursor is over it *****************************/
|
||||
|
||||
span.dynatree-drop-target
|
||||
{
|
||||
/*border: 1px solid gray;*/
|
||||
}
|
||||
span.dynatree-drop-target a
|
||||
{
|
||||
}
|
||||
span.dynatree-drop-target.dynatree-drop-accept a
|
||||
{
|
||||
/*border: 1px solid green;*/
|
||||
background-color: #3169C6 !important;
|
||||
color: white !important; /* @ IE6 */
|
||||
text-decoration: none;
|
||||
}
|
||||
span.dynatree-drop-target.dynatree-drop-reject
|
||||
{
|
||||
/*border: 1px solid red;*/
|
||||
}
|
||||
span.dynatree-drop-target.dynatree-drop-after a
|
||||
{
|
||||
}
|
||||
|
||||
|
||||
/*******************************************************************************
|
||||
* Custom node classes (sample)
|
||||
*/
|
||||
|
||||
span.custom1 a
|
||||
{
|
||||
background-color: maroon;
|
||||
color: yellow;
|
||||
}
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 844 B |
Binary file not shown.
|
After Width: | Height: | Size: 291 B |
Binary file not shown.
|
After Width: | Height: | Size: 266 B |
Binary file not shown.
|
After Width: | Height: | Size: 244 B |
Binary file not shown.
|
After Width: | Height: | Size: 262 B |
Binary file not shown.
|
After Width: | Height: | Size: 328 B |
Binary file not shown.
|
After Width: | Height: | Size: 327 B |
Binary file not shown.
|
After Width: | Height: | Size: 343 B |
Binary file not shown.
|
After Width: | Height: | Size: 344 B |
Binary file not shown.
|
After Width: | Height: | Size: 261 B |
Binary file not shown.
|
After Width: | Height: | Size: 277 B |
Binary file not shown.
|
After Width: | Height: | Size: 250 B |
Binary file not shown.
|
After Width: | Height: | Size: 275 B |
Binary file not shown.
|
After Width: | Height: | Size: 332 B |
Binary file not shown.
|
After Width: | Height: | Size: 249 B |
Binary file not shown.
|
After Width: | Height: | Size: 276 B |
Binary file not shown.
|
After Width: | Height: | Size: 299 B |
Binary file not shown.
|
After Width: | Height: | Size: 293 B |
Binary file not shown.
|
After Width: | Height: | Size: 286 B |
Binary file not shown.
|
After Width: | Height: | Size: 313 B |
Binary file not shown.
|
After Width: | Height: | Size: 296 B |
Binary file not shown.
|
After Width: | Height: | Size: 304 B |
Binary file not shown.
|
After Width: | Height: | Size: 309 B |
Binary file not shown.
|
After Width: | Height: | Size: 329 B |
Binary file not shown.
|
After Width: | Height: | Size: 283 B |
Binary file not shown.
|
After Width: | Height: | Size: 338 B |
Binary file not shown.
|
After Width: | Height: | Size: 363 B |
Binary file not shown.
|
After Width: | Height: | Size: 288 B |
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue