Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| run-ahead [2020/01/28 14:28] – created genetik57 | run-ahead [2021/12/26 01:14] (current) – removed atari | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Latency Reduction / Run-ahead ====== | ||
| - | The **run-ahead** feature enables some emulated video games to have lower controller latency than the actual hardware they were meant to run on. | ||
| - | |||
| - | This feature calculates a given number of frames in the background as fast as possible, in order to " | ||
| - | |||
| - | Here is a short video that compares a real NES console to an emulation with run-ahead (1 frame) | ||
| - | |||
| - | {{youtube> | ||
| - | |||
| - | **Parameters**: | ||
| - | * **USE RUN-AHEAD FRAMES**: How many frames you want to calculate in advance, from Auto (=0) to 6. Best results are with 2 to 3 frames | ||
| - | * **RUN-AHEAD USE SECOND INSTANCE**: Do you want to launch a second instance of the emulator to accelerate the run-ahead calculation. Yet, this option will take more CPU and RAM resources. | ||
| - | |||
| - | **Limitations**: | ||
| - | This feature is available only for libretro-powered emulators on Batocera, and is quite CPU intensive. It should work fine with most boards that are RPi3 or better for 8-bit and 16-bit generations though. | ||
- run-ahead.1580221695.txt.gz
- Last modified: 6 years ago
- by genetik57