# Yearn speed controls: fast-forward through waits and slow down actions
Language: en
Canonical: [Yearn speed controls: fast-forward through waits and slow down actions]()
中文：[中文 HTML]()
English: [English HTML]()
Published: 2026-10-23T00:00:00+08:00
Modified: 2026-10-23T10:49:32+08:00
Author: Bison
Compare normal, fast and slow speed step by step, checking button actions, sound, picture and save state, and distinguish running speed from turbo-fire controls.
English translation of the [Chinese original](), translated on 2026-10-23. The article body uses automated translation; app descriptions, historical reading notes and video subtitles receive separate editorial checks. Original publication dates, attribution, code and version notes are retained.
Fast-forward can help with repeated opening animations and slowly appearing text, while slow speed can help you observe actions. Yearn provides speed controls in the game menu as well as an on-screen fast-forward control. This guide first establishes a baseline at normal speed, then changes the pace a little at a time to distinguish the effects of speed settings from those of device performance.
## First save a checkpoint at normal speed
Open a game that already runs reliably, stop in a safe place, and first confirm that it is running at normal speed. Save a checkpoint manually and note the scene and save slot so that you can return to a known position while experimenting with speed changes. For your first attempt, avoid critical scenes where you only get one chance, and do not overwrite your only save with an experimental state.
Play a short section at normal speed and observe animation timing, text speed, and audio. Return to the same point for every later comparison: you are assessing changes caused by the speed setting, rather than differences in frame rate, dialogue length, or sound effects that naturally occur between scenes.
## Start with a lower fast-forward multiplier
Open the speed option in the game menu, choose a setting slightly faster than normal, then return to the game. Shorter waits through animations and faster character movement indicate that the actual execution timing has changed. If only the interface shows a multiplier while the game appears unchanged, note the current platform and scene. Do not immediately conclude that the setting has no effect on any content.
Try holding the on-screen fast-forward button briefly, then release it and check whether the speed indicator and actual pace return to normal. Check the speed level selected in the menu separately as well; before any action requiring precise input, explicitly return to normal speed, then continue.
## Use fast-forward separately for dialogue and action
For repeated dialogue, fast-forward reduces waiting; when it is time to choose an option, return to normal speed in advance so that a single button press does not skip through multiple choices. In walking or action scenes, fast-forward reduces your reaction time, and a distance that was easy to control may suddenly take you past the target, so test it in an open area first.
Do not treat enabling fast-forward and repeatedly pressing Confirm at the same time as the default way to play. You could skip important text, trigger menu options, or write an in-game save without realizing it. For your first comparison, speed up the parts that run automatically while continuing to control your inputs deliberately.
## Use slow speed for observation and still check normal operation
After selecting slow speed in the speed menu, choose an easily recognizable action, such as a character jumping, an object moving, or a menu animation. Compare it with the same action at normal speed to confirm that what you are seeing is the action taking longer, rather than the screen freezing or input becoming unresponsive.
Audio may behave differently at slow speed, and some content may not be suitable for prolonged operation at a nonstandard pace. After observing, restore normal speed and test directional input, confirm, and pause. If an issue occurs only at a nonstandard speed, include the multiplier in your report rather than describing it as an error that necessarily occurs during default operation.
## A speed multiplier does not guarantee device performance
Selecting a higher multiplier only sets a faster execution target; the device and emulation core may not be able to sustain it. More complex platforms, demanding scenes, or device heat may limit actual speed. If audio stutters or the display becomes unstable, return to normal speed for comparison instead of raising the multiplier further to try to ‘compensate.’
You can record your observations in two rounds: first, whether normal speed is stable, and second, whether a particular faster setting is useful. If normal speed itself is unstable, address the basic running problems first. Increasing the multiplier will not automatically make a slow device faster, nor can you use it to infer compatibility and performance for every console.
## Distinguish fast-forward from turbo input
Fast-forward changes the timing of game execution; turbo simulates repeatedly pressing a particular button. They work differently even though both can make actions look faster. To troubleshoot, first restore normal speed and check whether the same button still triggers repeatedly. This lets you assess execution speed and input state separately.
For example, if a menu scrolls rapidly on its own, first check whether a direction or confirm button is still held, then check the speed multiplier. A character repeatedly performing one action may indicate an input-state issue; if the whole image and music speed up, execution speed is more worth checking. Observing this distinction usually points you in the right direction faster than resetting settings at random.
## Questions and final checks
**The audio sounds wrong after fast-forwarding. Do I need to import the game again?** First restore normal speed and compare the same scene. If normal behavior returns, simply note which multiplier caused the change. There is no need to alter the original file immediately.
**What if the character keeps moving after I return to normal speed?** Release all buttons, pause, and check controller input. Speed settings and an input that remains held are separate issues. If necessary, reconnect the controller and compare with touchscreen controls.
When you finish the exercise, confirm that normal speed has been restored, then save a separate checkpoint that you are satisfied with. The ideal result is to understand which kinds of waiting suit fast-forward, which actions benefit from observation at slow speed, and how to return reliably to normal play, rather than finding the highest multiplier.
## Keep each comparison brief
For the first test, observe just one menu animation or a short straight route. Run it at normal speed, speed it up, and then return to normal. Keep the starting point the same for each run and note any audio stuttering or input that overshoots the target. If you need repeated attempts, keep the starting point in a separate practice slot rather than overwriting a confirmed milestone. A short, repeatable comparison makes suitable uses easier to identify than prolonged, aimless acceleration.
## Related tutorials and sources
Read next [Keep a saved checkpoint]() and [Troubleshooting running problems]().
Information checked on October 23, 2026. Public release information comes from [the Yearn store page]() and [Apple’s lookup API](), listing 1.0.2 and iOS / iPadOS 17 or later. Follow the interface shown by the version installed on your device.