138
edits
Changes
Jump to navigation
Jump to search
Added an Overview section explaining the "profiles" under Recommended Setups
==Recommended N64 Setups==
===Overview===
While in general only a small handful of plugins are necessary to play the vast majority of N64 games these days, there are nevertheless a variety of use cases which may necessitate using some plugins in specific combinations over others. The following section will be divided primarily by plugin specs, then further subdivided by the following use case "profiles":
*General Use - A profile that strikes a good balance of speed, accuracy and compatibility. Most games will be playable on average hardware and should run with few to no issues.
*Performance - Focuses primarily on speed for lower-end devices that cannot handle the General Use profile. Many games will be playable, but expect lower overall compatibility, glitches and missing effects.
*Accuracy - Attains the maximum compatibility and accuracy made possible by the emulator. Almost all games will be playable and look as intended, but requires much higher system specifications.
As a rule of thumb, start with the General Use profile. If it's too slow, move down to the Performance profile. Conversely, if there's a problem with the game (or you just want to be as close to real hardware as possible), move up to the Accuracy profile. It should be said there may be configurations within the emulator or plugin settings that may help with speed or compatibility, but it is generally not recommended to mess with them unless you know what you're doing, as both emulators and plugins are usually already optimized on a per-game basis, so moving settings around could result in breaking things. Should you wish to try to eke out more performance out of a given profile, it may be wise to consult with the emulator/plugin developers or communities centered around N64 emulation first.
===Project64 and Others===
**Static Interpreter RSP or Zilmar's RSP
**Either of the RSP plugins should be fine for most games. The Static Interpreter RSP is slightly more accurate, whereas zilmar's is much faster. Should you wish to use GLideN64 in LLE mode (or any LLE video plugin for that matter), if using zilmar's RSP, simply uncheck "Graphics HLE" in the Plugin configuration screen. If using the Static Interpreter RSP, you'll have to run the spconfig.exe that comes with that plugin, and tell it to NOT "simulate RSP graphics from external plugin" (in other words, type "0"). ParaLLEl-RSP only works in LLE, so GLideN64's HLE mode will be unavailable with that plugin.
*'''Best Performance'''
**Project64 Video or Glide64 Final
**Azimer's HLE Audio
**RSP: RSP-HLE (for GLideN64) or ParaLLEl-RSP (for ParaLLEl-RDP)
**Either one of these combinations will enable you to play the vast majority of N64 games while having reasonable system requirements. GLideN64 is faster and has more enhancement options, but ParaLLEl-RDP is much more accurate to the real console. You can also use the CXD4 RSP with GLideN64 if you want, but be sure to set it to pass display lists to the graphics plugin in mupen64plus.cfg, else GLideN64 will switch to its LLE mode, which is not generally recommended to use.
*'''Best Performance'''
**Video: Glide64mk2
**RSP: RSP-HLE
**RSP: HLE
**While GLideN64 also works with the ParaLLEl and CXD4 RSP plugins, using them will cause GLideN64 to switch to its LLE mode, which is currently glitchier and slower than the HLE mode, for few compatibility or accuracy benefits, if any. As such, it is recommended to stick with the HLE RSP for GLideN64.
*'''Best Performance'''
**Core: ParaLLEl-N64
**Video: Glide64
