Editing Using 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 1: | Line 1: | ||
==Basic Usage== | ==Basic Usage== | ||
{{Main|Dummies Guide: RetroArch}} | {{Main|Dummies Guide: RetroArch}} | ||
− | After downloading [[RetroArch]],[[File:Rgui.png|thumb| | + | After downloading [[RetroArch]],[[File:Rgui.png|thumb|205px|RGUI, RetroArch's original interface. XMB and GLUI follow the same basic structure.]] start up retroarch.exe. |
− | |||
− | |||
− | |||
− | start up retroarch.exe. | ||
To launch a game, select the libretro core you'd like to use under '''Load Core''', and select a ROM under '''Load Content>Select File'''. Alternatively, you can use '''Load Content>Select File And Detect Core''' to be presented with a list of cores detected based on the file extension of the content. | To launch a game, select the libretro core you'd like to use under '''Load Core''', and select a ROM under '''Load Content>Select File'''. Alternatively, you can use '''Load Content>Select File And Detect Core''' to be presented with a list of cores detected based on the file extension of the content. | ||
Line 16: | Line 12: | ||
sudo apt-get update | sudo apt-get update | ||
− | sudo apt-get install retroarch | + | sudo apt-get install retroarch retroarch-assets retroarch-joypad-autoconfig |
sudo apt-get install <corename> | sudo apt-get install <corename> | ||
Line 56: | Line 52: | ||
Set USE flags that you want, it is not required to enable every single one (you only need at least one audio and video output device; defaults are suitable enough). It is recommended to add udev for joystick support and netplay for netplay support. | Set USE flags that you want, it is not required to enable every single one (you only need at least one audio and video output device; defaults are suitable enough). It is recommended to add udev for joystick support and netplay for netplay support. | ||
+ | |||
Build and install RetroArch from the git repository | Build and install RetroArch from the git repository | ||
Line 74: | Line 71: | ||
The cores will be installed under /usr/lib/libretro/ | The cores will be installed under /usr/lib/libretro/ | ||
+ | |||
===Other Distros=== | ===Other Distros=== | ||
Line 98: | Line 96: | ||
If you are going to play in a system that needs a BIOS (e.g. PS1), place the [[Emulator_Files#Multi-System|BIOS files]] in RetroArch's 'system' directory. | If you are going to play in a system that needs a BIOS (e.g. PS1), place the [[Emulator_Files#Multi-System|BIOS files]] in RetroArch's 'system' directory. | ||
+ | |||
+ | Mednafen is very picky about which BIOS to use. The ones that you might need are: | ||
+ | |||
+ | <ul> | ||
+ | <li class="de2"><code>scph5500.bin</code></li> | ||
+ | <li class="de2"><code>scph5501.bin</code></li> | ||
+ | <li class="de2"><code>scph5502.bin</code></li> | ||
+ | </ul> | ||
===Disc images=== | ===Disc images=== | ||
− | + | [[Mednafen]] requires you to load games through CUE sheets. Ensure that the CUE sheet is properly set up in order for the game to run. See the [[Cue sheet (.cue)]] for more. | |
===Mupen64Plus=== | ===Mupen64Plus=== | ||
Line 113: | Line 119: | ||
*Angrylion is ultra accurate, but is too slow for most people to use. Requires the CXD4 RSP to work. Resolution must be set to 640x480 or higher. | *Angrylion is ultra accurate, but is too slow for most people to use. Requires the CXD4 RSP to work. Resolution must be set to 640x480 or higher. | ||
− | |||
− | |||
*The HLE RSP plugin is very fast and will work fine for most games. | *The HLE RSP plugin is very fast and will work fine for most games. | ||
Line 154: | Line 158: | ||
===Transfer PS1 Memory Card Files=== | ===Transfer PS1 Memory Card Files=== | ||
− | + | Mednafen creates memory card files for each individual game, in contrast to PCSX-R/ePSXe where all game saves are stored into 2 memory card files. To transfer memory card files from PCSX-R/ePSXe to RetroArch: | |
*Start game in RetroArch. | *Start game in RetroArch. | ||
Line 193: | Line 197: | ||
===SoftFilters=== | ===SoftFilters=== | ||
− | Classic emulator filters like SuperEagle or Blargg's NTSC have been available as | + | Classic emulator filters like SuperEagle or Blargg's NTSC have been available as bSNES filter plugins in the past, which is no longer supported in bSNES/higan but was still available in RetroArch. However, this filter format was recently replaced with the SoftFilter spec, which has been upgraded to support more platforms, multi-threading and SIMD usage. The filters are dynamic libraries which are loaded in the menu under Settings>Video>Video Filter, which will apply the filter before any shaders are applied. |
The filters are found [https://github.com/libretro/RetroArch/tree/master/gfx/video_filters here], which can be built for your platform with the makefile. These files should be included in nightly builds from the buildbot. | The filters are found [https://github.com/libretro/RetroArch/tree/master/gfx/video_filters here], which can be built for your platform with the makefile. These files should be included in nightly builds from the buildbot. | ||
− | Note that these filters are WIP and may not work with all cores as they need to have codepaths for the pixel format the core uses (either 32bpp XRGB8888 or 16bpp RGB565). Blargg's NTSC is currently limited to 16bpp cores for example ( | + | Note that these filters are WIP and may not work with all cores as they need to have codepaths for the pixel format the core uses (either 32bpp XRGB8888 or 16bpp RGB565). Blargg's NTSC is currently limited to 16bpp cores for example (bSNES is 32bpp so it won't work, but SNES9x is 16bpp so it works there). Cores that use Libretro GL for 3D like Mupen64plus can not use these filters. |
===Outputting log to a file=== | ===Outputting log to a file=== | ||
Line 240: | Line 244: | ||
===Menu runs too fast=== | ===Menu runs too fast=== | ||
− | If Vsync is disabled for any reason, the menu may run unthrottled and scroll too fast to be usable. To fix this, enable | + | If Vsync is disabled for any reason, the menu may run unthrottled and scroll too fast to be usable. To fix this, enable Limit Maximum Run Speed, and set Maximum Run Speed to 1.0x in Settings under Frame Throttle. In the config file, these options are called <code>fastforward_ratio_throttle_enable</code> and <code>fastforward_ratio</code>. However, this will make fast forward not work, you will need to increase the Maximum Run Speed higher than 1.0x for that to work. |
− | This tends to happen when you first start up RetroArch and not after loading a game. This is because without a core loaded, the menu is only throttled by Vsync when | + | This tends to happen when you first start up RetroArch and not after loading a game. This is because without a core loaded, the menu is only throttled by Vsync when Limit Maximum Run Speed is disabled, while cores are able to throttle on audio as well. Fastforward disables both Vsync and audio sync, which allows the core to run unthrottled unless it is specifically limited by the Maximum Run Speed setting. |
− | In newer RetroArch versions, you can just enable | + | In newer RetroArch versions, you can just enable Throttle Menu Framerate in setting under Frame Throttle to specifically limit the menu to 60fps without impacting fastforward speed. |
===Command prompt running and closing itself upon running retroarch.exe=== | ===Command prompt running and closing itself upon running retroarch.exe=== | ||
Line 254: | Line 258: | ||
===Performance issues while using the GL driver=== | ===Performance issues while using the GL driver=== | ||
− | + | Nvidia users may find that even while idle, RetroArch CPU usage is upwards of 12% or above while using the GL video driver. If this is the case, go into the Nvidia Control Panel, and under Manage 3D Settings, check to see if the Threaded Optimizations option is set to Auto or On. If so, add retroarch.exe to the list of programs, and then toggle it to Off. This should lower CPU usage drastically. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==External links== | ==External links== |