Editing RetroArch
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 8: | Line 8: | ||
|type = [[libretro]] frontend | |type = [[libretro]] frontend | ||
|prog-lang = C, C++ | |prog-lang = C, C++ | ||
| − | |website = [ | + | |website = [http://www.libretro.com/ libretro.com] |
|support = [https://www.patreon.com/libretro Patreon]<br/>[https://github.com/sponsors/libretro GitHub Sponsor]<br/>[https://liberapay.com/Libretro/donate Liberapay] | |support = [https://www.patreon.com/libretro Patreon]<br/>[https://github.com/sponsors/libretro GitHub Sponsor]<br/>[https://liberapay.com/Libretro/donate Liberapay] | ||
|source = [https://github.com/libretro GitHub] | |source = [https://github.com/libretro GitHub] | ||
| Line 40: | Line 40: | ||
*[https://buildbot.libretro.com/stable/{{RetroArchVer}}/nintendo/3ds/RetroArch_cia.7z RetroArch for Nintendo 3DS (.cia)] ({{RetroArchVer}}) | *[https://buildbot.libretro.com/stable/{{RetroArchVer}}/nintendo/3ds/RetroArch_cia.7z RetroArch for Nintendo 3DS (.cia)] ({{RetroArchVer}}) | ||
*[https://buildbot.libretro.com/stable/{{RetroArchVer}}/nintendo/switch/libnx/RetroArch.7z RetroArch for Nintendo Switch] ({{RetroArchVer}}) | *[https://buildbot.libretro.com/stable/{{RetroArchVer}}/nintendo/switch/libnx/RetroArch.7z RetroArch for Nintendo Switch] ({{RetroArchVer}}) | ||
| − | *[https://pyra-handheld.com/boards/threads/retroarch-1-7-2.81254/ RetroArch for Pandora on OpenPandora's repo] (1.7.3) and [ | + | *[https://pyra-handheld.com/boards/threads/retroarch-1-7-2.81254/ RetroArch for Pandora on OpenPandora's repo] (1.7.3) and [http://repo.openpandora.org/?page=detail&app=retroarch.lifning.001 old 2013 variant] (0.9.9.1) |
*[https://pyra-handheld.com/repo/apps/53 RetroArch for Pyra] (1.9.6) | *[https://pyra-handheld.com/repo/apps/53 RetroArch for Pyra] (1.9.6) | ||
*[https://boards.dingoonity.org/gcw-development/(test-release)-retroarch-for-gcw0/ RetroArch for GCW Zero (.opk)] (0.1b) {Unofficial test build} | *[https://boards.dingoonity.org/gcw-development/(test-release)-retroarch-for-gcw0/ RetroArch for GCW Zero (.opk)] (0.1b) {Unofficial test build} | ||
| Line 53: | Line 53: | ||
*Gamepad auto-configuration profiles, so that gamepads are mapped automatically when connected. XInput controller autoconfig is built into the application, with other controller types available as external profiles. | *Gamepad auto-configuration profiles, so that gamepads are mapped automatically when connected. XInput controller autoconfig is built into the application, with other controller types available as external profiles. | ||
*Per-core and per-game configuration overrides | *Per-core and per-game configuration overrides | ||
| − | * | + | *[https://docs.libretro.com/guides/crtswitchres/ <abbr title="On Windows OS you need CRT Emudriver OR CRT Modeline editor/EDID generator tool">Custom resolution/CRTSwitchRes</abbr>] and refresh rate for video output, with exclusive fullscreen mode and monitor index for multi-monitor setups. |
*Dynamic rate control for smooth audio and video, even when the game's output rate differs from your system's. Especially obvious with systems like GBA that do not run 60Hz. | *Dynamic rate control for smooth audio and video, even when the game's output rate differs from your system's. Especially obvious with systems like GBA that do not run 60Hz. | ||
| − | *Basic fast | + | *Basic fast forward, SRAM saving, savestate, etc. It supports serialization of the emulation state, which is used to provide real-time rewind and netplay. |
*[[Shaders and Filters|Pixel shaders]] and [[Shader_Presets|presets]], primarily using Slang, Cg and GLSL, with HLSL on Xbox 360. The shader format it uses is flexible and fairly easy to use, allowing for complex multi-pass effects with adjustable runtime parameters. Also supports traditional video filter plugins that are run in software. | *[[Shaders and Filters|Pixel shaders]] and [[Shader_Presets|presets]], primarily using Slang, Cg and GLSL, with HLSL on Xbox 360. The shader format it uses is flexible and fairly easy to use, allowing for complex multi-pass effects with adjustable runtime parameters. Also supports traditional video filter plugins that are run in software. | ||
*Supports audio DSP filter plugins through .dsp configuration files. | *Supports audio DSP filter plugins through .dsp configuration files. | ||
| Line 61: | Line 61: | ||
*FFmpeg recording and playback support. It can record either the native resolution output of the core or the post-processed output of the frontend. Playback is handled through an internal FFmpeg libretro core. | *FFmpeg recording and playback support. It can record either the native resolution output of the core or the post-processed output of the frontend. Playback is handled through an internal FFmpeg libretro core. | ||
*Streaming support. By adding your twitch account to RetroArch and making some small [https://www.retroarch.com/index.php?page=recording setup], it is possible to stream on Twitch the content of the game played. | *Streaming support. By adding your twitch account to RetroArch and making some small [https://www.retroarch.com/index.php?page=recording setup], it is possible to stream on Twitch the content of the game played. | ||
| − | *[[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 | + | *[[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. | *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 | + | *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 allows 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). |
*[https://retroachievements.org/download.php#ralibretro RetroAchievements support]. | *[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. | *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 75: | Line 75: | ||
==Netplay== | ==Netplay== | ||
| − | Netplay is now usable from the menu in current builds, under Settings>Netplay Options. You can get it to work with the [https://github.com/libretro/RetroArch/wiki/Using-command-line command line] or the long-deprecated [ | + | Netplay is now usable from the menu in current builds, under Settings>Netplay Options. You can get it to work with the [https://github.com/libretro/RetroArch/wiki/Using-command-line command line] or the long-deprecated [http://www.mediafire.com/download/yrydc78bl6y82z4/retroarch-phoenix.7z RetroArch-Phoenix Launcher] as well in older builds. |
You must specify whether you will be hosting (server) or joining (client) the game. If joining, you must also enter the host's IP address in the field below. Make sure your firewall is open on port 55435 (default; you can change it if you like) and that the port is forwarded in your router, if applicable. You can also specify 'spectator mode,' which will allow an arbitrary number of spectators to join and watch you play without being able to play themselves. | You must specify whether you will be hosting (server) or joining (client) the game. If joining, you must also enter the host's IP address in the field below. Make sure your firewall is open on port 55435 (default; you can change it if you like) and that the port is forwarded in your router, if applicable. You can also specify 'spectator mode,' which will allow an arbitrary number of spectators to join and watch you play without being able to play themselves. | ||
| Line 81: | Line 81: | ||
Delay frames denote the maximum number of frames RetroArch's libretro cores will need to emulate at once to maintain synchronization due to actual network latency. You can figure out an appropriate ballpark for this number by pinging the other player and dividing the time (in milliseconds) by 16 (roughly the number of milliseconds in a frame from a game running at 60 fps). If the gameplay is a bit choppy, try increasing the number of delay frames a bit. | Delay frames denote the maximum number of frames RetroArch's libretro cores will need to emulate at once to maintain synchronization due to actual network latency. You can figure out an appropriate ballpark for this number by pinging the other player and dividing the time (in milliseconds) by 16 (roughly the number of milliseconds in a frame from a game running at 60 fps). If the gameplay is a bit choppy, try increasing the number of delay frames a bit. | ||
| − | Similar to the GGPO platform, RetroArch creates a constant stream of savestates which, along with button presses, are exchanged and compared between the server and client machines. If the savestates start to diverge, the game rolls back in time to a point where they both agree | + | Similar to the GGPO platform, RetroArch creates a constant stream of savestates which, along with button presses, are exchanged and compared between the server and client machines. If the savestates start to diverge, the game rolls back in time to a point where they both agree and then the libretro cores emulates the missing frames all at once to get back to the appropriate spot. This gives the illusion of completely lagless inputs, which is invaluable for twitchy, fine controls. |
| − | If you try to connect to a server and it immediately says client disconnected, open your log and make sure your ROMs match exactly (it will complain about a hash mismatch otherwise). If it gives you a weird time-out error, just close the window and try to connect again | + | If you try to connect to a server and it immediately says client disconnected, open your log and make sure your ROMs match exactly (it will complain about a hash mismatch otherwise). If it gives you a weird time-out error, just close the window and try to connect again and it should work itself out (sometimes excessive spikes in network latency can cause the states to diverge catastrophically, resulting in this error). |
==Alternative Launchers and Frontends== | ==Alternative Launchers and Frontends== | ||
