Changes

===Debian Ubuntu based===

*This core has the option to choose between four graphics plugins and two RSP plugins:

**Glide64 is the most recommended general use graphics plugin, as it is very compatible and reasonably accurate while still being decently fast.

**Rice is much faster than Glide64, but it also suffers from a lot more issues. Only use if your device is too slow to handle Glide64.

**gln64 has even more problems than Rice, while not being much faster. Not recommended. Will likely be replaced with GLideN64 in the near future.

**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 paraLLEl is very fast a Vulkan renderer based on Angrylion. It is much faster than Angrylion, but is still incomplete and will work fine for most gameshas more issues. Turning Synchronous RDP off results in a speed boost, but also breaks many things.

**The CXD4 HLE RSP plugin is more accurate, very fast and is needed will work fine for a few most games to work correctly.

**A good general purpose setup is Glide64 with the The CXD4 RSP. If it's is more accurate, and is needed for a tad slow for your setup, switch few games to the HLE RSPwork correctly.

*There A good general purpose setup is currently a bug in Glide64 that makes it so texture filtering is applied to everything, even when with the Texture Filtering setting is set to AutomaticCXD4 RSP. To make If it display textures correctly's a tad slow for your setup, go switch to Core Options, toggle the setting to something other than Automatic, then set it back to Automatic. Glide64 will display textures correctly now, using the 3-point Bilinear methodHLE RSP.

*If you get strange There is currently a bug in Glide64 that makes it so texture issues while using Glide64filtering is applied to everything, such as even when the Texture Filtering setting is set to Automatic. To make it display textures partially disappearing or popping over polygonscorrectly, mess around with the Polygon Offset Factor setting in go to Core Options until , toggle the issue goes away. Keep in mind some games may require a more aggressive setting to something other than othersAutomatic, so experiment until you get a good balance that works for most gamesthen set it back to Automatic. The optimal setting tends to be GPUGlide64 will display textures correctly now, using the 3-specificpoint Bilinear method.

*If you get strange texture issues while using Glide64, such as textures partially disappearing or popping over polygons, mess around with the Polygon Offset Factor setting in Core Options until the issue goes away. Keep in mind some games may require a more aggressive setting than others, so experiment until you get a good balance that works for most games. The optimal setting tends to be GPU-specific. A few games, such as Star Fox 64, suffer from looking too dark due to a lack of gamma correction, which was done on real hardware. Short of implementing this in a plugin, a decent workaround is to use the image-adjustment.cg shader, and set the Target Gamma setting to 1.0. This will make such games look as they ought to.

Classic emulator filters like SuperEagle or Blargg's NTSC have been available as bSNES bsnes filter plugins in the past, which is no longer supported in bSNESbsnes/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.

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 bsnes is 32bpp so it won't work, but SNES9x Snes9x is 16bpp so it works there). Cores that use Libretro GL for 3D like Mupen64plus Mupen64Plus can not use these filters.

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.0xin ''Settings''→''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 ''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 ''Limit Maximum Run Speed '' setting. In newer RetroArch versions, you can just enable ''Throttle Menu Framerate'' under ''Settings''→''Frame Throttle'' to specifically limit the menu to 60fps without impacting fastforward speed.