RetroArch: Difference between revisions

Line 63:

*[[GGPO]]-like netplay (latency hiding rollback). It should be lag-free if everyone involved emulates at full speed, doesn't live on opposite sides of the world, and has decent internet speeds. It uses peer-to-peer UDP and supports two players. Due to rollback, it requires a fair amount of CPU power to run, and only works with cores that support serialization.

*Options for decreasing input latency related to vsync by eliminating buffering by the video driver, as well as using frame delay to delay polling of inputs until right before a vsync occurs on the display.

*Supports [[Input_lag|input lag-mitigating techniques]]. One of these setting is "Run-ahead" which allows cycle-accuracy emulators to run ahead of mandatory 1 or 2 frames of input lag. These settings allow emulators to [https://~~www.libretro~~.com/~~index.php~~/retroarch-1-7-2~~%E2%80%8A~~-~~%E2%80%8Aachieving~~-better-latency-than-original-hardware-through-new-runahead-method/ achieve better latency than original hardware] (Run-ahead option official debut in version 1.7.2).

*Supports [[Input_lag|input lag-mitigating techniques]]. One of these setting is "Run-ahead" which allows cycle-accuracy emulators to run ahead of mandatory 1 or 2 frames of input lag. These settings allow emulators to [https://medium.com/@libretro/retroarch-1-7-2-achieving-better-latency-than-original-hardware-through-new-runahead-method-1b80d26bb5d1/ achieve better latency than original hardware] (Run-ahead option official debut in version 1.7.2).

*[https://retroachievements.org/download.php#ralibretro RetroAchievements support].

*Libretro cores compatible with [[BizHawk]] and [[Virtual_reality#VR_game_room_simulations|EmuVR]], so if you don't like using RetroArch as a [[Frontends|frontend]] you have other options as well.

@@ Line 63: / Line 63: @@
 *[[GGPO]]-like netplay (latency hiding rollback). It should be lag-free if everyone involved emulates at full speed, doesn't live on opposite sides of the world, and has decent internet speeds. It uses peer-to-peer UDP and supports two players. Due to rollback, it requires a fair amount of CPU power to run, and only works with cores that support serialization.
 *Options for decreasing input latency related to vsync by eliminating buffering by the video driver, as well as using frame delay to delay polling of inputs until right before a vsync occurs on the display.
-*Supports [[Input_lag|input lag-mitigating techniques]]. One of these setting is "Run-ahead" which allows cycle-accuracy emulators to run ahead of mandatory 1 or 2 frames of input lag. These settings allow emulators to [https://www.libretro.com/index.php/retroarch-1-7-2%E2%80%8A-%E2%80%8Aachieving-better-latency-than-original-hardware-through-new-runahead-method/ achieve better latency than original hardware] (Run-ahead option official debut in version 1.7.2).
+*Supports [[Input_lag|input lag-mitigating techniques]]. One of these setting is "Run-ahead" which allows cycle-accuracy emulators to run ahead of mandatory 1 or 2 frames of input lag. These settings allow emulators to [https://medium.com/@libretro/retroarch-1-7-2-achieving-better-latency-than-original-hardware-through-new-runahead-method-1b80d26bb5d1/ achieve better latency than original hardware] (Run-ahead option official debut in version 1.7.2).
 *[https://retroachievements.org/download.php#ralibretro RetroAchievements support].
 *Libretro cores compatible with [[BizHawk]] and [[Virtual_reality#VR_game_room_simulations|EmuVR]], so if you don't like using RetroArch as a [[Frontends|frontend]] you have other options as well.